[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:
...
> You're the expect on Word (here). Are you saying that you can use it to
> generate ASCII, but not UTF-8?

Correct. The issue is the print driver.

>> page boundaries.
> 
> Navigate to tools.ietf.org, and print the HTML version from a browser.
> 
>> Those two seem like showstoppers.
> 
> I still don't understand how the problems you reported are different for
> ASCII.

I have a path for ASCII that I use regularly. Printing is native
(Wordpad). Viewing is native (Wordpad). Editing is a 3-step process
(edit in Word, print via generic/text-only, filter output to generate
FFs), and editing is WYSIWYG. Page boundaries in Word are output as a
token that a script converts to FFs; FFs are interpreted correctly by
Wordpad.

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).

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

iEYEARECAAYFAkjrmioACgkQE5f5cImnZrtIcgCgsei0B6Ey3g+i1ihxU80oOmsN
nRAAoNoBjT12xgZnAhGg91dva63qKEVM
=JJ6V
-----END PGP SIGNATURE-----