Start a new topic

Found a bug in non-translatable regexes

When I enter this:


|^[^#]+#


and reload, and start moving between segments, the segments editor (source, target), and the entire matchboard will go blank. No text in them whatsoever. The segments grid will stay visible.


All went back to normal when I deleted the regex.


Odd, isn't it? :-)


☺️

«alwayslockyourbike», may you live long and prosper, because you're a living CT user manual.

Or use Edit>Show Unicode.

Fortunately there is this WIki page with all Unicode code points:


https://en.wikipedia.org/wiki/List_of_Unicode_characters#Basic_Latin


:-)



Yep. Igor hasn't defined all common special characters (yet). 


Yesterday I found that I had to use the Unicode value for the capital omega sign:


 

|[\u2126]
|\bm[\u2126]
|\[m[\u2126]\]
|\bM[\u2126]
|\[M[\u2126]\]
|\bk[\u2126]
|\[k[\u2126]\]

 

Well, while the # character is a showstopper in a CT regex, I found that replacing it with the unicode codepoint of \u0023 has the desired effect.


So if you want to “Grab all text from the start that is not a # until you encounter a #”


enter 


|^[^\u0023]+\u0023




1 person likes this

Purpose of the regex: Grab all text from the start that is not a # until you encounter a #


Regex may do nothing or do too much if you get it wrong, but it should not switch off parts of the interface :-)

Anyway, one should be extremely careful with regexes, since they can make CT go bananas.
What’s the purpose of this regex?
Login to post a comment