SMC/AtomicChilluIsUnacceptable: Difference between revisions
No edit summary |
No edit summary |
||
| Line 40: | Line 40: | ||
4. Since the joiners has to be supported for backward compatibility it creates unnecessary complexity to all text processing application (sorting, searching) and it makes atomic chillus redundant and useless. | 4. Since the joiners has to be supported for backward compatibility it creates unnecessary complexity to all text processing application (sorting, searching) and it makes atomic chillus redundant and useless. | ||
5. As per the uncode stability policy, the existing chillu sequence has to be supported. In that case, inorder to process the text with atomic chillu and exiting chillu, there should be a canonical equivalence to old sequence. It is not provided and not mentioned in Unicode 5.1 and that breaks the existing applications and data and violates unicode stability policy. | 5. As per the [http://unicode.org/policies/stability_policy.html uncode stability policy], session 'Named Character Sequence Stability', the existing chillu sequence has to be supported. In that case, inorder to process the text with atomic chillu and exiting chillu, there should be a canonical equivalence to old sequence. It is not provided and not mentioned in Unicode 5.1 and that breaks the existing applications and data and violates unicode stability policy. | ||
6. Even after atomic chillus are made part of the standard many words cannot be written without joiners and it would be increasing the chaos. Thereby the atomic chillu doesnot solve the issue of ignorability of ZWJ or ZWNJ as mentioned in the proposal to encode chillu and atomic chillu is a partial incomplete solution. | 6. Even after atomic chillus are made part of the standard many words cannot be written without joiners and it would be increasing the chaos. Thereby the atomic chillu doesnot solve the issue of ignorability of ZWJ or ZWNJ as mentioned in the proposal to encode chillu and atomic chillu is a partial incomplete solution. | ||