Re: [l10n-dev] Thoughts on Localization
On Sun, 23 Dec 2007 05:59:05 +0200, Jean-Christophe Helary [EMAIL PROTECTED] wrote: On 23 déc. 07, at 01:53, Pavel Janík wrote: Charles: what should be used instead of SDF? Do you have at least an idea? Will you help to implement it? ... The answer is easy: XLIFF files directly generated from the XML for the help files and from the rest for the UI. That is equivalent to a source-po process, and that is the way to go. Here I should point out that preciously little tools work currently with the 1.1 XLIFF (even Sun's OLT didn't process 1.1 in Spring 2007). Anyway, such change, while disruptive to many, would also be at least useless, if with it won't come extended meta-information coverage (string context etc.) So, possibly the real answer is extend coverage of meta-information, extending the SDF format appropriately. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Thoughts on Localization
(Boris or anybody else, I Cc to OLT's dev list because that is relevant here. How hard do you think it would be to have OLT's filters work with OOo's l10n format: .sdf ?) On 23 déc. 07, at 18:00, Yury Tarasievich wrote: On Sun, 23 Dec 2007 05:59:05 +0200, Jean-Christophe Helary [EMAIL PROTECTED] wrote: XLIFF files directly generated from the XML for the help files and from the rest for the UI. Here I should point out that preciously little tools work currently with the 1.1 XLIFF (even Sun's OLT didn't process 1.1 in Spring 2007). Anyway, such change, while disruptive to many, would also be at least useless, if with it won't come extended meta-information coverage (string context etc.) So, possibly the real answer is extend coverage of meta- information, extending the SDF format appropriately. Yuri, I don't want to sound rude but you have it all wrong. I don't care about the SDF format. What I need and what translators need is a tool chain that does not _break_ the data as it does now with oo2po. What translators need is tools that support the format they use with the least transformation possible. Open Language Tools' problem is not that is does not support XLIFF 1.1, its problem is that its filter does not support SDF... Besides, if OLT does not support XLIFF 1.1 why not feed it with XLIFF 1.0 ? Have you thought about that ? All the source files are in plain XML, have you thought about the efficiency loss of converting an XML file to a non XML format in terms of checks ? Have you considered the efficiency gains of keeping a strictly XML based tool chain for the localization ? Pavel says that SDF is so easy to transform, then, what about OOo l10n developers took some time to improve OLT's filters so that we can use them directly with SDF ? _That_ would considerably improve the translation process. To a point that OLT could actually be used with the TMX by any community that wants to work with a professional grade tool... Any taker ? -- Jean-Christophe Helary http://mac4translators.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Thoughts on Localization
On Sun, 23 Dec 2007 11:55:31 +0200, Jean-Christophe Helary [EMAIL PROTECTED] wrote: Yuri, I don't want to sound rude but you have it all wrong. I don't care about the SDF format. Well, *I* don't care about modifications to the current (oo2po) process. However, I do care about lack of meta-information which renders many actual translation issues hard to resolve. Your scheme does not address that matter and actually would postpone its resolvement. As I see it, it's not quite possible to choose XLIFF 1.0 or 1.1, because some tools do 1.1 only (xliff-po toolkit) and free visual environments don't do 1.1 (Sun OLT - yet? Python XLIFF editor). Cheers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Native Language Confederation page (OT ?)
Jean-Christophe, (please reply to [EMAIL PROTECTED]) There is actually a reason for this: the languages (their full name) correspond to their ISO code and hence the names of the native-langage projects. Perhaps we should add a second column with the name of the language by itself, although we may want to wait for a web site upgrade... Best, Charles. Jean-Christophe Helary a écrit : I was just checking: http://projects.openoffice.org/native-lang.html to look for information on the Japanese pages and I found it weird that the language names are not displayed in their own language... Like, instead of Japanese (ja), have 日本語 (ja) etc. That would be a lot easier for users who are actually looking for information in their language... Where can this be fixed ? Is there an automatic way to fix that ? -- Jean-Christophe Helary http://mac4translators.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Eike: one maybe stupid question
Eike Rathke kirjutas: Hi Ain, On Friday, 2007-12-21 07:39:29 +0200, Ain Vagula wrote: In Windows, there is a settings field in Windows Contol Panel - Regional and language options - Advanced - Language for non-Unicode programs. [...] When this language is set to English, and all OO.o language settings are still not set after clean installation, OO.o seems to use this setting to set language for newly created empty documents (only documents, not UI), Are you referring to Default languages for documents under Tools.Options.LanguageSettings.Languages, which is used for character attribution and spell-checking in Writer documents? Yes ie. in localized versions working in Windows, where locale is set to native language but this setting by accident unchanged, language for new documents will be set to English (US). Is this correct behaviour? I honestly have no idea.. AFAIK to setup locales for the configuration LocaleBackend is called, which in turn calls the Windows API for different locales: SystemLocale : GetSystemDefaultLCID() Locale : GetUserDefaultLCID() UILocale : GetUserDefaultUILanguage() Digging around in desktop/source/app/langselect.cxx revealed that first it is tried to set some ominous Win16SysLocale obtained as SystemLocale, probably (just a guess) to support Win95 and the like. Next it is tried to obtain Locale and set that as the default document language, overriding Win16SysLocale, if any. It looks like this again may get overridden with a locale based on the installed UI language(s), with a fall-back to en-US, at least in certain cases. However, I may have misinterpreted things, I just took a short look. Much of the complicated handling seems to be related to http://qa.openoffice.org/issues/show_bug.cgi?id=32939 Thanks, this issue gives good overview. Just the name of windows setting was very confusing (as often in Windows) and I didnt understand what has this to do with document language ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Merry Christmas and Happy New Year from Chinese Community!
Hi, all I forward an email from zh.OOo to wish you： Merry Christmas and Happy New Year！ If you can read Chinese, it's very great; If you can't, never mind, you'll get a great chance to learn Chinese, because the next year is Chinese Olympic year! Welcome to China! Regards! -- ChengLin 2007-12-24 === Original Message 2007-12-24 14:28:01 === From: Zhang Xiaofei[EMAIL PROTECTED] Date: 2007-12-24 14:28:01 To: [EMAIL PROTECTED][EMAIL PROTECTED] CC: Subject: Re: [zh:dev]圣诞快乐！元旦快乐！ Hi all, 最近收到一条短信，觉得送给蛋蛋蛋中文社区的朋友们非常合适 :-P 今年送礼真难办， 挑来挑去三个蛋， 首当其冲是圣蛋， 祝你康健又平安， 接着要送是元蛋， 祝你薪水翻一番， 最后送个小鸡蛋， 祝你聪明又能干！ 祝新的一年蛋蛋蛋中文社区更加繁荣！ Best Regards, Felix.
