Mark E. Shoulson mark at kli.org
Tue Mar 17 20:28:55 CDT 2015

I think you're conflating glyphs with characters.  Multiple glyphs for a 
single character, selectable by the font or the software is fine; we 
don't necessarily need codepoints for things that are to be considered 
the same character. (This begs the question of whether or not these 
count as "the same character" as proposed originally, or something else.)


On 03/17/2015 01:45 PM, William_J_G Overington wrote:
> Suppose that plane 4 were introduced with a rule that if a rendering 
> system cannot find in a font a glyph for U+4PQRS then it first looks 
> in the font for a glyph for U+4P000 before using the .notdef glyph. P, 
> Q, R, S are here used as placeholders, each placeholding for a 
> hexadecimal value in the range 0 .. 15. In the example, Q, R and S are 
> not all simultaneously zero.
> This would allow for a graceful use of a generic glyph indicating the 
> meaning and indicating that there is an underlying encoding that could 
> be rendered using a font that supplies a correct glyph.
> That would allow for sixteen independent blocks each consisting of one 
> generic glyph and up to 4095 specific glyphs. One of those sixteen 
> blocks could be used for this encoding project. The other blocks would 
> be available for other encoding projects.
> Maybe smaller blocks and more of them with this particular encoding 
> project having several such blocks ringfenced for it.
> William Overington
> 17 March 2015
> _______________________________________________
> Unicode mailing list
> Unicode at unicode.org
> http://unicode.org/mailman/listinfo/unicode

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/unicode/attachments/20150317/95b642c8/attachment.html>

More information about the Unicode mailing list