Ahoj,<br><br>ďakujem, pomohlo ;o)<br><br><br><div class="gmail_quote">2008/1/18 Peter Tuhársky <<a href="mailto:tuharsky@misbb.sk">tuharsky@misbb.sk</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ahoj, Martin<br><br>Posielam Ti dokument, ktorý som vytvoril pre nováčikov.<br>Ostatní, prosím, skomentujte, chystám sa to poslať do GNOME-i18n<br><br><br>Peťo<br><br>Martin Babik wrote / napísal(a):<br><div><div></div><div class="Wj3C7c">
> (toto je resend, kedze si nie som isty ci predosli post presiel, ak ano<br>> tak sorry za SPAM ;-) )<br>><br>> Zdravím všetkých,<br>><br>> ako ďalší nováčik sa hlásim k pomoci s prekladmi.<br>> Potreboval by som niekoho kto mi v skratke pomôže so začiatkom resp.
<br>> odkáže na potrebné docu.<br>> Mám skúsenosti s prekladom aplikácií a textov do embedded zariadení v<br>> oblasti meracej a regulačnej techniky a jej vizualizácie, čo však<br>> neznamená, že musím prekladať práve v tejto oblasti.
<br>><br>> Teším sa na spoluprácu<br>><br>> Martin<br>><br>><br></div></div>> ------------------------------------------------------------------------<br>><br>> _______________________________________________
<br><div class="Ih2E3d">> sk-i18n mailing list<br>> <a href="mailto:sk-i18n@lists.linux.sk">sk-i18n@lists.linux.sk</a><br>> <a href="https://lists.linux.sk/mailman/listinfo/sk-i18n" target="_blank">https://lists.linux.sk/mailman/listinfo/sk-i18n
</a><br><br><br></div>--<br>Odchádzajúca správa neobsahuje vírusy, nepoužívam Windows.<br>=======================<br><br>Mgr. Peter Tuhársky<br>Referát informatiky<br>Mesto Banská Bystrica<br>ČSA 26<br>975 39 Banská Bystrica
<br><br>Tel: +421 48 4330 118<br>Fax: +421 48 411 3575<br><br>=======================<br><br>
<div dir="ltr">
<big><b><big>GNOME translation mini-HOWTO<br>
for the translation newbies</big></b></big><br>
<br>
<br>
<br>
Peter Tuhársky <tuharsky at misbb dot sk><br>
Last edited: 18.1.2008<br>
<br>
<br>
If You consider to improve the GNOME translation for Your language, first decide:<br>
1, Do You want just to <b>report</b> some incorrectly translated strings? Then everything You need is <a href="http://bugzilla.gnome.org/" target="_blank">GNOME bugzilla account</a>. You fill in the translation bug just like any other bug (that You hopefully report too).
<br>
2, Do You want to <b>help translating</b> some apps? Then the following piece information may be useful for You.<br>
I have written them because I joined the translation recently and I see
that such a piece of information would help me, and could help others.
Feel free to extend this material and correct the possibly wrong
statements.<br>
<br>
<br>
<br>
<ul>
<li><big><b>Join the </b></big><b><big><a href="mailto:gnome-i18n@gnome.org" target="_blank">gnome-i18n mailing list</a></big> </b>as that's the place where the majority of the Gnome Translation Project communication happens.
</li>
<ul>
<li>There is also an additional way of discussion - IRC channel at #i18n on <a href="http://irc.gnome.org" target="_blank">irc.gnome.org</a></li>
<li>If You wish to participate on the documentation, <a href="http://www.gnome.org/gdp" target="_blank">GDP</a> has gnome-doc mailing list and GDP IRC channel, #docs at
<a href="http://irc.gnome.org" target="_blank">irc.gnome.org</a>.</li>
</ul>
</ul>
<ul>
<li><big><b>Find Your local community</b> by the <a href="http://l10n.gnome.org/teams/" target="_blank">team</a> or by the <a href="http://l10n.gnome.org/languages/" target="_blank">language</a>.</big></li>
<ul>
<li><b>Contact Your team leader</b>. Let him know what You're
willing to do. He may offer You some help, guidance and coordination
with the tasks that others are working on.</li>
<li>Waiting for an answer, You can of course <b>move to next steps.</b></li>
<li>If the team leader didn't answer, contact some other team member.</li>
<li>If noone answers in reasonable time (say, two weeks), let the GTP heads know about that.</li>
<li>If the team for Your language dosen't exist either, <a href="http://live.gnome.org/TranslationProject/StartingATeam" target="_blank">start one</a>.</li>
</ul>
</ul>
<ul>
<li><big><b>Explore the terminology, keep translations consistent</b></big></li>
<ul>
<li><b>Meet the online resources</b></li>
</ul>
<ul>
<ul>
<li>Your translation team probably suggests some online translation
dictionary in order to help You with computer-specific terms. Look at
these resources and make them familiar to You. You will need them. Don't be shy to consult them.</li>
<li>Among the general online resources, look at these links: <a href="http://www.babelzilla.org/index.php?option=com_glossary&Itemid=73" target="_blank">Babelzilla glossary</a>, <put others here></li>
<li>You might even join them in order to keep these
resources as up-to-date and complete as needed. You do it for Yourself
and for newbies too. The higher quality of the resources, the better
translations and less work needed to keep them consistent.</li>
</ul>
<li><b>Follow the Microsoft terminology in reasonable way</b></li>
<ul>
<li>Although You may not like the Microsoft, there are good
reasons to make the translations consistent with their computing
terminology:</li>
<ul>
<li>The translations and terminology are usually the best
side of their products. This may vary for each country of course, since
the translation is held by the the local offices. Some of them
possibly have accomplished better job than others.</li>
<li>They have paid professionals, they have invested
resources. The resulting terminology does have it's value, although it
is not necessarry perfect.</li>
<li>You don't waste Your precious time and energy reinventing the wheel.</li>
<li>It might be "cool" somehow to create different terminology,
however at the end it probably dosen't help anyone.</li>
<li>Be kind to the average users. They probably have learned
the computer terminology on Microsoft's products, or will probably have
to use them somewhere. Don't make their computer experience harder than
necessarry. Don't make them feel hostile. If they are switching to
Linux from Windows, there is already much they must learn. Help them.
Let them feel comfortably and "home" at least in terms of terminology.
Otherwise they could just feel the system "strange" and turn away.</li>
<li>The professionals do.</li>
<li>The enterprise market demands the translations to keep the
standard PC terminology, that is, like it or not, mostly created by the
Microsoft. They have invested to their people. The less hassle, the
better chance to adopt opensource technologies.</li>
<li>If You really hate Microsoft, then remember: You fight them with their own weapons ;-)</li>
</ul>
</ul>
</ul>
</ul>
<ul>
<li><big><b>Choose Your software</b></big></li>
<ul>
<li>Although You can do it using any simple text editor that
preserves headers and syntax of the file (including Midnight Commander
Editor, VI, emacs or others), there also are much more comfortable programs. </li>
<ul>
<li>POedit is simple translation tool and quite good start point.
It offers all basic functionality needed: authomatic spellchecking,
plural editation,translation database etc. </li>
<li>gtranslator</li>
<li>KBabel is complex and feature rich application. It offers
some strong tools: catalogue manager, dictionary generator using
previous translations, translation following the source code, and an authomatic translation that realy works.</li>
</ul>
<li>Regardless of what You use, You will need <b>intltool</b> package.</li>
<li>First time You use Your chosen software, <b>set Your preferences</b>:
The language, name and E-mail address. They will be automatically
stored to the files You have edited in order to allow users or
translation team members to contact You for bugs, suggestions, business
offers and so on ;-)</li>
</ul>
</ul>
<ul>
<li><big><b>The translation process (technically)</b></big></li>
<ul>
<li>You don't need to be a programmer to translate GNOME packages. All translation is done using PO files.</li>
</ul>
<ul>
<li><b>Download</b> the latest .tar.bz2 sources file of some package from <a href="http://ftp.gnome.org/pub/GNOME/sources/" target="_blank">GNOME ftp</a>.</li>
<li>Unpack.</li>
<li>In the po subdirectory, You should find Your language's <b>.po file</b>. That's the point of Your interest.</li>
<li>If there isn't one, then the application is
not translated to Your language. You may either copy the file of the
closest language that users in Your country understand, or use the <b>msginit</b> tool with the --locale parameter with value in this form: sk_SK.UTF-8</li>
<ul>
<li>Either way, create the file xy.po (where xy is the
code of Your language).</li>
</ul>
<ul>
<li><b>check and possibly edit the header</b> of the file: the language
information, country, region, translation team, plural string, and save
the edited
file back to the po directory. You can borrow these from other .po
file of Your language, possibly from other application
that already is translated.</li>
<ul>
<li>the Project-Id-Version parameter should be in the form project-id version, e.q. gst-plugins-ugly 0.10.6</li>
</ul>
<li>run <b>intltool-update xy</b> (where xy is the language code) in order to upgrade the file against the most recent english version</li>
<li>now You can start translating the file in Your editor of choice...</li>
</ul>
<li>There are words that should NOT be translated: .desktop,
.sound and few others. They are usually labelled by translation
note.</li>
<li>The strings could have one of 3 possible status: <b>translated,
fuzzy and untranslated</b>. The "fuzzy" usually means, that it has been
automatically generated by some software and needs human review, or
that the previous translator has not been shure about the translation
of the string. You can also use this status to mark the strings that
You are not sure of.</li>
<li>The underscore letter "_" used before an alphabetical character
means, that the following letter is used as keyboard shortcut. Please
choose the letter in such way that there should be no problem accessing
the letter from standard keyboard (special national characters are not necessarily good idea here).</li>
</ul>
</ul>
<ul>
<li><big><b>Overall suggestions</b></big></li>
<ul>
<li><b>Keep Your priorities</b>. Look at <a href="http://l10n.gnome.org/" target="_blank">Damned lies</a> page, where the statistics is gathered among GNOME translations. Choose the applications You
want to translate, and choose an order of doing that. The amount of
work is usually huge, it is necessarry to split it to small pieces.</li>
<li><b>Work in steps.</b> Concentrate on finishing one translation
before moving to
another. Yes, it is sometimes easier to start the work than to finish
it. However, the complete translations have greater chance to get
accepted, and everytime You send new version of the translation,
someone has to review it and so on.</li>
<li><b>First take care of fuzzy strings.</b> They usually contain
considerable amount of nonsense, introduced by machine "approximate"
translations, however could be more easily overlooked than untranslated
strings and incorrectly marked as "translated" by the reviewer. At the
end, mis-translated or nonsense string causes more harm than
correct, yet untranslated (english) one.</li>
<li><b>There is never "too late"</b> in order to correct incorrect translations or improve the terminology. Just keep it consistent.</li>
<li><b>Community is valuable.</b> There is just too much work for
one-man-show. Help the newbies, recognize the talents. One quality team
member is probably more important than thousands of translated strings. I mean, that talents are worth the time invested.</li>
<li><b>Translation itself is more important than menu shortcuts.</b>
Of course the translation should be as good as possible, however if You can't see, where in the menu structure
is the string placed, <b>Don't hesitate on the shortcuts: translate the application first.</b>
Once You'll have enough time, You can still test the
shortcuts in real life, or correct reported bugs in menu
shortcuts. Until then, good translation with a possible few shortcut
glitches can bless end users more, than half-translated app with (in
fact) no better shortcuts, or even untranslated app.</li>
<li><b>Don't underestimate the importance of Your work.</b> The translation
enables the software to actually be used by the end users. Whatever
great the code behind could be, without clear and smooth tranlation,
hardly could anyone use it. Not everyone does handle english so well
that he could use the software that is not fully localised. The lack of
translation, or its low quality, certainly causes reasonable amount of
potential Linux users turn away.</li>
</ul>
</ul>
</div>
<br>_______________________________________________<br>sk-i18n mailing list<br><a href="mailto:sk-i18n@lists.linux.sk">sk-i18n@lists.linux.sk</a><br><a href="https://lists.linux.sk/mailman/listinfo/sk-i18n" target="_blank">
https://lists.linux.sk/mailman/listinfo/sk-i18n</a><br><br></blockquote></div><br>