![]() ![]() In OmegaT, click on Project > Properties. po files for your language (in path/to/_translator-files/po/xx) and copy/paste it into the “source” directory inside the Project folder ( path/to/jamulus/source/) that was just created. Select the source and target file languages at the top and leave the rest at defaults. A new window will open with the project parameters. “jamulus”) and a location for it to be stored in. OmegaT is a more powerful editor, but has a slightly more complicated set up: Qt Linguist or Lokalize can also be used, but they are strongly discouraged as they do not offer the option to disable text wrapping (Lokalize does, but it still messes it up). Double-click on any one of them to open it in a new window. po files and their current translation status. Click on New > Browse and enter the path to your. For an overall view of all files and their status, go to File > Catalogs Manager. Each editor seems to have its own criterion for text wrapping, so it has been disabled by the po4a scripts running on the repository. ![]() Otherwise it will wrap all the strings at a given column and we don’t want that, as changes in text wrapping cause a flood of edits to be added to pull requests. Once downloaded and installed, to get up and going: - Go to Edit > Preferences - In the “General” tab, uncheck “Automatically compile MO file when saving” - In the “Advanced” tab, uncheck “Wrap at:”. Poedit (cross-platform): Intuitive to use, though a couple of things need to be configured before starting to translate with it for the first time.OmegaT (cross-platform): the most complete and advanced, but also somewhat more complex.This is a guide on how to use two freely available editors to translate. Enabling JavaScript may give you additional functionality on this site. ![]() This site has been designed to provide basic functionality without JS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |