Thread: [Phpwiki-talk] patches 496662, 496654, 496158 completed

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I added patches from the SF site #496662, 496654, 496158 into PhpWiki so 
they can be closed off. (I updated the requests with some notes for each 
but can't close them myself).

Carsten

Hello,

27 Dec 2001, 05:51:16, you wrote:

> I added patches from the SF site #496662, 496654, 496158 into PhpWiki so=
=20
> they can be closed off=2E (I updated the requests with some notes for each=
=20
> but can't close them myself)=2E

Just wondering, why not #496664 ?
Because  iso-8859-15 is theorically the only one western latin encoding
to correctly render the Euro symbol (=80), and Euro is now not so far :)
But maybe I am wrong?

Bye,

--=20
 S=2E
 delahaye@frjv=2Eorg

Hi,

Oh, just no time to look at that patch yet. :-)

I know nothing about iso-8859-15, and want to answer for myself some=20
questions about it. Also I would want to make sure that nothing else =
will=20
be affected by changing to iso-8859-15. (Also see=20
<http://phpwiki.sourceforge.net/phpwiki/Utf8Migration>.)

Questions like:
- What are all the differences between iso-8859-1 and iso-8859-15?
- Which browser software, versions, and operating systems know about=20
iso-8859-15, and which don't?
- Do we need to change all the source code files to iso-8859-15?
- What needs to be investigated to make sure PHP works with iso-8859-15?
- Does PHP need to be compiled in a special way to understand =
iso-8859-15?
- Do all the databases (MySQL, PostgreSQL, Mini SQL etc.) work with the=20=

euro symbol or should it be converted to &euro; or &#8364;?
- Will any code in WikiNameRegExp need to be updated? (The code which=20
allows accented letters to be used in BumpyWords)
- If not all browsers work with iso-8859-15, will it be sufficient to =
use=20
&euro; and/or &#8364;?

Carsten

On Friday, December 28, 2001, at 05:39  pm, S. Delahaye wrote:

> Hello,
>
> 27 Dec 2001, 05:51:16, you wrote:
>
>> I added patches from the SF site #496662, 496654, 496158 into PhpWiki =
so
>> they can be closed off. (I updated the requests with some notes for =
each
>> but can't close them myself).
>
> Just wondering, why not #496664 ?
> Because  iso-8859-15 is theorically the only one western latin =
encoding
> to correctly render the Euro symbol (=80), and Euro is now not so far =
:)
> But maybe I am wrong?
>
> Bye,
>
> --
>  S.
>  del...@fr...

Hello,

28 Dec 2001, 23:58:43, you wrote:

> Questions like:
> - What are all the differences between iso-8859-1 and iso-8859-15?

The  main difference is the support of the Euro symbol=2E There are also
some  little changes about Finnish & French (well, probably characters
rarely used in French, 'cause I neved had problems with iso-8859-1)=2E
See this page for more infos:
http://bearn=2Eeikonex=2Enet/cgi-bin/man2html/usr/share/man/man7/iso-8859-15=
=2E7=2Egz

> - Which browser software, versions, and operating systems know about=20
> iso-8859-15, and which don't?

As far as I know, all are currently supporting it, even Netscape 4 (in
its 4=2E7x versions, not tried with previous versions)=2E

> - Do we need to change all the source code files to iso-8859-15?

Only  where  the  charset  is  declared=2E  ISO-8859-15 is just a better
ISO-8859-1 :)

> - What needs to be investigated to make sure PHP works with iso-8859-15?

It works=2E

> - Does PHP need to be compiled in a special way to understand iso-8859-15?

No=2E Perhaps with PHP3 (again, not tested=2E=2E=2E), but not with PHP4=2E

> - Do all the databases (MySQL, PostgreSQL, Mini SQL etc=2E) work with the=
=20
> euro symbol or should it be converted to &euro; or &#8364;?

I  don't know that=2E I never had problems with the euro symbol on MySQL
and  PGSQL,  but I must admit that I did not look precisely how it was
handled=2E

> - Will any code in WikiNameRegExp need to be updated? (The code which=20
> allows accented letters to be used in BumpyWords)

Maybe=2E Actually, it does not work :
in  http://phpwiki=2Esourceforge=2Enet/phpwiki/=80 , the =80 is interpreted =
as
"=E2=82=AC"=2E  Don't  know  if  it'll  remain  with  a  good encoding chars=
et
declared in the headers=2E Maybe yes, maybe not :)

> - If not all browsers work with iso-8859-15, will it be sufficient to use=
=20
> &euro; and/or &#8364;?

&euro;  is  not  supported by all browsers (Netscape 4=2E6 and less, for
example, but it's really old)=2E Maybe &#8364, but I doubt of it=2E
But  all  recent  (or  not  recent, see Netscape 4=2E7 :) ), browsers do
support iso-8859-15=2E

Bye,

--=20
 S=2E
 delahaye@frjv=2Eorg

Thread: [Phpwiki-talk] patches 496662, 496654, 496158 completed

phpwiki-talk