[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gzz] ``canon3_file_format``: A canonical, N3-based file format
From: |
Antti-Juhani Kaijanaho |
Subject: |
Re: [Gzz] ``canon3_file_format``: A canonical, N3-based file format |
Date: |
Wed, 2 Apr 2003 11:09:57 +0300 |
User-agent: |
Mutt/1.5.4i |
On 20030401T214550+0200, Benja Fallenstein wrote:
> The ``NEWLINE`` token may be any of CR, LF, and CRLF.
Any particular reason for not allowing the other Unicode
newline-function characters (such as the "canonical" Unicode newline,
U+2028 LINE SEPARATOR)? It does make sense not to generate them in CVS
context, but is this format exclusively for CVS?
> In contexts where the specific form used matters,
> the newline character is LF. (In particular, when computing
> a content hash-- e.g., when creating a Canon3 Storm block.)
Why not LINE SEPARATOR?
--
%%% Antti-Juhani Kaijanaho % address@hidden % http://www.iki.fi/gaia/ %%%
Taiteellisen ohjelmoinnin ystävien seura Toys - Ohjelmointi on myös taidetta
http://www.cc.jyu.fi/yhd/toys/
Re: [Gzz] ``canon3_file_format``: A canonical, N3-based file format, Tuukka Hastrup, 2003/04/02