Circles are not impossible, just a pain:
<http://tools.ietf.org/html/rfc5491#section-5.2.7>
Likewise for normal distributions:
<http://tools.ietf.org/html/draft-thomson-geopriv-uncertainty-04>
On Mar 16, 2010, at 2:57 PM, JFC Morfin wrote:
I developed tools to convert RFC from/to mediawiki pages. As long as
RFC 3935 obliges to use English ASCII, the simplest English ASCII
format is the best as it permits easy format conversion. The only
real problem I meet is the impossibility to use circles in figures.
jfc
2010/3/16 Julian Reschke <julian.reschke@xxxxxx>
On 16.03.2010 14:14, Doug Ewell wrote:
Brian E Carpenter <brian dot e dot carrpenter at gmail dot com> wrote:
Note that I am not arguing in favor of plain text as the IETF
standard. I just want to keep this part of the discussion real. There
is no requirement anywhere that plain-text files may contain only
ASCII characters.
That requirement is explicit for RFCs.
It is explicit for RFCs, but not for plain-text files in general. IETF
could theoretically change the RFC requirement, although you are
correct
that given the non-acceptance of draft-hoffman-utf8-rfcs, it seems
unlikely. The topic did come up again on the list, with the usual
conflation of "ASCII" and "plain text."
Indeed.
Speaking of which: did we ever *measure* the acceptance of draft-
hoffman-utf8-rfcs? As far as I recall, there was lots of support for
it.
Best regards, Julian
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf