[ESW Wiki] Update of "its0504ReqLinkedText" by MasakiItagaki

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 MasakiItagaki:
http://esw.w3.org/topic/its0504ReqLinkedText


------------------------------------------------------------------------------
  
  
  '''[[YS-''' I could also see some paragraph about the need to e able to modify the reference text as it is retrieved. For example, the data from a software UI "&File..." cannot be use as-it in the documentation, one need to remove the '&' (and maybe '...' too). But it also affect capitalization, etc. especially since different languages may have different rules for this. '']]''
+ 
+ ---- /!\ '''Edit conflict - other version:''' ----
  '''[[MI-''' This may require some noramlization in rendering external data but it's only if UI items are linked. So definitely some normalization machanism must be provided as an option. Maybe I should put this in Quick Guideline Thoughts. '']]''
  
  '''[[YS-''' Another aspect, maybe more important, is to have the reference mechanism language-aware. You don't want to have to change each reference 'path' to the files in each localized versions of the document that uses the references. In other words, the reference mechanism should have provision for possibly working in conjuction with the current language settings.''']]'''
  '''[[YS-''' This is also a rendering issue, correct? Datasource should be language-aware, but it can always refer to a language/locale in the superordinate element and fetch a correct langauage text. This should be mentioned in the Challenge/Issue section.''']]'''
  
+ ---- /!\ '''Edit conflict - your version:''' ----
+ '''[[MI-''' This may require some noramlization in rendering external data but it's only if UI items are linked. So definitely some normalization machanism must be provided as an option. Maybe I should put this in Quick Guideline Thoughts. '']]''
+ 
+ '''[[YS-''' Another aspect, maybe more important, is to have the reference mechanism language-aware. You don't want to have to change each reference 'path' to the files in each localized versions of the document that uses the references. In other words, the reference mechanism should have provision for possibly working in conjuction with the current language settings.''']]'''
+ '''[[MI-''' This is also a rendering issue, correct? Datasource should be language-aware, but it can always refer to a language/locale in the superordinate element and fetch a correct langauage text. This should be mentioned in the Challenge/Issue section.''']]'''
+ 
+ ---- /!\ '''End of edit conflict''' ----
+

Received on Thursday, 19 May 2005 06:43:26 UTC