@sam and @techAPJ: Can you please help me out here?
I’ve been looking into this a little bit. It looks like I have a few options for solving this:
Add the following transliteration rules to
server.de.yml and let the existing transliteration replace the German umlauts:
But I guess I would have to add those to
server.en.yml as well, otherwise they would get lost at the next pull from Transifex. I’m not feeling comfortable in doing that. Why should the translators of all the other languages have to worry about this? I’m not even sure why we already have some rules in there…
Add an additional, language specific translation file (e.g.
transliterations.de.yml) that just contains the transliteration rules and is not managed in Transifex.
Replace the German umlauts within slug.rb. Doing this with a regex wouldn’t be that hard since there are only 7 characters to replace. But, this feels wrong on so many levels. What if other languages want to do the same? I imagine this would become ugly quite fast.
Use stringex like it’s already done for Simplified Chinese. According to the documentation it should even have German transliterations out-of-the-box. However, I couldn’t get it working. Somehow it didn’t use the locale files that should come with stringex. It only used the two translations from
What I also like about it is the localization of stringex conversations:
It is possible to localize the different conversions and unidecoding in Stringex, so for example “100%” becomes “100 percent” in English and “100 prozent” in German.
Currently symbols like
% are always removed when the slug is created. Replacing it by e.g. “percent” would be great.