And that is the problem! I can't do a translation for any language and any possible plugin... The problem is that qmdilib uses string to identify menus and modify them. If I want these menu to be tranlatable I put a tr() around their name, huh? but what happens if a plugin doesn't bring a translation in the same language (and the same translation for the menu or toolbar titlle)? Then two menu get created and that's very wrong!!! I'm thinking about using phrasebooks instead of regular .ts and .qm but I don't know how to load them properly in the translator... Plus I'm too lazy to create them "by hand" with Qt Linguist so I'll need to create another program : ts2qph to take existing data in a .ts file and create the appropriate .qch... Bunch of work, isn't it?I think that there is no reason for it not to work if your plugins make sure that its translations are installed in the translator object.
Bookmarks