Bopomofo -> Limited_Use #1129
Bopomofo -> Limited_Use #1129
Conversation
There was a problem hiding this comment.
@asmusf First pass at this just assigning Bopomofo as Limited_Use resulted in a couple of double assignments from previous updates. Are these OK per the consensus? If not I think I can use override to force them to Limited_Use only.
312E ; Limited_Use Obsolete # 10.0 BOPOMOFO LETTER O WITH DOT ABOVE
02EA..02EB ; Limited_Use Not_XID # 3.0 [2] MODIFIER LETTER YIN DEPARTING TONE MARK..MODIFIER LETTER YANG DEPARTING TONE MARK
|
Hmmm. Not maintaining info on "obsolete" for "limited_use" scripts is acceptable, though discarding any vetted information is always regrettable, but I get that we may not want the burden of maintaining a consistent analysis. (While this means we inadvertently force people who want to support a limited_use script to start from scratch, we can survive this one for now). However, the Not_XID seems something that is "stronger" than "limited_use". It seems quite wrong to have that information "hidden", because we do want people to be able to add Limited_Use scripts to their own identifiers and that should not force them to recreated everything. However, again, this data is discoverable, and we can sit down and have a discussion on whether Not_XID should be handled differently. For now, let's just match all other limited_use scripts. |
[UTC-183-C37] Consensus: Change Bopomofo to "Limited Use" in UAX #31. For Unicode Version 17.0. See L2/25-087 item 5.5.
[UTC-183-A79] Action Item for Josh Hadley, PAG: Update Identifier_Status and Identifier_Type properties according to the change of status of Bopomofo to “Limited Use”. For Unicode Version 17.0. See L2/25-087 item 5.5.