Hi All, I'm just coming to realize something. I think I have a broader feature request.
Can the localisation support, offer the ability to use our own classes that provide the translation? Perhaps in a way where we can set the translation manager per class? I think most people that are hitting issues with the translation support, are wanting to have translations that simply can't be marked in the application source code. Instead, I assume, most people fetch this stuff from the database. On the other hand, most love the fact that all messages of qooxdoo widgets already have translations. Perhaps this could be part of a future roadmap? -- Met vriendelijke groeten, -- Ralf ( @ gong.nl // ****** ) 2010/7/18 Ralf Nieuwenhuijsen <[email protected]>: > 2010/7/18 thron7 <[email protected]>: >> Ralf, >> This has been fixed (http://bugzilla.qooxdoo.org/show_bug.cgi?id=3669). >> It's a good idea to put yourself on CC on the bugs that interest you so >> you get notifications. > > Agreed. I just didn't realize there was already a bug. I usually just > search the qooxdoo mailing list, rather than bugzilla. Perhaps I > should do it the other way around first. > >>> I at least need to 'patch' it at this side, so I'm hoping somebody can >>> guide me a little here. >>> - the generator needs to stop complaining when I pass in a variable. >>> (The "Could not extract translation .. ") >> >> It's down to only "complaining", but doesn't bomb anymore. Is there >> anything left open for you? > > Thank you. I guess i have to update to the development version. > >>> Is that all I need? Assuming I don't run "./generate translation" again? >> >> Well, if the issue is solved for you, you can safely again run >> "translation". But only string literals in this.tr() and friends are >> extracted to .po files. And, possibliy more importantly, only those >> strings are also used when doing "source" or "build" versions of your app. > > So far so good. > >> There is currently no way to include additional keys from .po file which >> you might have added by hand. > > Oh, I was assuming it would just be a matter of adding keys to the .po > file using some poEditor. > Hmm, perhaps I'm going to have to create a little script that > generates qooxdoo source-code containing a bunch of this.tr() > That would solve the warning problem as well. > > Thank you for your answer! > > -- Greetings > -- Ralf ( @ gong.nl // 06-*******) > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
