4 ms·
No need to get too much into the meaning of the length of a str. It's neat to know the definition but neither choice gives you a good “string length” for real t
by kzrdude 10y ago
No need to get too much into the meaning of the length of a str. It's neat to know the definition but neither choice gives you a good “string length” for real text.
Case in point: len("é") == 2, so even with unicode strings we don't have length as a character count.
As an english speaking person, I can clearly point at é and call it one character, but Python 2 or Python 3 doesn't agree. Rather, their str `len` doesn't agree with that, and that's fine. It's not a character count!
- dom0 10y agoThat one is maybe not the best example, since len(unicodedata.normalize('NFC', "é")) == 1 Though I don't know any "normal" character that requires composition ad-hoc that could serve as a better example.
- kzrdude 10y agoI think it's a fine example since the decomposed version clearly exists and can arrive as data into your program in a number of ways. That said, the grapheme cluster note will have examples of extended notions of characters that can't be represented by an equivalent single codepoint. There are some korean and indic examples and also emoji http://unicode.org/reports/tr29/ http://unicode.org/reports/tr29/ Oh and something that stirs the heart of us hackers: \r\n is a single grapheme!
- greglindahl 10y agoThis (different forms and no automatic normalization) is a "feature" of Unicode. It would be wrong of Python to try to cover it up.
- kzrdude 10y agoYes, so it's wrong for anyone to pretend len() or even indexing of a str is about characters, it's about codepoints of the string.
- wruza 10y agoIMO, len("") should raise OperationHasNoCommonSenseTodayException, just to not confuse unicode newbies. Modern text is not an array, it is a format, a complex format. Zero-width, double-width monotypes, combining, direction marks, normalization, etc. Almost no one wants to know about codepoint details when working with "just input strings", and those who want may use special namespaces for that. There is no point in making len() an alias for unicode.volatile_number_of_distinct_code_points(). visually_empty(s) is okay, len(s) is probably not.
- mrout 10y agoThey're all valid measurements. The length of a string could be measured in bytes (which doesn't require you to know the encoding), code points (which doesn't require huge Unicode grapheme clustering tables), grapheme clusters (which doesn't require a font) or even pixels (which does require a font).
- int_19h 10y agoThe best thing a language (or library) can do is to not bless any single one of these as the default. Strings shouldn't have a length at all. They should provide properties/methods/accessors like byte_count, codepoint_count, grapheme_count etc. Make the user of the API think every time they're asking for a length of the string - which one do they actually need? Which one is the best for whatever they're trying to do?
- greglindahl 10y agoCan you name a single language that does that? I can't think of one.
- int_19h 10y agoNone of the mainstream ones that I can think of. Which is really unfortunate, not the least because the defaults are all over the place - usually it's either bytes (when strings are UTF-8) or code units (when strings are UTF-16 - note, code units, not code points, so surrogate pairs count as 2!). Occasionally it's genuine code points, as in Python. Which, I think, goes to show why it's such a mess.
- deleted 10y ago[deleted]
- user5994461 10y agoß é à ç ñ How about these?
- derefr 10y ago"Character count" (i.e. grapheme cluster count) only exists once you apply a font—because of ligature rules and some other stuff. Do you want your programming-language stdlib String class to require a font metrics library? (This isn't a rhetorical question; you can go either way. Objective C cares about grapheme clusters, and so needs to know about fonts.)
- mrout 10y agoI disagree. A grapheme cluster and a glyph are different things. The former is not dependent on the font. 'fi' is two grapheme clusters even if the font renders it as a single glyph. 'é' is a single grapheme cluster even if the font renders it as two glyphs: 'e ́'
- derefr 10y agoConsider the https://en.wikipedia.org/wiki/Regional_Indicator_Symbol https://en.wikipedia.org/wiki/Regional_Indicator_Symbol s. In every way that matters, these "act as" one 'character': you can't set your cursor position to be between them; backspacing one should delete both; the flag takes up one terminal col (even if it is rendered as two) such that "\033[1Dx" (cursor-left 1, print "x") will overwrite the whole flag, etc. But it's the font that controls those semantics—because it's the font that knows what flags do or do not exist. For any pair of RIS codepoints that doesn't form a flag (in the opinion of a given font), they behave like two separate characters. Thus: one grapheme cluster, or two, depending on the font. And another example—this one much less "idiomatic", but not specifically decried by the Unicode committee: http://kudakurage.com/ligature_symbols/ http://kudakurage.com/ligature_symbols/ That's a font, making entirely-arbitrary clusters out of codepoints. As far as I am aware, it's fully within its rights as a font to do so. There's nothing in the Unicode standard saying that the code-points ['f', 'i', 'l', 'e'], put in a row, can't combine to form a single grapheme cluster. They don't have combining behavior themselves, but—unlike, say, things in the Unicode "Separator" class—they don't have any property that says they don't combine with anything.
- mrout 10y ago