In your case the complete paragraph has a bolded style assingned. A CAT tool is not for changing this. In this very special case the simplest way to cope would not bother with formatting in Studio, then create the target document and replace all parenthesis parts with certain style by the same content, but formatted wit a non-bold style. As you say, you are a programmer, so it should be next to no deal for you. And would take you seconds.

As for not being educated I beg to disagree. As a translator you must know ho formatting works, why styles are there and where the limits are. This is what I expect from translators (and obviously from myself too). So the mirror tells me, that I would solve this problem without having to write so many postings here.

I think you are just not interested in understanding. I know all the things you said... When I make something bold and then continue like this, trados starts becoming too religious. It is nothing less than stupid if all other software options named "CAT tools" are able to tackle this with a second ctrl +b for a second time. I paid for this and I deserve to have properly working cat tools. This is not the only problem Trados has. I use it because I am used to it. Otherwise the termbase is not working/tooooo slow/gets errors all the time. In the past, there were many many errors and these were corrected not because of people like you but because of people like me who reasonably criticize and give advanced suggestions... Don't cross the line by accusing others while you are just annoying reasonable people with great feedbacks... 

Indeed, memoQ would let me unbold text in a paragraph with a style defined as bold. However, this means a change in document formatting, which has not been intended by the layouter and in my opinion this is simply wrong. In cases I get documents for layouting and people do not use the styles from the source, I return the document and request the formatting to be corrected by the translator, as this is not my task.

In your very case the easiest way to work would be to change the formatting afterwards in target (a quite simple operation) or use another tool.

And before you criticize me for not being reasonable, take a little time to learn more about me. You simply assume something, what comes handy to you, just because I do not share your point of view.

You say, "use another tool" now, ok, since you let me have the "other cat tools actually are capable of doing this extremely simple thing", we can stop talking now. 

You still talk. Loooooong. I am giving a constructive feedback for the developers to read and implement in the next update. Why would I have to spend another 20-30 minutes just to implement bolds into a target file outside trados when this is a technology (not witchcraft, happy that you agree to this much) that other CAT TOOOLS (yes it appears I know what a "cat tool" is, thank you for giving me that also) just get it done simply with no "tag bla bla" fuss by making an automation in the tag management and therefore places the tags that I would have to place in the previous example automatically. But this is not aimed at you since I lost hope that you would be able to understand. You still insist on using stones to start a fire, you can, but stop pushing that conviction of yours to my nostrils. There are better ways. Goodbye. 

halit yilmaz

halit yilmaz said:

This helps, but seriously, ctrl B= make it bold, again ctrly B= make it not bold. Is this too hard to implement... Bold is older than tags... 

The point is that for CAT tools a tag is a tag is a tag.  This is not a word processor.  So yes, I'm sure a developer could do this but why?  Just so you can work with it for the bold tag only when using Studio?

I think it's just as easy to learn this process for all tags, and it doesn't matter what kind they are:

Insert tags:

Ctrl+, or if you are introducing tags into the target that were not in the source and if the filetype supports it Ctrl+B, Ctrl+I, CTRL+U etc. 

Turn off the tags:

Ctrl+. (Ctrl+dot)

I truly would not want a developer to waste time trying to do this for recognised filetypes only so that users who only ever work with Word files feel more comfortable.  

Knowing that almost 80% of content localization come in word form, and anything that has a bolding content in it is shown as that instead of merely just with tags, a sensible developer would "SPEND" time for what makes sense for most regular translators. More complex content come in other platforms anyways, not Trados, usually, to me. Anyways. Thank you for the secondary solution.

Showing bold as bold is a bad idea. As described above, in most cases another font will be used. The software has not to show WYSIWYG, but to tell me exactly what kind of formatting is being used there. Otherwise I produce crap translation and the layouter will be quite angry with that. The translation world is not only localization. And Studio is not a specialized localization tool.

Again, I am not working on a complicated file. It is a word file with numerous bold sections like this. So my suggestion would be much better. If there would be another font, then, the tag comes into play. 

Your Word file contains segments with a bold style applied. So the author of this text did not intend using not bold in that paragraphs. For me this is all. If the author of the text would have intended using not bold in these paragraphs, the way these are formatted should have been different.

Yeah, so, I created this file from a pdf that has bolds in it, making the company names bold etc. mimicking the PDF scans. And I definitely intended it to just become bold. Not some rocket science equivalent of tag alternative.