Studio 2021 RegEx file type - Inline tags: "Advanced"-Option missing

Jens Olaf Koch

I don't think this is a bug at all.  What kind of rule is that supposed to be?  Use something meaningful and it'll probably activate.

I have the same effect on all working production placeholders and tag pairs. I tried to deinstall plugins, I tried English as UI language, all to no avail. I haven't seen the dialog since installing 2021 ...

Hi Paul, I guess you mean these settings:

Jens Olaf Koch

Yes... but I meant your actual settings so I can see whether the problem is the settings or something local to you.  Click here:

Then export your filetype settings for this filetype.  You can zip them and attach them to the thread.

asciidoc.zip

Thanks Jens Olaf Koch Jerzy Czopik

I actually managed to repro this on my own machine... not sure how.  So I searched the bug database and did manage to find a bug for this.  It's logged under our reference CRQ-21027 and has apparently been resolved.  So it should be in the next update.

I can't find a workaround for this but the next update should not be too far away.

Thank you very much

Many thanks, Paul!

Hi Paul, the Advanced settings are back in the newest update, fine!

But there is one thing I still wonder (not directly related, but also in my very same Asciidoc context as described earlier in this thread):

If I set a colour for a tag pair and mark it as "not translatable" (sorry, can only see the German phrasing) the colour is not applied whereas other attributes like bold or italic are. It's not consistent this way and I don't see why colour shouldn't be applied regardless of the setting re the translation of the tag content.

I also wonder why some changes to the style attributes (like superscript) are shown in the preview but not in the editor view (when converting anew from asciidoc top sdlxliff when opening the file min the editor). Maybe there are still some inconsistencies in this area?

Maybe I'm missing something here?

Jens Olaf Koch

I don't have a sample file from you, only your settings file.  So created a new one and it works for me:

Send me your sample file for translation and I'll take a look at the settings file you provided before... or you send me an updated one?

Jens Olaf Koch

Maybe it's your editor settings ?

Thanks for testing! :-)

Just to be sure: Your test tag is a pair with content that should be _excluded_ from translation?

Just checked: Same setting re. formatting display style as in your screenshot!

Jens Olaf Koch

Apologies... I read it too quickly:

I think the reason is that the colour is greyed when it's non-translatable.  So you can see bold, italic, font-size for example... but the colour is always greyed.  This isn't a bug... this is by design.  If yo think non-translatables should still retain a colour based on your setting then please log an enhancement request:

http://ideas.sdl.com

Thanks again!

Well, I guessed that would be the reasoning ... 

I really think that colour should be applied here as well so thanks for the link! 

I have to check segments with just tags to see of all tags are part of the target segments and it is must easier to find them (even when only looking at segments with tags using the filter).

BTW: If you use the advanced filter to filter by colour, you can filter the non-translatable text by colour even if the colour is not showing. Is that by design also or more of a bug - I'm not sure

I think that if colours are omitted by design the option to change it (and font and font size as well) should be grayed out when the non-translatable option is set and they should.

Both behaviours are at least confusing. (They were at least for me. :-) )

Jens Olaf Koch

Jens Olaf Koch said:

BTW: If you use the advanced filter to filter by colour, you can filter the non-translatable text by colour even if the colour is not showing. Is that by design also or more of a bug - I'm not sure

By design.  Studio doesn't see the colour like we do... it just sees this:

Jens Olaf Koch said:

I think that if colours are omitted by design the option to change it (and font and font size as well) should be grayed out when the non-translatable option is set and they should.

Both behaviours are at least confusing. (They were at least for me. :-) )

You should note this in the idea when you create it.

I just created an enhancement request though I think it would be good to think things through from the user/translator perspective rather than from the program perspective. Important is what we users see, not what Trados see. :-)

Common senses would say: There is a tag pair, you can give its content colour, but it is not reflected in the program: In my own programs that would be something that I would treat as a bug, not a designed feature ... :-) It's clearly not the biggest issue...

... but I believe that one of the problems Trados often has is that such a incredibly useful and powerful program has too much areas that often feel a bit sloppy and designed with a bit of complicatedness or instability.

(Alignment is one of the areas which come to my mind and where I had lots of absolutely cryptic and unhelpful error messages and crashes lately. But that's clearly off-topic here :-). Just remembering ... )

I just created an enhancement request though I think it would be good to think things through from the user/translator perspective rather than from the program perspective. Important is what we users see, not what Trados see. :-)

Common senses would say: There is a tag pair, you can give its content colour, but it is not reflected in the program: In my own programs that would be something that I would treat as a bug, not a designed feature ... :-) It's clearly not the biggest issue...

... but I believe that one of the problems Trados often has is that such a incredibly useful and powerful program has too much areas that often feel a bit sloppy and designed with a bit of complicatedness or instability.

(Alignment is one of the areas which come to my mind and where I had lots of absolutely cryptic and unhelpful error messages and crashes lately. But that's clearly off-topic here :-). Just remembering ... )