Description
For example, many localisations use _desc or _name, while some use .name and .desc. The same applies for in-series localisations. Some are _NUM, and some are .NUM. Standardise the localisations across BTR. Some sub-keys are not properly named. Instead of being MyKey.desc or MyKey_desc they have a Unique.desc or Unique_desc where the scripter must accomodate this anomalous change. Localisations should be logically structured and extremely predictable.
Also many localisations are missing the 0 following their colon.
MyKey:0 "TEXT" ------------- NOT ------------- MyKey: "TEXT"
Location
./localisation and scripting files
Current State
There are inconsistencies in the localisation throughout BTR
Needed Information
Fix the mod.
Why Is This Important?
It creates confusion for scripters when trying to reference a localisation's desc, name or following chain.
Description
For example, many localisations use _desc or _name, while some use .name and .desc. The same applies for in-series localisations. Some are _NUM, and some are .NUM. Standardise the localisations across BTR. Some sub-keys are not properly named. Instead of being MyKey.desc or MyKey_desc they have a Unique.desc or Unique_desc where the scripter must accomodate this anomalous change. Localisations should be logically structured and extremely predictable.
Also many localisations are missing the 0 following their colon.
MyKey:0 "TEXT" ------------- NOT ------------- MyKey: "TEXT"
Location
./localisation and scripting files
Current State
There are inconsistencies in the localisation throughout BTR
Needed Information
Fix the mod.
Why Is This Important?
It creates confusion for scripters when trying to reference a localisation's desc, name or following chain.