|
Re: Next step: msg#00034ietf.apps-discuss
Clive D.W. Feather wrote: >> In theory your proposal is compatible with C044, but in practice I >> fear that it won't work as you expect it. I could live with e.g. >> "authors SHOULD either pick hex. NCRs as in XML or" (your proposal), >> but in fact I think that the XML-notation is much better. > My only, small, discomfort is that people will expect all protocols > to accept both hex (ሴ) and decimal (Ӓ). Then they are at odds with <http://www.w3.org/TR/charmod/#C043> and <http://www.w3.org/TR/charmod/#C045>, and missed the most important W3C last call in this millennium... slighty exaggerated. <g> Seriously, that's something where a MUST might do what we both want. RFC 4646 chapter 3.1 simply states this as fact, and it uses MUSTard elsewhere rather frankly. Decimal NCRs are horrible, and the last browser worldwide not supporting hex. NCRs in text/html is under my firm control... :-) Frank |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Typographical error in draft-klensin-unicode-escapes-00: 00034, John C Klensin |
|---|---|
| Next by Date: | Re: Next step: 00034, Frank Ellermann |
| Previous by Thread: | Re: Next stepi: 00034, Clive D.W. Feather |
| Next by Thread: | Re: Next step (Was: I-D ACTION:draft-klensin-unicode-escapes-00.txt: 00034, Clive D.W. Feather |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |