Re: Gnome 2.0 Localization for Solaris

[Wang Jian <lark linux net cn>]

Hello Damien,

I am zh_CN team coordinator. I think you can go translating
documents because we haven't touched it yet.

But for GUI interface, we have finished most of them, the QA is the
most important issue. Please don't silently change anything. Announce
your intention to work on our team's list.

Let your zh_CN team visit http://i18n.linux.net.cn to get useful
information.

Thursday, March 21, 2002, 2:32:56 AM, you wrote:


DD> Hi All,
DD> Myself and a few others are working out the details of 
DD> the localization plan for Gnome 2.0 on Solaris. Currently
DD> the plan is to do translation for all software to be included 
DD> in the Gnome 2.0 Solaris release which has not already been 
DD> completed by other members of the community. We will also 
DD> be doing translation for the documentation and help content 
DD> being provided by Sun. So far, the language list is as follows :

DD> de          German
DD> es          Spanish
DD> it          Italian
DD> fr          French
DD> pt_BR       Portugese Brazilian
DD> ja          Japanese
DD> zh_CN       Simplified Chinese
DD> zh_TW       Traditional Chinese
DD> ko          Korean
DD> pl          Polish
DD> sv          Swedish



DD> We are investigating the possibility of doing some additional 
DD> languages but these haven't been confirmed yet. All translations will 
DD> eventually go back into the community CVS tree. 

DD> We have a number  of issues which I'd be _very_ grateful to get input 
DD> & feedback on. They are :

DD> - Given the large amount of translation involved, how do you think
DD>   we ought to break this up? If we take everything at once and the
DD>   rest of the community continues doing translations are we
DD>   going to come unstuck when we attempt to merge our translations back?
DD>   I know we ought not but want to avoid as much as possible 
DD>   duplication of work between our translation teams and other members
DD>   of the community.
  
DD>   We are thinking about taking it in chunks e.g 6/7 CVS modules at
DD>   a time thereby reducing the incidence of this happening by having
DD>   a quicker translation turnaround. What do you think of this approach 
DD>   as opposed to just taking the lot at once? Would community CVS tagging 
DD>   before our translation be useful?
  
DD> - Are all modules now configured correctly to use xml-i18n-tools?
DD>   Can we rely on "xml-i18n-update --pot" as capturing all localizable 
DD>   content within software, .desktop AND .xml files in the community CVS 
DD>   tree or have some CVS modules yet to be configured to use this mechanism?
DD>   If so, which modules are not yet configured? 
  
  
DD> - I have seen messages like the following when I attempt to run 
DD>   "xml-i18n-update -pot" for certain modules :
  
DD>   basil% /usr/local/bin/xml-i18n-update --pot
DD>   Option type requires an argument
DD>   Try `xml-i18n-extract --help' for more information.
  
DD>   This appears to mean that I need to tell xml-i18n-extract which
DD>   xml tags flag the translatable content. How do I make xml-i18n-extract 
DD>   'know' which tags contain translatable content before I run 
DD>   xml-i18n-update  i.e how do I avoid this error if I am automatically
DD>   iterating through all modules generating the .pot files just using 
DD>   'xml-i18n-update --pot' to generate the English .pot files?
  
DD> - So far we are aware of the need to add translations to .po, .desktop and 
DD>  .xml files. Is there translatable content in other files? Someone mentioned
DD>   .server files as containing translatable content. What are they? 
DD>   Are there others?
  
DD> - Some .po files are not yet UTF-8 encoded. If we were to develop 
DD>   a mechanism for checking and converting message files to UTF-8 are we 
DD>   free to do so or would this have 'unforeseen' detrimental side-effects? 
  
DD> We'd be grateful for your feedback on these issues or any tips/caveats 
DD> or warnings about potential translation pitfalls which will help ensure that 
DD> our translation work goes smoothly.

DD> Big apologies for the 'epic' length of this email! 
DD> Looking forward to your replies.

DD> Damien



DD> ¤ºÿ°`°º¤ø,¸¸,ø¤º°`°º¤ø¤ºÿ°`°º¤ø,¸¸,ø¤º°`°º¤øø¤º°`°ºÿ¤
DD> Damien Donlon
DD> damien.donlon@sun.com
DD> 00 353 1 8199225
DD> x19225
DD> _______________________________________________
DD> gnome-i18n mailing list
DD> gnome-i18n@gnome.org
DD> http://mail.gnome.org/mailman/listinfo/gnome-i18n



-- 
  lark