-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Sunday 18 of April 2004 15:02, Alexander M. Turek wrote:

Hi there,

Michal Cihar wrote:

...

since I started to use utf-8 on some machines I noticed that we have some iso-8859-1 characters in ChangeLog. Wouldn't be better to make it utf-8 encoded?

... so your name can be encoded correctly? :o)

Yes :-) ... but currently there are already translators names, which are also non ASCII.

Äçtùálly, Î äm nòt wørkïng wîth ÜTF-8 rïght nôw, bút sînçe Ï ònly néèd ÄSCÍÌ chärs fôr mÿ nàmê and mÿ lög mëssàgês, Î hävè nö ôbjèçtíôns.

- -- Regards Michal Čihař http://cihar.com

On 19.04.2004 01:54 +0200, Alexander M. Turek wrote:

Hi Michal,

Michal Cihar wrote:

...

On Sunday 18 of April 2004 15:02, Alexander M. Turek wrote:

...

Hi there,

Michal Cihar wrote:

...

since I started to use utf-8 on some machines I noticed that we have some iso-8859-1 characters in ChangeLog. Wouldn't be better to make it utf-8 encoded?

... so your name can be encoded correctly? :o)

Yes :-)

So in Documentation.html and translators.html where you could use HTML entities, why didn't you use these characters there? ;-)

This was not primary reason why I'm asking. It was that vim each time I open ChangeLog says it was converted :-)

On 19.04.2004 09:09 -0400, Marc Delisle wrote:

Michal, would there be an impact for the conversion:

• users looking at the ChangeLog

You will allways have different users with different charsets. Some viewers can detect utf-8, Linux distros are currently moving towards utf-8 (Redhat has it as default for some time, SUSE had it optionally, now also default, current Debian policy also requires utf-8 files).

It's simply change that will happen sometimes, the only question is when :-)

• when I copy it on the web page for releases

http://sourceforge.net/project/shownotes.php?release_id=220762

This should not be a problem, you browser should convert it to html entities, which are hopefully handled okay by sf.

Hi there,

Marc Delisle wrote:

Ok let's try it! Can you commit the file?

Done. I hope iconv did a good job on it :-)

Regards,

Hi Olivier and list,

Olivier Mueller wrote:

...

...

Ok let's try it! Can you commit the file?

Done. I hope iconv did a good job on it :-)

it did but of course the browser still thinks it's "normal iso text": http://admin.omnis.ch/mysql-dev/ChangeLog (looks wrong here with mozilla, but fine with opera!)

Apache just has to send a correct Content-Type header. Could this be done with a proper .htaccess file?

If not, we could build a small php script for this purpose:

<?php

header('Content-Type: text/plain; charset=utf-8'); readfile('./ChangeLog');

?>

to make it looks correct, default content type at apache level should be changed to utf8... no sure if it's really the best way... ?

Should work, too.

I vote for a 7bit changelog :)

Is this why you avoid writing the umlaut in your last name? Be proud of it! :o)

Regards,

Hi

On 20.04.2004 01:04 +0200, Olivier Mueller wrote:

On Tue, 2004-04-20 at 00:16 +0200, Alexander M. Turek wrote:

...

Apache just has to send a correct Content-Type header. Could this be done with a proper .htaccess file?

maybe, but would be-apache only, and work only where .htaccess files are allowed, etc.

...

If not, we could build a small php script for this purpose:

<?php header('Content-Type: text/plain; charset=utf-8'); readfile('./ChangeLog'); ?>

Too much complicated and IMHO not needed.

ok why not, but it was fine before as simple .txt, so why this change?

oh well, spent the whole day on £&%@*& charset problems (pages supposed to work in english, french & arabic),

That's what unicode is supposed to solve :-)

so I will stick to 7bit for the changelog anyway, so do what you want :)

:-)

...

...

to make it looks correct, default content type at apache level should be changed to utf8... no sure if it's really the best way... ?

Should work, too.

sure, but I guess that most of pma users are not root, so not allowed to do that :)

You usually can add .htaccess and you allways can select charset in browser (thats what I have to do anyway, since my default is not iso-8859-1 :-)).

...

...

I vote for a 7bit changelog :)

Is this why you avoid writing the umlaut in your last name? Be proud of it!

with "ue" I know it will always look fine everywhere... :)

We had iso-8859-1 one, so change to 7bit would be also needed :-)

On 20.04.2004 14:26 +0200, Olivier Mueller wrote:

yes, that's also what I understood :) I even begin to like it, but it took some work until everything was converted and worked (the best were tables with mixed iso-8859 and utf8 data...)

I don't like mixed data and that's why I started this discussion :-)

yep, but isn't iso-8859-1 default for the most of us? :) for example on a vanilly suse 9.0 here:

om@linux:~> locale charmap ISO-8859-1

for 9.1 it is:

$ locale charmap UTF-8

:-) .. anyway for me default was iso-8859-2...

Alexander M. Turek a écrit:

Hi Olivier & list,

Olivier Mueller wrote:

...

On Tue, 2004-04-20 at 00:16 +0200, Alexander M. Turek wrote:

...

Apache just has to send a correct Content-Type header. Could this be done with a proper .htaccess file?

maybe, but would be-apache only, and work only where .htaccess files are allowed, etc.

You got me wrong: I wanted to use this .htaccess file for our website at SF, not for the distribution kit... :-)

Regards,

In the kit, Documentation.html has a link to ChangeLog located in the kit.

Marc