This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tchrist
Recipients ezio.melotti, mrabarnett, tchrist, terry.reedy
Date 2011-08-19.23:57:41
SpamBayes Score 8.163035e-05
Marked as misclassified No
Message-id <31486.1313798244@chthon>
In-reply-to <1313797005.69.0.593629032079.issue12753@psf.upfronthosting.co.za>
Content
Matthew Barnett <report@bugs.python.org> wrote
   on Fri, 19 Aug 2011 23:36:45 -0000: 

> For the "Line_Break" property, one of the possible values is
> "Inseparable", with 2 permitted aliases, the shorter "IN" (which 
> is reasonable) and "Inseperable" (ouch!).

Yeahy, I've shaken my head at that one, too.

It's one thing to make an alias for something you typo'd in the first 
place, but to have something that's correct which you then make a typo 
alias for is just encouraging bad/sloppy/wrong behavior.

    Bidi_Class=Paragraph_Separator
    Bidi_Class=Common_Separator
    Bidi_Class=European_Separator
    Bidi_Class=Segment_Separator
    General_Category=Line_Separator
    General_Category=Paragraph_Separator
    General_Category=Separator
    General_Category=Space_Separator
    Line_Break=Inseparable
    Line_Break=Inseperable

And there's still set, which makes you wonder
why they couldn't spell at least *one* of them out:

    Sentence_Break=Sep SB=SE
    Sentence_Break=Sp  SB=Sp

You really have to look those up to realize they're two different things:

    SB ; SE        ; Sep
    SB ; SP        ; Sp

And that none of them have something like SB=Space or SB=Separator
so you know what you're talking about.  Grrr.

--tom
History
Date User Action Args
2011-08-19 23:57:42tchristsetrecipients: + tchrist, terry.reedy, ezio.melotti, mrabarnett
2011-08-19 23:57:41tchristlinkissue12753 messages
2011-08-19 23:57:41tchristcreate