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

Re: [ddlm-group] Handling of null byte in CIF2. .

• To: "'Group finalising DDLm and associated dictionaries'" <ddlm-group@iucr.org>
• Subject: Re: [ddlm-group] Handling of null byte in CIF2. .
• From: "Bollinger, John C" <John.Bollinger@STJUDE.ORG>
• Date: Wed, 16 Jun 2010 09:39:56 -0500
• Accept-Language: en-US
• acceptlanguage: en-US
• In-Reply-To: <20100616100809.GA27077@emerald.iucr.org>
• References: <20100616100809.GA27077@emerald.iucr.org>

On Wednesday, June 16, 2010 5:08 AM, Brian McMahon wrote:
>I hope this already has a simple answer. What is the status
>of a zero byte (i.e. value 0) in a CIF ? Is it handled clearly
>in the current draft specification, or do we need specifically
>to exclude it as an acceptable character, or otherwise make a
>comment on how to handle it?

Change 2 specifies exactly which Unicode characters are allowed in CIF, and the only ASCII control characters among them are horizontal tab (U+0009), line feed (U+000A), and carriage return (U+000D).  In particular, null (U+0000) is not in the set.


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

Reply to: [list | sender only]

• References:
  • [ddlm-group] Handling of null byte in CIF2 (Brian McMahon)

• Prev by Date: Re: [ddlm-group] UTF-8 BOM
• Next by Date: Re: [ddlm-group] UTF-8 BOM
• Prev by thread: [ddlm-group] Handling of null byte in CIF2
• Next by thread: [ddlm-group] Vote on BOM
• Index(es):
  • Date
  • Thread