![]() ![]() properties (somewhat hastily put together, sorry), that would be really awesome. If any native English speakers wanted to edit the. ![]() Any further help and/or comments are very welcome. And therefore from time to time, one might need to call up Project properties and get their hands dirty with the rules.Īll the credits go to Yu Tang for cool Groovy coding and Dimitry Prihodko for the idea and hard pushing. Or there might be a rule somewhere that is simply wider than the one just added, so the desired split or merge wouldn’t actually occur. Of course, the script isn’t too universal, and if one joined two segments together and later wanted to split them, the chances are it won’t work as the added rules will clash. It will also prompt to reload the project, and that prompt was added because there might be a situation when several rules need to be added, and reloading after each of them would be a waste of time. ![]() The script will show a confirmation message with the perspective merge/split result, so it could be canceled. If a segment needs to be split, activate it, select the part that needs to become the next segment (till the very end), and run the script. So, in order to merge just run the script, and it will try to put the current and the next segments together. If anything else is selected, even in the current source, it will be ignored and the merge with the next segment will be attempted. It will try to split the segment when there’s a selection in the current source that goes from the split point up to the end of the segment (right before the segment marker). When the script is invoked, it will try to split the current segment or merge it with the next. The script works only with project-specific segmentation. properties (only English and Russian so far) can be downloaded from SF.net. And that’s what I’ve added and what I’m sharing here. There was only a minor issue that the script couldn’t be used to split segments. It wasn’t limited to any OS or dependent on other tools (so much for hard Pascal coding, Dimitry). If I understood it right, Dimitry asked Yu Tang to rework his thingy, and Yu Tang came up with a Groovy script that did all the merging using only OmegaT internals. One of the most recent attempts was Dimitry Prihodko’s Merge utility (don’t bother to download it, it won’t work as expected, just read on). There were a few attempts to address the issue, but they required a third-party utility that would edit nf. One of the complaints OmegaT gets is the impossibility to split and merge segments without editing projects’ or global segmentation rules. The updated solution to the merge and split problem is published here. UPDATE (December 2022): This post below might be interesting only for historical reasons, but even that is highly doubtful. ![]()
0 Comments
Leave a Reply. |