I tried it ; it doesn't work.
é ë è results into Ú Þ Ù standard, & using htmlentities
é ë è results into é è ë using htmlspecialchars
é ë è results into %E9%20%E8%20%EB using rawlurlencode
The charset ISO-8859-1 (western europe) is supported
in my apache, php, and on the global win
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
rawurlencode was originally intended for URLs, but all it does is encode
certian characters- it can be used for anything, and if the percentage of
characters is low enough, the returned string is smaller than that which is
returned by base64_encode,
the problem is, there is already an application running
(written in VB) using that ms sql server ; so i must find a way
to enter the characters in the db in a proper way...
isn't rawurlencode supposed to be used for urls?
i'm just talking about a plain text string...
is there anybody else who got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
can you do a rawurlencode() on the data before you put it in the DB, and a
rawurldecode when you suck it out? It's a hack, but it would prolly work
fine.
On Thursday 27 March 2003 09:46 am, Filip De Graeve wrote:
> Hello,
>
> Using PHP 4.3.1 on a W
4 matches
Mail list logo