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

[ESW Wiki] Update of "its0505WordCount" by MasakiItagaki

From: <w3t-archive+esw-wiki@w3.org>
Date: Tue, 31 May 2005 08:31:18 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050531083118.20054.4068@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 MasakiItagaki:
http://esw.w3.org/topic/its0505WordCount


------------------------------------------------------------------------------
  }}}
  ''' this is a tough one to crack : basically in our XLIFF impl, we just had to admit that there may be translatable text in the programlisting, but we don't know how to wordcount it  end TF]]'''
  
+ [[MI The only way to manage the case above should be as as follows (you don't need the translate attribute, though...) and instruct the parser to extract only text from the programlisting element just as JDOM can do: 
+ 
+ {{{
+ <para>This is a section of java code :
+ <programlisting>
+   // this string is never used
+   String sqlConnect = "connect / as sysdba";
+   String sqlSelect = "select name from mytable where name=\"Tim\"";
+   System.out.println("<message translate="yes">But of course, you should translate this string !</message>");
+ </programlisting>
+ }}}
+ NO?
+ end of MI]]
+ 
  I realize the importance of a common way to calculate the counts, but something like GMX seems, maybe, out of scope, has it's not something to do with making documents, in general, easier to localize.
  
  Well, I guess I could see it as a guideline just in case some schema designers would want to include a word-count storage mechanism in their format. ''']]'''
Received on Tuesday, 31 May 2005 09:12:40 GMT

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