[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ddlm-group] options/text vs binary/end-of-line. .. .

• To: "'Group finalising DDLm and associated dictionaries'" <[email protected]>
• Subject: Re: [ddlm-group] options/text vs binary/end-of-line. .. .
• From: "Bollinger, John C" <[email protected]>
• Date: Mon, 21 Jun 2010 11:30:48 -0500
• Accept-Language: en-US
• acceptlanguage: en-US
• In-Reply-To: <[email protected]>
• References: <[email protected]><[email protected]><[email protected]><[email protected]><8F77913624F7524AACD2A92EAF3BFA54165DF3381E@SJMEMXMBS11.stjude.sjcrh.local><[email protected]><[email protected]><[email protected]><[email protected]><[email protected]><[email protected]><[email protected]><[email protected]><[email protected]><[email protected]><[email protected]><[email protected]><8F77913624F7524AACD2A92EAF3BFA541661229516@SJMEMXMBS11.stjude.sjcrh.local><[email protected]>

On Monday, June 21, 2010 1:13 AM, James Hester wrote:

>I prefer the XML treatment of newline (ie translated to 0x000A for
>processing purposes).  I would be in favour of restricting newline to
><0x000A>, <0x000D> or <0x000D 0x000A>, which means that only these
>combinations have the syntactic significance of a newline.

I would be satisfied with that approach.

> From
>memory, this significance is restricted to:
>
>1. end of comment
>2. whitespace
>3. use in <eol><semicolon> digraph

The significance also extends to 'single'- and "double"-quote delimited data values, in that these cannot contain end-of-line.

>I would also restrict the appearance of the remaining Unicode newline
>characters to delimited datavalues, to maintain consistent display of
>data files.

I'm seeing more and more upside to restricting *all* non-ASCII characters to delimited data values.  I don't have any objection to restricting U+0085, U+2028, and U+2029 (did I miss any?) to such contexts.


John
--
John C. Bollinger, Ph.D.
Department of Structural Biology
St. Jude Children's Research Hospital




Email Disclaimer:  www.stjude.org/emaildisclaimer

_______________________________________________
ddlm-group mailing list
[email protected]
http://scripts.iucr.org/mailman/listinfo/ddlm-group

Reply to: [list | sender only]

• Follow-Ups:
  • Re: [ddlm-group] options/text vs binary/end-of-line. .. . (Herbert J. Bernstein)

• References:
  • Re: [ddlm-group] [SPAM] ASSP UTF-8 BOM (Herbert J. Bernstein)
  • Re: [ddlm-group] [SPAM] ASSP UTF-8 BOM (Herbert J. Bernstein)
  • Re: [ddlm-group] [SPAM] ASSP UTF-8 BOM (James Hester)
  • Re: [ddlm-group] UTF-8 BOM (Brian McMahon)
  • Re: [ddlm-group] UTF-8 BOM (Bollinger, John C)
  • Re: [ddlm-group] UTF-8 BOM (James Hester)
  • Re: [ddlm-group] UTF-8 BOM (Herbert J. Bernstein)
  • Re: [ddlm-group] UTF-8 BOM (James Hester)
  • Re: [ddlm-group] UTF-8 BOM (Herbert J. Bernstein)
  • Re: [ddlm-group] UTF-8 BOM (SIMON WESTRIP)
  • Re: [ddlm-group] UTF-8 BOM (James Hester)
  • Re: [ddlm-group] UTF-8 BOM (Herbert J. Bernstein)
  • Re: [ddlm-group] UTF-8 BOM (James Hester)
  • Re: [ddlm-group] UTF-8 BOM (Herbert J. Bernstein)
  • Re: [ddlm-group] UTF-8 BOM (James Hester)
  • Re: [ddlm-group] UTF-8 BOM (Herbert J. Bernstein)
  • [ddlm-group] options/text vs binary/end-of-line (Herbert J. Bernstein)
  • Re: [ddlm-group] options/text vs binary/end-of-line. . (Bollinger, John C)
  • Re: [ddlm-group] options/text vs binary/end-of-line. . (James Hester)

• Prev by Date: Re: [ddlm-group] Recommended character set and use restrictions. .
• Next by Date: Re: [ddlm-group] options/text vs binary/end-of-line. .. .
• Prev by thread: Re: [ddlm-group] options/text vs binary/end-of-line. .
• Next by thread: Re: [ddlm-group] options/text vs binary/end-of-line. .. .
• Index(es):
  • Date
  • Thread