po editor to remove the most obvious wrong suggestions. This removes all the non-fuzzy strings, and then removes the "fuzzy" tag from all the remaining strings. Run the command msgattrib with the parameter -fuzzy.This will result in a translation file for the new version, with all matching and almost-matching strings from the old version. Run the command msgmerge on the two files.See Downloading and importing translation files for details. Export a template file for the new version, and a translation file for the old version(s).
خطای poedit how to#
Here's how to make such a file and import it into the localization server: However, since the old translations are not exact translations of the new text, the best thing to do is to mark them as "fuzzy". For these strings, it's useful to have the translations for the old strings available for reuse. When there's a new version of a module or core, some of the source strings will have minor changes from the previous version, such as corrections of grammar and typos. Msguniq -u -no-location -strict with_duplicates.po > clean_file_for_import.po Finding "fuzzy" translations Here is a command that will remove duplicate strings from a PO file: Msgattrib -s -no-location -translated huge.po > clean_file_for_import.po Removing duplicates Here is a command that will remove the untranslated strings from a PO file (suggested to run before importing it): If you have a number of PO files in a single directory, you can open up a command window, change to that directory, and run the following command to make them into one big file called nl.po (change the file name to your language):įor %f in (*.po) do type "%f" > module.po Removing untranslated strings
خطای poedit windows#
name "*.nl.po"` > nl.po Combining files on Windows command line If msgcat does not work for some reason, you can try a command like this to combine all PO files in subdirectories (for instance, starting at the root of your Drupal installation):Ĭat `find. You will need to make appropriate changes for your situation. This command assumes that the main file you have is called general.po (its headers will be used for the output), and that your output language is Dutch, so that the final file should be called nl.po. $ msgcat -use-first general.po *.po | msgattrib -no-fuzzy -o nl.po If you have a number of PO files in a single directory with different strings in them, and you have the gettext project installed on your computer, you can run a command similar to this in the directory to make one big file:
خطای poedit software#
Most PO file editing software supports merging.There are several ways to merge translations: Merging is the process of taking your existing translations and merging in new translations for the same strings from a new file, without losing your original translations. Most of the commands will run only on MacOS/Linux command lines, and require the gettext package to be installed. Here are some commands that can be used to combine several PO translation files into one larger file, merge in translations from another source, and other operations.
0 kommentar(er)
