[Issue 1] Re: [Ietf-calsify] draft-ietf-calsify-rfc2445bis-01.txt
lists at block-online.eu
Wed Aug 23 04:45:51 PDT 2006
Am Mittwoch, 23. August 2006 04:13 schrieb Bernard Desruisseaux:
> Let me try to put this another way. We need to decide and justify:
> 1- Whether we want to allow "multi-octet characters" to be split
> across lines.
> Answer: No.
> Why : Otherwise the resulting text would end up being invalid
> in the specified encoding.
> 2- Whether we want to allow "combining character sequences" to be
> split across lines.
> Answer: Yes.
> Why : (1) I'm assuming that it is valid for a "combining
> character" to be preceded by the LF character (but I
> don't know this for a fact...), and thus the resulting
> text would still be valid in the specified encoding
> (but would sure "look" different).
> (2) A "combining character sequence" could probably be
> longer than 75 octets in *theory*! But I'm sure we would
> never see this in practice though...
> With this approach:
> - You could open an iCalendar object specified in the charset 'X'
> in any application that support 'X' without errors.
> - You would still need to unfold the iCalendar object to be able
> to "interpret" all the characters properly.
> What do you think?
That's exactly how I understand your preceding proposal. Even if it did not
mention combining character sequences. And that's how I understood Mark in
his agreement on that issue.
Leben ist mehr als schneller - weiter - höher
More information about the Ietf-calsify