On 26 October 2016 at 00:53, Mikhail V <mikhail...@gmail.com> wrote: > On 25 October 2016 at 23:50, Chris Barker <chris.bar...@noaa.gov> wrote: > >>that was kind of a throwaway comment, >>but I think it's a LONG way out, but ideally, >>the OWTDI would be "curly quotes". The fact that in ASCII, >>a single quote and a apostrophe are teh same, >>and that there is no distinction between opening >>and closing quotes is unfortunate. > > Yes from readability POV, curly quotes would make > sense, and better than many other options, eg. «these». > Also from POV of parser this could be > beneficial to have opening/closing char (or not?). > This only means that those chars should be in > ASCII ideally. Which is not the case. > And IMO not that now code should allow > all characters. > > Mikhail
Extended ASCII 145 ‘ ‘ ‘ Left single quotation mark 146 ’ ’ ’ Right single quotation mark 147 “ “ “ Left double quotation mark 148 ” ” ” Right double quotation mark 149 • • • Bullet 150 – – – En dash 151 — — — Em dash 152 ˜ ˜ ˜ Small tilde So we all must repent now and get back to 8-bit charcters. _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
