Re: [l10n-dev] Re: [qa-dev] switching to XLIFF
The future of OOo localization is clearly XLIFF, and we are working on it. Even if they are not yet part of the Translate Toolkit documentation, sometime ago, Dwayne wrote filters to translate directly fron SDF to XLIFF and back. Now the Pootling team is working on testing and improving these tools, adding a xliffupgrade tool that will allow upgrades from XLIFF to new sets of XLIFF files. In about a month we will probably feel safe enough to release the whole cycle in stable format, together with Pootling 0.2 or Pootling 0.2.1 Pootling is being specially designed to get the most out of XLIFF files. The present version gives direct information about glossary to be used, signaling which words need to be considered as terminology, and their translation (if available). It also uses translation memory in its own format and in standard formats (TMX). It attempts to give the highest level of aid while being package independent (e.g. not knowledgeable about OpenOffice)... which means that the intelligence must be in the filters. OpenOffice has multiple variable formats, and it is nice that the program recognises them as units of text that need to be replicated exactly at the target. XLIFF uses for this the in-line tag. The introduction of the tags must me done by the filters SDF to XLIFF. Translation memory must learn to deal with tags. Independently of which tools are being used, I am glad to hear agreement on the fact that the future of OOo localization is XLIFF. Javier Jean-Christophe Helary wrote On Aug 11, 2007, at 8:02 PM, Clytie Siddall wrote: So I'm not talking about converting between SDF, PO and XLIFF, or between any combination of the three. I'm talking about using XLIFF as the base translation format for OpenOffice.org. This is what I suggested in a mail here at the beginning of July. But currently all the XLIFF conversion have to go through the SDF->PO thing first. The original help files are in XML so converting them directly to XLIFF should be way easier (for the translator but also for the processors as well) than going through the current SDF->PO thing. People who still want to do PO will be able to do so with the conversions from XLIFF. Jean-Christophe - 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] Burmese Language Project
Wunna Ko Ko wrote Dear Javier SOLA, On 8/11/07, Javier SOLA <[EMAIL PROTECTED]> wrote: Wunna Ko Ko Wunna Ko Ko wrote Dear Javier SOLA, Thanks for your information. I understand the situation. The latest proposal change has already been accepted by UTC, and at stage 6 by ISO/IEC. Please check http://www.unicode.org/alloc/Pipeline.html Great Our team would like to start with Internationalization, like line breaking, searching, collation, etc. So, translation process is not necessary at this stage, I think. It is the only possible step right now, as far as I understand. It is. You can start working on the OpenOffice locale file, as well as the collation sequence, if you have the correct ordering sequence. OK. I & my team will start working on Locale files. You can also start patching the OpenOffice files that are required to include Burmese among the existing locales. Searching should not be a problem. It has still problem. It can't get exact search till now. We also have some problems for Khmer in OpenOffice. I have to figure out what it really is. We can search for full syllables, but not for parts of it, even if it is a correct sequence. Line-breaking is handled by the ICU library, which is used by OpenOffice. You have to look onto how Thai is handled, and do something similar, the simpler way is to do it dictionary/based... but you need a word-list. Our idea is starting the line-break by syllable break. We will place the syllable segmentation rules. Where should we put? The breakiterator of the ICU library, but I do not have a clue of how it is done. Can Myanmar be broken at the end of any syllable? You do not need to wait for the end of a word? A spell-checker is also a very useful feature to work on. As Microsoft will not localize to Myanmar yet for a number of years, a spell checker would give you a very strong reason for people to change to OpenOffice. Javier With Best Regards, Please look into http://www.khmeros.info/tools to see which files already have Burmese included, and which do not. If you can prepare patches for the other files, wonderful, otherwise we will help you. The most important thing is to gather all the necessary information for the locale file and collation. Javier Could you please let me know how can I create a project to do I18n? With Best Regards, Wunna Ko Ko On 8/11/07, Javier SOLA <[EMAIL PROTECTED]> wrote: Dear Wunna Ko Ko, Very good to hear from you. The first step for localisation of Burmese is to have support for your script and fonts. Support for Myanmar in Linux is still not available. Is tarted some work on it with Ngwe Tun, but we did not continue because the state of Unicode Burmese was unclear, I am not sure what the state of the latest proposal for change is now. Burmese is not officially supported by Microsoft Windows, but there are ways around it. This support should already be enough to start the localization and translation process. Does NLP already have a glossary of words for computer use in Myanamar? We can give you a first list of about 1,500 words that you should have in order to start the translation work in a coherent way (all translators translating the same word in the same way). Please look at: http://l10n.openoffice.org/ http://www.khmeros.info/tools for information about OOo localization. Regards, Javier Wunna Ko Ko wrote Dear All, I am the team leader of the Myanmar NLP research center, organized and funded by Myanmar Government. Is there anybody who is working on Burmese Language for OO projects? We would like to start with I18n by creating locale and go to the localization by translating OO. I would like to know whether there is anybody working on it and how much level has been developed. With Best 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] strings changed in help section
Pavel Janík pravi: > Hi, > >>> please update your translation to the latest SRC680 milestone!!! >> >> Does this mean update to OpenOffice.org-SRC680_m222-POT? > > yes, right now, the latest milestone to update to is SRC680_m222. > > Once OOG680_ POTs will pop up, switch to them. http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT/OpenOffice.org-OOG680_m1-POT.tar.gz was created on August 10th. Does this mean that a translation update is/will be extended? There are some new strings in helpcontent. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: [qa-dev] switching to XLIFF
On Aug 11, 2007, at 8:02 PM, Clytie Siddall wrote: So I'm not talking about converting between SDF, PO and XLIFF, or between any combination of the three. I'm talking about using XLIFF as the base translation format for OpenOffice.org. This is what I suggested in a mail here at the beginning of July. But currently all the XLIFF conversion have to go through the SDF->PO thing first. The original help files are in XML so converting them directly to XLIFF should be way easier (for the translator but also for the processors as well) than going through the current SDF->PO thing. People who still want to do PO will be able to do so with the conversions from XLIFF. Jean-Christophe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Burmese Language Project
Wunna Ko Ko, welcome to the OpenOffice.org i18n project. :) Would you please send any new information on Unicode locales and resources for Burmese, to Ed Trager <[EMAIL PROTECTED]> of the Unicode Font Guide? http://www.unifont.org/fontguide/ He wants to improve the section on Burmese. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part
[l10n-dev] Re: [qa-dev] switching to XLIFF
Actually, this should be on l10n-dev. I think I sent it to the wrong list initially. Sorry. (I'm not quite sure how that happened... :S ) On 09/08/2007, at 10:32 PM, Jean-Christophe Helary wrote: On 9 août 07, at 21:22, Vito Smolej wrote: Back-Conversion to PO!? SUN: XML<->SDF<->PO<->XLIFF :Translators SUN: XML<->SDF<->TMX :Translators The PO->XLIFF and SDF->TMX conversions do not encapsulate any code contents so we have all the code as translatable... Even if PO were not used we'd still have: XML<->SDF<->XLIFF XML<->SDF<->TMX Which is just as bad for the same reason: SDF removes all XML benefit from the file since it flattens everything (with plenty of ugly escapes) to text. And the current converters don't seem to be smart enough to encapsulate all that anyway. I have no idea why SUN can't do: XML<->XLIFF(<->PO) XML<->TMX I did not know about that ... You're of course absolutely right about losing everything. I tried the last OOo 2.3 translation files with PO first and gave up. Then I hacked the SDF to have something that looked like the original XML and used OmegaT to translate. The results were very satisfying, but the hack was a pain in the butt (it is documented on the [EMAIL PROTECTED] list). My initial email [A] was to request that OpenOffice.org convert entirely to XLIFF. The SDF format is extremely cumbersome, and I've yet to see any translation benefit in it whatsoever. PO is a useful translation format, but XLIFF is far superior. So I'm not talking about converting between SDF, PO and XLIFF, or between any combination of the three. I'm talking about using XLIFF as the base translation format for OpenOffice.org. Translators can choose to convert back to PO if they like, since we already have the conversion tools, but those of us using the XLIFF format will have its major advantages: an XML standard designed for i18n. Its metadata capacities and sheer manipulability are way ahead of PO format. (Since SDF format has neither metadata capacity or any appreciable level of manipulability, I can't compare it.) If OpenOffice.org adopted OpenDocument, it certainly should adopt XLIFF. So, where do we start? :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [A] XLIFF is the standard [1] for professional translation, and is becoming the standard for free-software translation. It is XML for translators: extremely easy to manipulate, and rich with metadata capabilities which save us a lot of time. Compared even to PO format, XLIFF has serious advantages. It is exactly what we need to manage the complex background of an OpenOffice.org translation file. It also handles document translation extremely well, and enhances TM capability. There are a number of free-software translation tools already available for XLIFF [2], and Pootle is based on XLIFF. My offline editor, LocFactoryEditor, is also based on XLIFF: I expect Pootling, the Wordforge offline editor, is as well. There are a great many advantages to switching to XLIFF. When can we start? :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://www.oasis-open.org/committees/xliff/documents/xliff- specification.htm [2] e.g. http://xliff-tools.freedesktop.org/wiki/Projects/xlifftool http://sourceforge.net/projects/xliffroundtrip PGP.sig Description: This is a digitally signed message part
Re: [l10n-dev] Burmese Language Project
Dear Javier SOLA, On 8/11/07, Javier SOLA <[EMAIL PROTECTED]> wrote: > Wunna Ko Ko > > Wunna Ko Ko wrote > > Dear Javier SOLA, > > > > Thanks for your information. > > > > I understand the situation. > > > > The latest proposal change has already been accepted by UTC, and at > > stage 6 by ISO/IEC. > > Please check > > http://www.unicode.org/alloc/Pipeline.html > > > Great > > Our team would like to start with Internationalization, like line > > breaking, searching, collation, etc. So, translation process is not > > necessary at this stage, I think. It is the only possible step right > > now, as far as I understand. > > > It is. You can start working on the OpenOffice locale file, as well as > the collation sequence, if you have the correct ordering sequence. OK. I & my team will start working on Locale files. > > You can also start patching the OpenOffice files that are required to > include Burmese among the existing locales. > > Searching should not be a problem. It has still problem. It can't get exact search till now. > > Line-breaking is handled by the ICU library, which is used by > OpenOffice. You have to look onto how Thai is handled, and do something > similar, the simpler way is to do it dictionary/based... but you need a > word-list. Our idea is starting the line-break by syllable break. We will place the syllable segmentation rules. Where should we put? With Best Regards, > > Please look into > > http://www.khmeros.info/tools > > to see which files already have Burmese included, and which do not. If > you can prepare patches for the other files, wonderful, otherwise we > will help you. The most important thing is to gather all the necessary > information for the locale file and collation. > > Javier > > > Could you please let me know how can I create a project to do I18n? > > > > With Best Regards, > > > > > > Wunna Ko Ko > > > > > > On 8/11/07, Javier SOLA <[EMAIL PROTECTED]> wrote: > > > >> Dear Wunna Ko Ko, > >> > >> Very good to hear from you. > >> > >> The first step for localisation of Burmese is to have support for your > >> script and fonts. > >> > >> Support for Myanmar in Linux is still not available. Is tarted some work > >> on it with Ngwe Tun, but we did not continue because the state of > >> Unicode Burmese was unclear, I am not sure what the state of the latest > >> proposal for change is now. > >> > >> Burmese is not officially supported by Microsoft Windows, but there are > >> ways around it. This support should already be enough to start the > >> localization and translation process. > >> > >> Does NLP already have a glossary of words for computer use in Myanamar? > >> We can give you a first list of about 1,500 words that you should have > >> in order to start the translation work in a coherent way (all > >> translators translating the same word in the same way). > >> > >> Please look at: > >> > >> http://l10n.openoffice.org/ > >> http://www.khmeros.info/tools > >> > >> for information about OOo localization. > >> > >> Regards, > >> > >> Javier > >> > >> Wunna Ko Ko wrote > >> > >>> Dear All, > >>> > >>> I am the team leader of the Myanmar NLP research center, organized and > >>> funded by Myanmar Government. > >>> > >>> Is there anybody who is working on Burmese Language for OO projects? > >>> > >>> We would like to start with I18n by creating locale and go to the > >>> localization by translating OO. > >>> > >>> I would like to know whether there is anybody working on it and how > >>> much level has been developed. > >>> > >>> With Best 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] > > -- Wunna Ko Ko Get Paid To Read Emails. Free To Join Now! http://www.emailcashpro.com/?source=Email&r=onlinestore - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Updating the language lists
Pavel Janík pravi: Was this list updated? Pavel did that, the latest revisions of /cvs/l10n/www/languages.* are of 2007-07-13 I update it in batches - there is what I have received in the past. Update for Slovenian language: just state "Supported" since we guarantee all versions to be 100% translated. Should I open a new issue or is this message enough? Regards Robert Ludvik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Burmese Language Project
Wunna Ko Ko Wunna Ko Ko wrote Dear Javier SOLA, Thanks for your information. I understand the situation. The latest proposal change has already been accepted by UTC, and at stage 6 by ISO/IEC. Please check http://www.unicode.org/alloc/Pipeline.html Great Our team would like to start with Internationalization, like line breaking, searching, collation, etc. So, translation process is not necessary at this stage, I think. It is the only possible step right now, as far as I understand. It is. You can start working on the OpenOffice locale file, as well as the collation sequence, if you have the correct ordering sequence. You can also start patching the OpenOffice files that are required to include Burmese among the existing locales. Searching should not be a problem. Line-breaking is handled by the ICU library, which is used by OpenOffice. You have to look onto how Thai is handled, and do something similar, the simpler way is to do it dictionary/based... but you need a word-list. Please look into http://www.khmeros.info/tools to see which files already have Burmese included, and which do not. If you can prepare patches for the other files, wonderful, otherwise we will help you. The most important thing is to gather all the necessary information for the locale file and collation. Javier Could you please let me know how can I create a project to do I18n? With Best Regards, Wunna Ko Ko On 8/11/07, Javier SOLA <[EMAIL PROTECTED]> wrote: Dear Wunna Ko Ko, Very good to hear from you. The first step for localisation of Burmese is to have support for your script and fonts. Support for Myanmar in Linux is still not available. Is tarted some work on it with Ngwe Tun, but we did not continue because the state of Unicode Burmese was unclear, I am not sure what the state of the latest proposal for change is now. Burmese is not officially supported by Microsoft Windows, but there are ways around it. This support should already be enough to start the localization and translation process. Does NLP already have a glossary of words for computer use in Myanamar? We can give you a first list of about 1,500 words that you should have in order to start the translation work in a coherent way (all translators translating the same word in the same way). Please look at: http://l10n.openoffice.org/ http://www.khmeros.info/tools for information about OOo localization. Regards, Javier Wunna Ko Ko wrote Dear All, I am the team leader of the Myanmar NLP research center, organized and funded by Myanmar Government. Is there anybody who is working on Burmese Language for OO projects? We would like to start with I18n by creating locale and go to the localization by translating OO. I would like to know whether there is anybody working on it and how much level has been developed. With Best 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] Burmese Language Project
Dear Javier SOLA, Thanks for your information. I understand the situation. The latest proposal change has already been accepted by UTC, and at stage 6 by ISO/IEC. Please check http://www.unicode.org/alloc/Pipeline.html Our team would like to start with Internationalization, like line breaking, searching, collation, etc. So, translation process is not necessary at this stage, I think. It is the only possible step right now, as far as I understand. Could you please let me know how can I create a project to do I18n? With Best Regards, Wunna Ko Ko On 8/11/07, Javier SOLA <[EMAIL PROTECTED]> wrote: > Dear Wunna Ko Ko, > > Very good to hear from you. > > The first step for localisation of Burmese is to have support for your > script and fonts. > > Support for Myanmar in Linux is still not available. Is tarted some work > on it with Ngwe Tun, but we did not continue because the state of > Unicode Burmese was unclear, I am not sure what the state of the latest > proposal for change is now. > > Burmese is not officially supported by Microsoft Windows, but there are > ways around it. This support should already be enough to start the > localization and translation process. > > Does NLP already have a glossary of words for computer use in Myanamar? > We can give you a first list of about 1,500 words that you should have > in order to start the translation work in a coherent way (all > translators translating the same word in the same way). > > Please look at: > > http://l10n.openoffice.org/ > http://www.khmeros.info/tools > > for information about OOo localization. > > Regards, > > Javier > > Wunna Ko Ko wrote > > Dear All, > > > > I am the team leader of the Myanmar NLP research center, organized and > > funded by Myanmar Government. > > > > Is there anybody who is working on Burmese Language for OO projects? > > > > We would like to start with I18n by creating locale and go to the > > localization by translating OO. > > > > I would like to know whether there is anybody working on it and how > > much level has been developed. > > > > With Best Regards, > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Wunna Ko Ko Get Paid To Read Emails. Free To Join Now! http://www.emailcashpro.com/?source=Email&r=onlinestore - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
