A few improvement you can make to your translation (to maintainer: Zlatan is starting to work on debconf translations, hence the minor comments I'm doing. They don't affect the translation quality per se)
Quoting Zlatan Todoric ([email protected]): > # SOME DESCRIPTIVE TITLE. > # Copyright (C) 2011 > # This file is distributed under the same license as the dash package. > # Zlatan Todoric <[email protected]>, 2011. > # > #, fuzzy You should probably remove the "SOME DESCRIPTIVE TITLE part in header". Better also remove the "fuzzy" marker line. For reference, here's a typical header used by the French team: # Translation of mantis debconf templates to French # Copyright (C) 2011 Debian French l10n team <[email protected]> # This file is distributed under the same license as the mantis package. # # Translator: # Christian Perrier <[email protected]>, 2011. (the translator name here seems redundant with what we have in "Last-Translator" but it indeed allows listing more than one translator > msgid "" > msgstr "" > "Project-Id-Version: PACKAGE VERSION\n" Here you can put the package name. No need to put the package version. > "Report-Msgid-Bugs-To: [email protected]\n" > "POT-Creation-Date: 2009-07-27 12:43+0000\n" > "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" Here, it is much better if you fill in the "PO-Revision-Date" with the date of the last change you made. Of course, integrated tools such as lokalize or poedit do this automagically > "Last-Translator: Zlatan Todoric <[email protected]>\n" > "Language-Team: LANGUAGE <[email protected]>\n" Here, better mention the Language team mail address. Of course, when there is noone, it can be harder. No other comment. However, a good practice you could adopt would be running the following on the file before sending it: msgmerge -c --statistics -o /dev/null sr.po It will give you stats about the number of translated, untranslated and fuzzy strings (have I explained you what "fuzzy" is?).
signature.asc
Description: Digital signature
