The story

We are making some changes in our UI, streamlining it more. Before we could have localized strings like "Name:", but now we only want to store "Name" (as we have both versions in our database).

The longer story

Translators doesn't like to translate the same thing twice - sometimes they will actually translate "the same string" (only with/without colon in the end) to two different things (and that would be okay if it there where different context comments, but there isn't). So we ask them "why it's different?" and they respond "why do we translate it twice?".

Merging feature to merge "Name:" and "Name" already requested.

My process

When I change "Name:" into "Name" I want to do it through the tool. I know my product, so I know I want to change "Name:" into "Name" everywhere and the easiest way to do so, is by editing the "Original Text" through the tool, forcing a popup that will allow me to apply the change everywhere the string is used (by the way: very nice feature!).

Now I want to give my translators a new file with changes (new strings and changed strings) - but when I changed the Original text, it marked my Original string as "edited", but all other languages status isn't changed. I would expect all other languages (and not Original Text) to somehow be marked as "edited".

We don't have the same team translate to all languages - so what will happen when I import Danish and afterwards export French? Will it reset Original Text's status when Danish is imported and then ignore the string when French is exported?

All about the process - am I seeing this wrong?

The process isn't clear to me. On one hand, I want to mark the change so I can export the edited strings - but I also want the status to "reset" at some point so I don't send the same string to my translators without changes until all languages has been reviewed and I've manually reset the Original Text status. If "Original Text" behaved a little different from all other "languages", it might change the status of all the other languages instead of changing the status of "Original Text". I consider "Original Text" as my master, and all other languages should "obey".

Sorry...

Sorry about the long description/request - It's not 100% clear to me how it works today - I just know it isn't behaving as I expect, and that's why I try to write all the details of how I experience the tool vs what I expect from the tool. I hope my process description makes sense and it helps clarify my request.

More examples where this applies in our solution:
"Name:" => "Name"
"NAME" => "Name"
"First name" => "First Name"
"Customer Name" => "Name" (tricky, but applies in rare scenarios in our solution)