So, this is the current state:
- the win-build 16rc1 packages work as expected, show all languages and one can
select all and they work
- the Mac OS X universal 16rc1 packages work as expected, show all languages
and one can select all and they work
- The linux packages that are installed system wide only show english and the
current selection as local, but the LOCAL variables are respected, so
widelands starts up in the local language
So windows and mac are optimal, linux is suboptimal but better than build 15 was. I deem this uncritical even though it is not as we expected; i am very fearful of touching the locales code again and maybe break things for windows and mac that we do not have the time to test anymore.
So, this is the current state:
- the win-build 16rc1 packages work as expected, show all languages and one can
select all and they work
- the Mac OS X universal 16rc1 packages work as expected, show all languages
and one can select all and they work
- The linux packages that are installed system wide only show english and the
current selection as local, but the LOCAL variables are respected, so
widelands starts up in the local language
So windows and mac are optimal, linux is suboptimal but better than build 15 was. I deem this uncritical even though it is not as we expected; i am very fearful of touching the locales code again and maybe break things for windows and mac that we do not have the time to test anymore.
I suggest pushing this to after build 16.