Converted translation system to Gettext #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g is still screwed up.
the long type does have different sizes on 32- or 64bit environments
eXpl0it3r
force-pushed
the
feature/gettext
branch
from
a5114fe to
93823e9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rebased from #20
There were some issues with the translations, e.g. changes in the English strings that the translators couldn't notice and didn't fix, and obsolete strings that wouldn't need translating anymore. Also adding, new strings was quite unwieldy.
So, I decided to try my hand at switching ths translation system over to Gettext. This has the additional advantage that translators can use all kinds of nifty translation tools.
There is quite a bit of string converting going on in this branch due to the ways that SFML handles strings. I can't initialize the SFML srings with a locale, because the desired locale might not be available on the system. So, toAnsiString is not usable...
This has been tested on Ubuntu and MinGW64.