keropsolid.blogg.se - خطای poedit

خطای poedit update#
خطای poedit code#

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.

Add French translation (fr_FR)) that adds the translated. Open a git pull request for the plug-in repository.Ĭreate a commit titled Add translation () (e.g. The translation will be added to the plug-in. po file to the following email: khalim19 AT gmail DOT com. You can do so by submitting your translated. It would also be a great idea if you shared your translation with the rest of the world. You may want to test your translation first to make sure it works correctly, as described in the next section. Once you updated the translated string, make sure to remove the, fuzzy comment, otherwise the string will show up untranslated in the plug-in. These strings have a so-called “fuzzy” translation.Ībove each of these strings is a, fuzzy comment.

خطای poedit update#

In case the plug-in was updated, translation update is necessary if: po file in a text editor and update the translated strings. po file is preserved and has “.po.old” file extension. po file in a text editor and translate each string in the msgid field to a string in the corresponding msgstr field. If in doubt, you can consult the list of available language and country codes on the following pages:

خطای poedit code#

Ll is the language code and CC is the country code.įor example, the French language is represented as “fr_FR”. represents your language in the format ll_CC. po file is generated in the same folder as the current working directory. in Ubuntu you would type:Ĭd /export_layers/locale The command varies across Linux distributions, e.g. Make sure that the gettext package is installed in your system. If you don’t want to use Poedit, you may use the terminal on Linux (or a Unix-like environment for Windows, such as Cygwin). If you don’t correct the fuzzy strings, they will show up untranslated in the plug-in. These strings have a so-called “fuzzy” translation and have a different color than other strings. pot file were modified and thus the translated strings may no longer be up-to-date. In case the plug-in was updated, update is necessary if: po file, select “Catalog → Update from POT file…” and find the. po file or the plug-in is updated since the last translation was made, you may need to update the translation: If you spotted some translation errors in the. If you don’t do this, warning messages may pop up when saving, but they should be harmless.

If desired, go to “Catalog → Properties…” and edit the translation file properties.

Translate the strings (by filling in the “Translation” text field for each string).

pot file in the “export_layers/locale” folder.

Open Poedit, select “File → New from POT/PO file…” and select the.

To create a new translation for your language: The following steps apply if you want to use Poedit. If you want to provide translations for Export Layers, it is recommended to use a translation tool such as Poedit for easier usage.