Alberto Valverde schrieb: > > On Sep 26, 2006, at 5:50 AM, Gregor Horvath wrote: > >> >>What I dont see yet is how to integrate the standard compiled >>FormEncode >>messages to my own projects TG messages. Is there any proposed >>mechanism >>or idea in TG for that? > > > I see two possible solutions for this: > > 1) Subclass FormEncode's validators in turbogears.validators under > the same name, copy&paste their messages and wrap the strings in _(), > hen jst collect those _() wrapped strings in the usual way.... yuck! > > 2) Hack the string collecting function in i18n to walk all FE's > modules, grab the validator's "messages" attribute and extract those > strings into the .pot files. > > Disclaimer: I'm no i18n expert whatsoever so please excuse me if any > of the above are crazy suggestions. > > i18n for FE's messages is something I've always longed and a feature > (shamefully :( ) missing from TG so your work on this is much > appreciated! :)
I think I can finish this at end of the week. The prototype is working already. The message extraction and translation is not the problem, it's already working. The problem is that as long as I understand there is one message.mo file for a TG project. This includes the costum messages of a TG Project. Now I have a FormEncode.mo for the Formencode validators messages (and probably another Validators.mo or similar for TG's validators). How can I merge those files, or how can TG's translation function be instructed to use all *.mo files instead just the messages.mo? Is there a mechansim I am not aware of or has this to be done? -- Greg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
