Ivo wrote: >This imply we know all languages that will be included in the near future or include ALL languages that are spoken on this planet.
I _think_ the suggestion was that language and locale data be included, not the User Interface. [IOW, one could select a locale of Zulu-ZA or Zulu-SW, rather than have to select Afrikaans, or English(ZA) as the locale. Or for languages one could select Xhosa, rather than the current "user1" option. (And I doubt that I am the only person who thinks it is bizarre to have the user interface in a language that I can't select as option for writing in.)] Including all 8 717 languages that ethnologue knows about does require a couple of things to happen. i) Walk thru the existing code base, and replace the non-unicode string library calls with unicode string library calls; ii) Walk thru the code base, and change all string calls to _one_ format, instead of the current ten or so formats that are used; iii) Hve OOo recognize all Unicode characters, not just those in Plane 0; [These require nothing more than grunt work, doable by anybody that can fluently read code, and knows how to write good code.] Including all those languages can make for some interesting marketing. > Pavel created a script that filters all words that occur 4 times or more > often in the translation. Does that meet your requirements ? That would be step one. Step two is a list of all words used in the User Interface, along with the definition, and how it is used within OOo. > Is there realy a need for such glossary if you use a po based translation > memory system? Yes. xan jonathon -- Does your Office Suite conform to ISO Standards? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
