[Clipart] character coding

[Jonadab the Unsightly One]

"Stephen Silver" <ocalocal at btinternet.com> writes:

> Jonadab wrote:
>
>> If there is an extra step it can take that will convert those
>> form-entered metadata into UTF8, would that solve the problem?
>
> Well, there appear to be two problems.  Form-entered metadata does
> need to be converted to UTF-8, but that won't fix the problem of
> metadata in the uploaded file somehow being converted to Latin-1.

Do we know that the latter is happening?  Isn't it possible that all
the metadata causing the problems are form-entered?  I think we should
solve the problem we know we have first, and then see if there's still
a problem.

> I think you can probably cheat with the form-entered metadata by using
>
>   accept-charset="UTF-8 US-ASCII"
>
> in the <form> tag, then you should only receive UTF-8.  But very old
> browsers may not know about accept-charset, and might send the data
> in some other encoding.

I will try this and see if the problem goes away.  How "very old" does
a browser have to be to ignore this?  Are we talking the Netscape 3
kind of very old, or are we talking IE5?

> By the way, if you click the W3C XHTML 1.0 link at the bottom of the
> upload page, the validator finds some problems: 

Oh, dear.  I thought I knew XHTML pretty well by now...

> <input> elements should be empty, 

Indeed, they should all be empty...  [checks]
Aha, I see the problem.  That one's an easy fix.

> and the file should start with the XML declaration (rather than a
> line feed).

That line feed is present in the framework I'm getting from shell.php

-- 
$;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b->()}}
split//,"ten.thgirb\@badanoj$/ --";$\=$ ;-> ();print$/