Thanks for this. I am afraid there is nothing we can do about it right now, but I will keep it in the pipeline and see what we can do about it in the long run.

Thanks for this. I am afraid there is nothing we can do about it right now, but I will keep it in the pipeline and see what we can do about it in the long run.

Thanks for this. I am afraid there is nothing we can do about it right now, but I will keep it in the pipeline and see what we can do about it in the long run.

Thanks for this. I am afraid there is nothing we can do about it right now, but I will keep it in the pipeline and see what we can do about it in the long run.

Thanks for this. I am afraid there is nothing we can do about it right now, but I will keep it in the pipeline and see what we can do about it in the long run.

Thanks for this. I am afraid there is nothing we can do about it right now, but I will keep it in the pipeline and see what we can do about it in the long run.

Thanks for this. I am afraid there is nothing we can do about it right now, but I will keep it in the pipeline and see what we can do about it in the long run.

Good catch, this slipped our attention. Fixed that.

And what exactly is the problem? The text is too small to read? In what situations? What UI settings do you have?

Ok, so I consider this closed. Thank you. If you discover this or something related to this is still not fixed, please report another ticket, explain into detail and attach screenshots of the wrong text. Thank you!

Fixed, thank you.

I have corrected all but: U_B_CTRG_2 (T-shirt) is translated into (UBASC2) => Correct translation : "T-shirt" - can you provide a precise text of this in French? Or a screenshot?

Changed as suggested. It should propagate in one of the future development branch updates. If you still find it is wrong let's say a month from now, please let me know here or in a new report. Thank you so much!

Changed as suggested, thank you. Will propagate in one of the future development branch updates. Thanks!

str_a3_cfgmagazines_laserbatteries0
str_a3_cfgmagazines_laserbatteries1

Thanks for the note. All community reports are pending, we'll get to it once our hands are free after the Tanks DLC.

Can you please provide screenshot showing this bug, or at least write the precise and exact text which is wrong? Thanks.

Thanks, I am monitoring this thread and fixing it in-game is planned, I however cannot say when exactly. Thank you for this, though!

Fixed, thank you!

When reporting a mistake next time, please always clearly say what is wrong, and most importantly - what is the correct version. Thanks!

Good catch, fixed it. Thank you!

Fix in progress, thanks.

We will fix this in the next update. Thank you.

Thanks, we will check this as soon as we can.

Apex file processed, the rest will have to be done when there is more time.

Will have to close this, many changes have been made since. Some of it will be fixed, some of it probably will not. In any case, feel free to report any remaining errors and we will try to fix them more swiftly. Thank you very much!

Translation has been revamped since.

Should be fixed now. If some issues persist, please report in https://forums.bistudio.com/topic/192541-arma-3-apex-localizationtranslation-feedback and follow the reporting guidelines closely. Thanks.

Closing this, please inform us if the issue persists.

Should be fixed now. Please let us know if that is not the case.

Please provide the exact Russian text so that I can copy-paste it and thus find it. Thank you.

Please assign to a person responsible to investigate. Thanks.

This is intentional, we have unified the names of MP modes to English across all language versions.

We had no capacity to verify and correct this right away, and in the meantime we made some changes. Please, if you are still willing, report the errors on the current version (if they are still present) and create a new Feedback Tracker issue and let me know here: https://forums.bistudio.com/topic/192541-arma-3-apex-localizationtranslation-feedback/?page=2 Thank you and sorry for the annoyance!

Will be fixed in the next update. Thanks.

Fixed, should be in-game after the next update. Thank you!

Thank you for reporting. sprzężone KM has been fixed, we are investigating the other issue.

Fixed, will get in-game after the next dev branch update. Thanks!

They do, because the original English name for these grenades is RGO Grenade and RGN Grenade. The Russian translation has to reflect this, not to suddenly invent its own terms.

Hello. Thank you for your report.

May I ask what is wrong with the original terms?

<Key ID="str_a3_cfgmagazines_handgrenade0">

            <Original>RGO Grenade</Original>
                       <Russian>Осколочная граната РГО</Russian> //Need without РГО, because it is not RGO.//

