Values in tables (comma and/or point notation) automatic converted/translated

Question

Morning, 
 We work with very large tables and it is very annoying that we have to go to a translation agency again if we need to update a value of that table. (E.g., it was in English 12.7 V and it should now be 12.6 V). Status will be: "This is not in SDL Trados, you have to go into in translation" => translation/processing cost! 
 Is there a manner in SDL to tackle this? 
 
 Like inserting a very long Excel list with the . notation and , notations? 
 Impossible to make use of variables => loosing time when creating/inputting the table 
 A setting in SDL that takes these values into account 
 
 Problem is also when writing and finishing a manual, we import translations. Then the engineers are coming and says: "In test room we saw that this value is not correct anymore, please change". We need then to update this value, reprocess the content, the value is not found, the content needs to be sent to translation agency,.... Conclusion: we pay a lot of money and loose a lot of time for just modifying a value in a table. 
 Please a step-by-step explanation and instruction if there are solutions because I'm a newbie/dummy. 
 
 Hope somebody can helps.

Paul · Answer

Jesse Victoor 
 If this is the exact example you have in mind it is fairly simple. Numbers are normally placeables by default, so if 12.7V becomes 12.6V and you run the file through the translation memory used in the first place then you'll get a 100% match and the number will be changed. For example, I have this table: 
 
 I translate it like this and save it to my translation memory: 
 
 I then change the table like this: 
 
 So all the values have changed. Now I run this straight through the original translation memory: 
 
 Even though I changed the numbers I'm now getting 100% matches and the translations are correct. I would expect an agency to want to make sure this all happened correctly, because if the measurements are more complex, or numbers are not as simple as this, then a QA check is essential to make sure they are all correct. 
 Conclusion: you pay for ensuring that everything is still correct and nothing has been missed. I guess you could ask the agency to simply run the file through the translation memory and then you take responsibility for finding any problems, and you should accept that it won't be the agencies fault if anything is wrong. There are things that can go wrong unless the examples are really as simple as this one!

Trados Studio > 1. Trados Studio

Values in tables (comma and/or point notation) automatic converted/translated