W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2005

[ESW Wiki] Update of "its0503ReqEntities" by AndrzejZydron

From: <w3t-archive+esw-wiki@w3.org>
Date: Wed, 15 Jun 2005 08:38:39 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050615083839.14361.58110@localhost.localdomain>
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.

The following page has been changed by AndrzejZydron:
http://esw.w3.org/topic/its0503ReqEntities


------------------------------------------------------------------------------
   2. Entity definition does not fit with the surrounding context language-wise. Example: The context in 'Das Produkt &productName; ist mit vielen Erweiterungen ausgestattet worden' is German whereas the definition may be in English
   3. Entity definition does not fit with the surrounding context grammar-wise. Example: The syntax in 'The &productName; features have been enhanced in many ways' will be incorrect. '''[[YS-''' Maybe I'm wrong but I think it seems OK since 'the latest version' is the subject going with 'features'. Am I right? and if so: Better example anyone? ''']]''' '''[[AZ-''' You are correct Yves, I have adjusted the text accordingly. ''']]'''
  
- In addition, even if the entity itself is translated there may be significant grammatical problems for inflected languages for nouns. The translation will inevitably follow the case of the original. For example, if the original is genitive, the translation is genitive as well (of course this requires that the original language and the translation language have a concept for "genitive").
+ In addition, even if the entity itself is translated there may be significant grammatical problems for inflected languages for nouns. The translation will inevitably follow the case of the original. For example, if the original is genetive, the translation is genitive as well (of course this requires that the original language and the translation language have a concept for "genitive").
  
  Since entities affect the content of the document, and XSLT processors and other kinds of XML processors act on the content, various processing-related issues may arise. An XSLT stylesheet for example, which is sensitive to content contributed by an entity, may fail to work as expected (e.g. may not be able to generate the 'alt' for HTML pages).
  
Received on Wednesday, 15 June 2005 09:53:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:45 GMT