![]() \/g" > target-language-script.txtĪn even nicer extraction method without saving via poedit is the following : Thanks to the programmer(s) that included the "speaker" in the comments of the po-files (Ivanovic?)! Those are definitely helpful and make this approach possible. to read it in a bus, a train or in a car. (Checks whether there is a trailing space and the next line is empty.)įor proof-reading of a campaign it might be much easier to print it out in a more "scriptlike" format (: ) (target language only), e.g. Your "diff" will only contain your changes and will look much nicer - your language maintainer will like you even more :).Īt the end of each translated "string", spaces should be avoided. This may be done by executing the following:ĭiff -u file.po > file.po.diff Especially, it must be undone prior to "diff" the new version against the old one. ![]() ![]() Or using msgcat (part of GNU gettext), save the file with the -no-wrap switch,Īnyhow, those changes introduced by poEdit should be undone prior sending the new po-File to your language maintainer. Without saving the file with poEdit, the number of text-lines would be undefined. As result, a normal entry consists of 4 lines, where one line contains the "characters text" and a prior line the "characters name". The reason is, that then the texts are saved in separated lines without interfering /n's. Prior to use the shell scripts, the po-File needs to be opened and saved with poEdit. 9 Style scripts following the typographic style guide.6 Extracting a script with original and translated strings.To check what you have changed look for lines with a star in front of the original text. You easily can see if a translation contains a comment by the comment icon in front of the original text in the mainview. The second source for fuzzy strings are msgmerge or something similar, when mergin an old translation with an updated template (.pot) msgmerge will note updated english strings with fuzzy to notify the translator to review the translations.ĭo not leave fuzzy strings in translations considered done!įor editing/making a comment simply click on the edit button (next to fuzzy button) and insert a comment in the Window which will appear. If a string is roughly translated and needs more attention it's wise to mark it fuzzy to make it easy to find and review. The first one being yourself - or one of your peers. (hint: ctrl+up/down arrow moves between the strings)Ī translation can be marked as fuzzy, a fuzzy translation can originate from more or less two sources. Simply select the strings you want to translate by click on them and insert the translation in the empty box under the original text (look at the Image). You should see something like this (If it doesn't check Menu->View). lxde/lxmusic/po and open lxmusic.po with Poedit and open the file. This way when you want to edit an existing yourlanguage.po file. Please name it like de_DE.po/es_ES.po/zh_TW.po/. ![]() Now you have to choose the *.po file which will be generated. Now insert the wanted informations (if you want) and click OK. lxde/lxmusic/po and open lxmusic.pot with Poedit and open the file. Click on File->New catalog from POT file, navigate to. This way when there is no yourlanguage.po file. In this example we are going to translate LXMusic (Just change the path for another Program). Of course we need Poedit, so just install it (as root).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |