Cockpit language

[FC2 liga - poredak]

FC2 liga - poredak

FC2 League - Stats and Ladder

IL-2 League - Stats and Ladder

[BabaLooey]

Boberros is currently working on pic files, so I will leave that part of report to him

As of other cockpit stuff, I found out following:

ABRIS_localizer.lua
- Can be localized, translate english text in second part of the strings
localize_table["EN"]["ВСЕ"]   ="ALL"

Hint_localizer.lua
- This bugger refuses changes in strings. If I change EN part, it displays RU text, and vice versa. Regardless of cockpit lanugage chosen.

EKRAN_localizer.lua
- Also bugger refuses changes in strings.

Some localizer lua file start with:

country = "EN"
if  LockOn_Options.cockpit_language == "russian" then
    country = "RU"
end
(..)
localize_table["RU"] = {}
-- CPT MECH
localize_table["RU"]["Gear lever"]   ="Кран шасси"

Then in the rest of the lua file you have EN and RU options. However, they are quite messy. In one lua, Russian is defined as RUS, in second localize_table is RU, in third it is EN....
Still looking where it could be possible to add another cockpit lang.

IMPORTANT EDIT !!!
Thanks to ZaltysZ, now it is possible to display localized cockpit hints!
For instructions see: http://lockonhr.com/forum/index.php?topic=1090.msg4131#msg4131

I'll upload files with prepared string to SVN soon.

[Boberros]

As babalui mentioned I tried to do some Polish translate of cockpit language. Here you have to unpack from CCDS big files bitmaps. I don't post its names, you can alone decide what you wanna to translate. Whole process isn't difficult, most time is loosing by looking for good fonts and trying to do same effect as on original. I advice to use it Photoshop, easy to use and powerfull application, but if you can use another go and use your own application than learning Photoshop, but remember if u learn Photoshop - basic is enough -  then all will be much easier ;]

CDDS files are in Bazar\World

After editing file, place it in Bazar\TempTextures.

To extract bitmaps from CDDS file I use Modman from Lockonfiles.com. I don't post direct link to this utility, cos registration is needed. I show you example of early work of mine cockpit:







Links:

www.lockonfiles.com

[cfz8688]

well,I tried many times,and the result is DCS can't support chinese in the game.......

The localization program of GUI has finished,our new project is to translate DCS English manuals.....

[BabaLooey]

well,I tried many times,and the result is DCS can't support chinese in the game.......

The localization program of GUI has finished,our new project is to translate DCS English manuals.....

Any screenshots?

I've created Chinese and Thai folders in SVN with some basic files and structure. Current SVN address is for practising only. I'll create a fresh DCS localization project on Sourceforge and then we will be able to use more appropriate address
I wanted to have a chance to investigate all necessary files and actions beforehand.

[ZaltysZ]

I just thinking... Is it worth to translate whole cockpit? I mean, that GUI, tooltips are ok to translate, but whole cockpit might be too much (lost authenticity; after all it is Russian helicopter). Personally, I would fly it as it is, even if labels were in Chinese. As I said, just some thoughts...

[BabaLooey]

I also prefer Russian version, but then again, I do not have much trouble reading it. Some users may found that problematic, and later one when Western edition will be out - and according to last info you could choose ENG cockpit inscriptions - some may preffer that, or not. Personally, I rather have it in RU or in CRO - english is totaly unnatural for russian cockpits! Not only that it detaches you from authenticity, but more importantly - I don't think they are correctly translated in the spirit of the game.
For isntance, that "LA" on english HUD in FC? Each time I hear someone else talking about it, I think about Los Angeles
Also, it is displayed when you are in range for cannon fire. "Launch" of cannon shells!??! 
Is that realy the way such a message would be displayed in western aircraft? Don't think so. Very poor translation indeed.

[Boberros]

Cockpit as is only as addictional.  Beyond basic translation of GUI, so it has lower priority than missions ect

Now when I am finishin creating and correcting font time to do rest GUI translate, leaving cockpit for end.

[BabaLooey]

Regarding cockpit tooltips, I am still not able to make DCS use translated strings. No matter what I change, DCS uses unchaged string. Exmaple, I've tried to check CRO chars in-game, and I've shanged first string in a way that I only added CRO chars in the middle of existing string:

(from Hint_localizer.lua)

Kôd:

-- In next string to enter "RU" for Russian localisation or "EN" for English localisation
country = "EN"
if  LockOn_Options.cockpit_language == "russian" then
    country = "RU"
end
localize_table = {}

function LOCALIZE(str)
if localize_table[country] == nil then
return str
else
if localize_table[country][str] == nil then
return str
end
return localize_table[country][str]
end
end

