Difference between revisions of "NL.openoffice.org"
(→ToDo) |
Brandelune (Talk | contribs) (→Translation using OmegaT with TM and Glossary) |
||
| Line 51: | Line 51: | ||
* Download and unzip [http://sourceforge.net/projects/omegat OmegaT] | * Download and unzip [http://sourceforge.net/projects/omegat OmegaT] | ||
| + | * Within the directory you use for this translation create a few OmegaT specific folders: | ||
| + | ** '''source''' will contain the above .po file | ||
| + | ** '''tm''' will contain the translation memory file you will download from [http://www.openoffice.org/issues/show_bug.cgi?id=73150 this issue], or any other TMX you want to use | ||
| + | ** '''glossary''' will contain the glossary you'll export from SunGloss (or any other glossary you want to use) | ||
| + | ** '''target''' will contain the translated files you can create at any point during the translation | ||
| + | |||
| + | OmegaT uses a lot of memory to load the source files, the TMX files, the glossaries ''as well as'' all the correspondences between all the files that it creates at load time. It may sometimes run out of memory. If that is the case start OmegaT from the command line using: | ||
| + | (on Windows) javaw -Xmx512m -jar OmegaT.jar (512mb is an indicative value and you can actually put more than the amount or ram you really have) | ||
| + | |||
* Start OmegaT and create a new project | * Start OmegaT and create a new project | ||
| − | * | + | * Make sure the language codes match the codes of the TMX file you've decided to use |
| − | * | + | * Select the above directories to be used as project directories |
| − | * | + | * OK |
| − | * | + | |
| − | + | * Translate your assigned files | |
| + | * Whenever you want to check the files, open the '''target''' folder. The contents of '''target''' is temporary and will be overwritten by any modifications made from within OmegaT. | ||
| + | |||
| + | To export a glossary from SunGloss you need to be a registered user. | ||
| + | * Export only the relevant parts (StarOffice/StarSuite for ex), only in the relevant languages. You'll mostly need the source term, the target term and the target term comments | ||
| + | * Rename the file (name).csv and open it in Calc | ||
| + | * Make sure you only have three columns (see above) | ||
| + | * Save while editing the CSV filter: Character set=utf-8, Field delimiter=tab, Text delimiter=(nothing) | ||
| + | * Rename the file (name).utf8 | ||
| + | * Make sure the file is in the '''glossary''' directory | ||
| + | |||
| + | Any modifications to the source files, the TMX file or the glossary files will require the project to be reloaded to be taken into account. | ||
| − | + | OmegaT comes with a 10mn tutorial that is displayed at startup. Make sure you read it before you start. | |
=== po to sdf === | === po to sdf === | ||
Revision as of 00:36, 19 June 2007
Welcome to the NL.OpenOffice.org wiki pages. This project is part of the Native-Language Confederation and uses this wiki to coordinate parts of its work that need to be updated regularly and/or by more than one person.
We communicate mainly by mail. For this we use the mailing list localization@nl.openoffice.org [mainly Dutch]. To view the mailing list archive or for subscription see: http://nl.openoffice.org/about-mailinglist.html Sometimes we use the #nl.openoffice.org channel on irc.freenode.net.
There are a number of things we are currently working on inside the Dutch localization project:
Contents
Localization testing on new releases of OOo
- For TCM-tool see: http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo
- For more information see the TCM page
- To see how this fits into the release cycle Release Action List for QA
- About the testtool and how to localize it
- Roadmap OpenOffice.org 2.2
Translation for OOo 2.2
- Collaboration with the Sun/Globalization team see: http://l10n.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7230
- Translation information Translation_for_2.2
- The translation tool OLT can be found at: https://open-language-tools.dev.java.net.
- A quick guide on how to use the tool can be found at: http://developers.sun.com/techtopics/global/technology/translation/downloads/QuickGuide_XLIFF_T9n_Editor.pdf
- 16-01-2007 : Translation of the Dutch files for OOo 2.2 has been completed (see http://www.openoffice.org/issues/show_bug.cgi?id=73150)
Translation for OOo 2.3
sdf-files
Download and unzip the sdf-files
- HC2_93824_89_2007-06-05_31.sdf (Wordcount: 22116)
- UI_93824_89_2007-06-05_31.sdf (Wordcount: 3320)
sdf to po
oo2po -l nl UI_93824_89_2007-06-05_31.sdf UI oo2po: warning: Output directory does not exist. Attempting to create processing 48 files... [###########################################] 100%
oo2po -l nl HC2_93824_89_2007-06-05_31.sdf HC2 oo2po: warning: Output directory does not exist. Attempting to create processing 35 files... [###########################################] 100%
Translation using OmegaT with TM and Glossary
- Download and unzip OmegaT
- Within the directory you use for this translation create a few OmegaT specific folders:
- source will contain the above .po file
- tm will contain the translation memory file you will download from this issue, or any other TMX you want to use
- glossary will contain the glossary you'll export from SunGloss (or any other glossary you want to use)
- target will contain the translated files you can create at any point during the translation
OmegaT uses a lot of memory to load the source files, the TMX files, the glossaries as well as all the correspondences between all the files that it creates at load time. It may sometimes run out of memory. If that is the case start OmegaT from the command line using:
(on Windows) javaw -Xmx512m -jar OmegaT.jar (512mb is an indicative value and you can actually put more than the amount or ram you really have)
- Start OmegaT and create a new project
- Make sure the language codes match the codes of the TMX file you've decided to use
- Select the above directories to be used as project directories
- OK
- Translate your assigned files
- Whenever you want to check the files, open the target folder. The contents of target is temporary and will be overwritten by any modifications made from within OmegaT.
To export a glossary from SunGloss you need to be a registered user.
- Export only the relevant parts (StarOffice/StarSuite for ex), only in the relevant languages. You'll mostly need the source term, the target term and the target term comments
- Rename the file (name).csv and open it in Calc
- Make sure you only have three columns (see above)
- Save while editing the CSV filter: Character set=utf-8, Field delimiter=tab, Text delimiter=(nothing)
- Rename the file (name).utf8
- Make sure the file is in the glossary directory
Any modifications to the source files, the TMX file or the glossary files will require the project to be reloaded to be taken into account.
OmegaT comes with a 10mn tutorial that is displayed at startup. Make sure you read it before you start.
po to sdf
po2oo -l nl -t UI_93824_89_2007-06-05_31.sdf ./UI UI.sdf processing 48 files... [###########################################] 100%
check sdf
gsicheck UI.sdf
Translation of documentation
Several members of nl.openoffice.org also partcipate in the OOoAuthors project.
OOoAuthors.org
is a development site for OpenOffice.org documentation.
We are a group of volunteer reviewers, writers, editors, proofreaders, indexers, and translators producing documentation for OpenOffice.org Writer, Calc, Draw, Impress, Math and Base.
There are also documents in German, English, Romanian, and other languages.
