extractIsolatedStrings.b=falseextractAllPairs.b=trueuseKeyAsName.b=trueuseFullKeyPath.b=true<filter className="net.sf.okapi.lib.omegat.JSONFilter" enabled="true"> <files sourceFilenameMask="*.json" targetFilenamePattern="${filename}"/> <option name="includeTUName" value="yes"/> <option name="useCustom" value="C:\_mesProgs\OmegaT\plugins\okf_...@myself.fprm"/> <option name="useDefault" value="no"/> </filter>Actually a group of people including me once tried to write a Filter Step as a generic solution over years. But it turned out such Step is much more difficult than we thought. It was so easy to break the complex file formats like .docx, .xlsx etc.The activity stopped here.
https://bitbucket.org/okapiframework/okapi/pull-requests/300/subfiltering-step/diff
Kuro
It's a pitty, that it stopped, but I understand, that it is complex.
Perhaps for most use cases it would be sufficient to be able to protect patterns within segments with regex in general, like it is already possible for some file formats.x
However I understand, that someone needs to have the possibility and motivation to put enough time and/or money in this.x
best
Marc
--
You received this message because you are subscribed to the Google Groups "okapi-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-users/4b9c9d91-d76d-49ee-bf55-b92ed0e4719fn%40googlegroups.com.