[Ietf-calsify] I18n considerations section in rfc2445bis

[Reinhold Kainhofer]

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

Am Dienstag, 12. Juni 2007 schrieb Aki Niemi:
> The current rfc2445bis draft has an internationalization considerations
> section but it's empty. How about:
>
> <section title='Internationalization Considerations'>
>
>    <p>
>      All the implementations of iCalendar conformant to this
>      specification MUST generate UTF-8 and accept either UTF-8 or
>      US-ASCII encoding.

Hmm, isn't US-ASCII a subset of UTF-8? What's the exact meaning of the second 
part? An Implementation that only accepts US-ASCII is worthless, as it breaks 
with all international characters (German umlaute, French accents, the 
Spanish ñ, etc.), and should not be considered conformant in my opinion. And 
an implementation that accepts UTF-8 automatically accepts US-ASCII.


Cheers,
Reinhold

- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: reinhold at kainhofer.com, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGbm0ZTqjEwhXvPN0RAjRZAJ9EAvz4HthAM12kMsfFZtT6Bx8NgwCgic0A
2zvTAATl17vCAnNbsi2o77k=
=dcvn
-----END PGP SIGNATURE-----