1 / 9

Code Point Variant Allocation Rules in LGRs

Understand code point variants allocation rules across Chinese and Japanese LGRs with case studies and examples. Learn about potential allocation and blocking rules for label variants.

xyla-salinas
Télécharger la présentation

Code Point Variant Allocation Rules in LGRs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Variant Mapping – C, J and K

  2. The Variant Mapping must be the same for the same code point for all LGRs. Principle:

  3. Disposition of a Code Point Variant Allocatable A potential allocation rule says that once the variant label is generated, that variant label may be allocated to the applicant for the original label. Blocked A blocking rule says that a particular label must not be allocated to anyone under any circumstances.

  4. Example to Illustrate 爱 (U+7231) 愛 (U+611B)

  5. Chinese LGR

  6. Japanese LGR

  7. Integrated LGR

  8. Applying for U+611B using the und-jpanblocks the use of U+7231 in the same location in any label, no matter which tag it is applied under. This is so, even though U+7231 is not a character in Japanese at all. and does not appear in the tagged repertoire und-jpan. Because it is not part of that repertoire, it cannot be used in any label applied for with the und-jpantag.

  9. Case Study 一 (U+4E00) 壹 (U+58F9) 弌 (U+5F0C) 壱 (U+58F1)

More Related