t;
> -Original Message-
> From: Richard Quadling [mailto:rquadl...@gmail.com]
> Sent: Tuesday, April 12, 2011 2:59 PM
> To: Eli Orr
> Cc: php-general@lists.php.net
> Subject: Re: [PHP] Eliminatimg PHP UTF-8 BOM in a returned stream to a Mobile
> App
>
> On 12 April 2011 1
esday, April 12, 2011 2:59 PM
To: Eli Orr
Cc: php-general@lists.php.net
Subject: Re: [PHP] Eliminatimg PHP UTF-8 BOM in a returned stream to a Mobile
App
On 12 April 2011 12:50, Richard Quadling wrote:
> On 12 April 2011 11:59, Eli Orr wrote:
>>
>> Hi Richard,
>>
>> Tha
] Eliminatimg PHP UTF-8 BOM in a returned stream to a Mobile
App
On 12 April 2011 11:59, Eli Orr wrote:
>
> Hi Richard,
>
> Thanks.
> Indeed, that is the case - I've included a code that has UTF-8 string
> contants -so I guess the PHP parser set the UTF-8 mode to ON so that the
&
Thanks
>>
>> Eli
>>
>> -Original Message-
>> From: Richard Quadling [mailto:rquadl...@gmail.com]
>> Sent: Tuesday, April 12, 2011 12:45 PM
>> To: Eli Orr
>> Cc: php-general@lists.php.net
>> Subject: Re: [PHP] Eliminatimg PHP UTF-8 BOM in
il.com]
> Sent: Tuesday, April 12, 2011 12:45 PM
> To: Eli Orr
> Cc: php-general@lists.php.net
> Subject: Re: [PHP] Eliminatimg PHP UTF-8 BOM in a returned stream to a Mobile
> App
>
> 2011/4/12 Eli Orr :
>> Dear PHP Gurus,
>>
>> I would like to Eliminate the
roper
3 bytes offset.
Anyhow I was looking for a service to control that behaviour.
Thanks
Eli
-Original Message-
From: Richard Quadling [mailto:rquadl...@gmail.com]
Sent: Tuesday, April 12, 2011 12:45 PM
To: Eli Orr
Cc: php-general@lists.php.net
Subject: Re: [PHP] Eliminatimg PHP
2011/4/12 Eli Orr :
> Dear PHP Gurus,
>
> I would like to Eliminate the 3 UTF-8 BOM enforced on my returned BLOB:
>
> The PHP server adds utf-8 BOM (UTF-8 Byte Order Mark - in the beginning of
> UTF-8 files) which
> consists of three bytes: EF BB BF.
>
> The Mobile App served by the server Does
Dear PHP Gurus,
I would like to Eliminate the 3 UTF-8 BOM enforced on my returned BLOB:
The PHP server adds utf-8 BOM (UTF-8 Byte Order Mark - in the beginning of
UTF-8 files) which
consists of three bytes: EF BB BF.
The Mobile App served by the server Does not need that. How can I elimi
Tom Worster wrote:
Because, I thought, HTML files were basically just text files with
different file extensions, and that those other characters would not
store or display properly if saved in .txt format. Was I mistaken?
yes. see http://www.w3.org/TR/html401/charset.html
which says that html
The consensus seems to be that the proposed "ifset()" and "ifempty()"
functions are more effort than they are worth. What I'd like to know
is, why "empty()" still exists when every time I turn around, the
mentors I turn to locally tell me not to use it, to use "isset()"
instead. Because empty()
On 4/30/09 6:15 PM, "Reese" wrote:
> Tom Worster wrote:
>
>> why use SGML character entity references in a utf-8 file or stream? can't
>> you just put the character in the file?
>
> Because, I thought, HTML files were basically just text files with
> different file extensions, and that those ot
It'd be a hassle to just remove a function from a language, I suppose...
On Thu, Apr 30, 2009 at 6:15 PM, Reese wrote:
> Tom Worster wrote:
>
>> why use SGML character entity references in a utf-8 file or stream? can't
>> you just put the character in the file?
>
> Because, I thought, HTML files
Tom Worster wrote:
why use SGML character entity references in a utf-8 file or stream? can't
you just put the character in the file?
Because, I thought, HTML files were basically just text files with
different file extensions, and that those other characters would not
store or display properly
On 4/29/09 6:52 PM, "Reese" wrote:
> Tom Worster wrote:
>> On 4/28/09 4:05 PM, "Reese" wrote:
>>
>>> Granted, this isn't a PHP question but I'm curious, how does UTF-8 solve
>>> this display issue?
>>
>> if we're talking about web browsers, they are quite good at automatically
>> choosing font
Tom Worster wrote:
On 4/28/09 4:05 PM, "Reese" wrote:
Granted, this isn't a PHP question but I'm curious, how does UTF-8 solve
this display issue?
if we're talking about web browsers, they are quite good at automatically
choosing fonts that can display the unicode characters it finds in a pa
On 4/28/09 4:05 PM, "Reese" wrote:
> Granted, this isn't a PHP question but I'm curious, how does UTF-8 solve
> this display issue?
if we're talking about web browsers, they are quite good at automatically
choosing fonts that can display the unicode characters it finds in a page.
--
PHP Gene
Tom Worster wrote:
On 4/27/09 4:25 PM, "PJ" wrote:
Exactly what are the advantages of using utf-8? How will it solve my
problem?
actually, i have no idea because i have no idea what problem you are trying
to solve and i apologize for presumptuous. i presumed that you have a php
app with a bu
PJ wrote:
Tom Worster wrote:
On 4/27/09 4:25 PM, "PJ" wrote:
Exactly what are the advantages of using utf-8? How will it solve my
problem?
actually, i have no idea because i have no idea what problem you are trying
to solve and i apologize for presumptuous. i presumed that you have a
Tom Worster wrote:
> On 4/27/09 4:25 PM, "PJ" wrote:
>
>
>> Exactly what are the advantages of using utf-8? How will it solve my
>> problem?
>>
>
> actually, i have no idea because i have no idea what problem you are trying
> to solve and i apologize for presumptuous. i presumed that you h
On 4/27/09 4:25 PM, "PJ" wrote:
> Exactly what are the advantages of using utf-8? How will it solve my
> problem?
actually, i have no idea because i have no idea what problem you are trying
to solve and i apologize for presumptuous. i presumed that you have a php
app with a bunch of data in mysq
f that
> would be of interest.
>
> here, at least, are the web pages i referred to:
>
> http://www.phpwact.org/php/i18n/utf-8
> http://www.phpwact.org/php/i18n/charsets
> http://www.phpwact.org/php/i18n/utf-8/mysql
> http://devlog.info/2008/08/24/php-and-unicode-utf-8/
>
p/i18n/utf-8/mysql
http://devlog.info/2008/08/24/php-and-unicode-utf-8/
http://www.sitepoint.com/blogs/2006/08/09/scripters-utf-8-survival-guide-sli
des/
http://www.nicknettleton.com/zine/php/php-utf-8-cheatsheet
http://www.cs.tut.fi/~jkorpela/chars.html
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
I think you should switch to utf8-general-ci all the way.
Since I have to use a number of Western languages that have those
annoying accents on many characters, I am already finding some
annoyances in my code results; like having to enter the á type of
stuff in inputs for searches & queries.
MySql db is set up for InnoDB with latin1_swedish_ci for Collati
haliphax wrote:
On Mon, Mar 30, 2009 at 12:34 PM, Merlin Morgenstern
wrote:
HI there,
I now compiled php with zend multibyte. The trouble with the extra
characters is now gone, but all special characters are now replaced with a
questionmark! The document type shows utf-8, but somehow php seems
On Mon, Mar 30, 2009 at 12:34 PM, Merlin Morgenstern
wrote:
> HI there,
>
> I now compiled php with zend multibyte. The trouble with the extra
> characters is now gone, but all special characters are now replaced with a
> questionmark! The document type shows utf-8, but somehow php seems not to
>
HI there,
I now compiled php with zend multibyte. The trouble with the extra
characters is now gone, but all special characters are now replaced with
a questionmark! The document type shows utf-8, but somehow php seems not
to pars the content OK.
Does nobody have the same problem?
Regards,
On 3/26/09 11:36 AM, "Nisse Engström" wrote:
> On Wed, 25 Mar 2009 11:32:42 +0100, Nisse Engström wrote:
>
>> On Tue, 24 Mar 2009 08:15:35 -0400, Tom Worster wrote:
>>
>>> strtr() with three parameters is certainly unsafe. but my tests are showing
>>> that it may be ok with two parameters if th
On Wed, 25 Mar 2009 11:32:42 +0100, Nisse Engström wrote:
> On Tue, 24 Mar 2009 08:15:35 -0400, Tom Worster wrote:
>
>> strtr() with three parameters is certainly unsafe. but my tests are showing
>> that it may be ok with two parameters if the strings in the second parameter
>> are well formed ut
thanks for the info.
i'll leave 2-param uses of strtr in my code alone. i have a replacement for
the 3-param version.
btw: i have quite a long checklist of stuff to do when upgrading code for
utf-8, including notes on about 100 functions. do you think it would be
worth putting it on a wiki somewh
On Tue, 24 Mar 2009 08:15:35 -0400, Tom Worster wrote:
> On 3/23/09 2:02 PM, "Tom Worster" wrote:
>
>> i havea general replacement or workaround for every php function in my code
>> that i know to be utf-8-unsafe. except one: strtr().
>
> strtr() with three parameters is certainly unsafe. but m
On 3/23/09 2:02 PM, "Tom Worster" wrote:
> i havea general replacement or workaround for every php function in my code
> that i know to be utf-8-unsafe. except one: strtr().
strtr() with three parameters is certainly unsafe. but my tests are showing
that it may be ok with two parameters if the s
i havea general replacement or workaround for every php function in my code
that i know to be utf-8-unsafe. except one: strtr().
the only ideas i have to implement strtr in php with known utf-8-safe php
functions would be rather inefficient.
any ideas, suggestions, pointers? or maybe you're bette
Hi,
I'm trying to load an external rss feed into a DomDocument, the feed
says it's uft-8 but DomDocument rightly disagrees. This causes a
warning: Input is not proper UTF-8, indicate encoding ! Bytes: 0xA3 0x36
0x35 0x20
Is there any way I can get DomDocument to skip that part of the feed.
Hi,
I'm trying to load an external rss feed into a DomDocument, the feed
says it's uft-8 but DomDocument rightly disagrees. This causes a
warning: Input is not proper UTF-8, indicate encoding ! Bytes: 0xA3 0x36
0x35 0x20
Is there any way I can get DomDocument to skip that part of the feed.
you don't have to have your files in utf-8 for it to work, just the
browser header.
although any utf-8 characters in your files will look funky. it just
depends where the content comes from... you could always use ®
for the (r) registered symbol for example.
i'd be more apt to figuring out how to
the user agents in question are various mobile phones, which as you
might guess are premature technology and have their own ways with
things.
here is an example posting from a Samsung D600 which insists on
posting form data in UTF-8 even though i serve it ISO-8859-1 and it
claims to support all ch
On Jan 8, 2008 1:31 PM, tedd <[EMAIL PROTECTED]> wrote:
> Last night I read a chapter in the book "Core Web Application
> Development with PHP and MYSQL" by Wandschneider who said basically
> that -- a good read, btw.
I'm guess it was his name which comprised the first chapter.
--
Daniel P.
At 11:57 AM +0200 1/8/08, Arvids Godjuks wrote:
To author:
You'r going the wrong way.
Make your page utf-8, all text on it. Set utf-8 encoding and treat all
incoming data as UTF-8. If some agent (definetly not some browser - they all
know UTF-8) doesn't understand that (that could be some "hacke
Olav Mørkrid wrote:
> i specify iso-8859-1 in both header and body:
>
> accept-charset="iso-8859-1">
Have you checked 1) what the webserver sends in the header and 2) what
the browser actually uses? I'm pretty certain I've had issues where
the meta tags were fine, but the server overrode me s
To author:
You'r going the wrong way.
Make your page utf-8, all text on it. Set utf-8 encoding and treat all
incoming data as UTF-8. If some agent (definetly not some browser - they all
know UTF-8) doesn't understand that (that could be some "hacker" writing
it's own bot) - that's his problem. The
Olav Mørkrid wrote:
i specify iso-8859-1 in both header and body:
if two different people post the norwegian phrase "Godt nytt år"
(happy new year), it may appear in the following variations:
[CONTENT_TYPE] => application/x-www-form-urlencoded;charset=iso-8859-1
$_POST["input"] = "Godt nytt
I have to ask... WHY are you forcing ISO-8859-1? If anything, you should be
forcing UTF-8. Then you can send, receive, and store data in UTF-8 ad cover
most human languages without having to change character set.
On Monday 07 January 2008, Olav Mørkrid wrote:
> i specify iso-8859-1 in both h
maybe look at iconv functions
but the content-type is the only thing i set, and it works 100%
fine. all javascripts, forms, etc. inherit it from the looks of it
properly.
On 1/7/08, Olav Mørkrid <[EMAIL PROTECTED]> wrote:
> i specify iso-8859-1 in both header and body:
>
>
>
>
> if two differe
i specify iso-8859-1 in both header and body:
if two different people post the norwegian phrase "Godt nytt år"
(happy new year), it may appear in the following variations:
[CONTENT_TYPE] => application/x-www-form-urlencoded;charset=iso-8859-1
$_POST["input"] = "Godt nytt år"
[CONTENT_TYPE] =>
>
>
> My experience is that this does not affect only the displayed
> characters, but the way the form fields are transported.
>
> But perhaps I am wrong,
> Iv
This works for me as well.
Put in utf-8 and you should be good to go.
You don't -technically- need to even change your database fields
Olav Mørkrid wrote:
hello
does php have any built-in functions to convert post data from
whatever format it arrives in to whatever format i wish?
example:
i use iso-8859-1 internally, and even specify
accept-charset=iso-8859-1 in my html, but some browsers (phones) send
utf-8 anyway.
do i hav
hello
does php have any built-in functions to convert post data from
whatever format it arrives in to whatever format i wish?
example:
i use iso-8859-1 internally, and even specify
accept-charset=iso-8859-1 in my html, but some browsers (phones) send
utf-8 anyway.
do i have to manually check if
Yes it will, trim() was given the option to specify other characters in
PHP 4.1.0.
Rember that it's a byte function, so single byte characters can be
handled, you just can't use it for multi-byte characters.
~ DM
Naz Gassiep escreveu:
Great! Thanks for the answer, that's very helpful. Will
Great! Thanks for the answer, that's very helpful. Will trim() work if I
specify charlists in the ASCII range? Not that I ever do, but just curious.
- Naz
Daniel Macedo wrote:
Hi Naz,
Any byte function is NOT safe for UTF-8.
trim() works properly with UTF-8 IF you don't specify the charlist
(
Hi Naz,
Any byte function is NOT safe for UTF-8.
trim() works properly with UTF-8 IF you don't specify the charlist
(second argument). This is because all whitespace characters are in the
ASCII range, and therefore it won't corrupt the UTF-8 string.
The explode() function will handle UTF-8 as
I've seen that, there is no mb_trim() that I can see.
- Naz.
adel wrote:
http://www.php.net/manual/en/ref.mbstring.php
On 8/3/07, Naz Gassiep <[EMAIL PROTECTED]> wrote:
The functions trim() and explode() appear to be munging multibyte UTF-8
strings. I can't find multibyte safe versions of t
http://www.php.net/manual/en/ref.mbstring.php
On 8/3/07, Naz Gassiep <[EMAIL PROTECTED]> wrote:
> The functions trim() and explode() appear to be munging multibyte UTF-8
> strings. I can't find multibyte safe versions of them in the manual, do
> they exist, or do I have to make my own?
> - Naz.
>
Naz Gassiep wrote:
The functions trim() and explode() appear to be munging multibyte
UTF-8 strings. I can't find multibyte safe versions of them in the
manual, do they exist, or do I have to make my own?
In what way are they munging the strings? I just tried with a bunch of
UTF-8 characters p
The functions trim() and explode() appear to be munging multibyte UTF-8
strings. I can't find multibyte safe versions of them in the manual, do
they exist, or do I have to make my own?
- Naz.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
I'm somewhat new to this stuff as well, so take this with a grain of salt...
Someone else was hinting at this, but more directly, try running
utf8_encode() on whatever part of your data that requires utf8 encoding.
In the case of your example, you could just utf8_encode the test get
variable.
Hello ppl,
I have a big prob.
I have a page which post some input.
This input can be UTF-8 like chinese or other utf-8 chars.
Also i need it to return UTF-8 and it has to be xml.
For some strange reason this isn't working.
Small example.
PHP Code:
'."\n";
print ''.$_GET['test'].''."\n";
?>
a
nt'l: +7 8362-468693
email:[EMAIL PROTECTED]
> -Original Message-
> From: Curt Zirzow [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 23, 2005 9:02 AM
> To: php-general@lists.php.net
> Subject: Re: [PHP] utf-8 in mysql but not outputting as utf-8 on web
>
>
On Thu, Dec 22, 2005 at 07:01:07PM -0800, jonathan wrote:
> I'm inserting some info into a mysql table which has the charset set
> to utf-8.
>
> When I do a select via the command-line from mysql, it looks like this:
> Clams and mussels with Dijon-cr�me fra�che-saffron sauce
>
> assuming this i
Have you read this article - http://www.phparch.com/sample.php?mid=57 .
jonathan wrote:
I'm inserting some info into a mysql table which has the charset set to
utf-8.
When I do a select via the command-line from mysql, it looks like this:
Clams and mussels with Dijon-crème fraîche-saffron sa
Hello Jonathan,
You probably don't have php5 compiled with mbstrings enabled, if you
have complied php5 with iconv instead you can try
iconv('utf-8' , 'html', $string);
I don't know what to recommend if you don't have any of these complied
into php5.
Best regards,
Kenneth
--
jonathan wro
Hello,
why not simply convert the text to html
mb_convert_encoding($string, 'html', 'utf-8');
Best regards,
Kenneth
jonathan wrote:
I'm inserting some info into a mysql table which has the charset set
to utf-8.
When I do a select via the command-line from mysql, it looks like this:
Clam
I'm inserting some info into a mysql table which has the charset set
to utf-8.
When I do a select via the command-line from mysql, it looks like this:
Clams and mussels with Dijon-crème fraîche-saffron sauce
assuming this is coming out in your email client ok, it should look
good.
On a web
So, I'm parsing some XML and dumping some stuff to a web-site.
The character-encoding for the HTML of the output has already been set
by headers() to ISO-8859-1 for me, and I'm stuck with that.
So be it.
The XML has this at the top:
We don't (and won't soon) have recode nor iconv installed, bu
--- Jiøí Nìmec <[EMAIL PROTECTED]> wrote:
> I have problem with encoding UTF-8 and PHP scripts. Scripts send
> information about encoding and this disallow send HTTP headers. Is
> possibility to solve this problem?
I don't understand your question, but maybe this will help.
HTTP is encoded with I
Hello Jiri,
I'm not sure I understand your problem (I had some trouble with your English), but
have
you tried PHP's utf8_encode() and utf8_decode() functions? Check out the PHP manual
in your native language for more information on these functions.
Cheers,
Erik
On 15 Jan 2004 at 12:52, Ji ¡
On Thursday 15 January 2004 19:52, JiÅÃ NÄmec wrote:
> I have problem with encoding UTF-8 and PHP scripts. Scripts send
> information about encoding and this disallow send HTTP headers. Is
> possibility to solve this problem?
If I understand your problem correctly, the solution is to arrange your
Hello,
I have problem with encoding UTF-8 and PHP scripts. Scripts send
information about encoding and this disallow send HTTP headers. Is
possibility to solve this problem?
Jiri Nemec
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
There are 2 separate extenssions - iconv and recode
Michael Mulligan wrote:
Hi
So say I have some UTF-8 (not certain, but probably in UTF-8 format, I need
to check some more) encoded text. The text comes in encoded already, so it's
not an htmlspecialchars kind of quick fix. For instance, I get '
Hi
So say I have some UTF-8 (not certain, but probably in UTF-8 format, I need
to check some more) encoded text. The text comes in encoded already, so it's
not an htmlspecialchars kind of quick fix. For instance, I get 'ê' and I
want to output 'ê'--how do I convert from the two high ASCII charact
Hello!
I would appreciate if anybody could tell me how to use an utf8 encoded
string in a regular expression.
I have tried this
$string = "a username written in greek letters";
preg_match('#^[\w][\w0-9_]{2,39}$#', $string);
Which does not work, i have also tried to utf8_decode the string and pa
On Wed, 22 May 2002, Miguel Cruz wrote:
> For detection of encoding, perhaps you could include a hidden field with
> some shibboleth characters. Research how they are transformed by various
> encodings, and then just look at them to figure out what for that the rest
> of the data is in.
Yes,
For detection of encoding, perhaps you could include a hidden field with
some shibboleth characters. Research how they are transformed by various
encodings, and then just look at them to figure out what for that the rest
of the data is in.
miguel
On Wed, 22 May 2002, Peter Johansson wrote:
>
Hi all,
I've got a problem with character encoding in combination with a
FormMail-script (coded in PHP). Everything works fine as long as I stick
to ISO-8859-1 as charset, but when I call the script from pages that use
UTF-8 as encoding, special characters (e.g. those special chars with dots
and
74 matches
Mail list logo
