A handy way to easily view and distinguish between translated and untranslated segments is to click on View > Mark Translated Segments and View > Display Source Segments. To jump to a specific file, click on Project > Project Files and click on any of them.īy default, the view of the source and target segments may be all in black text on a white background with no highlighting. Look at the second column, “Remaining Segments”, to see how many segments remain to be translated for each file. Click on Tools > Statistics and a window will open with all the stats for the. OmegaT can give you an overview of the current state of translation of all files so you don’t have to go through each one checking what needs to be done. In Options > Editor, enable “Allow translation to be equal to source”. po files from: path/to/_translator-files/po/. At the bottom, for “Translated Files Folder”, set it to the directory where you copied the. Go down and under “File Locations” make sure the “Source Files Folder” points to where you copied your. Under “Options”, disable “Enable Sentence-level Segmenting”. The same “Edit Project” window will open again. 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:”.
0 Comments
Leave a Reply. |