Interesting. I didn't think non-ASCII characters could be displayed
properly by any version of Rivendell prior to 3.x.
One thing they tend to do is blow up RLMs, causing rdairplay to crash. For
that reason, I used to filter out non-ASCII characters from any titles
going into an RD 2.x system.
RD 3.x handles them beautifully, even Cyrillic text.
Rob
--
Я со звёздами сдружился дальними,
Не волнуйся обо мне и не грусти.
Покидая нашу Землю, обещали мы,
Что на Марсе будут яблони цвести!
On Tue, 30 May 2023, Hoggins! wrote:
Okay, just found what to do.
It might not be very clever nor clean, but it's working.
In lib/rddb.cpp, I just added, at the end of QSqlDatabase *RDInitDb
(unsigned *schema,QString *error) :
QSqlQuery *q2=new QSqlQuery("set names latin1");
delete q2;
Now my comms from and to the database are good again.
Though oddly enough, the global variable DEFAULT_MYSQL_COLLATION is not
taken into account by Rivendell when creating tables for example. With my
database driver, it will still try to collate with utf8mb4_general_ci, the
error message says "'utf8mb4_general_ci' is not valid for CHARACTER SET
'latin1'".
I had to manually edit conf_create_table_postfix in lib/rdconfig.cpp to have
the correct collation.
Cheers!
Hoggins!
Le 30/05/2023 à 18:08, Hoggins! a écrit :
Hello there,
It's me, again, with the same problem... again. I'm running
Rivendell 2.19.3 (I know. But believe me, if I'd had a chance to
successfully compile a 3.x version, I would be using it right
now) on a new Fedora 38 machine and the issue is here again.
The "charset" setting in rd.conf does not affect the result, and
I still get display issues like UTF8->ISO conversion glitches.
An artist named "Chloé" shows as "Chloé" on this new machine
but is correctly displayed on another (older) one.
The default charset of both the Rivendell database and the table
CART is "latin1".
So I know it's a long shot and this version is not supported
anymore, but do you think someone could point me out where in
the code I could tweak it so that I get a "normal" behavior
again? It has to do much with the MariaDB driver I guess because
previous conversations I had with Fred showed that when
updating/downgrading to some package versions the problem
disappeared. But I would like to rule it out once and forever.
And I promise : as soon as I can compile a 3.x version of
Rivendell, I'll proubly use it!
Thanks for your help!
Hoggins!
Le 18/07/2018 à 16:35, Fred Gleason a écrit :
On Jul 18, 2018, at 06:21, Hoggins! <fucks...@wheres5.com>
wrote:
There was a new update for Fedora 28 with
MariaDB 10.2.16, and the
problem is gone, so it was probably on their
side, although I can't seem
to find any relevant entry in the Changelog
that would explain that.
Probably a distro-specific issue.
Cool. Thank you for the update!
Cheers!
|----------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer
|
| | Paravel Systems
|
|----------------------------------------------------------------------|
| A room without books is like a body without a soul.
|
| -- Cicero
|
|----------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