localize_table["RU"] = {}
-- CPT MECH
localize_table["RU"]["Gear lever"] ="Кран šđčžć x ŠĐČŽĆ шасси"

DCS display English string. If I insert "šđčžć x ŠĐČŽĆ" into English string - DCS displays Russian string! Same goes for all combinations of cockpit lang and [RU]/[EN] definitions in this file.

[ZaltysZ]

Here I will show how to change hints. I am using Lithuanian as target language, modify for your needs.

The whole procedure:

Open ..\Ka-50\BlackShark\modules\me_options_form.lua
Search for:

Kôd:

    -- dictionary for combo boxes
    dicts = {
        ....
        russian = _("RUSSIAN"),
        english = _("ENGLISH"),
    }

Add one more line to associate your language name with localized string:

Kôd:

    dicts = {
        ....
        russian     = _("RUSSIAN"),
        english     = _("ENGLISH"),
        lithuanian  = _("LITHUANIAN"),
    }

Save.

Open ..\Ka-50\BlackShark\modules\me_options.lua
Search for:

Kôd:

-- IDs of items
local ids = {
    ...
    cockpitLanguage = { "russian", "english" },
    ...
}

Add your language to array of available cockpit languages:

Kôd:

-- IDs of items
local ids = {
    ...
    cockpitLanguage = { "russian", "english", "lithuanian" },
    ...
}

Save.

Open ..\Ka-50\Scripts\Aircrafts\Ka-50\Cockpit\Hint_localizer.lua
Search for:

Kôd:

if  LockOn_Options.cockpit_language == "russian" then
    country = "RU"
end

Modify it to:

Kôd:

if  LockOn_Options.cockpit_language == "russian" then
    country = "RU"
else
if LockOn_Options.cockpit_language == "lithuanian" then
country = "LT"
end
end

Add:

Kôd:

localize_table["LT"] = {}
localize_table["LT"]["Gear lever"]       ="Važiuoklės rankena"
localize_table["LT"]["Main/Common hydraulics for emergency gear"]      ="Avarinis važiuoklės hidraulikos (pagrindinė/bendra) jungiklis"
...

Save.

Open missioneditor.po
Add:

Kôd:

msgid "LITHUANIAN"
msgstr "LIETUVIŲ"

Save. Make missioneditor.mo. Put it where it belongs.

That's all. Don't forget to change your cockpit language to the newly added one (in options screen).

Analogically translate ABRIS, EKRAN and etc.

[BabaLooey]

WOW! Great work man!
 
I will test it later on and commit to SVN by tomorrow

< ------         ------ >
  spojene poruke
< ------         ------ >

YIPIE!!! IT WORKS!!!

ZaltysZ, you're a genius!

Here are sample screenshots...

Basic files uploaded to SVN. I'll upload edited files to template_ru soon, with definition strings for other languages soon.

Again, A-MA-ZZZ-ING

[=CVFS=Stuck]

Stvarno nije moj fah, ali "dečki" stvarno ste genijalni!

[cfz8688]

That's amazing!Congratulations and bravo!

I'm nearly crazy.....I had a dream that I finally made chinese display in the game,and after I woke up I was deeply sad.....I even want to kidnap ZaltysZ to China to help me with it......

[Boberros]

Cool to see it can be done. I am also finalizing final fonts to game - my last decision is to use monotype fonts.  They looks even good, didn't know it will look so good.

[BabaLooey]

OK, I've added all files to SVN. I hope that I've edited them correctly for individual languages:

..\Ka-50\BlackShark\modules\me_options.lua
..\Ka-50\BlackShark\modules\me_options_form.lua
..\Ka-50\Scripts\Aircrafts\Ka-50\Cockpit\Hint_localizer.lua
..\Ka-50\l10n\ru\LC_MESSAGES\missioneditor.po

NOTES:
me_options.lua - check according to ZaltysZ's instructions:

Kôd:

    cockpitLanguage = { "russian", "english" , "chinese" , "croatian" , "lithuanian" , "polish" , "thai" },

me_options_form.lua - check according to ZaltysZ's instructions:

Kôd:

        russian = _("RUSSIAN"),
        english = _("ENGLISH"),
        chinese = _("CHINESE"),
        croatian = _("CROATIAN"),
        lithuanian = _("LITHUANIAN"),
        polish = _("POLISH"),
        thai = _("THAI"),

Hint_localizer.lua - check according to ZaltysZ's instructions:

Kôd:

if  LockOn_Options.cockpit_language == "russian" then
    country = "RU"
    else
if LockOn_Options.cockpit_language == "chinese" then
country = "CN"
end
end

For two-letter country codes see -> ISO country codes

missioneditor.po -  check PO tutorial appendix -> Updating your PO files