Isaac Morland writes:
> I like your way of putting this - "straight face" indeed. The third
> option really is a hack to allow working around nonsensical situations
> (and even the META tag is pretty questionable). All this complexity
> because people can't be bothered to do things proper
On Tue, 26 Aug 2014 11:25:19 +0900, "Stephen J. Turnbull"
wrote:
> R. David Murray writes:
>
> > Also, as has been discussed in this thread previously, any program that
> > deals with filenames is dealing with human readable languages, even
> > if posix itself treats the filenames as bytes.
>
R. David Murray writes:
> Also, as has been discussed in this thread previously, any program that
> deals with filenames is dealing with human readable languages, even
> if posix itself treats the filenames as bytes.
That's a bit extreme. I can name two interesting applications
offhand: git's
Nick Coghlan writes:
> "purge_surrogate_escapes" was the other term that occurred to me.
"purge" suggests removal, not replacement. That may be useful too.
neutralize_surrogate_escapes(s, remove=False, replacement='\uFFFD')
maybe? (Of course the remove argument is feature creep, so I'm only
On Sat, 23 Aug 2014, Marko Rauhamaa wrote:
Isaac Morland :
HTTP/1.1 200 OK
Content-Type: text/html; charset=ISO-8859-1
For HTML it's not quite so bad. According to the HTML 4 standard:
[...]
The Content-Type header takes precedence over a element. I
thought I read once that the
On Sat, 23 Aug 2014 19:33:06 +0300, Marko Rauhamaa wrote:
> "R. David Murray" :
>
> > The same problem existed in python2 if your goal was to produce a stream
> > with a consistent encoding, but now python3 treats that as an error.
>
> I have a different interpretation of the situation: as a rul
Hi! Thank you very much, Nick, for long and detailed explanation!
On Sun, Aug 24, 2014 at 01:27:55PM +1000, Nick Coghlan
wrote:
> On 24 August 2014 04:37, Oleg Broytman wrote:
> > On Sat, Aug 23, 2014 at 06:40:37PM +0100, Paul Moore
> > wrote:
> >> Generally, it seems to be mostly a reaction
