Re: Encoding problem when migration hsqldb->Firebird

sberg wrote > ... > see ; > "Firebird: migration from HSQLDB does not respect language-specific > characters" for how this has been addressed for column names (but > apparently not for table names) > ... Indeed, I commented here: https

Re: Encoding problem when migration hsqldb->Firebird

On 30/01/2019 10:13, Julien Nabet wrote: I noticed that if "content.xml" from odb file contained encoded characters like this "Formulär" script/database contained characters with \u... How to convert \u... to the "real" character? see

Re: Encoding problem when migration hsqldb->Firebird

Kaganski Mike wrote > ... > It might be some artifact of the tracing machinery, which e.g. could use > a font without the codepoint, or output all non-ascii chars like that? > because \u00c5 is a valid UTF-18 escape sequence [1] (U+00C5, [2]), and > so "\u00c5r" maybe is just "År" in the real st

Re: Encoding problem when migration hsqldb->Firebird

On 30.01.2019 14:00, Kaganski Mike wrote: > ... a valid UTF-18 escape sequence ... Why not, if there is UTF-9? :-) Sorry for the typo. -- Best regards, Mike Kaganski ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedeskt

Re: Encoding problem when migration hsqldb->Firebird

Hi Julien, On 30.01.2019 12:13, Julien Nabet wrote: > Giving a try to tdf#123020 (which is finally a dup), I added some traces > and noticed this kind of string (OUString): > "CREATE CACHED TABLE "\u00c5r"("\u00c5r" INTEGER NOT NULL PRIMARY KEY)" > ... > How to convert \u... to the "real" charact

Encoding problem when migration hsqldb->Firebird

Hello, Giving a try to tdf#123020 (which is finally a dup), I added some traces and noticed this kind of string (OUString): "CREATE CACHED TABLE "\u00c5r"("\u00c5r" INTEGER NOT NULL PRIMARY KEY)" It seems it prevents from migration process (hsqldb->Firebird) Here is the location where it's gen