On Wednesday 14 of April 2010 18:48:25 Samu Voutilainen wrote: > If this case is same than with uic, let’s just take copy of lupdate from > qt-4.6 to jambi for now. Or qt-4.5, if 4.6 one is already fixed.
No it isn't. See my previous mail from 13.4 "Bug in lupdate?". I have tested 4.6-linux32-community qtjamb's lupdate. Only difference between 4.5 and 4.6 lupdate is that 4.6 told "Package keyword should be followed by..." and dies and 4.5 lupdate extracted translations, but without package name. I can't found a problem with java source because we have a tons of file similar to this one translated without problems... > Java’s properties system is bad for translating Yes it is. We must stay with qt linquist. As I said, I have a proof-of-concept java-lupdate written ( I took about 30 minutes to do with JavaParser package ! ). It extracts strings from tr(), QApplication/QCoreApplication.translate(). Also I have a java class which reads .ts files and provides a qt translator for it done. Only think to do is to make a code which will save extracted strings into .ts files ( to be used by linguist ). And I thing that jaxb should be used for this ( because we know dtd for .ts file ). I thing that I will do that nevertheless, because my company have several products based on qtjambi and we still have a problems with translations. And it will be much faster to maintain simple java code ourselves than wait for nokia's bugfixed c++ lupdate releases. ... btw still no answer on qt-interest about .java lupdate support ... -- Dusan _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
