Addison Phillips scripsit:
> >Bokm?$B%F!&l (which is the
> >way it got to me, sans ESC characters) is nothing but rubbish.
>
> Well, that's mozibake: it's ISO 2022-JP encoding of the Shift-JIS
> characters made by mis-interpreting UTF-8 bytes. Lovely.
Not even. My mailer suppresses ESC characters altogether,
so the result is pure printable ASCII again, ergo unreconstructible.
> But that consideration doesn't apply to the registry file. It only
> applies to the discussion of a registry entry on ietf-languages.
> Admittedly MUAs vary greatly in their support for encodings, but we can
> certainly specify directions for how to send the registration request to
> the list so that everyone can tell what code points are intended and
> other instructions for how to encode those characters in the registry.
Directions which work uniformly across all native encodings, operating
environments, and mailers? I venture to doubt it.
> Suggestions to limit the character repertoire strike me as counter
> productive too.
+1
--
John Cowan cowan at ccil.org http://ccil.org/~cowan
In the sciences, we are now uniquely privileged to sit side by side
with the giants on whose shoulders we stand.
--Gerald Holton
_______________________________________________
Ltru mailing list
Ltru at ietf.org
https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.