[Ietf-calsify] Status of simplification work

[Reinhold Kainhofer]

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

Am Donnerstag, 25. Mai 2006 11:46 schrieb Arnaud Quillaud:
> So even if you split a 4 bytes UTF8 character by inserting a space+CRLF in
> the middle, the parser at the other end should remove this space+CRLF even
> before interpreting the stream as UTF-8.

Exactly, however, this makes the files invalid UTF-8 encoded text-files, so 
editing them in a text editor will typically not work and mess up the events. 
In KOrganizer, we try to split the lines at a word boundary (i.e. at a 
whitespace "character") between 70 and 75 bytes and if that's not possible, 
we use the glyph boundary before 75 bytes. This makes the ics files valid 
text files that are easy to read in a text editor.

However, this should not got into a standard definition, but maybe it should 
be included in a "best practices" FAQ?

Cheers,
Reionhold

- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna, 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.3 (GNU/Linux)

iD8DBQFEdaqETqjEwhXvPN0RAhn8AJ43goJFF7oFtwV2nilMgKi3/OU4cACgghc9
+ayCXSOIcQKHsW+U5Chg8Rs=
=WqyL
-----END PGP SIGNATURE-----