Sentences from .cfg files are not translated

[illwieckz]

Example in pkg/unvanquished_src.dpkdir/configs/buildables/barricade.attr.cfg:

humanName         "Barricade"
description       "Living alien wall.
Absorbs large amounts of damage and obstructs movement.
Can shrink to allow aliens to pass over it."

[illwieckz]

I don't want to write a custom parser for this to extract the strings, it's better if we use a standardized format with ready-to-use parsing libraries available for any language…

[slipher]

Some of the files (those using Parse_LoadSourceHandle) have C processor functionality enabled, so we could define the N_ macro there. But many .cfg files don't use that parser, so it's probably a bad idea.

On the other hand almost all files have C/C++ comments enabled, so we could define a custom marker using a comment e.g. /*T*/ before the string constant. A custom parser would be less than 10 lines in our Python script, so we hardly need to worry about that.

[ghost]

I think we should drop that weird format of us for config files and move to something more ini-style, or maybe deb822 format. This would be much easier to parse as those are just key-value based.

I even have some work on that around, which includes moving hard-coded values such as range or obituaries into the weaponAttr_t struct, which have the side effect to make bots more aware of gameplay rules without having to duplicate hard-coded values.

In regard of translations, that would basically mean, load the "normal" config files, and then load the translation config files, which would overwrite some fields such as name, description, and the likes.