[sk-i18n] Zdravim
Peter Tuhársky
tuharsky at misbb.sk
Mon Jan 21 06:27:01 CET 2008
To som rád.
Posielam máliÄko rozÅ¡Ãrenú verziu.
Priatelia, prosÃm pripomienkujte, ak sa vám chce.
Peťo
Martin Babik wrote / napÃsal(a):
> Ahoj,
>
> Äakujem, pomohlo ;o)
>
>
> 2008/1/18 Peter Tuhársky <tuharsky na misbb.sk <mailto:tuharsky na misbb.sk>>:
>
> Ahoj, Martin
>
> Posielam Ti dokument, ktorý som vytvoril pre nováÄikov.
> OstatnÃ, prosÃm, skomentujte, chystám sa to poslaÅ¥ do GNOME-i18n
>
>
> Peťo
>
> Martin Babik wrote / napÃsal(a):
> > (toto je resend, kedze si nie som isty ci predosli post presiel,
> ak ano
> > tak sorry za SPAM ;-) )
> >
> > ZdravÃm vÅ¡etkých,
> >
> > ako ÄalÅ¡Ã nováÄik sa hlásim k pomoci s prekladmi.
> > Potreboval by som niekoho kto mi v skratke pomôže so zaÄiatkom resp.
> > odkáže na potrebné docu.
> > Mám skúsenosti s prekladom aplikácià a textov do embedded zariadenà v
> > oblasti meracej a regulaÄnej techniky a jej vizualizácie, Äo vÅ¡ak
> > neznamená, že musÃm prekladaÅ¥ práve v tejto oblasti.
> >
> > TeÅ¡Ãm sa na spoluprácu
> >
> > Martin
> >
> >
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > sk-i18n mailing list
> > sk-i18n na lists.linux.sk <mailto:sk-i18n na lists.linux.sk>
> > https://lists.linux.sk/mailman/listinfo/sk-i18n
> <https://lists.linux.sk/mailman/listinfo/sk-i18n>
>
>
> --
> Odchádzajúca správa neobsahuje vÃrusy, nepoužÃvam Windows.
> =======================
>
> Mgr. Peter Tuhársky
> Referát informatiky
> Mesto Banská Bystrica
> ÄŒSA 26
> 975 39 Banská Bystrica
>
> Tel: +421 48 4330 118
> Fax: +421 48 411 3575
>
> =======================
>
> *GNOME translation mini-HOWTO
> for the translation newbies*
>
>
>
> Peter Tuhársky <tuharsky at misbb dot sk>
> Last edited: 18.1.2008
>
>
> If You consider to improve the GNOME translation for Your language,
> first decide:
> 1, Do You want just to *report* some incorrectly translated strings?
> Then everything You need is GNOME bugzilla account
> <http://bugzilla.gnome.org/>. You fill in the translation bug just
> like any other bug (that You hopefully report too).
> 2, Do You want to *help translating* some apps? Then the following
> piece information may be useful for You.
> 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.
>
>
>
> * *Join the **gnome-i18n mailing list
> <mailto:gnome-i18n na gnome.org> *as that's the place where the
> majority of the Gnome Translation Project communication happens.
> o There is also an additional way of discussion - IRC
> channel at #i18n on irc.gnome.org <http://irc.gnome.org>
> o If You wish to participate on the documentation, GDP
> <http://www.gnome.org/gdp> has gnome-doc mailing list
> and GDP IRC channel, #docs at irc.gnome.org
> <http://irc.gnome.org>.
>
> * *Find Your local community* by the team
> <http://l10n.gnome.org/teams/> or by the language
> <http://l10n.gnome.org/languages/>.
> o *Contact Your team leader*. 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.
> o Waiting for an answer, You can of course *move to next
> steps.*
> o If the team leader didn't answer, contact some other
> team member.
> o If noone answers in reasonable time (say, two weeks),
> let the GTP heads know about that.
> o If the team for Your language dosen't exist either,
> start one
> <http://live.gnome.org/TranslationProject/StartingATeam>.
>
> * *Explore the terminology, keep translations consistent*
> o *Meet the online resources*
> + 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.
> + Among the general online resources, look at these
> links: Babelzilla glossary
> <http://www.babelzilla.org/index.php?option=com_glossary&Itemid=73>,
> <put others here>
> + 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.
> o *Follow the Microsoft terminology in reasonable way*
> + Although You may not like the Microsoft, there are
> good reasons to make the translations consistent
> with their computing terminology:
> # 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.
> # They have paid professionals, they have
> invested resources. The resulting
> terminology does have it's value, although
> it is not necessarry perfect.
> # You don't waste Your precious time and
> energy reinventing the wheel.
> # It might be "cool" somehow to create
> different terminology, however at the end it
> probably dosen't help anyone.
> # 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.
> # The professionals do.
> # 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.
> # If You really hate Microsoft, then remember:
> You fight them with their own weapons ;-)
>
> * *Choose Your software*
> o 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.
> + POedit is simple translation tool and quite good
> start point. It offers all basic functionality
> needed: authomatic spellchecking, plural
> editation,translation database etc.
> + gtranslator
> + 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.
> o Regardless of what You use, You will need *intltool*
> package.
> o First time You use Your chosen software, *set Your
> preferences*: 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 ;-)
>
> * *The translation process (technically)*
> o You don't need to be a programmer to translate GNOME
> packages. All translation is done using PO files.
> o *Download* the latest .tar.bz2 sources file of some
> package from GNOME ftp
> <http://ftp.gnome.org/pub/GNOME/sources/>.
> o Unpack.
> o In the po subdirectory, You should find Your language's
> *.po file*. That's the point of Your interest.
> o 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 *msginit* tool with the --locale
> parameter with value in this form: sk_SK.UTF-8
> + Either way, create the file xy.po (where xy is the
> code of Your language).
> + *check and possibly edit the header* 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.
> # the Project-Id-Version parameter should be
> in the form project-id version, e.q.
> gst-plugins-ugly 0.10.6
> + run *intltool-update xy* (where xy is the language
> code) in order to upgrade the file against the
> most recent english version
> + now You can start translating the file
> in Your editor of choice...
> o There are words that should NOT be translated: .desktop,
> .sound and few others. They are usually labelled by
> translation note.
> o The strings could have one of 3 possible status:
> *translated, fuzzy and untranslated*. 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.
> o 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).
>
> * *Overall suggestions*
> o *Keep Your priorities*. Look at Damned lies
> <http://l10n.gnome.org/> 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.
> o *Work in steps.* 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.
> o *First take care of fuzzy strings.* 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.
> o *There is never "too late"* in order to correct
> incorrect translations or improve the terminology. Just
> keep it consistent.
> o *Community is valuable.* 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.
> o *Translation itself is more important than menu
> shortcuts.* 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, *Don't hesitate on the
> shortcuts: translate the application first.* 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.
> o *Don't underestimate the importance of Your work.* 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.
>
>
> _______________________________________________
> sk-i18n mailing list
> sk-i18n na lists.linux.sk <mailto:sk-i18n na lists.linux.sk>
> https://lists.linux.sk/mailman/listinfo/sk-i18n
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> sk-i18n mailing list
> sk-i18n na lists.linux.sk
> https://lists.linux.sk/mailman/listinfo/sk-i18n
--
Odchádzajúca správa neobsahuje vÃrusy, nepoužÃvam Windows.
=======================
Mgr. Peter Tuhársky
Referát informatiky
Mesto Banská Bystrica
ÄŒSA 26
975 39 Banská Bystrica
Tel: +421 48 4330 118
Fax: +421 48 411 3575
=======================
------------- dal¹í èást ---------------
HTML p��loha byla odstran�na...
URL: http://lists.linux.sk/pipermail/sk-i18n/attachments/20080121/a2093926/attachment-0001.html
More information about the sk-i18n
mailing list