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

[ESW Wiki] Update of "its0509SpecScoping" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Fri, 07 Oct 2005 02:10:08 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20051007021008.3062.36492@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 YvesSavourel:
http://esw.w3.org/topic/its0509SpecScoping


------------------------------------------------------------------------------
  
  '''[[FS-START['''
  
- I think a high priority should be that the ITS tag set should be as small as possible. Yves proposal allows to reuse its:rule for various kinds of rules, depending on the attributes. I just would like to have the same tags for the in situ and the dislocated case. A general solution for this looks like this:
+ I think a high priority should be that the ITS tag set should be as small as possible. Yves proposal '''[[YS-'''That is Christian's proposal ''']]''' allows to reuse its:rule for various kinds of rules, depending on the attributes. I just would like to have the same tags for the in situ and the dislocated case. A general solution for this looks like this:
  
  {{{
  <myns:myElement its:translateNo="//para">..</myns:myElement>
@@ -156, +156 @@

  }}}
  
  The information "This is some locinfo" would apply to all kinds of locinfo.
+ 
+ '''[[YS- But myns:para has its own purpose. How could we put loc info in it? Maybe I don't understand...]]'''
  
  So the general way to express rules and other kinds of information:
  
@@ -179, +181 @@

  The good message here is again that the myns:myElement element has no need to be deleted or converted into its:ruby. It is interpreted as its:ruby via the attribute its:ruby.
  ''']END-FS]]'''
  
+ '''[[YS-''' but it seems to generalized. ruby and translatibility are very different things. Using XPath to point to elements that are ruby seems rather strange (not to mention very complicated to process): why in the world would someone want to put that info anywhere else that in the actual element? I could see {{{its:ruby="yes"}}}, but using XPath would make things a bit confusing (you could point to an attribute for example, but an attribute could not have rb/rt info), also what about cascading effects: they would be different for ruby abd translateYes?''']]'''
+ 
Received on Friday, 7 October 2005 11:33:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:06 UTC