Le 10/06/2010 11:26, Dave Page a écrit :
> On Thu, Jun 10, 2010 at 10:19 AM, Massa, Harald Armin 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
On Thu, Jun 10, 2010 at 10:19 AM, Massa, Harald Armin 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?
>>
>> D
>
> > 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 requir
On Wed, Jun 9, 2010 at 10:04 AM, Massa, Harald Armin 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
>
>
> > 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
>
p
On Tue, Jun 8, 2010 at 2:20 PM, Massa, Harald Armin 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 los
>> 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. to
On Tue, Jun 8, 2010 at 1:55 PM, Massa, Harald Armin 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 capabilit
>> 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
On Tue, Jun 8, 2010 at 12:53 PM, Massa, Harald Armin 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
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
11 matches
Mail list logo
