3 ms·
This is exactly what's happening here. But note that UTF-8 is self-synchronizing, so no encoding of one character contains the encoding of another as a subseque
by yorwba 2y ago
This is exactly what's happening here. But note that UTF-8 is self-synchronizing, so no encoding of one character contains the encoding of another as a subsequence. Instead, both tag characters and the Byzantine music notation in the article look like "<some prefix bytes> <byte pattern of the corresponding ASCII character + 96>"
They share this property with the Fullwidth Latin block, which does occur in the wild interspersed with Japanese or Chinese text.
- xg15 2y agoAh, that makes sense. Thank you!
- thaumasiotes 2y ago> They share this property with the Fullwidth Latin block, which does occur in the wild interspersed with Japanese or Chinese text. How common is that? In my experience it's much more normal for Chinese text to intersperse ordinary ascii characters. https://www.zdic.net/hans/%E8%84%B8 https://www.zdic.net/hans/%E8%84%B8 I'm not sure what purpose fullwidth characters are supposed to serve, but whatever it is, it doesn't seem like they're succeeding.
- yorwba 2y agoFullwidth Latin characters exist so that you can arrange your text into a grid without the occasional word in Latin script messing up your alignment. Most people don't really care about this, or, if they do, simply use a font that renders regular Latin at full width (or half width to be more space-efficient) but very occasionally the Fullwidth Latin codepoints get some use. It's more common in Japanese (though still rare) than Chinese in my experience, but e.g. the Project Gutenberg ebook of 阿Ｑ正傳 https://gutenberg.org/cache/epub/25332/pg25332-images.html https://gutenberg.org/cache/epub/25332/pg25332-images.html uses fullwidth Qs.