Hi everybody, as the title says, I need to find and replace many simple hyphens with non-breaking hyphens in Trados 2015.
If I simply copy and paste a non-breaking hyphen tag in the search and replace window, trados converts it (very smartly) in a normal hyphen.
Could you please inform me if there is a solution to this problem?
Thank you very much,
Bruno
Hi Bruno,
It's a little tricky as non-breaking hyphens in Studio are usually inserted with a tag from the quick insert toolbar. But you can do a search and replace if you first insert the tag, like this:
Then copy paste the tag into the search and replace... it will look like this:
So very difficult to see any difference. But when you search/replace the target will now all have non-breaking hyphens. At least it worked for me and my target file did not break at the hyphens anymore.
Regards
Paul
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Paul,
I've tried this, but isn't there any way to do this in a way that will show those as tags in the target segment as well? I am expecting my proofreader to correct all these instances (literally hundreds of them) and mark them as an error...
MTIA,
Erik
for SDL Trados Studio version 2017, it is still there "Home > QuickInsert > 3rd small Icon"
and
if you want change "this" into "that" (vice versa) is a kind of simple job even for several hundreds of them.
regards
Why is it necessary for these to be a tag? Can't they be search/replaced across the entire file in one or two goes? Probably I'm missing some context from your question which would help me to provide you with a sensible answer.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Thanks for your quick reply!
They don't need to be a tag per se, but they are when I insert them via QuickInsert (and also when they come from the TM). They need to be recognizable as non-breaking. With the method you propose, they are indistinguishable from regular hyphens, which is why the proofreader will mark them as errors.
I haven't tested yet... but couldn't you create a QA check to find them? Then if any were missed from a global search & replace it would be trivial to spot them as the QA check would flag them.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Even if I could do this, I can't tell the proofreader how to do their work. Shouldn't non-breaking and regular hyphens be clearly distinguishable? How is my proofreader (who is working on the SDLXLIFF) supposed to know whether I've used a regular or a non-breaking hyphen in any given case?
That's a good point of course. How do you tell in Microsoft Word?
The answer I think, is you can't. This is probably why Studio uses a tag for this. I think your best bet is to use a QA check and report on normal hypens in the scenario you need them and then Studio will flag them so the proofreader can make the correction:
Do you have an example of the scenario you're dealing with?
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
for version 2017 SDL Trados Studio
It has problem with ;
Unicode Character 'NON-BREAKING HYPHEN' (U+2011)
Unicode Character 'HYPHEN' (U+2010).
It is just blind to it.
I have tried both of them, but it changed into plain "Minus(U+002D)" at final docx file
Of course, I am testing it. I am far from professionals.
test with your fingers using attaced docx file3 Hyphens.zip
In Word, regular and non-breaking hyphens do look different when you toggle the "Show/Hide" function (i.e. they differ in Show mode, they're the same in Hide mode).
By "example of the scenario", do you mean an SDLXLIFF file?
Translate
