Closed Mte90 closed 2 years ago
I see what you mean.
I like the fact that the full path is explicit in the po files: some start with$GSH_HOME
, others with $MISSION_DIR
, etc.
All problems arising from misspelled path variables should be easy to detect when testing the mission.
The test-bash
target in the Makefile
runs through all 42 missions and aborts if any auto.sh
script fails.
You can do it by hand with
$ ./utils/archive.sh -a
$ ./gameshell.sh -dc 'for _ in $(seq 42); do gsh auto --abort; done'
I'm not sure it would catch all such errors, but probably most of them!
Ohhh cool this is very useful I found another bug in the translation. Maybe add it to the documentation?
A common issue during the localization is people that escape variable or don't write them rightly in po files.
The game is not able to report that issue to the user, in my opinion those cases should be like 0.
As example GSH_Home should not something in the po files as is the official path for the game or break it.
Basically:
$GSH_HOME
variable in po files