2010-03-22, 11:22 AM
Almost there sort of... here (\<span> site blocked, contact your administrator/ex/lang/KING%E2%80%99S%20FIELD/) is an example of a directory page.
The translation system is fully functional as far as I can tell... Ie. if anyone wants to go ahead and start using it your work will not be dashed by future developments. I kinda wanna get the directories up, and eventually a good guide page (as much as I hate that sort of thing) ...but the big problem atm is whenever you start revising a translation the gettext utilities commonly installed on hosts really don't respect the context heavy comments generated by Exgettext (so basically the comments get shoved around) ...I have a very clever plan for this which will also make the framework in general very stable. I'm just not sure how soon I will get cracking on that (fairly soon I'm sure.)
I'm really ready to be completely done with all of this translation business. I always get the difficult/boring stuff out of the way first anyway, and internationalization is not something to put on the back burner, so it's cool.
The final plan will actually use the translation files on the server to translate the template on the fly. That way the translation page will always look like the template. And the template can also be edited via WordPress if necessary. Even if something is removed from the template it won't get lost, so the translation will come back if is added back to the template. Gettext is incredibly powerful but it was never designed for the world of online collaboration... wiki-like anything is a relatively new phenomenon, and the Linux world is pretty set in its ways. It's a shame the philosophy of the framework cannot be revisited. Most websites use it for on the fly translation, but editing the translation on the website is pretty damn cutting edge. The website itself will be translated in much the same way... only with tighter security and coordination / language selection.
The translation system is fully functional as far as I can tell... Ie. if anyone wants to go ahead and start using it your work will not be dashed by future developments. I kinda wanna get the directories up, and eventually a good guide page (as much as I hate that sort of thing) ...but the big problem atm is whenever you start revising a translation the gettext utilities commonly installed on hosts really don't respect the context heavy comments generated by Exgettext (so basically the comments get shoved around) ...I have a very clever plan for this which will also make the framework in general very stable. I'm just not sure how soon I will get cracking on that (fairly soon I'm sure.)
I'm really ready to be completely done with all of this translation business. I always get the difficult/boring stuff out of the way first anyway, and internationalization is not something to put on the back burner, so it's cool.
The final plan will actually use the translation files on the server to translate the template on the fly. That way the translation page will always look like the template. And the template can also be edited via WordPress if necessary. Even if something is removed from the template it won't get lost, so the translation will come back if is added back to the template. Gettext is incredibly powerful but it was never designed for the world of online collaboration... wiki-like anything is a relatively new phenomenon, and the Linux world is pretty set in its ways. It's a shame the philosophy of the framework cannot be revisited. Most websites use it for on the fly translation, but editing the translation on the website is pretty damn cutting edge. The website itself will be translated in much the same way... only with tighter security and coordination / language selection.