"textels" (was: Default character encoding for each operating system?)

[Eli Zaretskii]

> From: jsbien at mimuw.edu.pl (Janusz S. Bień)
> Date: Thu, 15 Sep 2016 21:12:53 +0200
> Cc: mufi-fonts <mufi-fonts at googlegroups.com>
> 
> On Thu, Sep 15 2016 at 16:36 CEST, john.w.kennedy at gmail.com writes:
> 
> [...]
> 
> > In the new Swift programming language, which is white-hot in the Apple
> > community, Apple is moving toward a model of a transparent, generic
> > Unicode that can be “viewed” as UTF-8, UTF-16, or UTF-32 if necessary,
> > but in which a “character” contains however many code points it needs
> > (“e” with a stacked macron, acute accent, and dieresis is
> > algorithmically one “character” in Swift). Moreover,
> > e-with-an-acute-accent and e followed by a combining acute accent, for
> > example, compare as equal. At present, the underlying code is still
> > UTF-16LE.
> 
> For several years I use the name "textel" (text element, in Polish
> "tekstel") for such objects. I do it mostly orally in my presentations
> for my students, but I used it also in writing e.g. in
> http://bc.klf.uw.edu.pl/118/, unfortunately without a proper
> definition.

Isn't "grapheme cluster" the definition you are looking for?