> Oh, I was assuming it would just be a matter of adding keys to the .po > file using some poEditor.
The way its done currently is to use the set of keys from the source as a filter. This makes sure you're not drawing in unused keys from a .po file where they're might still hang around. But if you have a good use case to use *all* (non-obsoleted) keys from a .po file, open an enhancement bug for it. > Hmm, perhaps I'm going to have to create a little script that > generates qooxdoo source-code containing a bunch of this.tr() That's what others do, too. You can fall back to this.marktr() for these cases. > That would solve the warning problem as well. No, as it will still warn about occurrences of this.tr(<expression>) ;). T. ------------------------------------------------------------------------------ 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
