William A. Rowe, Jr. wrote:
Nick Kew wrote:
So what does the HTML spec have to say? The submission element
does include the accept-charset attribute, perhaps that is what you are
looking for? Otherwise, if the user agents don't observe RFC 2388 then
you should really take that up with the use
Nick Kew wrote:
>
>> So what does the HTML spec have to say? The submission element
>> does include the accept-charset attribute, perhaps that is what you are
>> looking for? Otherwise, if the user agents don't observe RFC 2388 then
>> you should really take that up with the user agent vendors.
William, Nick,
William A. Rowe, Jr. wrote:
[...]
The reason your search was futile is that you want to focus on searching
internet-draft where there are proposals in this sphere. Also watch the
dependencies of the http draft, many of those have also evolved and are
beginning to solve the utf8
On 18 Oct 2008, at 20:22, William A. Rowe, Jr. wrote:
Comments inline; You painted this situation today with an overly
broad brush,
there are some remaining issues but they are much narrower than you
identify
below...
You seem to have summed up the issues. Just to expand with a
practic
Comments inline; You painted this situation today with an overly broad brush,
there are some remaining issues but they are much narrower than you identify
below...
André Warnier wrote:
>
> It is becoming urgent to create a new HTTP standard/version/revision,
> that would be organised around Unico
- Start Opprinnelig Melding -
Sendt: Sat, 18 Oct 2008 19:02:17 +0200
Fra: André Warnier <[EMAIL PROTECTED]>
Til: users@httpd.apache.org, Tomcat Users List <[EMAIL PROTECTED]>
Emne: [EMAIL PROTECTED] I18N, HTTP 2.0 ?
> I am sending this to both the Apache httpd and Tomcat
Hi.
I am sending this to both the Apache httpd and Tomcat users lists, in
the hope that because together these HTTP servers cover a good fraction
of the market, there might be a chance to reach the righ people.
My hope is that someone who is aware of, and connected to, the process
of RFC gen
