SMC/AtomicChilluIsUnacceptable: Difference between revisions

Line 12:

Here , the fundamental problem lies in Unicode's way of treating only representational forms without checking linguistic correctness. Most of the Indic languages are unlike Latin and collations are based on linguistics. If you are not considering it, it will become a play yard of people with vested interests.

3. All these arguments were once considered and rejected by UTC and the only new argument in support of atomic chillus is the issue of missing domain names in IDN. The examples given ~~in 1)~~ can't be considered real as these are contrived just to make a case for atomic chillus. Even if were real it is similar to case folding in Latin (You can't register two sites PenIsland.com and PenisLand.com). How can already rejected proposal be accepted when the new arguments in supports is not only proved to be real, but creates a lot of new chaos and security problems.

3. All these arguments were once considered and rejected by UTC and the only new argument in support of atomic chillus is the issue of missing domain names in IDN. The examples given above can't be considered real as these are contrived just to make a case for atomic chillus. Even if were real it is similar to case folding in Latin (You can't register two sites PenIsland.com and PenisLand.com). How can already rejected proposal be accepted when the new arguments in supports is not only proved to be real, but creates a lot of new chaos and security problems.

4. Introducing atomic chillus will create dual encoding and makes URL spoofing very easy. This has already been illustrated with the following examples .

Line 23:

5. 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.

6. 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. As per the [http://unicode.org/policies/stability_policy.html unicode 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.

7. 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.

@@ Line 12: / Line 12: @@
 Here , the fundamental problem lies in Unicode's way of treating only representational forms without checking linguistic correctness. Most of the Indic languages are unlike Latin and collations are based on linguistics. If you are not considering it, it will become a play yard of people with vested interests.
-. All these arguments were once considered and rejected by UTC and the only new argument in support of atomic chillus is the issue of missing domain names in IDN. The examples given in 1) can't be considered real as these are contrived just to make a case for atomic chillus. Even if were real it is similar to case folding in Latin (You can't register two sites PenIsland.com and PenisLand.com). How can already rejected proposal be accepted when the new arguments in supports is not only proved to be real, but creates a lot of new chaos and security problems.
+. All these arguments were once considered and rejected by UTC and the only new argument in support of atomic chillus is the issue of missing domain names in IDN. The examples given above can't be considered real as these are contrived just to make a case for atomic chillus. Even if were real it is similar to case folding in Latin (You can't register two sites PenIsland.com and PenisLand.com). How can already rejected proposal be accepted when the new arguments in supports is not only proved to be real, but creates a lot of new chaos and security problems.
 . Introducing atomic chillus will create dual encoding and makes URL spoofing very easy. This has already been illustrated with the following examples .
@@ Line 23: / Line 23: @@
 . 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.
-. 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.
+. As per the [http://unicode.org/policies/stability_policy.html unicode 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.
 . 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.