Usually the result is that when a tag appers in a position where there should be a split, the regular expressions do not match anymore and the split does not occur. OmegaT did not take care of these values right now: it considered tags as part of the text. In SRX header you have the possibility to define how to deal with formatting tags which would appear in a position of a split: you can chose whenever you want to have these tags in the segment before or after the split. We already provide our specific segmentation rules in this format, but since this is experimental, it is not yet used by default.Īgain all of this should be seen as a proposal : feel free to comment these rules and propose alternative ones, if you want. This format is not a standard but it has a specification, also available in XML Schema, and it is easy to convert to SRX (the contrary would be more difficult): in the current implementation, if you use this format, change made via Segmentation Rules window will imply conversion to SRX, because this window looses CSC-specific features - the only case where OmegaT writes CSC is if you are using the popup menus. The application will first check for segmentation.cscx, eventually with -2srx or -2conf for auto-conversion, exactly as done for SRX. This format enables to create template for redundant rules such as long lists of abreviations. The GitHub pull request is pending since then.ĮXPERIMENTAL a limited, read-only support is implemented (in test/3.4 and dev/3.5 only) for Culter Segmentation Compatible Format (CSCX). In 2018 the core OmegaT team asked us for a port to OmegaT, but with different rules. In any case SRX has priority over CONF format. The same rule is applied for the contents of common config directory as well as for project-specific segmentation. If segmentation-2conf.srx exists, on first load DGT-OmegaT will convert it to nf, then continue.If nf exists, on first load DGT-OmegaT will convert it to segmentation.srx, then continue.If nf exists, use it (but SRX has priority).What is implemented in OmegaT 3.0 update 9 is the following rule: ![]() The two formats seem semantically equivalent, however we are not absolutely sure, that is the reason why we searched for a solution which also preserves compatibility and also easiness to convert between the two formats. Then we found that there was already an old RFE asking whenever it would be possible to use SRX format instead of specific one. Users have more luck resorting to friendlier apps for executing professional translations between multiple languages.After discussion about RFE 1348, it appeared not clear to us why OmegaT uses two different formats for segmentation rules: the main rules, present in the JAR file, are in SRX format while the user-defined rules use an XML but OmegaT-specific format. On the other hand, its interface and options are not intuitive at all, making it quite difficult to work with. It has a good response time and did not hang, crash or pop up error messages in our testing. OmegaT is low-demanding when it comes to CPU and RAM, so it does not hog system resources. Microsoft, Google), change the font, view and edit file filters, enable an automatic spellchecker, use proxies if necessary, as well as to modify the default name/ID that marks your team name for translations. Modify program optionsĪs far as app settings are concerned, you can select the translation service (e.g. It is possible to create glossary entries by adding comments, source and target terms, build alternative translations, insert or replace words with matches, change the text case, insert source tags, jump to specific segments, validate tags, and more. Source files can be easily imported from the disk, while URLs can be added from MediaWiki webpages. glossary, dictionary, translation memory). To create a new project it is necessary to specify the saving directory (an empty one) and configure settings pertaining to the languages of the source and translated files, sentence-level segmenting, tags removal, and file locations (e.g. The GUI consists of a seemingly outdated window that shows instructions on how to get started, divided into multiple panes like instant start, fuzzy matches and glossary. Another possibility is to save OmegaT to a USB flash disk or similar storage unit, in order to run it on any PC easily. You can drop the app directory in any location on the hard disk and just click the JAR file to run. Installation is not necessary, as long as Java is installed on the computer. It integrates numerous options that might take a while to figure out. OmegaT is a free and open-source Java-based application that aims to help professional users translate documents fast and easy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |