Author, WebMarketer, Self-Development Coach, Drop-Out and Eco-Village-founder. German Expat living in Paraguay.
prossbngmonster Would be cool to see actually 2 German versions, since we have the "formal" and "informal" way to address people ("Sie" vs. "Du") and while it does not matter much for the backend, it certainly does on the frontend. One more reason why I suggested splitting up the language file in my comment above and earlier on the forums.
2 years, 1 month ago on PageLines in Your Language: The New Translation Center..
bngmonster the Google one was not even funny... ;-)
See you around, I will start working on the German translation as well.
Good to see you do something about the localisation issue! And even if I think that a 200-bucks-per-theme+paid-plugins company might not want to (ab)use their paying customers as translators... well, better that, than nothing. And definitely better than the unusable Google-translated mess we had so far... *lol*
Two suggestions to make it easier for all of us:
- split up language files and translations for backend and frontend. 90% of webmasters have no problems using an English backend, but need one or more 100% legible and complete translation(s) for the frontend. Would reduce translation efford by 95% ;-)
- It would be great if the online interface included a feature that we know from Poedit: to show where this string is actually used. Poedit shows it for the source code, even better would be a man-made comment like: "shows up in the byline in single post view". Esp. for small snippets like "by" you have to actually see them in context before you can translate them correctly.