Marc-Andre Lemburg <m...@egenix.com> added the comment: Christoph Burgmer wrote: > > Christoph Burgmer <cburg...@ira.uka.de> added the comment: > >> * U+0027 APOSTROPHE > hardcoded (see below) >> * U+00AD SOFT HYPHEN (SHY) > has the "Format (Cf)" property and thus is included automatically >> * U+2019 RIGHT SINGLE QUOTATION MARK > hardcoded (see below) > > I hardcoded some characters into Tools/unicode/makeunicodedata.py: >>>> print ' '.join([u':', u'\xb7', u'\u0387', u'\u05f4', u'\u2027', > u'\ufe13', u'\ufe55', u'\uff1a'] + [u"'", u'.', u'\u2018', u'\u2019', > u'\u2024', u'\ufe52', u'\uff07', u'\uff0e']) > : · · ״ ‧ ︓ ﹕ ： ' . ‘ ’ ․ ﹒ ＇ ． > > Those cannot currently be extracted automatically, as neither > DerivedCoreProperties.txt nor the source file for property > "Word_Break(C) = MidLetter or MidNumLet" are provided in the script.
As long as those code points are defined somewhere in the Unicode standard files, that's ok. It would be good to add a comment explaining the above in the code. BTW: It's better to use "if (....)" instead of \-line joining. The parens will automatically have Python do the line joining for you and it looks better. > As I said, the patch is only a second best solution, as the correct > path would be implementing the word breaking algorithm as described in > the newest standard. This patch is just an improvement over the current > situation. We could handle the work-breaking in a separate new method. For .title(), I think your patch is an improvement and it will fix most of the cases that issue7008 mentions. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6412> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
