Tags that are at the beginning and end of a segment are by default usually hidden. This behavior is controlled by the filters, although how it is done in a given filter is different depending on the file type. For Java Resources files like yours you'd need to go to the Embedded Content section of that filter and create some tag definition rules. They will need to be regular expressions that will catch your placeholders. For example \{\w\} would catch your example above, although make sure that using that will only catch what you want it to catch and nothing else. When creating the content rule there is an advanced button that when clicked gives some additional options. The one you want to focus on for your desired behavior is the segmentation hint. This option defines what WS or Studio should do with the tag when it's found at the beginning or the end of a segment. The one you likely want is the Include with Text option.

This link should provide some more detailed help if you need it.

Thank you for your reply Eric. I activated the option Include with Text and here is what I get in the Editor view of Studio:

My problem now is that the tags in question are not placeholders anymore and I'm afraid they appear as an individual word. So, for big projects containing a lot of strings with many tags like these ones, the total wordcount will be huge, right?

Thank you for your reply Eric. I activated the option Include with Text and here is what I get in the Editor view of Studio:

My problem now is that the tags in question are not placeholders anymore and I'm afraid they appear as an individual word. So, for big projects containing a lot of strings with many tags like these ones, the total wordcount will be huge, right?

Hi,

Try setting the filter to All content instead of the default All segments in your original file (which had the tags as tags, and not text). This might display the tags between the segments, so to speak.

Hi Daniel,

Thank you for the tip. It works in my Editor view:

And also in Browser Workbench:

It might help but I'm afraid this solution might also be confusing.

How do we do if the location of these tags need to be changed in the target language (I mean the order of words/tags/placeholders is different from one language to another)? The target file would contain errors and strings with duplicate tags...

Do you have any other workaround?