Oh, I see. Well, I wouldn't be able to help, unfortunately : my only incursions into Rivendell's code are limited to changing the value of CURL_TIMEOUT before compiling. I guess we'll have to stick to that.
Thanks for the info ! Le 15/11/2014 15:19, Wayne Merricks a écrit : > > Hi, > > QT3 encodes strings/chars as unicode as long as you use QString and > QChar so the support in QT3 is there to use. The only other obstacle > is that the mysql tables do not specify utf8 encoding by default. > "Fixing" MySQL is fairly trivial but from the few sections of Riv code > I've messed with there is a mix of QString and char pointers all over > the place. > > To make sure everything was represented properly would require > reworking all the code that uses char pointers instead of > QString/QChar. I don't really know how much of a rewrite this would be > without doing some code searching but its certainly not impossible to > fix. However due to the amount of changes you'd need lots of testing. > > More QT3 specific info is here: > > http://doc.qt.digia.com/3.3/i18n.html > > On 2014-11-15 12:29, Hoggins! wrote: >> Hello all, >> >> It's already been discussed a lot, but I don't see much movement on >> that, and I don't even know if anything is planned. >> What is the roadmap for supporting special characters ? >> >> For example, we have an artist called ∆AIMON (I hope it will render >> correctly on this mail, the first character is a delta), and we have no >> other choice but to name it AAIMON. Trying to rename it via RDLibrary >> gives us ?AIMON. >> >> Any idea ? >> >> Thanks ! > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
