| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
CRYO: Move all static engine data into cryo.dat
|
|
|
|
|
|
Though it's unlikely that we'll ever have that many changes, it's
better to provision for more space now, for versioning
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 4858b3fc5836dbf2f33fe0d1452bf0cb3a9f75b2.
|
|
This reverts commit 1db02c7bd8ffee2aa0a27264669d11f83d95b491.
|
|
|
|
|
|
Some formal function parameters are not used in all overloaded
functions, which results in loads of 4100 warnings when building
CREATE_PROJECT. This change silences warning 4100 together with
the others
|
|
DEVTOOLS: Create project fixes
|
|
CRYO: New engine
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We have been abusing the 'Language' field to store the language name
that appears in the GUI for a translation. But this field is officially
supposed to store the language code, and most tools that edit po file
set it automatically. This has caused the language being changed by
mistake in the paste.
There is a provision for custom fields with a name starting with 'X-'
though. So Now, if defined, it will use the custom 'X-Language-name'
field, and fall back to 'Language' in case that custom field is not defined.
This should prevent the language being lost when not careful while
editing the translation.
|
|
|
|
|
|
|
