Menu
▾
▴
#1698 Limit for characters in translation (per segment)
Hello, my request is to add character limit per segment. OmegaT already provides character counter in the right-down corner of the program, so I can always see if my translation is longer than original text or not.
But I would like an option to globally block myself from putting a translation longer than original text.
For example if I'm translating from english and the segment is "Dog", I would like to limit my translations to 3 characters only. OmegaT shouldn't allow putting more than 3 characters for a translation.
For another segment like "Elephhant", translation should be limited to 8 characters long etc. etc.
Also if for some reason translation is already longer than original text, for example after importing PO file after translating it a little in "POEdit" program, OmegaT should warn me somehow that some translated segments are already longer than original text. It can be a warning message or segments colored to some specific color e.g. red.
Of course, such limitations should be possible to enable and disable in global settings for each file type :)
I hope that you will be able to fulfill this request.
Best Regards.
Any progress on this?
No.
Registering a request here does not mean that somebody will work on it. It is just a convenient way to make sure that requests are not lost and that volunteer developers have a readily accessible list at their disposal in the case they are looking for a feature to implement.
Hi. I couldn't wait any longer for OmegaT developers to implement this feature, so I've decided to implement it on my own. :)
I am a Python developer in my full-time job, so initially I had some troubles understanding OmegaT API and some Java nuisances as well, but it didn't stop me and I was able o create a plugin that fullfills my original request on this site
Here is the source code and the plugin download link:
https://github.com/bartlomiejduda/OmegaT-Character-Limiter-Plugin
I highly encourage OmegaT developers to include this plugin in a native OmegaT installer in one of the future public version (probably 6.1 or later) as I think it happened with some plugins in the past.
If that's not possible, then I'm allowing to use this plugin source code as a base to implement new feature in OmegaT as it was requested in my first message here (would be great to be mentioned in the changelog or something ;) )
I would be happy to provide some more info or add some fixes to the plugin if needed.
P.S. you can close this future request now.
Cheers,
Bartlomiej Duda.
Oh, I forgot, can you please add link to plugin's repository to this list?
https://omegat.org/resources
See, isn't it quite amazing what people can achieve when they decide to scratch their itch ?!? :-) Thank you so much for what you did.
Honestly, I think you're just a few steps away from integrating the plugin yourself to OmegaT. And I really encourage you to try to do so. When that is the case, I'm sure you'll have other developers (or me) suggest things here and there so that the new functonality feels "OmegaTish".
Let me also suggest you to announce the plugin to the user list.
Thank you again!
It was quite an adventure. :) My plan for near future is to use this plugin for my next localization project to test it more deeply and check if there is no more bugs. Maybe I will also add some new features.
You mean by pull request? Do I have to fork omegat repository to do this?
How can I do that?
I mean that your plugin is now just a plugin that people need to install. It might be nice to have that functionality within OmegaT. That means integrating the plugin as code in OmegaT. You may want to check the development documentation for that.
You can subscribe to th user list and send your message there. The list is hosted on SourceForge, you'll find a link to it in the "Mailing Lists" tab of this project site.