Hi! Thank you very much, Nick, for long and detailed explanation!
On Sun, Aug 24, 2014 at 01:27:55PM +1000, Nick Coghlan ncogh...@gmail.com
wrote:
On 24 August 2014 04:37, Oleg Broytman p...@phdru.name wrote:
On Sat, Aug 23, 2014 at 06:40:37PM +0100, Paul Moore p.f.mo...@gmail.com
wrote:
On Sat, 23 Aug 2014 19:33:06 +0300, Marko Rauhamaa ma...@pacujo.net wrote:
R. David Murray rdmur...@bitdance.com:
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
On Sat, 23 Aug 2014, Marko Rauhamaa wrote:
Isaac Morland ijmor...@uwaterloo.ca:
HTTP/1.1 200 OK
Content-Type: text/html; charset=ISO-8859-1
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
meta http-equiv=Content-Type content=text/html; charset=utf-16
For HTML
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
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
On Tue, 26 Aug 2014 11:25:19 +0900, Stephen J. Turnbull step...@xemacs.org
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
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 properly.
