Colin Guthrie wrote:
> UTF-8 works by using special bits at the MSB end of the byte to say,
> "I can't represent this character in one byte, I need to use 2 bytes
> (or 3 bytes)" (and maybe also 4? can't remember of the top of my
> head).
Yep, a UTF8 character is 1 to 4 bytes.
/Per Jessen, Zür
At 12:36 PM -0500 9/28/07, Edward Vermillion wrote:
My question was more mental prodding than anything else. The OP had
a function to convert incoming text into UTF-8 before they did
anything with it. A couple of folks said that was unnecessary, if
you set your form to UTF-8 your incoming data
Edward Vermillion wrote:
> On Sep 28, 2007, at 1:05 PM, Per Jessen wrote:
>>
>> Ed, your question was a good one, but so was my answer. In my case,
>> I don't cater to an open community, but to a closed one. If you're
>> not authenticated, you're not getting anywhere to start with. If you
>> s
On Sep 28, 2007, at 1:05 PM, Per Jessen wrote:
Edward Vermillion wrote:
I pretty much gave up on the thread when I got the reply along the
lines of "if it breaks something it's their problem, not mine".
Ed, your question was a good one, but so was my answer. In my case, I
don't cater to an
Edward Vermillion wrote:
> I pretty much gave up on the thread when I got the reply along the
> lines of "if it breaks something it's their problem, not mine".
Ed, your question was a good one, but so was my answer. In my case, I
don't cater to an open community, but to a closed one. If you're
On Sep 28, 2007, at 11:34 AM, tedd wrote:
At 2:01 PM -0500 9/27/07, Edward Vermillion wrote:
So back to my original question, what breaks if you're *expecting*
UTF-8 and you don't *get* UTF-8?
Ed
Isn't UTF-8 the big fish here?
Sure there' UTF-16 and larger, but everything else is a subse
At 2:01 PM -0500 9/27/07, Edward Vermillion wrote:
So back to my original question, what breaks if you're *expecting*
UTF-8 and you don't *get* UTF-8?
Ed
Isn't UTF-8 the big fish here?
Sure there' UTF-16 and larger, but everything else is a subset of
UTF-8, is it not?
So, what's the probl
Edward Vermillion wrote:
> ... and you can guarantee that any data coming into your site comes
> from your form?!? WOW!!!
>
> ;)
>
> So back to my original question, what breaks if you're *expecting*
> UTF-8 and you don't *get* UTF-8?
As long as my server isn't vulnerable to it, I couldn't care
On Sep 27, 2007, at 1:49 PM, Per Jessen wrote:
Edward Vermillion wrote:
But what happens if you get data that's *not* UTF-8? Just because
your html/form is set to UTF-8 doesn't mean that all your incoming
data will be UTF-8.
Yes it does. If your HTML page was sent in UTF-8, any request
orig
On 9/27/07, Edward Vermillion <[EMAIL PROTECTED]> wrote:
> But what happens if you get data that's *not* UTF-8? Just because
> your html/form is set to UTF-8 doesn't mean that all your incoming
> data will be UTF-8.
just my experience, but as long as it has the meta tag w/ utf-8 in it,
the browse
Edward Vermillion wrote:
> But what happens if you get data that's *not* UTF-8? Just because
> your html/form is set to UTF-8 doesn't mean that all your incoming
> data will be UTF-8.
Yes it does. If your HTML page was sent in UTF-8, any request
originating from that page will also be in UTF8.
Colin Guthrie wrote:
> Per Jessen wrote:
>> I work almost exclusively in UTF-8 (language irrelevant), but I've
>> never had to do any of the above. The mb_convert_encoding()
>> fromUTF-8 to UTF-8 doesn't seem to make much sense?
>
> I agree. Provided you HTML is dished out with UTF-8 in the doct
On Sep 27, 2007, at 10:09 AM, Colin Guthrie wrote:
Per Jessen wrote:
David Christopher Zentgraf wrote:
Your biggest problem will be if you accept any kind of user input
which could be in any kind of language.
Depending on your server configuration you'll probably have some
serious cleaning a
13 matches
Mail list logo
