• State Suggested Answer
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 130 subscribers
  • Views 3853 views
  • Users 0 members are here
Options
Related

Studio 2017 Regex find command not reliably finding ":$"

Bruce Campbell

I am not sure whether anyone has previously noticed this.

I have attached a test file with five paragraphs of text that shows the problem I am currently having with a translation.

The first paragraph is "Text:".

The second paragraph is "Text: " (i.e. space after the colon).

The third paragraph is "Text: More text".

The fourth paragraph is "Text".

The fifth paragraph is "Text " (i.e. trailing space).

Studio creates the source segment "Text:" for paragraphs 1 and 2. (The trailing space does not show up in the editor unless you filter on "All content".)

Studio splits the third paragraph into two segments, "Text:" and "More text".

A regex search for ":$" only finds the first segment. It does not find the other two "Text:" segments that are showing in the editor.

A regex search for ": $" finds the second segment, even though the trailing space does not show up in the editor unless you filter on "All content". It does not find the other two "Text:" segments that are showing in the editor.

Neither ":$" nor ": $" finds the third "Text:" segment. As far as I can tell, there is no way to find the third "Text:" segment.

I am not sure whether this problem is specific to the colon character only, as a regex search for "Text$" finds both of the last two segments and a regex search for "Text $" fails, even though there is a trailing space in the last paragraph (which shows up if you filter on "All content").

Now that I know about the problem, it is just a nuisance. I can search for ":" until I find a segment that ends with a colon.

I am bringing it up in the forum because it is not clear why this is happening, and it might indicate a bigger problem somewhere in the code.

Best regards,
Bruce Campbell
ASAP Language Services5187.test.docx
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply
  • 0 in reply to Paul

    Hi Paul,

    Yes, the problem is with the Find command.

    I was using the find command because I had to merge some segments broken in half by a colon in an sdlxliff provided by a client.

    Using the Review ribbon or Advanced Display Filter would have been slower, because I would not be able to see and merge the segment following the colon until I had cancelled the filter.

    That is, I would have to apply the filter, select the next applicable segment ending in a colon, cancel the filter, merge the two segments, apply the filter again, etc. That is why I naturally gravitated to the Find command -- and was instantly confused when I failed to find the segments I knew were there...

    Sorry about the final two paragraphs that were missing from the test file. That was the second part of my test, namely checking whether the problem also occurred without the colon. I must have accidentally attached my first test file with just the first three paragraphs.

    I am sure you added the last two paragraphs properly, but just in case I have attached the correct test file here :-)

    test.docx

    Best regards,
    Bruce Campbell
    ASAP Language Services
Children
No Data