Almost perfect, now:
>Some improvement is underway - the longer non-translatable match (that contains the short one) should take precedence.
Thank you so much! Great improvement.
That's really great news. After this, I have only one feature wish left (it starts with an r).
> Would be nice if this could be changed.
Some improvement is underway - the longer non-translatable match (that contains the short one) should take precedence.
Exposing regular expressions in the interface is like opening the hood of the car. The user should not be bothered with them.
>The non-translatable numbers are hard-corded in CafeTran and take precedence over any regular expression that contain them.
From a user perspective: is there any valid reason for this?
>That's why you can see them listed separately when they are nested in your regular expression.
Would be nice if this could be changed. And also: that non-translatables are locked (protected) and cannot be modified in any way (manually, in the target segments pane, or via F&R, or by CafeTran Espresso 2019, via propagation).
> Purple colour matches the non-translatables, but they aren't displayed in the F4 pick list:
The non-translatable numbers are hard-corded in CafeTran and take precedence over any regular expression that contain them. That's why you can see them listed separately when they are nested in your regular expression.
The relevant files.
alwayslockyourbike
Regular expressions that are displayed in the non-translatables pane, aren't available in the F4 pick list.
Previous attempt:
|\d+\.\d+\smm doesn't work either for the F4 pick list.Of course I'm aware of the Do Not Match list, but isn't there a solution?