[l10n-dev] Changed UI string in m1 compared to m0
Hello, I saw that for Windows installer the UI string for installation type, "Full" was changed to "Typical" in m1 (compared to OOO330m0). Isn't there a string freeze on? Lp, m. - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OpenOffice 3.3
Hello Frank, > Hi Sokhem, > the DEV300m84 on Pootle-server is equal to OOO330m0. So mean that If I want OpenOffice (UI+help) for 3.3 get fully translated, I have to use OOO330m0? > Which language do you have in focus? Khmer. Thanks, Sokhem > -Frank > > Khoem Sokhem schrieb: > > Hello All, > > > > I plan to translate OpenOffice 3.3 (UI+Help) from now on. but I am not > > clear, Does OOO3.3_m0-POT is suitable for 3.3 ? > > > > Thanks, > > Sokhem > > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org > > For additional commands, e-mail: dev-h...@l10n.openoffice.org > > - > To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org > For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OpenOffice 3.3
Hi Sokhem, the DEV300m84 on Pootle-server is equal to OOO330m0. Which language do you have in focus? -Frank Khoem Sokhem schrieb: Hello All, I plan to translate OpenOffice 3.3 (UI+Help) from now on. but I am not clear, Does OOO3.3_m0-POT is suitable for 3.3 ? Thanks, Sokhem - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OpenCTI use?
On 20 juil. 10, at 18:06, Andre Schnabel wrote: > Hi, > >> Von: Reiko Saito >> An: dev@l10n.openoffice.org > >> >> Could anyone let me know why TBX is desireble, >> rather than csv in your translation ? > > Because it is a LISA standard that can be (and is) implemented by > several tools? :) Indeed that is the best answer. There is a standard that is going to be much simpler to use and implement and that will also be a LISA standard, it is GlossML, developed by Rodolfo Raya of Maxprograms. It is currently under discussion at LISA. Its structure is much closer to what we need in real life for localization activities but since it is not yet a standard it may be too early to discuss it even if it is very promising. Jean-Christophe Helary fun: http://mac4translators.blogspot.com work: http://www.doublet.jp (ja/en > fr) tweets: http://twitter.com/brandelune - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OpenCTI use?
Hi, > Von: Reiko Saito > An: dev@l10n.openoffice.org > > Could anyone let me know why TBX is desireble, > rather than csv in your translation ? Because it is a LISA standard that can be (and is) implemented by several tools? So instead of using csv (where each and every tool might have a different idea, what values to export in what order) we might use a file format where tools have a common understanding how to process the content. regards, André -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OpenCTI use?
Hello Reiko, > Could you or anyone let me know how you want to > use TBX format of glossary ? > > I believe OmegaT supports csv format in > glossary feature. That is correct. Test versions of OmegaT support normal TSV files (.utf8 or .txt), CSV files (.csv) and TBX files (.tbx). Supported fields are source term/target term/comment but I am not sure how they are labelled in TBX. > Could anyone let me know why TBX is desireble, rather than csv in your > translation ? My guess is that TBX allows the glossary maintainer to have a finer control on the glossary contents by using all the allowed categories and labels, and to let the tools do their parsing according to their ability. Jean-Christophe Helary fun: http://mac4translators.blogspot.com work: http://www.doublet.jp (ja/en > fr) tweets: http://twitter.com/brandelune - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OpenCTI use?
Hi JC, Thanks! Could you or anyone let me know how you want to use TBX format of glossary ? I believe OmegaT supports csv format in glossary feature. Could anyone let me know why TBX is desireble, rather than csv in your translation ? Regards, -Reiko (2010/07/19 7:41), Jean-Christophe Helary wrote: On 19 juil. 10, at 06:23, Elsa Blume wrote: Hi Sophie, Getting back to you on this topic! And gathering info about the import/export option in TBX format to help you update the TD. Could you please tell me which are the tools/editors the Community wants to use to work with TBX format? OmegaT or Virtaal both support TBX. Jean-Christophe Helary fun: http://mac4translators.blogspot.com work: http://www.doublet.jp (ja/en > fr) tweets: http://twitter.com/brandelune - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
