At 01:33 PM 9/3/98 -0700, Paul Hoffman / IMC wrote:
No, it is *not* reasonable to use an RFC1766 tag there since there is
nothing to differentiate the tag from the body. Inline tagging as specified
in the new draft clearly differentiates what is a language tag from the
content. It also allows more than one language tag per string, which is
something that some Asians need if their two names are from different
languages.
Great. I love not making changes.
I don't think any change is needed. Freel free to take out the
"human-readable" thing above, but leaving it in won't cause undue damage.
I've already started a -08 draft, on the off chance it's needed. The only
things in it are Ulf Moeller's implementation note, and adding an L to all
the constants in the CRC sample code. Does anyone else have an opinion
anout the words "human-readable"?
Jon
-----
Jon Callas jon(_at_)pgp(_dot_)com
CTO, Total Network Security 3965 Freedom Circle
Network Associates, Inc. Santa Clara, CA 95054
(408) 346-5860
Fingerprints: D1EC 3C51 FCB1 67F8 4345 4A04 7DF9 C2E6 F129 27A9 (DSS)
665B 797F 37D1 C240 53AC 6D87 3A60 4628 (RSA)