[issue15444] Incorrectly written contributor's names

Antoine Pitrou added the comment: Ok, then I've committed the patch. Closing the issue now, thank you. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: -Python 2.7 ___ Python tracker

[issue15444] Incorrectly written contributor's names

Roundup Robot added the comment: New changeset 3654c711019a by Antoine Pitrou in branch '3.2': Issue #15444: Use proper spelling for non-ASCII contributor names. http://hg.python.org/cpython/rev/3654c711019a New changeset 867de88b69f0 by Antoine Pitrou in branch 'default': Issue #15444: Use prop

[issue15444] Incorrectly written contributor's names

Serhiy Storchaka added the comment: Non-ascii characters already used in a lot (43-50) of doc files. LC_ALL=C find Doc/ -type f -name '*.rst' -exec egrep --color "$(printf '[\x80-\xFF]+')" '{}' + All touched files already contains non-ascii characters (and Misc/HISTORY contains invalid UT

[issue15444] Incorrectly written contributor's names

Antoine Pitrou added the comment: The patch looks ok to me so, unless someone is opposed to using utf-8 in the doc files, I think it can be committed in 3.x. -- nosy: +pitrou ___ Python tracker ___

[issue15444] Incorrectly written contributor's names

Changes by Serhiy Storchaka : Removed file: http://bugs.python.org/file26504/doc-nonascii-names.patch ___ Python tracker ___ ___ Python-bugs-l

[issue15444] Incorrectly written contributor's names

Serhiy Storchaka added the comment: What about patch review? -- keywords: +needs review ___ Python tracker ___ ___ Python-bugs-list ma

[issue15444] Incorrectly written contributor's names

Chris Jerdonek added the comment: > While working on issue 15437, it occurred to me that storing the names in a > structured form might come in handy. In a separate discussion, Ezio pointed out a case where we are already scraping data about members from doc files: http://hg.python.org/tracke

[issue15444] Incorrectly written contributor's names

Chris Jerdonek added the comment: The idea also to include a romanization is a good one. While working on issue 15437, it occurred to me that storing the names in a structured form might come in handy. This would let us do things like list the username(s) associated with each contributor alo

[issue15444] Incorrectly written contributor's names

Terry J. Reedy added the comment: I basically agree with Marc-André. Indeed, I think Acks, at least, should contain names in native spelling plus, if that is not Latin-based, a romanization. Three reasons: 1. I want English-speaking Python programmers to feel welcome to contribute and be ackn

[issue15444] Incorrectly written contributor's names

Serhiy Storchaka added the comment: All names interpreted correctly except cyrillic (Alexander “Саша” Belopolsky and Марк Коренберг). I think it's just because of lack of some non-installed package (of course, Latex supports cyrillic). -- ___ Pytho

[issue15444] Incorrectly written contributor's names

Ezio Melotti added the comment: > Indeed, PDF rendering is important. OTOH, Latex T1 does support Ž. I tried to put a Ž directly in an rst source and indeed the pdf has been created correctly. -- ___ Python tracker

[issue15444] Incorrectly written contributor's names

Martin v. Löwis added the comment: Indeed, PDF rendering is important. OTOH, Latex T1 does support Ž. Untested, \v{Z} should generate that character. If this doesn't work, the build process needs to be fixed. -- ___ Python tracker

[issue15444] Incorrectly written contributor's names

Ezio Melotti added the comment: Make sure that it's still possible to generate the pdf of the docs (with `make latex` and then `make all-pdf` in build/latex/). Latin1 should be fine, but IIRC non-latin1 will break (sorry Žiga). -- nosy: +ezio.melotti __

[issue15444] Incorrectly written contributor's names

Chris Jerdonek added the comment: To be clear on this issue's scope, I would state in a single comment a white list of which directories or individual files are being corrected (or if necessary, the rules to determine such a list, e.g. any file whose name root is "NEWS", etc). I would also r

[issue15444] Incorrectly written contributor's names

Marc-Andre Lemburg added the comment: Thank you for taking the initiative. Regarding use of UTF-8 for text files: I think we ought to acknowledge that UTF-8 has become the defacto standard for non-ASCII text files by now and with Python 3 being all Unicode, it feels silly not make use of it in

[issue15444] Incorrectly written contributor's names

Serhiy Storchaka added the comment: Well, here is updated patch. Also fixed names of Walter Dörwald (was Walter D�rwald) and Martin von Löwis in Misc/HISTORY. All changed files (documentation, ACK-files, Misc/HISTORY) already in UTF-8 and contains non-ASCII names. Löwis written as Loewis in