This document:Public document·View comments·Disposition of Comments·
Nearby:Efficient Extensible Interchange Working Group Other specs in this tool
Quick access to LC-2103 LC-2104 LC-2105 LC-2106 LC-2107 LC-2108 LC-2109 LC-2110 LC-2130 LC-2132 LC-2133 LC-2164 LC-2165 LC-2166 LC-2167 LC-2168 LC-2169 LC-2170 LC-2171 LC-2172 LC-2173 LC-2174 LC-2175 LC-2176 LC-2177 LC-2178 LC-2179 LC-2180 LC-2181 LC-2182 LC-2183 LC-2184 LC-2185 LC-2186 LC-2187 LC-2188 LC-2189 LC-2190 LC-2191 LC-2192 LC-2193 LC-2194 LC-2196 LC-2197 LC-2198 LC-2227 LC-2248
Previous: LC-2180
I think the terminology used In Appendix E can be improved. From the title, you would expect this appendix to give a function for guessing the character set: e.g. ISO 9959-1, or Latin1 or whatever. It is much better to use the industry jargon from the Unicode Encoding Character Model: http://unicode.org/reports/tr17/ Using that terminology, the appendix should substitute "character repertoire" where is currently uses "character set", and "repertoire" instead of "charset". Flowing through, 7.1.10.1 Restricted Character Sets should have "coded character set (CCS) for restricted character repertoire" rather than "restricted character set". Cheers Rick Jelliffe