Issue with empty target values and the regex-filter

[Martin Brocksch]

Hello,

I use okapi-apps_win32-x86_64_0.36. I have the following problem with my software localization workflow in Rainbow:

I have stored several strings with their translations into several languages in a TAB-seperated text-file. The task is to combine two versions of this text-file using the ID-based Aligner in Rainbow. One version is an older text file which is the result of a translation process (create translation kit, merge translation kit). The second version is a newer text file which potentially includes additional strings with an empty translation in the target language. The text files are converted to filter events using the regex-filter producing a bilingual input with IDs. The filter events are processed with the id-based aligner and converted to raw documents again.

Now the problem occurs, that the regex-filter fills empty target values with the source text in the output file. This is undesired and produces an output file which is not usable in my software project.

Before using the regex-filter I tried the Table filter. However I cannot use it because of the following issue: https://bitbucket.org/okapiframework/okapi/issues/642/tablefilter-empty-target-columns-are In this case the translated target values are not taken over at all.

Can you add an option to the regex-filter to not fill empty target values with the source text? Or is there something else I can do to change this behaviour?

You can find my Rainbow project file, the filters and the input and output files in the attachment.

Regards Martin Brocksch

[YvesS]

Allowing empty target on the output of the RegEx filter would be possible as an option (off by default), but we would need to change a current limitation that allows empty targets only for multilingual files (e.g. TMX, TS, etc.). I'm not completely sure why there is that limitation. I'll do some research and follow up.

[YvesS]

See also: https://groups.google.com/forum/#!topic/okapi-devel/peNkn2DNQxo

[Martin Brocksch]

Thank you for the quick response. I'm looking forward to any news on this issue.

[Martin Brocksch]

I have seen on your development list, that the change will not make it into version M37. Do you already know a rough time frame when you will find the time to implement the change? I assume I can already build a development version myself as soon as you commit the change into your CVS? Is there already a release date scheduled for version M38? I really would like to use your tool in our development process, so this is the reason why I'm bugging you with my questions.

[YvesS]

Unfortunately I do not have a time frame: I will try to get the change done for M38. I have had no time to look at it since a while but my recollection is that it was close to be done, the only obstacle was that filter we since decided to drop support for. -ys