Re: [l10n-dev] Purpose of < ... name= ... >
if you don't have the name attribute in your language but the source language has it you will get "Property 'name' missing in Translation" errors on gsicheck. So you need a name attribute if there is one in the en-US string. Gregor Ain Vagula schrieb: 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 \\ name=\\\"Design Mode\\\"\\>Design Mode\\, 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Purpose of < ... name= ... >
I didnt mean to leave attribute out :) Its ok to translate target but leave name untranslated. You can of course translate it too, most of errors in names should be fixed now (earlier this was a reason I didnt want to translate them). ain On Tue, Mar 4, 2008 at 2:09 PM, Gregor Hartmann <[EMAIL PROTECTED]> wrote: > if you don't have the name attribute in your language but the source > language has it you will get "Property 'name' missing in Translation" > errors on gsicheck. > > So you need a name attribute if there is one in the en-US string. > > Gregor > > Ain Vagula schrieb: > > > 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 \\ >> > name=\\\"Design Mode\\\"\\>Design Mode\\, 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] > > > > > - > 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 wrote: 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. It is already possible to render Myanmar text conformant to Unicode 5.1 using OpenType and Graphite. Existing OpenType fonts such as Myanmar3, Padauk and Parabaik can be used in OpenOffice using Uniscribe on Windows and Harfbuzz on Linux (though there may be some minor rendering issues with the latter). Graphite OOo patches can also be used to render using Graphite with the Padauk font see http://www.openoffice.org/issues/show_bug.cgi?id=69129 and http://scripts.sil.org/OOo_20_graphite for example. What should I do without the basic componets of burmese localization. We just need to collect our locales and wish list among burmese communities. The my locale issue is being tracked at http://www.openoffice.org/issues/show_bug.cgi?id=83349 I hope to translate some glossary first. It might be useful for this project right now. Yes, I agree we need to consolidate a glossary of basic computer terms in Burmese. This can then be used to assist reviewing, correcting and completing the existing, partial, OOo Burmese translation. No more possible activities before having stable standards and rendering engine support for burmese. I think there is a lot that can be done. Unicode 5.1 will be released within a month. If and when Microsoft implement Myanmar specific features into Uniscribe, then there may need to be some changes to fonts' OpenType rules, but these are outside OpenOffice. We are not reliant on them to produce a fully functioning Myanmar localized OpenOffice. If you are serious about being involved in the Myanmar/Burmese localisation effort, please join the mailing lists at http://my.openoffice.org/ cheers, Keith - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle on port 80
Hi Paolo and all, I heard from Sunvirtuallab admin that they are currently working on the issue. One dedicated machine is setup, which handles all :80 requests in Sunvirtuallab. All the work (including testing) hopefully will be done in 1-2 weeks. I'll keep updating the progress. Thanks, Aijin Aijin Kim wrote: Hi Paolo, Oh yes, I'm aware of the issue. I asked Sunvirtuallab admin to have a look into it some time ago, I have to say sorry not following the progress these days. The thing is that this issue can't be solved in Pootle server machine itself. There is a front-end machine in Sunvirtuallab, which manages all the requests. It redirects a requests on a certain port to the port of another machine. For Pootle, port 32300 of the front-end machine is redirected to the port 81 of Pootle machine. To handle :80 requests, one highlighted webserver might need to be set up in Sunvirtuallab. I asked again the Sunvirtuallab admin current progress. I'll get back to you with update as soon as possible. Thanks, Aijin Paolo Pozzan 쓴 글: 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] - 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] Pootle on port 80
I wonder why we need TCM on :80, we are really working mostly on pootle more than TCM. Having Pootle python engine to hear on 80 and apache (httpd) to hear on 32300 will have a better solution for both camps. On Tue, 04 Mar 2008 21:59:19 -0600, Aijin Kim <[EMAIL PROTECTED]> wrote: Hi Paolo and all, I heard from Sunvirtuallab admin that they are currently working on the issue. One dedicated machine is setup, which handles all :80 requests in Sunvirtuallab. All the work (including testing) hopefully will be done in 1-2 weeks. I'll keep updating the progress. Thanks, Aijin Aijin Kim wrote: Hi Paolo, Oh yes, I'm aware of the issue. I asked Sunvirtuallab admin to have a look into it some time ago, I have to say sorry not following the progress these days. The thing is that this issue can't be solved in Pootle server machine itself. There is a front-end machine in Sunvirtuallab, which manages all the requests. It redirects a requests on a certain port to the port of another machine. For Pootle, port 32300 of the front-end machine is redirected to the port 81 of Pootle machine. To handle :80 requests, one highlighted webserver might need to be set up in Sunvirtuallab. I asked again the Sunvirtuallab admin current progress. I'll get back to you with update as soon as possible. Thanks, Aijin Paolo Pozzan 쓴 글: 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] - 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] -- Alexandro Colorado CoLeader of OpenOffice.org ES http://es.openoffice.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle on port 80
Hi Alexandro, There are several servers for different projects in Sunvirtuallab and TCM is not only for OO.o project. So it can't be simply said TCM is less used than Pootle. The best solution might be all the servers can hear on 80 and it's what virtuallab admin is currently trying. Thanks, Aijin Alexandro Colorado wrote: I wonder why we need TCM on :80, we are really working mostly on pootle more than TCM. Having Pootle python engine to hear on 80 and apache (httpd) to hear on 32300 will have a better solution for both camps. On Tue, 04 Mar 2008 21:59:19 -0600, Aijin Kim <[EMAIL PROTECTED]> wrote: Hi Paolo and all, I heard from Sunvirtuallab admin that they are currently working on the issue. One dedicated machine is setup, which handles all :80 requests in Sunvirtuallab. All the work (including testing) hopefully will be done in 1-2 weeks. I'll keep updating the progress. Thanks, Aijin Aijin Kim wrote: Hi Paolo, Oh yes, I'm aware of the issue. I asked Sunvirtuallab admin to have a look into it some time ago, I have to say sorry not following the progress these days. The thing is that this issue can't be solved in Pootle server machine itself. There is a front-end machine in Sunvirtuallab, which manages all the requests. It redirects a requests on a certain port to the port of another machine. For Pootle, port 32300 of the front-end machine is redirected to the port 81 of Pootle machine. To handle :80 requests, one highlighted webserver might need to be set up in Sunvirtuallab. I asked again the Sunvirtuallab admin current progress. I'll get back to you with update as soon as possible. Thanks, Aijin Paolo Pozzan 쓴 글: 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
