Marc Prior
What's happening?
-
Comment: Show non-breakable space
LibreOffice uses the greyed space. Not to talk down the new feature, which I find very useful, but all it does is to apply grey highlighting to the non-breaking space character to distinguish it from the normal space character. The non-breaking space character as such has always been a "function" in OmegaT. It's a unicode character and the non-breaking function is applied by the...
2012-04-28 06:05:16 PDT in OmegaT - multipla...
-
Comment: Google Translate API v2 for KO-EN no MT output
I think we can assume that that isn't Jun's actual API key. ;-) Jun, create a new script and just copy and past your working command-line command into it, then launch the new script. That should work. Or are you launching the script in some way that it doesn't have the same rights as the command line (e.g. from a different user account)? If you don't want to put your API key into a script...
2012-03-24 00:43:31 PDT in OmegaT - multipla...
-
Comment: Optional to highlight spaces next to tags
> The thing that caused me to submit this RFE was when I realised that the "insert tags" function in OmegaT adds spaces between tags even if there are none in the source text. This means that the translator has to delete the spaces manually I have noticed that too, and agree with your conclusions. But wouldn't it be simpler (theoretically), with regard to this particular issue...
2012-03-15 13:06:27 PDT in OmegaT - multipla...
-
Comment: Optional to highlight spaces next to tags
My specific issue is that if I have something like: After 15 m<f1>2</f1>there is a space missing. I am more likely to spot it if I can see: After 15 m2there is a space missing. And by the same token, if I have: After 15 m<f1>2 </f1> there is a space too many. I am more likely to spot it if I can see: After 15 m2 there is a space too many. >...
2012-03-15 10:57:13 PDT in OmegaT - multipla...
-
Comment: Optional to highlight spaces next to tags
This is indeed a problem. I have already suggested (not as an RFE) a different solution: a feature to hide tags, to make reading through second and subsequent drafts much easier. This would be a read-only mode; in order to make any changes, the translator would have to switch back to tags unhidden mode.
2012-03-12 04:42:53 PDT in OmegaT - multipla...
-
Comment: Ability to mark segments as provisional
I would like a similar feature, but for different reasons. When working on second and subsequent drafts of a translation, it is useful to be able to distinguish between segments that have been processed in the draft concerned, and those that have not. This is easy during the first draft, since the status is translated vs. untranslated. Effectively, I would like a function a) to flag an...
2012-03-12 04:40:09 PDT in OmegaT - multipla...
-
Comment: Go to: next unique segment
I don't think it's even documented in the user manual yet, is it? It's logical, but arguably not very intuitive. Marc.
2012-01-31 07:09:51 PST in OmegaT - multipla...
-
Comment: Go to: next unique segment
To add to Didier's good advice: There's a shortcut for "Go to next untranslated segment" - you don't have to go through the Go To > Next Untranslated Segment menu items repeatedly. The filter function in the Find menu is very powerful and worth exploring. An advantage in this context over simply iterating to the next untranslated segment is that it can be used in the second...
2012-01-31 05:59:02 PST in OmegaT - multipla...
-
Comment: Export TMX for particular document
Make a copy the file for which you want a TMX file. (You don't have to delete anything.) Put it in a folder somewhere. Then in Project > Properties, change the Source Files folder to that folder. F5 to reload the project and Ctrl+D to create the target documents again. The three output TMX files (level1.tmx, level2.tmx and omegat.tmx) will now contain only the segments contained in the...
2011-12-10 05:41:52 PST in OmegaT - multipla...