Hmm, I did a bit of reading (in particular, this: https://multifarious.filkin.com/2015/01/01/autosuggest/), and think this can/should be done via the Regex AutoSuggest app. But how?

Drat. I tried:

\(\d\)

And was wondering why nothing was happening. This is a shame, as I have tons of these patterns in the texts I regularly do:

(1), (2), (3), etc.

(A), (B), (C), etc.

(a), (b), (c), etc.

(6d), (8f), (99j), etc.

etc.

Incidentally, I wonder why just adding them all to my TB manually doesn't work. I tried adding the following term pairs, e.g.:

nl = en
(1) = (1)
(2) = (2)
etc. 

Hi both,

The problem is that the brackets are special characters and autosuggest doesn't like this at all.  I don't think it's a problem with the app either, I think it's a more fundamental problem with autosuggest.

Maybe one workaround would be to use the SDLXLIFF Tookit and first do a source search and replace across all the files in your project, maybe something like this:

Then use the regex autosuggest provider as you work like this:

So look for the pattern you replaced instead.  Then when you're done a search & replace in the target like this:

#

And maybe also in the source so you can update your TM with a final update using the correct translations.  In fact this would be a good usecase for using a Project TM so you fill that up with the crappy xxxnrxxxx and then do the final update to the Main TM after you put all the source and target back.

Not the most elegant workaround but if you were comfortable with the texts when translating then a few search & replace operations wouldn't take very long afterwards.

Regards

Paul

Hi both,

The problem is that the brackets are special characters and autosuggest doesn't like this at all.  I don't think it's a problem with the app either, I think it's a more fundamental problem with autosuggest.

Maybe one workaround would be to use the SDLXLIFF Tookit and first do a source search and replace across all the files in your project, maybe something like this:

Then use the regex autosuggest provider as you work like this:

So look for the pattern you replaced instead.  Then when you're done a search & replace in the target like this:

#

And maybe also in the source so you can update your TM with a final update using the correct translations.  In fact this would be a good usecase for using a Project TM so you fill that up with the crappy xxxnrxxxx and then do the final update to the Main TM after you put all the source and target back.

Not the most elegant workaround but if you were comfortable with the texts when translating then a few search & replace operations wouldn't take very long afterwards.

Regards

Paul

In fact this worked doing source and target replacements at the same time:

One click to fix the final file before updating the TM and saving the target.  So perhaps a useful workaround?

Paul

Hmm. Looking at it now, I am reminded of memoQ's Regex Tagger. Couldn't we just convert all of them into tags when importing the file (and then use QuickPlace to insert them)? Is there sth like Regex Tagger in Studio?

Yes, this is another approach you could take.  Another article for you!!

Or even do it in Word first, if your documents have been written in Word?

Wow, that looks quite complicated. So how could I just quickly tag all the stuff like: (1), (2), (3), etc.?

I installed it, and can open it from Batch Tasks, but now what?

Incidentally, all my patent applications are just normal .docx files, so would it be easier to do it the other way (as per your other article)?

You need to "Use conversions" and then create rule to pick up all the tags as embedded tags.  So maybe something like this:

\(\w+\)

Probably worth scanning this article from Jesse Good who developed the plugin: