Pascal Zotto said:

Is there a way to define these via regex as 1 word so they get counted as 1 word? The same would go for quite long Standard names (e.g. DIN 2137-1:2018-11 or even longer ones) or badly formatted URLs and some other strings.

Just to make sure: No, it’s not an option to convert them to tags or untranslatable text as they need to be adapted (e.g. adding word joiners and no-break spaces to avoid wrapping)

Pascal Zotto 

I understood that the numbers were the problematic part – do they also change in the translation, such as  "2137-1:2018-11" in the above example?

Hi Daniel Hug,

the numbers themselves should not change (although it happened that a client mixed up numbers of a standard and I had to correct it) but I need to replace and add other characters:

e.g. (the brackets only show which char was added/replaced)

DIN 535/2137-1:2018-11 > DIN(narrow nbsp)535/(word joiner)2137(non-breaking hyphen)1:(word joiner)2018(non-breaking hyphen)11

Pascal Zotto 

It's not worth it for such a small document, but if you have this case more often, you might want to do your replacements in the source (with CleanUp Task e.g.) and then make them into tags (I hope that is possible, but should). Once you've made them into tags their content can't be altered anymore - as I am sure you know.

Daniel Hug 

Yes, I get these quite often in larger texts too but as I said several times by now: TAGs are NOT an option as I⁠ need to be able to change parts of the string AND I need them to be counted as 1 word: say DIN 535/2137-1:2018-11 = 1 word. So yes I know they can’t be altered ^^ and it would also give a wrong word count as tags are not counted during analysis.

I’m rater looking for a way to define word count as regex for DIN standards to be taken as 1 word. Even saying string between spaces is 1 word which would then still be closer to the correct word count (at least for these strings, but it would then result in problems with other strings).

But I guess this is not possible at the moment.

Pascal Zotto 

I tend to agree with you... I'd also like a feature like that in Studio.  But it's not there.  A workaround might be to use the Cleanup Tasks app - https://appstore.rws.com/Plugin/23 - or the Data Protection Suite - https://appstore.rws.com/Plugin/39 - as you could use regex with these and add the batch task in a custom project prep (if you have the Professional Version of Studio) when you create your projects.  With the Freelance it's just an additional step to run the batch task after preparing your project and then run the analysis again. 

Paul 

Yes, but the problem is that I don’t need tags of these at all (they would even be counterproductive), so I don’t see how the plugin (which I⁠ use regularly in my professional version) would help me with that problem?

Pascal Zotto 

What I meant (see above) and how I understand Paul is that you modify the DIN standard notation as needed in the source, using CleanUp Task. Then you "protect" the numerical part of the standard (e.g. "535/2137-1:2018-11") as a tag. This would result in the standard being counted as one word, and in being written the way you need it. I agree with Paul, for special use cases like yours it might be desirable to be able to define word boundaries freely, but since that is not an option at this point, this looks like a viable workaround.

Pascal Zotto 

What I meant (see above) and how I understand Paul is that you modify the DIN standard notation as needed in the source, using CleanUp Task. Then you "protect" the numerical part of the standard (e.g. "535/2137-1:2018-11") as a tag. This would result in the standard being counted as one word, and in being written the way you need it. I agree with Paul, for special use cases like yours it might be desirable to be able to define word boundaries freely, but since that is not an option at this point, this looks like a viable workaround.

Daniel Hug

I know, but you always miss the point where I explained several times already that I MUST be able to replace the hyphens and add special space characters. So tags are NOT an option at all.

Pascal Zotto 

You do this IN THE SOURCE. You MODIFY THE SOURCE to match your requirements. THEN you make it a tag. Target will have the formatting you did to the source via CleanUp Task.

Daniel Hug 

Okay, but altering source text in pre-generated xliff exports or even sdlxliff files is again a problem with most clients as they do not allow this as else the files to import back differ from their CAT tool.

I would then have to reset everything back to initial state after translation is done as else the files to import differ from their memoQ or whatever files. On the other side, I’m not sure if that will then not cause internal issues when they import their files back. In theory it should not, but I⁠ had such issues in the past where I then had to use original files and re-run them against TM another time and fill in all tags manually to get them right. Sometimes this makes me lose hours on a single project.