[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
[ddlm-group] Vote on BOM
- To: ddlm-group <ddlm-group@iucr.org>
- Subject: [ddlm-group] Vote on BOM
- From: James Hester <jamesrhester@gmail.com>
- Date: Wed, 16 Jun 2010 11:31:59 +1000
For clarity, by 'UTF8 BOM' I mean the byte sequence 0xEF,0xBB,0xBF, which corresponds to Unicode code point 0xFEFF. A UCS2 BOM is the byte sequence 0xFE, 0xFF or the reverse. Please indicate your preferred behaviour below. I have inserted mine already: 1. Treatment of UTF8 BOM as first three bytes of a CIF2 file (a) Syntax error/Non CIF2 file (b) UTF8-BOM followed by #\#CIF2.0 is a valid CIF2 magic number James 2. Treatment of UTF8 BOM in a CIF file, other than as the first three bytes: (a) Always a syntax error (b) Syntactic whitespace (c) An ordinary character: (i) May appear only in delimited data values and comments James (ii) May appear anywhere other ordinary characters can appear (i.e. including datanames, datablock names etc.) (d) Silently ignored 3. Treatment of UCS BOM in a CIF file (a) Syntax error James (b) Encoding switch -- T +61 (02) 9717 9907 F +61 (02) 9717 3145 M +61 (04) 0249 4148 _______________________________________________ ddlm-group mailing list ddlm-group@iucr.org http://scripts.iucr.org/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
- Follow-Ups:
- Re: [ddlm-group] Vote on BOM (Bollinger, John C)
- Re: [ddlm-group] Vote on BOM (Brian McMahon)
- Prev by Date: Re: [ddlm-group] UTF-8 BOM
- Next by Date: Re: [ddlm-group] UTF-8 BOM
- Prev by thread: Re: [ddlm-group] Handling of null byte in CIF2. .
- Next by thread: Re: [ddlm-group] Vote on BOM
- Index(es):