Nikolaus Rath writes:
> In that case, maybe it'd be nice to also explain why you use the
> term "bilingual" for codepage based encoding.
Modern computing systems are written in languages which are invariably
based on syntax expressed using ASCII, and provide by default
functionality for express
Nick Coghlan writes:
As some examples of where bilingual computing breaks down:
* My NFS client and server may have different locale settings
* My FTP client and server may have different locale settings
* My SSH client and server may have different locale settings
*
On 27 Aug 2014 02:52, "Terry Reedy" wrote:
>
> On 8/26/2014 9:11 AM, R. David Murray wrote:
>>
>> On Sun, 24 Aug 2014 13:27:55 +1000, Nick Coghlan
wrote:
>>>
>>> As some examples of where bilingual computing breaks down:
>>>
>>> * My NFS client and server may have different locale settings
>>> *
On 8/26/2014 9:11 AM, R. David Murray wrote:
On Sun, 24 Aug 2014 13:27:55 +1000, Nick Coghlan wrote:
As some examples of where bilingual computing breaks down:
* My NFS client and server may have different locale settings
* My FTP client and server may have different locale settings
* My SSH c
On 24 August 2014 04:27, Nick Coghlan wrote:
> One of those areas is the fact that we still use the old 8-bit APIs to
> interact with the Windows console. Those are just as broken in a
> multilingual world as the other Windows 8-bit APIs, so Drekin came up
> with a project to expose the Windows co
On Sun, 24 Aug 2014 13:27:55 +1000, Nick Coghlan wrote:
> As some examples of where bilingual computing breaks down:
>
> * My NFS client and server may have different locale settings
> * My FTP client and server may have different locale settings
> * My SSH client and server may have different lo
On 2014-08-26 03:11, Stephen J. Turnbull wrote:
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')
How about:
r
Am 24.08.14 03:11, schrieb Greg Ewing:
> Isaac Morland wrote:
>> In HTML 5 it allows non-ASCII-compatible encodings as long as U+FEFF
>> (byte order mark) is used:
>>
>> http://www.w3.org/TR/html-markup/syntax.html#encoding-declaration
>>
>> Not sure about XML.
>
> According to Appendix F here:
>
Antoine pointed out that it would still be a good idea to forward
packaging PEP acceptance announcements to python-dev, even when the
actual acceptance happens on distutils-sig.
That makes sense to me, so here's last week's notice of the acceptance
of PEP 440, the implementation independent versio