This item is called RGO Grenade. So it needs to have this name even in Russian.

<Key ID="STR_A3_CfgMagazines_MiniGrenade_dns">

    <Original>RGN Grenade</Original>        
    <Russian>RGN граната</Russian> //This is Мини-граната.//

This item is called RGN Grenade. So it needs to have this name even in Russian.

<Key ID="STR_A3_CfgMagazines_HandGrenade_dns">

            <Original>RGO Grenade</Original>          
            <Russian>RGO граната</Russian> //This is Осколочная граната.//

This item is called RGO Grenade. So it needs to have this name even in Russian.

We cannot change names of these grenades just like that, the translations have to reflect/follow the English original, which is established somehow, and we cannot name the grenades completely different for one language. So, is it a wrong translation, or the term itself in English is wrong?

Thanks for letting me know.

Fixed. Please test after the next update. Thank you!

Fixed. Please check after the next update. Thank you very much for reporting!

Fixed. Thank you for reporting!

Thank you for these reports! I have fixed as much as I could. If you could check the fixes after the next Steam development branch update, that would be wonderful. Just report anything that is still wrong. Also a suggestion how to make me spotting the mistakes easier - please always submit a screenshot showing the error so that I can find the text. It is not always possible without a screenshot. So it is better to always add screenshots to your reports. Thanks!

Thanks for the reports. One or two things is already fixed. But I am not sure from this description what and where exactly is wrong. What I am going to need is a screenshot for each of these issues, so that I can find it clearly. Could you please kindly take a screenshot for each of these issues, and underline in the screenshot what is wrong? Thank you!

Ok, any other mistakes or bugs?

Thanks, we will fix it with the next SPOTREP.

This should be fixed now (see comments in http://feedback.arma3.com/view.php?id=24020). Please test after the next update.

My colleagues will try to investigate, but no promises on this one.

Thanks for the report. Is the issue still present?

Processing via internal communication.

Hello. I will contact you as soon as I can.

Hello. Can you please let me know your email? I will contact you.

Should be all fixed now. Please test after the next update. And thanks for the reporting, keep sending more! Sometimes it just might take a while before we have time to make a fix. Huge thanks anyway!

Ok, I can reopen the ticket, but I am going to need a detailed report what is wrong and what is the correct variant, ideally with screenshots. Otherwise I am not sure what to change and where. Could you please provide:

1. Screenshots with marked errors
2. Wrong text
3. Correct text

Thank you!

Toysoldier: OK, please provide a screenshot and describe what is wrong and with what to replace it. I need a detailed report. Thank you! :)

Corrected, please test after the next update and let me know. Thank you very much!

Should be fixed after the next update. Please test it afterwards and let me know. Thank you!

We have been working here on internal localization testing of several key parts of Arma III. We have changed a lot of things in Russian and some of them might be from your list, some of the might not. Unfortunately we cannot use your changes at the moment, as we would risk overwriting some changes made here internally. I am very sorry, but it will be needed to check the game again (after the next development branch update, some time next week) and report new list of current bugs. Some of them might be actually repaired already. If you want to help with this, please do not just copy the old lists, it is indeed needed to go through the game again and see what is changed or not. Thank you! And sorry for this inconvenience.

All fixed, it will be in the game after the next update. Thanks a lot and keep on reporting, please! :)

Good then. Please, feel free to report more mistakes if you find them, after release of the next update, which should happen very soon. Thank you for your enthusiasm and hard work!

We have been working here on internal localization testing of several key parts of Arma III. We have changed a lot of things in Russian and some of them might be from your list, some of the might not. Unfortunately we cannot use your changes at the moment, as we would risk overwriting some changes made here internally. I am very sorry, but it will be needed to check the game again (after the next development branch update, some time next week) and report new list of current bugs. Some of them might be actually repaired already. If you want to help with this, please do not just copy the old lists, it is indeed needed to go through the game again and see what is changed or not. Thank you! And sorry for this inconvenience.

