[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Change by Serhiy Int : -- nosy: +Serhiy Int ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Changes by Ezio Melotti : -- versions: +Python 3.3, Python 3.4 -Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Terry J. Reedy added the comment: Christoph is responding above to a previous version of this message with an erroneous conclusion based on a misreading of his original message. The proposed patch makes this issue overlap #7008, which had some contentious discussion, so I am adding some peopl

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Changes by Terry J. Reedy : -- Removed message: http://bugs.python.org/msg112715 ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Christoph Burgmer added the comment: @Terry How is the behavior changed? To me it seems the same to as initially reported. The results are consistent but nonetheless wrong. It's not about whether your agree with the result, but rather about following the Unicode standard. -- ___

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Terry J. Reedy added the comment: 3.1.2 >>> 'H\u0301ngh'.istitle() False >>> 'H\u0301ngh'=='H\u0301ngh'.title() False >>> 'H\u0301ngh'.title() 'H́Ngh' which suggest that initial False is correct, not a bug. In any case, behavior is changed. Is new behavior wrong? I disagrees with proposed new

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Marc-Andre Lemburg added the comment: Jeff Senn wrote: > > Jeff Senn added the comment: > > So, is it not considered a bug that: > "This isn't right".title() > "This Isn'T Right" > > !?!?!? That's http://bugs.python.org/issue7008 and is fixed as part of http://bugs.python.org/issue641

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Jeff Senn added the comment: So, is it not considered a bug that: >>> "This isn't right".title() "This Isn'T Right" !?!?!? -- ___ Python tracker ___ ___

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Jeff Senn added the comment: Referred to this from issue 4610... anyone following this might want to look there as well. -- nosy: +senn ___ Python tracker ___ __

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Christoph Burgmer added the comment: New patch - updated comments to reflect needed integration of DerivedCoreProperties.txt - cleaned up if(...) construct - updated (from issue7008) and integrated testcase When applying this patch, run Tools/unicode/makeunicodedata.py to regenerate the h

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Marc-Andre Lemburg added the comment: Christoph Burgmer wrote: > > Christoph Burgmer 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 >

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Christoph Burgmer 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/makeunicode

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Marc-Andre Lemburg added the comment: The patch looks good, but it doesn't include the few extra characters that are also considered case-ignorable: * U+0027 APOSTROPHE * U+00AD SOFT HYPHEN (SHY) * U+2019 RIGHT SINGLE QUOTATION MARK Could you add those as well ? Thanks. -- nosy: +lem

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Changes by Gabriel Genellina : -- nosy: +gagenellina ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Christoph Burgmer added the comment: I should add that I didn't include the two header files generated by Tools/unicode/makeunicodedata.py -- ___ Python tracker ___ _

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Christoph Burgmer added the comment: Implementing full patch solving it the old way (UTR#21). The correct way for the latest Unicode version would be to implement the word breaking algorithm described in (UAX#29) [1] first. [1] http://www.unicode.org/reports/tr29/#Word_Boundaries -- A

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Christoph Burgmer added the comment: Casing algorithms should follow Section 3.13 "Default Case Algorithms" in the standard itself, not UTR#21. See http://www.unicode.org/Public/5.2.0/ucd/DerivedCoreProperties-5.2.0d11. Unicode 5.2. A nice mail on the Unicode mail list has a bit explanation to

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Christoph Burgmer added the comment: Adding a incomplete patch in need of a function Py_UNICODE_ISCASEIGNORABLE defining the case-ignorable class. I don't want to touch capitalize() as I don't fully understand the semantics, where it is different to title(). It seems though following UTR#21 not

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

Changes by Ezio Melotti : -- nosy: +ezio.melotti priority: -> normal stage: -> needs patch type: -> behavior versions: +Python 2.7 ___ Python tracker ___ __

[issue6412] Titlecase as defined in Unicode Case Mappings not followed

New submission from Christoph Burgmer : Titlecase, i.e. istitle() and title(), is buggy when the string includes combining diacritical marks. >>> u'H\u0301ngh'.istitle() False >>> u'H\u0301ngh'.title() u'H\u0301Ngh' >>> The string given already is in titlecase so that the following result is ex