Обсуждение: hints in 1.12.0 Beta 1 (rev: 8328) do not honour UTF-8
Hello, when hints are displayed, the UTF-8 Meta-Tag within those hint-htmls is not honoured. So all Umlaut are displayed ugly. Harald -- GHUM Harald Massa persuadere et programmare Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 no fx, no carrier pigeon - Using PostgreSQL is mostly about sleeping well at night.
bummer... OS = Windows 7 German -------------------------- Hello, when hints are displayed, the UTF-8 Meta-Tag within those hint-htmls is not honoured. So all Umlaut are displayed ugly. Harald -- GHUM Harald Massa persuadere et programmare Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 no fx, no carrier pigeon - Using PostgreSQL is mostly about sleeping well at night. -- GHUM Harald Massa persuadere et programmare Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 no fx, no carrier pigeon - Using PostgreSQL is mostly about sleeping well at night.
On Tue, Jun 8, 2010 at 12:53 PM, Massa, Harald Armin <chef@ghum.de> wrote: > Hello, > > when hints are displayed, the UTF-8 Meta-Tag within those hint-htmls > is not honoured. So all Umlaut are displayed ugly. Hmm, guess we need to use entity codes instead. Care to work up a patch? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company
>> when hints are displayed, the UTF-8 Meta-Tag within those hint-htmls >> is not honoured. So all Umlaut are displayed ugly. > > Hmm, guess we need to use entity codes instead. Care to work up a patch? > It is within my capabilities to recode those .html files, can do and submit. But is that an okay solution? Esp. since source-readability of languages like .cz really goes down when using encoded entitites... I think something in the range of "hey, wxHTMLWindow, everything we feed is UTF-8" would be more stable... (if that exists) Harald -- GHUM Harald Massa persuadere et programmare Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 no fx, no carrier pigeon - Using PostgreSQL is mostly about sleeping well at night.
On Tue, Jun 8, 2010 at 1:55 PM, Massa, Harald Armin <chef@ghum.de> wrote: >>> when hints are displayed, the UTF-8 Meta-Tag within those hint-htmls >>> is not honoured. So all Umlaut are displayed ugly. >> >> Hmm, guess we need to use entity codes instead. Care to work up a patch? >> > > It is within my capabilities to recode those .html files, can do and submit. > > But is that an okay solution? Esp. since source-readability of > languages like .cz really goes down when using encoded entitites... > > I think something in the range of "hey, wxHTMLWindow, everything we > feed is UTF-8" would be more stable... (if that exists) I assumed we were doing that anyway - after all, Hiroshi hasn't complained that it doesn't like Japanese text :-) Is the HTML *actually* UTF-8? I assume it hasn't just got munged into something else by someones editor? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company
>> I think something in the range of "hey, wxHTMLWindow, everything >we feed is UTF-8" would be more stable... (if that exists) > > I assumed we were doing that anyway - after all, Hiroshi hasn't > complained that it doesn't like Japanese text :-) I would have assumed that UTF-8 as default. too, esp. as the Query-Window also uses UTF-8. Maybe Hiroshi does not longer need the hints and has switched them off? :):) > Is the HTML *actually* UTF-8? I assume it hasn't just got munged into > something else by someones editor? I opened the HTML with Firefox, it looks fine. I opened the HTML with SCITE, switched to UTF-8, it looked fine (also checked the .cz files, could not read, but looked fine) ... I just used SCITE to save those files as "UTF-8 with BOM", and: CHAKKA, pgAdmin shows great HTML, with ü and ä and all... So it would be enough to resave those files with BOM.... Harald -- GHUM Harald Massa persuadere et programmare Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 no fx, no carrier pigeon - Using PostgreSQL is mostly about sleeping well at night.
On Tue, Jun 8, 2010 at 2:20 PM, Massa, Harald Armin <chef@ghum.de> wrote: > ... I just used SCITE to save those files as "UTF-8 with BOM", and: > CHAKKA, pgAdmin shows great HTML, with ü and ä and all... > > So it would be enough to resave those files with BOM.... There's a fairly high chance they will get lost upon the next edit. Which file was causing problems for you? encoding-ascii.html seems to display properly here, and looking at the filesystem, only multiple.html is not recognised as UTF-8, but it doesn't seem to include any umlauts anyway. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company
There's a fairly high chance they will get lost upon the next edit.
> So it would be enough to resave those files with BOM....
I fear the same :(
Which file was causing problems for you? encoding-ascii.html seems to
display properly here, and looking at the filesystem, only
problem is manifesting itself with
docs\de_DE\hints\instrumentation.html
WHEN it pops up as an "error" like "your server is missing instrumentation...."
Maybe that is a different call to the hints-window?
Beste wishes
Harald
--
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
Using PostgreSQL is mostly about sleeping well at night.
On Wed, Jun 9, 2010 at 10:04 AM, Massa, Harald Armin <chef@ghum.de> wrote: >> >> > So it would be enough to resave those files with BOM.... >> >> There's a fairly high chance they will get lost upon the next edit. >> > I fear the same :( > >> >> Which file was causing problems for you? encoding-ascii.html seems to >> display properly here, and looking at the filesystem, only > > problem is manifesting itself with > docs\de_DE\hints\instrumentation.html > WHEN it pops up as an "error" like "your server is missing > instrumentation...." > Maybe that is a different call to the hints-window? Different call, same interface. And the API certainly doesn't require the caller to specify the encoding. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company
> problem is manifesting itself withDifferent call, same interface. And the API certainly doesn't require
> docs\de_DE\hints\instrumentation.html
> WHEN it pops up as an "error" like "your server is missing
> instrumentation...."
> Maybe that is a different call to the hints-window?
the caller to specify the encoding.
so what chances to fix are there? Shall I run recode->htmlentities over those files and send them to you, or do you see chances to force the detection of UTF-8 by the wxWidget?
Harald
--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
Using PostgreSQL is mostly about sleeping well at night.
On Thu, Jun 10, 2010 at 10:19 AM, Massa, Harald Armin <chef@ghum.de> wrote: >> > problem is manifesting itself with >> > docs\de_DE\hints\instrumentation.html >> > WHEN it pops up as an "error" like "your server is missing >> > instrumentation...." >> > Maybe that is a different call to the hints-window? >> >> Different call, same interface. And the API certainly doesn't require >> the caller to specify the encoding. > > so what chances to fix are there? Shall I run recode->htmlentities over > those files and send them to you, or do you see chances to force the > detection of UTF-8 by the wxWidget? I don't have time to look in depth right now, but maybe Ashesh can take a look at the code and see if there is anything obvious that could be done to properly detect the encoding. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company
Le 10/06/2010 11:26, Dave Page a écrit : > On Thu, Jun 10, 2010 at 10:19 AM, Massa, Harald Armin <chef@ghum.de> wrote: >>>> problem is manifesting itself with >>>> docs\de_DE\hints\instrumentation.html >>>> WHEN it pops up as an "error" like "your server is missing >>>> instrumentation...." >>>> Maybe that is a different call to the hints-window? >>> >>> Different call, same interface. And the API certainly doesn't require >>> the caller to specify the encoding. >> >> so what chances to fix are there? Shall I run recode->htmlentities over >> those files and send them to you, or do you see chances to force the >> detection of UTF-8 by the wxWidget? > > I don't have time to look in depth right now, but maybe Ashesh can > take a look at the code and see if there is anything obvious that > could be done to properly detect the encoding. > Some time ago, I recoded in UTF-8 all the french hints. And it did work. -- Guillaumehttp://www.postgresql.frhttp://dalibo.com