Re: [l10n-dev] Re: problem strings in OmegaT
Aijin, Thanks for your comments. Yes, I agree that it'd be the best way to switch the style from msgid_comment to msgctxt. I also confirmed that msgctxt works ok in OmegaT. I did not have the time to check. What do you mean by msgctxt works ok in OmegaT ? Is it displayed separately as a comment or is it simply ignored ? Jean-Christophe Helary http://mac4translators.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: problem strings in OmegaT
Hi JC, In OmegeT 1.7.3, msgctxt seems to be simply ignored. There is no display for msgctxt. What I meant was that OmegaT works ok with 'msgid' and 'msgstr' fields regardless of msgctxt field. Regards, Aijin Jean-Christophe Helary 쓴 글: Aijin, Thanks for your comments. Yes, I agree that it'd be the best way to switch the style from msgid_comment to msgctxt. I also confirmed that msgctxt works ok in OmegaT. I did not have the time to check. What do you mean by msgctxt works ok in OmegaT ? Is it displayed separately as a comment or is it simply ignored ? 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] Re: problem strings in OmegaT
Aijin, Ok, very good. It would have been a very good surprise to see msgctxt appear somewhere though ;) Also, OmegaT 1.8 with a spellchecker (hunspell, works with OOo dictionaries) has been released in test version yesterday: http://mac4translators.blogspot.com/2008/03/omegat-173-18-19.html JC On 3 mars 08, at 17:56, Aijin Kim wrote: Hi JC, In OmegeT 1.7.3, msgctxt seems to be simply ignored. There is no display for msgctxt. What I meant was that OmegaT works ok with 'msgid' and 'msgstr' fields regardless of msgctxt field. Regards, Aijin Jean-Christophe Helary 쓴 글: Aijin, Thanks for your comments. Yes, I agree that it'd be the best way to switch the style from msgid_comment to msgctxt. I also confirmed that msgctxt works ok in OmegaT. I did not have the time to check. What do you mean by msgctxt works ok in OmegaT ? Is it displayed separately as a comment or is it simply ignored ? Jean-Christophe Helary K.K. DOUBLET - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Purpose of ... name= ...
Hello I am not sure if we have to translate the content of the name= attribute such as in the example below. Samples in the French and Italian language seems to indicate a translation, but the Spanish has both english and spanish content. Can someone shed some light on that matter? Example: If you switch off the \\link href=\\\text/shared/02/01170500.xhp\\\ name=\\\Design Mode\Design Mode\\/link\\, you can see that $[officename] adds a labeled input field for every inserted database field. Thank you Olivier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Purpose of ... name= ...
Olivier Hallot pravi: Hello I am not sure if we have to translate the content of the name= attribute such as in the example below. Samples in the French and Italian language seems to indicate a translation, but the Spanish has both english and spanish content. Can someone shed some light on that matter? Example: If you switch off the \\link href=\\\text/shared/02/01170500.xhp\\\ name=\\\Design Mode\Design Mode\\/link\\, you can see that $[officename] adds a labeled input field for every inserted database field. Yes, you have to translate it. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] New languages
I'm wonder that making localization in openoffice for burmese. Burmese is being Lack of support by popular text rendering in Uniscribe, Pango, Qt and ICU. What should I do without the basic componets of burmese localization. We just need to collect our locales and wish list among burmese communities. Javier and we are keep trying to develop Myanmar Rendering on FOSS. We can't touch on Windows Platform. Burmese are based own script shape and need complex text layout engine. There are still migration stage in Unicode Standards. The tweaks burmese opentype fonts for windows are released by mutual agreement of burmese font developers and UTN-11. I hope to translate some glossary first. It might be useful for this project right now. No more possible activities before having stable standards and rendering engine support for burmese. Best Ngwe Tun. On Mon, Mar 3, 2008 at 3:44 PM, Charles-H. Schulz [EMAIL PROTECTED] wrote: Hello Javier, Le 1 mars 08 à 07:43, Javier SOLA a écrit : I am starting a new localization effort for some minority languages in Cambodia. The goal is not to translate the user interface, but to create locales that will allow the use of local forms and spell- checkers. Three of this languages: Brao (brb, also known as Lave), Tampuan (tpu) and Bunong (bun) use the Khmer script, while the forth one - Cham - has its own script. The languages are listed in 639-3, except for Cham (cmc) that is listed in 639-2. These are excellent news. For the localization in Burmese, Wunna Ko Ko is working on it (see http://my.openoffice.org); perhaps you two could join your efforts? Best, Charles. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- In Burmese; Ngwe mean 1) Silver 2) Money 3) Second Awards; Tun mean 1) Light 2) be prominent.
Re: [l10n-dev] Purpose of ... name= ...
AFAIK this attribute will be used by screenreaders and when you dont have one in your language, you dont need to translate it. ain On Mon, Mar 3, 2008 at 1:06 PM, Robert Ludvik [EMAIL PROTECTED] wrote: Olivier Hallot pravi: Hello I am not sure if we have to translate the content of the name= attribute such as in the example below. Samples in the French and Italian language seems to indicate a translation, but the Spanish has both english and spanish content. Can someone shed some light on that matter? Example: If you switch off the \\link href=\\\text/shared/02/01170500.xhp\\\ name=\\\Design Mode\Design Mode\\/link\\, you can see that $[officename] adds a labeled input field for every inserted database field. Yes, you have to translate it. Regards - 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] New languages
Ngwe Tun, Javier, Let me introduce you to Wunna Ko Ko, lead of the Burmese NL team and localization. I think you should work in a common effort on the Burmese localization. Cheers, Charles. Le 3 mars 08 à 11:42, Ngwe Tun a écrit : I'm wonder that making localization in openoffice for burmese. Burmese is being Lack of support by popular text rendering in Uniscribe, Pango, Qt and ICU. What should I do without the basic componets of burmese localization. We just need to collect our locales and wish list among burmese communities. Javier and we are keep trying to develop Myanmar Rendering on FOSS. We can't touch on Windows Platform. Burmese are based own script shape and need complex text layout engine. There are still migration stage in Unicode Standards. The tweaks burmese opentype fonts for windows are released by mutual agreement of burmese font developers and UTN-11. I hope to translate some glossary first. It might be useful for this project right now. No more possible activities before having stable standards and rendering engine support for burmese. Best Ngwe Tun. On Mon, Mar 3, 2008 at 3:44 PM, Charles-H. Schulz [EMAIL PROTECTED] wrote: Hello Javier, Le 1 mars 08 à 07:43, Javier SOLA a écrit : I am starting a new localization effort for some minority languages in Cambodia. The goal is not to translate the user interface, but to create locales that will allow the use of local forms and spell- checkers. Three of this languages: Brao (brb, also known as Lave), Tampuan (tpu) and Bunong (bun) use the Khmer script, while the forth one - Cham - has its own script. The languages are listed in 639-3, except for Cham (cmc) that is listed in 639-2. These are excellent news. For the localization in Burmese, Wunna Ko Ko is working on it (see http://my.openoffice.org); perhaps you two could join your efforts? Best, Charles. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- In Burmese; Ngwe mean 1) Silver 2) Money 3) Second Awards; Tun mean 1) Light 2) be prominent. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Change of kn_IN team coordination
Hi, Vikram Vincent wrote: Hello, I would like to propose a change in Coordinator for the OO l10n for Kannada(kn_IN). The Swatantra.Org [Kannada localisation project] has initiated the localisation work at http://translate.swatantra.org/main.php and we would like to ensure a sustained team effort. Our team is working in coordination with Kannada Depts. of various educational institutions, with Christ College(Automomous), Bangalore,http://christcollege.edu extending maximum support. I am CC'ing the current coordinator(Mr. Pramod) for his comments. Currently, I am the Coorinator for localisation of Debian and I would like to take up the responsibility of Coordinator of OO Kannada l10n as well. Our list is [EMAIL PROTECTED] Thank you. Regards, you have my support in changing the leadership of the Kannada Native-Language project. However, it is important that we make sure that this is what the OOo Kannada team wants. Can you propose this change at the projects_leads list? Is there an ooo Kannada mailing list you can also cc: to make sure this announcements reaches all interested people? Thanks, Rafaella - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Change of kn_IN team coordination
Hello, Charles-H. Schulz wrote: Hi, Le 3 mars 08 � 16:05, Rafaella Braconi a �crit : you have my support in changing the leadership of the Kannada Native-Language project. However, it is important that we make sure that this is what the OOo Kannada team wants. Mr. Pramod initially took up the coordination of localisation of various projects but seems to be unable to focus on them now. Since there is no existing work in Kannada w.r.t. OO, we would like to take it up. Can you propose this change at the projects_leads list? Is there an ooo Kannada mailing list you can also cc: to make sure this announcements reaches all interested people? There is at this time no NLP for kannada. A former attempt was aborted, perhaps it might be time to relaunch the idea? Yes, definitely. We would be happy with any guidance that you can give us. Thanks. With warm wishes, -- Vikram Vincent +91 9448810822 http://www.swatantra.org http://translate.swatantra.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Change of kn_IN team coordination
Hi, Le 3 mars 08 à 16:34, Vikram Vincent a écrit : Hello, Charles-H. Schulz wrote: Hi, Le 3 mars 08 � 16:05, Rafaella Braconi a �crit : you have my support in changing the leadership of the Kannada Native-Language project. However, it is important that we make sure that this is what the OOo Kannada team wants. Mr. Pramod initially took up the coordination of localisation of various projects but seems to be unable to focus on them now. Since there is no existing work in Kannada w.r.t. OO, we would like to take it up. Can you propose this change at the projects_leads list? Is there an ooo Kannada mailing list you can also cc: to make sure this announcements reaches all interested people? There is at this time no NLP for kannada. A former attempt was aborted, perhaps it might be time to relaunch the idea? Yes, definitely. We would be happy with any guidance that you can give us. Thanks. Sure. Check out here: http://native-lang.openoffice.org and http://wiki.services.openoffice.org/wiki/NLC Even if you create a native-lang project you will be tightly working with the L10N project. Best, Charles. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Pootle on port 80
Hello Aijin, some italian translators are experiencing problems with Pootle because of firewalls / traffic shaping appliances. I remember you are already aware about this annoyance. Do you have any good news? :-) Thanks! Paolo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle on port 80
On Tuesday 04 March 2008 02:18:01 Paolo Pozzan wrote:
Hello Aijin,
some italian translators are experiencing problems with Pootle because of
firewalls / traffic shaping appliances.
I remember you are already aware about this annoyance. Do you have any good
news? :-)
As a workaround I use tr.ooo server as a proxy:
http://pootle.openoffice.org.tr/
P.S. It is not an official solution and provided without any warranty. :)
--
Best regards,
Rail Aliev
http://{ru,tr}.openoffice.org
Beware of a tall blond man with one black shoe.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
