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

Re: [Cif2-encoding] A new(?) compromise position. .

• To: Group for discussing encoding and content validation schemes for CIF2 <cif2-encoding@xxxxxxxx>
• Subject: Re: [Cif2-encoding] A new(?) compromise position. .
• From: "Bollinger, John C" <John.Bollinger@xxxxxxxxxx>
• Date: Wed, 29 Sep 2010 09:38:50 -0500
• Accept-Language: en-US
• acceptlanguage: en-US
• In-Reply-To: <AANLkTin=991tdnoUif0J40hsKZ0iYTf506A4i-Z_rdy2@mail.gmail.com>
• References: <AANLkTin=991tdnoUif0J40hsKZ0iYTf506A4i-Z_rdy2@mail.gmail.com>

On Wednesday, September 29, 2010 9:25 AM, James Hester wrote:

>Here is a newish compromise:
>Encoding: The encoding of CIF2 text streams containing only code points in the ASCII range is not specified. >CIF2 text streams containing any code points outside the ASCII range must be encoded such that the encoding can >be reliably identified from the file contents.  At present only UTF8 and UTF16 are considered to satisfy this >constraint.

I would accept this compromise, or, preferably, a similar one that substitutes Herb's definition of "text" for "not specified".

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
cif2-encoding@iucr.org
http://scripts.iucr.org/mailman/listinfo/cif2-encoding

Reply to: [list | sender only]

• References:
  • [Cif2-encoding] A new(?) compromise position (James Hester)

• Prev by Date: Re: [Cif2-encoding] Skype conference call 8:45 am EDT,Thursday 30 September 2010
• Next by Date: Re: [Cif2-encoding] A new(?) compromise position
• Prev by thread: [Cif2-encoding] A new(?) compromise position
• Next by thread: Re: [Cif2-encoding] A new(?) compromise position
• Index(es):
  • Date
  • Thread