From: Ruszlan Gaszanov (email@example.com)
Date: Sun Jan 21 2007 - 10:18:51 CST
Unicode standard currently allows PUA (private use areas) for whatever anyone might want to use it. This tends to create problems, since, sometimes PUA code points are used for process-internal purposes and other times - for storing non-standardized character data. Because there is no way for users with a need to represent non-standardized character data to know which PUA code points some application might use for process-internal purposes and there is no way for an application designer which PUA code points someone might chose for encoding non-standard characters, this can various create issues.
So, why don't we split the PUA into character-PUA (reserved for representing non-standard characters) and non-character-PUA (reserved for process-internal uses)? For instance, we define the ranges of BMP PUA, which are known to be used by popular applications and the entire Plane 16 as non-character PUA, while reserve the rest of BMP PUA along with Plane 15 for encoding private characters exclusively. This way there would be no more confusion.
Also, if we define Plane 16 code points as reserved for process-internal use, we will no longer need to be able to interchange those code points, so future encodings schemes for that purpose could save an extra bit.
This archive was generated by hypermail 2.1.5 : Sun Jan 21 2007 - 10:21:15 CST