> Hi there. > > I still have a problems with internalization of qtjambi applications. As a > qtjambi maven plugin author, I am looking for people who are translating > their qtjambi apps to see how they do that and if they have a problems with > it. Because I have ... > > I've asked qt-interest with simple question - is .ts extraction by lupdate > for .java files supported after discontinuing qtjambi by nokia? But no > response until now. > > My idea ( if trolls will not support that ) is to abandon lupdate binary > and to handle translation extractions myself in qtjambi plugin. I already > have a java code which do the same stuff like lupdate ( but still without > saving anything into xml/ts ). Of course, .qm will not be then supported > and we will need to implement it or to invite our native format ( now I am > using custom Translator which uses .ts files instead of .qm ). > > Benefit of this will be complete independency from lupdate binary, faster > response for bugs, no c++ for this ... ) > > What do you thing? Well, I think that we must be sure about the deprecation of the lupdate for .java files. If that is true, we should have three options:
1.- Create or own version of lupdate, compatible with Qt. 2.- Create a new whole translation system only for jambi. 3.- Use the internationalization of java (works well in eclipse). For now, a will check the code of lupdate, to see if I can figure what happed. PD: I'm currently working with the mac tests, but I'm very slow with that because I'm new in that platform. _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
