[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: [Cif2-encoding] Drafting issues
- To: Group for discussing encoding and content validation schemes for CIF2 <cif2-encoding@xxxxxxxx>
- Subject: Re: [Cif2-encoding] Drafting issues
- From: James Hester <jamesrhester@xxxxxxxxx>
- Date: Tue, 5 Oct 2010 22:44:16 +1100
- In-Reply-To: <8F77913624F7524AACD2A92EAF3BFA5416659DEDFD@SJMEMXMBS11.stjude.sjcrh.local>
- References: <[email protected]><[email protected]><[email protected]><[email protected]><[email protected]><8F77913624F7524AACD2A92EAF3BFA5416659DEDFB@SJMEMXMBS11.stjude.sjcrh.local><8F77913624F7524AACD2A92EAF3BFA5416659DEDFD@SJMEMXMBS11.stjude.sjcrh.local>
There having been no objections to this rewrite, I will now incorporate it into the main document and submit the whole document to the DDLm group for their approval. James. On Sat, Oct 2, 2010 at 1:44 AM, Bollinger, John C <[email protected]> wrote: > > On Friday, October 01, 2010 9:10 AM, I wrote: > >>I think with that we have reached an acceptable position. �I do >>propose three editorial changes, however, that I intend to clarify >>the wording without changing its meaning in any way: > > Here is specific proposed wording that realizes my suggestions, keeping everything in the same section rather than moving anything to an annex: > > ==== > CIF2 files are standard variable length plain text files, which for compatibility with older processing systems will have a maximum line length of 2048 characters. As discussed above and below, however, there are some restrictions on the character set for token delimiters, separators and data names. > > For compatibility with CIF1 behaviour, there is no formal restriction on the encoding of CIF2 files, providing they contain only code points from the ASCII range. �If a CIF2 file contains characters equivalent to Unicode code points greater than U+0077 (127 decimal), then the particular encoding used must either be UTF8 or algorithmically identifiable from the CIF2 file itself. �Acceptable identification algorithms will be published as necessary as annexes to this standard (see description of magic code and encoding disambiguation in Change 1). �Annexes notwithstanding, > (i) a CIF2 file containing characters outside the ASCII range with no BOM and no disambiguation signature will be a UTF8 file, and > (ii) a CIF2 file containing characters outside the ASCII range with a valid UTF8 or UTF16 BOM and no disambiguation signature, will be a Unicode file written in the indicated encoding. > > The use of a BOM for Unicode encodings, including UTF8, is recommended. > ==== > > Regards, > > John > -- > John C. Bollinger, Ph.D. > Department of Structural Biology > St. Jude Children's Research Hospital > > > Email Disclaimer: �www.stjude.org/emaildisclaimer > > _______________________________________________ > cif2-encoding mailing list > [email protected] > http://scripts.iucr.org/mailman/listinfo/cif2-encoding > -- T +61 (02) 9717 9907 F +61 (02) 9717 3145 M +61 (04) 0249 4148 _______________________________________________ cif2-encoding mailing list [email protected] http://scripts.iucr.org/mailman/listinfo/cif2-encoding
Reply to: [list | sender only]
- References:
- [Cif2-encoding] Drafting issues (James Hester)
- Re: [Cif2-encoding] Drafting issues (James Hester)
- Re: [Cif2-encoding] Drafting issues (James Hester)
- Re: [Cif2-encoding] Drafting issues (Herbert J. Bernstein)
- Re: [Cif2-encoding] Drafting issues (James Hester)
- Re: [Cif2-encoding] Drafting issues (Bollinger, John C)
- Re: [Cif2-encoding] Drafting issues (Bollinger, John C)
- Prev by Date: Re: [Cif2-encoding] Drafting issues
- Prev by thread: Re: [Cif2-encoding] Drafting issues
- Next by thread: [Cif2-encoding] A new(?) compromise position
- Index(es):