[rfc-i] Data point [Re: Fwd:I-D ACTION:draft-hoffman-utf8-rfcs-03.txt]

[Joe Touch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Julian Reschke wrote:
> Joe Touch wrote:
>>>> I have no similar path for UTF-8, at least not yet - the tools I use
>>>> today that preserve page boundaries (only Wordpad) fails on UTF-8  - it
>>>> renders them fine on the screen, but when I print them, they are
>>>> corrupted (they print as if the content is ASCII).
>>> So, the inability of your preferred tool chain to produce UTF-8 is a
>>> reason not to *allow* it?
>>
>> I've shown you that the one I currently use does not. Show me a tool
>> chain that works.
> 
> xml2rfc will be made to work if we decide that we want to.

xml2rfc is a way to write docs, not to read or print them.

...
> We apparently disagree on the merits of xml2rfc. Calling it "stone-age"
> doesn't help in this discussion.
> 
> We will make the "stone-age" tool generate UTF-8. If that's possible, I
> would assume that it should be possible to adapt more "modern" tools as
> well.

Assume it all you like; until someone shows it, it has not been proven.

I am not claiming it's not possible, but I will claim that without a
demonstration, Paul's original assertion remains false:

"Now that UTF-8 [RFC3629] is nearly universally available in text-
editing and display systems,"

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjruSIACgkQE5f5cImnZrtQvACgnataVjJdbFMVxi8PXO9Pbab/
d9kAn3UiBngEhvco/t15/q8AGKLZJOj+
=JZ0v
-----END PGP SIGNATURE-----