W3C home > Mailing lists > Public > xproc-dev@w3.org > August 2009

Re: Dealing with encodings and file: URIs

From: Norman Walsh <ndw@nwalsh.com>
Date: Sat, 1 Aug 2009 07:01:16 -0400
Message-ID: <4227d1df0908010401u6b8f7b5exc6bcee5d4711b8af@mail.gmail.com>
To: Mike Sokolov <sokolov@ifactory.com>
Cc: XProc Dev <xproc-dev@w3.org>
On Wednesday, July 29, 2009, Mike Sokolov <sokolov@ifactory.com> wrote:
>
> It also might be nice if an HTTP server reporting "text/plain" (no
> character set) didn't override the client specification of "text/plain;
> windows/1252", since they don't in fact conflict: the server is simply
> providing less information.

I believe, though it isn't convenient for me to check right now, that
the absence of an encoding decl in an http response is a declaration
that the text is US-ASCII.
>
> -Mike
>
> Norman Walsh wrote:
>
>   "Toman_Vojtech@emc.com" <Toman_Vojtech@emc.com> <Toman_Vojtech@emc.com> <Toman_Vojtech@emc.com> writes:
>
>
>     Um. What kind of filesystem are you using that tells you the content
> type?
>
>
>
> I suppose, on reflection, that that gives me justification to ignore
> the content type reported by java.net.URL. There really isn't a server
> involved.
>
>                                         Be seeing you,
>                                           norm
>
>
>
>
>
>
Received on Saturday, 1 August 2009 11:01:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 1 August 2009 11:01:58 GMT