With straightforward replacements, you can use literal strings. The first step is figuring out what to search for and what to replace it with. Especially because you can create a list of regular replacements that you will apply across projects, saving the time that it normally takes to do this manually. Automatic replacement requires exercising caution, of course, but the ability itself is terrific. Yet it does allow you to run multiple replacements, fully unmanned. Unfortunately, just like most other scripts in OmegaT, it is not as straightforward as searching and replacing through a window like in Microsoft Word. OmegaT does not have a built-in search and replace functionality yet-a frequent valid reason for criticism-but you can use this script as a workaround.
We definitely needed a better way to deal with this in the future, and one of the Kos’s scripts provided the solution. We spent several hours fixing this problem, and this was for unpaid 100% matches. This resulted in multiple cases of lines ending with a number, while the next word, such as a measurement unit, ended up on the next line.
In the course of post-DTP review, we noticed that the 100% matches we had not touched did not have non-breaking spaces after numbers. This job included DTP and post-DTP review.
#HOW TO SEARCH NON BREAKING SPACE WORD FULL#
We had a job recently that in addition to new text, had some 40,000 full (100%) matches that we agreed with the client not to review. Recently, I wrote about how Kos Ivantsov’s scripts help make better use of OmegaT.
0 kommentar(er)
