Qt3 to 4 porting. QTranslatorMessage disappeared



  • Class QTranslatorMessage was a public API in Qt3 but disappeared in Qt4.

    Bug is in Open state: http://bugreports.qt.nokia.com/browse/QTBUG-1449

    Are any recommendations exist about replacement during porting?



  • There seems to be no replacement api provided for QTranslatorMessage



  • Judging by the age and status of the bug mentioned: don't count on it being fixed at all anymore. Qt 3 is quite old, and I don't think more work will be put into the Qt3Support module.

    Perhaps you can take the sources from Linguist? According to the bugreport you link, the source is still there.



  • As far as I remember, there will be no updates to the Q3Support libs anymore. I wouldn't expect any replacement for this in Qt4, too.



  • blex, what are you QTranslatorMessage using for? Do you need access to the complete translator database or are you just looking up a particular item?



  • Thanks all for information.

    [quote author="Volker" date="1291316850"]blex, what are you QTranslatorMessage using for? Do you need access to the complete translator database or are you just looking up a particular item?[/quote]

    I am porting very-very large application. QTranslatorMessage is returned by some virtual functions in the class, inherited from QTranslator. I still not investigate the internal logic of these functions.



  • blex, I think the best that you can do is to change logic of this class. I think that another way (without QTranslatorMessage) exists.



  • [quote author="Denis Kormalev" date="1291320294"]blex, I think the best that you can do is to change logic of this class. I think that another way (without QTranslatorMessage) exists.[/quote]

    Thanks, I think it will be the simplest solution. Porting QTranslator message from Linguist is impossible because I work with new implementation of QTranslator. No other reasonable approaches...

    It is a bad news for me that Q3Support will not be improved in the next releases.



  • blex, maybe these news are bad (and for someone who porting from Qt3 they are definitely bad), but it is fair enough. Qt should go forward and sometimes it means losing relations with past.



  • [quote author="Denis Kormalev" date="1291320964"]blex, maybe these news are bad (and for someone who porting from Qt3 they are definitely bad), but it is fair enough. Qt should go forward and sometimes it means losing relations with past.[/quote]

    Sorry for off-topic, but it is good news that Qt goes forward. I hope to port the same application from Qt4 to Qt5 for our valuable customer :)



  • [quote author="blex" date="1291320115"]I am porting very-very large application. QTranslatorMessage is returned by some virtual functions in the class, inherited from QTranslator. I still not investigate the internal logic of these functions.[/quote]

    Maybe you can create a translation file (.ts/.qm extension) and put it into the resources (.qrc). You then can load it via "QTranslator::load()":http://doc.qt.nokia.com/latest/qtranslator.html#load-2



  • [quote author="Volker" date="1291322625"]
    Maybe you can create a translation file (.ts/.qm extension) and put it into the resources (.qrc). [/quote]

    Thanks for advice, but the problem is that message slightly modified after getting from *.qm in the reimplemented virtual function of QTranslator that does not exists any more. And function returns QTranslatorMessage.

    I will report to this thread about the solution, but later. Now it is not ready :)



  • Then the virtual "QTranslator::translate()":http://doc.qt.nokia.com/latest/qtranslator.html#translate seems to be your friend :-)


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.