Working on it.

Changed what I could from 1.47_dev_ver.Fixes_09.07.2015.txt. I did not open the earlier files. I presume all the fixed are already in the latest file (1.47_dev_ver.Fixes_09.07.2015.txt). Is that correct, or do I need to open some of the older files too?

This is a duplicate of http://feedback.arma3.com/view.php?id=24020.

Please, Triada, do not create this issue again. We know about this and we are working on it. No need to report it more than once. Thank you.

This will be fixed in the next update. Thank you!

It will be fixed in the next launcher update. Thank you!

Good! Thank you for your help!

Ok, so what do you suggest? But is the current version wrong, or just uncomfortable?

redux: Are you sure that it should be named "ОФ"? What about Triada, do you agree?

Ok, the last issue with ПП instead of ОФ should be solved by changing STR_A3_CfgMagazines_50Rnd_120mm_Mo_shells_dns.

Please test it after the next update.

1. Ok, I changed this, exactly as it is written:

1)<Key ID="str_a3_cfgmagazines_nlaw0">
2)Граната для NLAW
3)ПТ выстрел NLAW

1)<Key ID="str_a3_cfgmagazines_nlaw1">
2)Тип: выстрел для NLAW
Кол-во: 1
Применение: NLAW
3)Тип: Противотанковый
Кол-во: 1
Применение: NLAW

1)<Key ID="str_a3_cfgmagazines_rpg32_aa_f0">
2)ОФ выстрел РПГ-42
3)ПП выстрел РПГ-42

(and the abbreviation (top-right corner) for "ПП выстрел РПГ-42" must be "ПП" instead "ОФ")

1)<Key ID="str_a3_cfgmagazines_law2">
2)Тип: ОФ выстрел РПГ-42
Кол-во: 1
Применение: РПГ-42
3)Тип: Противопехотный
Кол-во: 1
Применение: РПГ-42

1)<Key ID="str_a3_cfgmagazines_law0">
2)выстрел РПГ-42
3)ПТ выстрел РПГ-42

1)<Key ID="str_a3_cfgmagazines_law1">
2)Тип: выстрел РПГ-42
Кол-во: 1
Применение: РПГ-42
3)Тип: Противотанковый
Кол-во: 1
Применение: РПГ-42

2. I did not change this:

Inventory with NLAW missil.jpg - wrong!!!
not "многоцелевой"!! --> "противотанковый" (ПТ - is abbreviation from type: "Противотанковый" already!)

Аламут.jpg - wrong!!!
ПТ - is abbreviation from type: "Противотанковый" it's type, it's not the Redux ammo name "ПГ-42В" - THIS WILL STAY ПТ (Anti-Tank)

Аламут тбг-42.jpg - wrong!!!
ОФ - is abbreviation from type: "Осколочно-фугасный" it's type, it's not the Redux ammo name "ТБГ-42В" - THIS WILL STAY ОФ (High-Explosive)

These stay as they currently are.

This should be fixed after the next update. Please test it afterwards and let me know if it already is OK.

Thanks, that might help. I'll see what we can do here.

Looking into this.

Sorry, I don't have enough information from this report, and as I don't speak Russian, I cannot change anything just like that. I cannot find a lot of this text you marked as wrong.

What I need from you:

1. String/key ID (like <Key ID="str_a3_cfgmagazines_nlaw0">
2. What text is in this string/key ID
3. Correct text to change it to

Example:

1. <Key ID="str_a3_cfgmagazines_nlaw0">
2. выстрел РПГ-42
3. ПТ выстрел РПГ-42

I cannot change anything without having all of this information - I need precisely the string/key ID to change and the correct text assigned to this string, otherwise I might change something wrong. Thank you very much for providing these.

I changed this:
Противопехотная ракета Титан / Противопехотная / ББ (wrong mark)
to
Противопехотная ракета Титан / Противопехотная / ПП

The rest cannot be changed to what you suggest due to length. The text would be too long, it would overflow or get cut. Is there any other shorter variant?