[rfc-i] Character sets, was Comments on draft-iab-rfcformat

Marc Petit-Huguenin petithug at acm.org
Tue Dec 18 18:01:32 PST 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/18/2012 05:25 PM, John R Levine wrote:
>> Accents may or may not be 99% prevalent.  Equally, I am sure that there
>> are unicode elements which are missing from 99% of deployed machines.
>> 
>> Trying to make rules around the likely prevalence of representability of 
>> individual code points in widely deployed scripts seems a recipe for
>> unending grief.
> 
> We've spent the past decade saying that we can't do anything that might 
> inconvenience the ever smaller number of people who use 80 character ASCII
> page printers, while totally ignoring the ever larger number who use the
> kinds of devices that people actually use these days, web browsers,
> tablets, and the like.  Really, it's time to get beyond that.

I do not have any number about this, but I would guess that the percentage of
people who want only ASCII is higher if you count only the people who actually
implement I-Ds/RFCs.  I find strange that nobody yet talked about the fact
that RFCs and I-Ds are used by very different people and for very different
usages and that the optimal presentation is highly dependent on the reason you
use a spec.  I need one format when reviewing (a format enabling annotations
sharing), another format when reading back to back to understand what it is
about (whatever works on an e-reader), and yet another format when implementing.

I am a developer, and when I have to carefully read each word and analyze the
meaning of each sentence, there is no better support for me than a printed
page in ASCII.  In this mode I do not care about anything that is before the
RFC 2119 section or after the Normative References section - put Unicode
characters, images, embed sound clips in them if you want.  But between these
sections, it should be ASCII and ASCII only.

> 
> While I agree that it would probably not be a great idea to fill our RFCs
> with glyphs used only in classical Tibetan, it wouldn't be hard to pick a
> profile of commonly used Unicode characters, e.g. the ones that IDNA2008
> allows, and tell people that if their display device doesn't handle them,
> it's time to upgrade, or if they just can't, to use the ugly downgraded
> version of the documents.


- -- 
Marc Petit-Huguenin
Email: marc at petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQ0R/5AAoJECnERZXWan7E9NEP/12We1SODlkvJWGQRJQk8xUV
/UXnzic87bcMQQtwo9tew0GWqBsoLC/soxoQuDELs/Dy49x99RWpZbXsaQbI0Tiu
2A5BvZ1tXcvfjTKz8RXXqZPokg504jAM84eZ/ks5cOU9bUdjxEUUR3Xnv9zbbL7j
NmYiqm2dc/jGcBYH5h3epfC0u2xoXS5t7madtJjTkWFi6VK3CWBQNc3V6c2i+k6s
Ny/K7Ic88zS/rUXgR8fr0PWzeUmCgjhuuA41L69oUqsEyPNItHK8q4+f0M94PeUe
mDfjTaTQQzSp0fK2tBUxvowxIvvrlcD0dT+e4IPSvnVziGoyLV46c6TsJibrGboQ
5CBCl8vufcylN/s5uDQmQdZ451fOGn8I/AfS5XvZTkaFaYVVCIFuh78ZAL41YrpD
Cl3n51JIO//f81GdMEH6oGeOZ8mNIbNyfUY5skRRy4/Plq5lkTXAiQONfuOq45hn
AV7nOWZkuy3xdYKfRxtuozWulq9ThJTx27BMqthzzNIQGMqqtSN0mtyM2WLpu5KZ
GpHiW98vUX3DGFdLoTkVPAkh+aJF14aWm3/5U2DfJfrnZWprHq7ogUJSrWxXgR9G
rg9bKFiKHev8MKP1jIExqFjX4eGTCzb0ReinCWYddjf2cl235mH6pqhU4//mqIeB
oWyTtDfYfS+bLv3ReklG
=Tdmf
-----END PGP SIGNATURE-----


More information about the rfc-interest mailing list