Difference between revisions of "NL.openoffice.org"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Translation for OOo 2.4)
m (Pagina's op de Nederlandstalige OOo-Wiki)
 
(100 intermediate revisions by 8 users not shown)
Line 8: Line 8:
  
  
== Localization testing on new releases of OOo ==
+
== Pagina's op de Nederlandstalige OOo-Wiki ==
  
* For TCM-tool see: http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo
+
Sinds medio 2008 is er het beleid om pagina's een gestructureerde naam te geven. Om te helpen de wiki wat overzichtelijker te houden en voor onderhoudswerk e.d.
* For more information see [[Test_Case_Management|the TCM page]]
+
Alle pagina's van het Nederlandstalige Native Language-project zijn geplaatst op
* To see how this fits into the release cycle [[Release Action List for QA]]
+
http://wiki.services.openoffice.org/wiki/NL/  
* About the [[Testtool|testtool]] and [[HowTo_localize_qatesttool_environment|how to localize it]]
+
Daarbinnen is de onderverdeling:
* Roadmap [[OOoRelease22|OpenOffice.org 2.2]]
+
* Documentation/
 +
* Localisatie/
 +
* QA/
 +
* FAQ/
 +
* [[TipsEnTrucs]]
 +
* Bijeenkomsten/
 +
* Marketing/
 +
(Dit kan uiteraard worden uitgebreid.)
 +
 
 +
== Localization testing on new releases of OOo ==
  
== Translation for OOo 2.2 ==
+
* Information is moved to [http://wiki.services.openoffice.org/wiki/NL_QA this] page.
  
* Collaboration with the Sun/Globalization team see: http://l10n.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7230
+
== Problems with ID-strings (OmegaT / poEdit) ==
* 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 ==
+
On behalf of the Dutch translators is below a description of fixing the problem with the ID-strings which are merged with the msgstr inside OmegaT and poEdit.
  
* [http://www.openoffice.org/issues/show_bug.cgi?id=78177 Invitation from Sun]
+
== Problemen met ID-tekenreeksen (OmegaT / poEdit) ==
* Translation information [[Translation_for_2.3]]
+
* 26-07-2007 : Translation 2.3 completed
+
  
== Translation for OOo 2.4 ==
+
The following issue relates to the use of KDE style comments to disambiguate duplicate messages.
 +
If you use the following:
  
* [http://www.openoffice.org/issues/show_bug.cgi?id=82027 Invitation from Sun]
+
  oo2po --duplicates=msgctxt
* Translation information [[Translation_for_2.4]]
+
  
 +
then these will appear in msgctxt entries.  Newer versions of poEdit can manage msgctxt. I'm not
 +
sure about OmegaT's abilities with msgctxt.  KBabel can handle KDE style comments without any issues.
  
{| border="1" class="prettytable"
+
In de tekenreeksen zijn ID's ingebouwd. Dit ziet er bij het bewerken in OmegaT zo uit:
| part
+
| translator
+
| trans-status
+
| reviewer
+
| rev-status
+
  
|-
+
  _: 02110000.xhp#par_id3150955.12.help.text\nContents
| ui
+
  <segment 0043> _: 02110000.xhp#par_id3150955.12.help.text\nContents <einde segment>
| simonbr
+
| not translated
+
| natalie
+
| not translated
+
  
|-
+
Het probleem zit in onderstaand stukje binnen het segment:
| sbasic
+
( beginnend met een onderstrepingsteken + dubbele punt en eindigend op ....text\n)
| corno
+
| not translated
+
| natalie
+
| not translated
+
  
|-
+
  '''_: 02110000.xhp#par_id3150955.12.help.text\n'''
| scalc (incl. scalc.po)
+
| dickgr
+
| started
+
| natalie
+
| not translated
+
  
|-
+
Dat is een ID-reeks die uit het te vertalen gedeelte moet worden gehaald.
| schart
+
Gelukkig zit het niet in alle segmenten ;-)
| henkbu
+
| not translated
+
| natalie
+
| not translated
+
  
|-
+
  <segment 0043> _: 02110000.xhp#par_id3150955.12.help.text\nContents <einde segment>
| sdraw
+
| henkbu
+
| not translated
+
| natalie
+
| not translated
+
  
|-
+
wordt dan
| shared (incl. shared.po)
+
| unknown
+
| not translated
+
| unknown
+
| not translated
+
  
|-
+
  <segment 0043> Contents <einde segment>
| simpress (incl. simpress.po)
+
| unknown
+
| not translated
+
| unknown
+
| not translated
+
  
|-
+
Het vertaalde segment dient er, vertaald, als volgt uit te zien:
| smath (incl. smath.po)
+
| unknown
+
| not translated
+
| unknown
+
| not translated
+
  
|-
+
  _: 02110000.xhp#par_id3150955.12.help.text\nContents
| swriter (incl. swriter.po)
+
  <segment 0043> Inhoud <einde segment>
| unknown
+
| not translated
+
| unknown
+
| not translated
+
  
|}
+
Bij het maken van de vertaalde documenten komt, in OmegaT, dan alles toch op zijn juiste plek terecht.
  
 
== Translate Tools ==
 
== Translate Tools ==
Line 122: Line 81:
 
</div>
 
</div>
  
Execute oo2po -h for help.
+
Execute [http://translate.sourceforge.net/wiki/toolkit/oo2po oo2po] -h for help.
  
 
   oo2po -l nl UI_93824_89_2007-06-05_31.sdf UI
 
   oo2po -l nl UI_93824_89_2007-06-05_31.sdf UI
Line 146: Line 105:
  
 
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:
 
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)
+
(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
Line 211: Line 170:
  
 
[[Category:NLC]]
 
[[Category:NLC]]
 +
[[Category:NL.OpenOffice.org]]

Latest revision as of 16:28, 3 May 2010

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:


Pagina's op de Nederlandstalige OOo-Wiki

Sinds medio 2008 is er het beleid om pagina's een gestructureerde naam te geven. Om te helpen de wiki wat overzichtelijker te houden en voor onderhoudswerk e.d. Alle pagina's van het Nederlandstalige Native Language-project zijn geplaatst op http://wiki.services.openoffice.org/wiki/NL/ Daarbinnen is de onderverdeling:

  • Documentation/
  • Localisatie/
  • QA/
  • FAQ/
  • TipsEnTrucs
  • Bijeenkomsten/
  • Marketing/

(Dit kan uiteraard worden uitgebreid.)

Localization testing on new releases of OOo

  • Information is moved to this page.

Problems with ID-strings (OmegaT / poEdit)

On behalf of the Dutch translators is below a description of fixing the problem with the ID-strings which are merged with the msgstr inside OmegaT and poEdit.

Problemen met ID-tekenreeksen (OmegaT / poEdit)

The following issue relates to the use of KDE style comments to disambiguate duplicate messages. If you use the following:

 oo2po --duplicates=msgctxt

then these will appear in msgctxt entries. Newer versions of poEdit can manage msgctxt. I'm not sure about OmegaT's abilities with msgctxt. KBabel can handle KDE style comments without any issues.

In de tekenreeksen zijn ID's ingebouwd. Dit ziet er bij het bewerken in OmegaT zo uit:

 _: 02110000.xhp#par_id3150955.12.help.text\nContents
 <segment 0043> _: 02110000.xhp#par_id3150955.12.help.text\nContents <einde segment>

Het probleem zit in onderstaand stukje binnen het segment: ( beginnend met een onderstrepingsteken + dubbele punt en eindigend op ....text\n)

 _: 02110000.xhp#par_id3150955.12.help.text\n

Dat is een ID-reeks die uit het te vertalen gedeelte moet worden gehaald. Gelukkig zit het niet in alle segmenten ;-)

 <segment 0043> _: 02110000.xhp#par_id3150955.12.help.text\nContents <einde segment>

wordt dan

 <segment 0043> Contents <einde segment>

Het vertaalde segment dient er, vertaald, als volgt uit te zien:

 _: 02110000.xhp#par_id3150955.12.help.text\nContents
 <segment 0043> Inhoud <einde segment>

Bij het maken van de vertaalde documenten komt, in OmegaT, dan alles toch op zijn juiste plek terecht.

Translate Tools

sdf to po

Windows users

To open the Command Prompt click Start, click Run, type cmd, and then click OK. Use the command cd to go to the directory where your translation toolkit is located.

 C:\Documents and Settings\user>cd "C:\Program Files\translate-toolkit"
 
 C:\Program Files\translate-toolkit>

Execute oo2po -h for help.

 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 file that you can 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

The first part of the po-file contains a header. Nothing to translate there.

 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: http://qa.openoffice.org/issues/enter_bug.cgi?subcomponent=ui&comment=&short_desc=Localization%20issue%20in%20file%3A%20helpcontent2\source\text\scalc.oo&component=l10n&form_name=enter_issue\n"
 "POT-Creation-Date: 2007-06-18 22:04W.
 
 Europe Daylight Time\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n"
 "X-Generator: Translate Toolkit 1.0\n"
 "X-Accelerator-Marker: ~\n"
  • Use Project > Create Translated Documents to write the results so far to the target directory
  • 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.
  • The contents of the po-files can be seen with text editors that know how to handle LF as a line-ending. Be carefull not to accidentaly save changes to the po-files.

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.

http://www.oooauthors.org/nl

Personal tools