[issue20906] Issues in Unicode HOWTO

Change by Filip Bengtsson : -- pull_requests: +13019 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue20906] Issues in Unicode HOWTO

STINNER Victor added the comment: I see a change, so I guess that this old issue can now be fixed. Anything, the issue didn't get much activity last years. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python t

[issue20906] Issues in Unicode HOWTO

miss-islington added the comment: New changeset 84fa6b9e5932af981cb299c0c5ac80b9cc37c3fa by Miss Islington (bot) in branch '3.7': bpo-20906: Various revisions to the Unicode howto (GH-8394) https://github.com/python/cpython/commit/84fa6b9e5932af981cb299c0c5ac80b9cc37c3fa -- nosy: +

[issue20906] Issues in Unicode HOWTO

Change by miss-islington : -- pull_requests: +12153 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue20906] Issues in Unicode HOWTO

A.M. Kuchling added the comment: New changeset 97c288df614dd7856f5a0336925f56a7a2a5bc74 by Andrew Kuchling in branch 'master': bpo-20906: Various revisions to the Unicode howto (#8394) https://github.com/python/cpython/commit/97c288df614dd7856f5a0336925f56a7a2a5bc74 -- ___

[issue20906] Issues in Unicode HOWTO

Change by A.M. Kuchling : -- assignee: docs@python -> akuchling nosy: +akuchling ___ Python tracker ___ ___ Python-bugs-list mailing

[issue20906] Issues in Unicode HOWTO

Change by A.M. Kuchling : -- keywords: +patch pull_requests: +7921 stage: needs patch -> patch review ___ Python tracker ___ ___ Pyt

[issue20906] Issues in Unicode HOWTO

Ezio Melotti added the comment: See also #1581182. -- stage: -> needs patch versions: +Python 3.5 -Python 3.3 ___ Python tracker ___

[issue20906] Issues in Unicode HOWTO

Graham Wideman added the comment: @R David: I agree with you. Thanks for extending the line of thinking I outlined. -- ___ Python tracker ___ __

[issue20906] Issues in Unicode HOWTO

R. David Murray added the comment: On the other hand, I wonder if such problem/solution pairs should go in the FAQ list rather than the howto, perhaps with a pointer to the howto for those wanting more general information. Specifically the Python on Windows section in this case. I realize th

[issue20906] Issues in Unicode HOWTO

R. David Murray added the comment: Although I agree that the Unicode Howto needs to provide enough information for someone to reason correctly about python3 unicode, I'd like to note that someone running into the encoding error on windows is *not* going to reach for the unicode howto to solve

[issue20906] Issues in Unicode HOWTO

Martin v. Löwis added the comment: "4. Many Internet standards are defined in terms of textual data" I believe the author was thinking of the "old" TCP-based protocols (ftp, smtp, RFC 822, HTTP), which have their commands/messages as ASCII-strings, with a variable-length records (often termin

[issue20906] Issues in Unicode HOWTO

Graham Wideman added the comment: @Andre: _I_ know more or less the explanations behind all this. I am just putting it forward as an example which touches several concepts which are needed to explain it, and that a programmer might reason with to change a program (or the environment) to prod

[issue20906] Issues in Unicode HOWTO

Antoine Pitrou added the comment: > "UnicodeEncodeError: 'charmap' codec can't encode character '\u265e' in > position 13: character maps to undefined". That's because stdout is treated as a regular bytestream under Windows (as it is under POSIX), and it therefore uses the current "codepage"

[issue20906] Issues in Unicode HOWTO

Graham Wideman added the comment: At the moment I've run out of time to exert much forward push on this. By way of temporary summary/suggestion for regrouping: Focus on what this page is intending to deliver. What concepts should readers of this page be able to distinguish and understand when

[issue20906] Issues in Unicode HOWTO

Graham Wideman added the comment: Marc-Andre: Thanks for your latest comments. > We could also have called encodings: "character set", "code page", > "character encoding", "transformation", etc. I concur with you that things _could_ be called all sorts of names, and the choices may be arbitra

[issue20906] Issues in Unicode HOWTO

Marc-Andre Lemburg added the comment: On 20.03.2014 11:49, Graham Wideman wrote: > >> An encoding is a mapping of characters to ordinals, nothing more or less. > > In unicode, the mapping from characters to ordinals (code points) is not the > encoding. It's the mapping from code points to byte

[issue20906] Issues in Unicode HOWTO

Graham Wideman added the comment: Marc-Andre: Thanks for commenting: > > 2. 1. Python string --> some other code system, such as > > ASCII, cp1250, etc. The destination code system doesn't > > necessarily have anything to do with unicode, and whole > > ranges of unicode's characters either r

[issue20906] Issues in Unicode HOWTO

Marc-Andre Lemburg added the comment: Just to clarify a few things: On 20.03.2014 00:50, Graham Wideman wrote: > > I think part of the ambiguity problem here is that there are two subtly but > importantly different ideas here: > > 1. Python string (capable of representing any unicode text) --

[issue20906] Issues in Unicode HOWTO

Graham Wideman added the comment: Antoine: Thanks for your comments -- this is slippery stuff. > It's better, but how about simply "In this article"? I was hoping to inform the reader that the hex representations are found in many articles, not just special to this one. > [ showing the glyph

[issue20906] Issues in Unicode HOWTO

Antoine Pitrou added the comment: > Agreed. How about "In documentation such as the current article..." It's better, but how about simply "In this article"? > I concur with reducing unnecessary abstraction. No sure what you mean > by "true form". Do you mean show the glyph which the code point

[issue20906] Issues in Unicode HOWTO

Changes by A.M. Kuchling : -- nosy: -akuchling ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue20906] Issues in Unicode HOWTO

Graham Wideman added the comment: A further issue regarding "one-to-one mappings". Article: "Encodings don’t have to be simple one-to-one mappings like Latin-1. Consider IBM’s EBCDIC, which was used on IBM mainframes." I don't think this paragraph is about one-to-one mappings per se. (ie: one

[issue20906] Issues in Unicode HOWTO

Graham Wideman added the comment: > Do you want to provide a patch? I would be happy to, but I'm not currently set up to create a patch. Also, I hoped that an author who has more history with this article would supervise, especially where I don't know what the original intent was. > I find us

[issue20906] Issues in Unicode HOWTO

Antoine Pitrou added the comment: Do you want to provide a patch? > In a narrative such as the current article, a code point value is usually > written in hexadecimal. I find use of the word "narrative" intimidating in the context of a technical documentation. In general, I find it disappoin

[issue20906] Issues in Unicode HOWTO

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue20906] Issues in Unicode HOWTO

Changes by Éric Araujo : -- nosy: +benjamin.peterson, eric.araujo, ezio.melotti, haypo, lemburg, pitrou title: Unicode HOWTO -> Issues in Unicode HOWTO versions: -Python 3.1, Python 3.2, Python 3.5 ___ Python tracker