2008/1/23 Aljosa Mohorovic <[EMAIL PROTECTED]>: > > this is part of translation but only "Save" part is applied, any ideas > what i did wrong or why this could happen? > this isn't the only part that doesn't work. > > Aljosa > > 519 #: contrib/admin/templates/admin/submit_line.html:4 > 520 msgid "Save as new" > 521 msgstr "Spremi kao novi unos" > 522 > 523 #: contrib/admin/templates/admin/submit_line.html:5 > 524 #, fuzzy > 525 msgid "Save and add another" > 526 msgstr "Spremi i dodaj novi unos" > 527 > 528 #: contrib/admin/templates/admin/submit_line.html:6 > 529 #, fuzzy > 530 msgid "Save and continue editing" > 531 msgstr "Spremi i nastavi uređivati" > 532 > 533 #: contrib/admin/templates/admin/submit_line.html:7 > 534 msgid "Save" > 535 msgstr "Spremi" >
As a general rule, when the .po file is processed to generate the .mo file by the msgfmt GNU gettext utility (called from Django make-messages.py) the fuzzy translations (marked by the ",fuzzy" comment in the previous line) are ignored and as a result the text shown on the UI (in this case a web page) for these liteals is the original (in this case in English (because the runtime machinery of gettext doesn't find the correspding translation on the .mo file). I'd suggest to "unfuzzify" the translation. That is, review all the file and check all the literals marked as fuzzy, make sure they are correctly translated by modifying them if necessary and delete the ", fuzzy" flag (eliminationg the complete line if it's the only flag). Then if the .po is part of the Django souce code and you are using Django from SVN submit a diff attached to a new ticket on Django Trac (http://code.djangoproject.com/simpleticket) so all users can benefit from your effort. See http://www.djangoproject.com/documentation/i18n/#how-to-create-language-files and http://www.djangoproject.com/documentation/contributing/#patch-style for instructions. (The fuzzy flag is generally aded by gettext tools to indicate an human must review it. For example: the text "Save and continue editing" is added to the Django literals catalog by the Django developers, then when the .po file for your language is updated from the master catalog using these tools they have two choices: a) if the literal is lexicographically similar in english to another already translated literal the translation is copied from it and the translation is marked as fuzzy. b) if there is no similar translated literal the translation is left empy [msgstr ""]) -- Ramiro Morales --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N?hl=en -~----------~----~----~----~------~----~------~--~---
