Under Community Review

default value for tag definition

Hi,

it would be nice if the default behaviour for tags would be "Must be inside of segment" instead of whatever it is now. The problem is that many PMs and clients don't know what they are doing when defining file type definitions or defining tags in TM settings and thus many tags that should be shown by default are hidden just because they are at the beginning or end of a segment respectively. The second issue it that most translators again don't know they can make these tags visible and copy them where needed via "All contents" filter.

The next issue with wrongly defined tags is that if they get copied into the segment by those translators who know how to handle them, then QA tool runs berzerk by flagging additional tags. So in fact it's producing FPs .

So with the new default value there would be less issues and those PMs and clients who know how to correctly flag tags then defining them can still do so if they need to hide them.

Br,

Pascal

Pascal Zotto
  • in reply to Paul

    maybe it depends on the source and target languages, but unfortunately I encounter this issue quite often. 3 to 4 times a week. :( Or maybe add an option to Trados Editor to automatically put tags into the respective segment via a checkbox option in settings. If ticked, the translator sees tags in the segments (those flagged can be outside of segment) and they then do also not create FPs during QA.

  • I wouldn't agree with this being the default behaviour.  I think it's an exception rather than the norm that these external tags need to be brought into the segment and making this default would not only add work for all translators whenever they come across a bold sentence (for example) but it would also affect leverage from existing TMs and would cause considerable disruption.

    I agree we should have an option to always be able to control the behaviour of potential external tags, but the default should be as it is today.