|
Re: Next step: msg#00035ietf.apps-discuss
John C Klensin wrote: [􂍅 might be ugly] > Use of a sequence of special characters, none of which may > be completely familiar to those who don't regularly use a > fairly full set of Roman characters and both of which, IIR, > are assigned to "national use" positions in ISO 646 BV No C trigraph for "&", but "#" has "??=". IMO that's a historic foot note, nobody used weird "national variants" of ASCII for at least a decade. And we're talking about US ASCII anyway. > the ability to get help from common programming-oriented > editors and syntax-checkers, favors paired delimiters over > subjectively unmatched ones Is that about protocols needing a new escape mechanism, or about the prose in RFCs ? In the former case some piece of software will do it, in the latter case an editor macro can take care of the raw UTF-8 or whatever it is. An example is <http://purl.net/xyzzy/kex/x-wiki.kex> for an XEDIT-clone. Frank |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Next step: 00035, Frank Ellermann |
|---|---|
| Next by Date: | Re: FWD: I-D ACTION:draft-klensin-unicode-escapes-00.txt: 00035, John C Klensin |
| Previous by Thread: | Re: Next step (Was: I-D ACTION:draft-klensin-unicode-escapes-00.txti: 00035, John C Klensin |
| Next by Thread: | Re: Next step (Was: I-D ACTION:draft-klensin-unicode-escapes-00.txt: 00035, der Mouse |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |