Ian Bicking schrieb: > > Ah. OK then, your strategy sounds right then. Though I guess it means > that TG will have to do: > > Validator.gettextargs['domain'] = 'FormEncode' > > ? I.e., it will have to TGify the Validator class on startup.
Exactly. Like any other software that want's to hook into FE's message translation process can do this with a _ (gettext) function in __builtins__ or state._ and the Validator.gettextargs attribute. > > How does the turgogears.mo file get generated? Is it every translatable > string in TG? Or is it every translatable string in the individual > project? If it's just the project itself, then an extraction process I think of 3 mo files: messages.mo: the translatable strings of an individual project (like it is now) FormEncode.mo: the translated Formencode messages (the same files should be shipped with FormEncode itself) TurboGears.mo: the translated TurboGears messages (For example TG's validator messages) > that understands validators and schemas could do it. If not, then > people will have to carefully look at their code to see what portion of > FormeEncode.mo needs to be translated (assuming they don't feel like > translating the entire thing, though I suppose contributors could > translate it and distribute the entire translation with FormEncode itself). I think the best solution is to translate the whole thing and ship the whole translations with FormEncode or TG. I already did the german translation and it took me 2 hours. > > If FormEncode does start distributing translations, I should say that I > don't really want to manage that process, though I'm more than happy to > give someone access to manage that. > Yes I can do this if you want to. But I can only translate into german. I think FormEncode and TG should ship this, they also ship English and other languages should be on an equal footing with English. I love cultural diversity :-) -- Greg, Vienna --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
