Help:Extension:Translate/Translation best practices/lt

Visada reikia daugiau vertimų negu yra vertėjų. Nors ir savanorių vertėjų darbas yra ypatingai vertingas Vikipedijos judėjime, dauguma iš jų neturi tinkamo pasiruošimo. Norint tapti geru vertėju reikia daug praktikuotis ir mes tikrai norėtume jiems padėti pasitobulinti savo darbo kokybę. Vertimai Vikimedijos puslapiuose gali turėti didelį socialinį aspektą ir vertėjai yra skatinami dirbti kartu, imdamiesi "klausk, nespėk" požiūrio. Mes taip pat skatiname vertimo administratorius būti atsakingus klausimams ir priimti naujus vertėjus.

Daugiakalbiai Vikimedijos dalyviai gali tapti gerais vertėjais tam tikromis temomis net ir be oficialaus mokymosi, tačiau norint pasiekti profesionalius standatrtus, paprastai reikia ilgametės patirties. Šį mokymąsi galima pagreitinti, jei vertėjai turės tiesioginį bei konstruktyvų grįžtamąjį ryšį per recenzijos procesą. Net ir patyrę vertėjai gali mokytis, ir visada naudinga, kad kas nors kitas patikrintų jų darbą, kad ir dėl smulkių klaidelių.

Ilga kelionė prasideda nuo pagrindų. Vertėjai turėtų sugebėti kopijuoti ir redaguoti savo kalba ir mokėti gramatiką, be to, turėtų turėti suprasti kalbą, iš kurios verčia.

For languages with few speakers, who themselves are just starting to use computers and the internet, even the way to spell words or the vocabulary itself might still be under discussion. Regardless, translators should be prepared to create something new – there are bound to be words and concepts that have not been translated into their language before.

Nuo ko pradėti
Prieš pradedant, įsitikinkite, kad galite spausdinti ir skaityti savo kalba. Gali prireikti įsidiegti papildomus šriftus ir klavišų planus į jūsų kompiuterį.

Orient yourself. You might find many reasons to translate, whether you just do it for fun, hone your skills and accumulate credit or just want to give something back to the causes you support. You should understand and adopt the core principles of translation, like translating the meaning, not word by word, but still trying to be as close as possible to the original text.

Try to join pre-existing translation communities and ask others to review your work. You will encounter non-linguistic mark-up like variables and wiki text when translating. The gist in that is to recognize what parts should be left untranslated and what is the special meaning of them.

Pranešimo dokumentacija
The plain source text is not enough to make good translations. This is more relevant in shorter texts, but it applies to all texts. With the Translate extension, along with each message, there is a place to provide context and more information for translators; such message documentation is wiki text and can contain anything from links to images. It might take a few minutes to write good documentation for a message, but that documentation will save each of the potentially hundreds of translators a minute or more and produce higher quality translations, so it's definitely worth it.

It is possible to configure an Ask question button to show up in the translation editor. This provides a low barrier and very direct way for translators to make sure they are making a good translation, instead of making a best guess translation. Of course you should make sure that someone will be on the target support page to answer the questions and update the message documentation, otherwise translators will only be discouraged.

Consistency
The translation administrators can make glossaries and link them from the group description or use them in the translation documentation descriptions. When multiple translators work together, it is crucial that they first of all recognize the terminology, and secondly that they use the same translations. When making glossaries, it is a good idea to write a short definition for each term instead of just providing translations. The definition helps translators to understand and apply them better in their translations, and is also a good exercise to improve consistency in source texts.