[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
From: James Hester <jamesrhester@gmail.com>
To: ddlm-group <ddlm-group@iucr.org>
Sent: Monday, 24 April 2017, 0:45
Subject: [ddlm-group] Treatment of CIF2 unicode characters with CIF1 equivalents
One issue raised was what to do about CIF2 datavalues that contained unicode characters that have equivalent ASCII sequences described by the CIF markup conventions (e.g. Greek characters).
_______________________________________________
ddlm-group mailing list
ddlm-group@iucr.org
http://mailman.iucr.org/cgi-bin/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
Re: [ddlm-group] Treatment of CIF2 unicode characters withCIF1 equivalents
- To: Group finalising DDLm and associated dictionaries <ddlm-group@iucr.org>
- Subject: Re: [ddlm-group] Treatment of CIF2 unicode characters withCIF1 equivalents
- From: SIMON WESTRIP <simonwestrip@btinternet.com>
- Date: Mon, 24 Apr 2017 11:09:55 +0000 (UTC)
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=s2048;t=1493032452; bh=IbGYbyyaAwqE7kwNp0Sgb2iBkl5lFbEvGQeJP06JlFE=;h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject;b=fZu3iUO6tccIG4yIfJ8Co4SZqq/6tAu6BCWOvdulPfOM39LukxnoAwV8LHmYjdCGJR469rr0VTI5o0EItkeVnIaUrvbyEF3bE1CD3BJPi5cqoNnlQ6v7VMjcaOY2Xv7zmjx4G0QwUY3//bJgkZWMaxPlM8iCFtjfn7MSJPdMzRYP7jzT+A4WWfw9E6wF57DxnJHcJj1V2W4n+gHEGd2k9/sFkpnCLlVhyq/Ol6OcveNRJP3NUB7um1UE7el6MSFSURGVAHdpMvJf9ygKsI2Va5kV59V2b1L41DhzTfEvpmWNFAAsMVwQmj3i86lPGFz652Uxxl1+HvbewZsZKFVExg==
- In-Reply-To: <CAM+dB2fj5b9wvBk2JZU4ATX-4qjJkKJfY1p8zst5k8jrR_XiWQ@mail.gmail.com>
- References: <CAM+dB2fj5b9wvBk2JZU4ATX-4qjJkKJfY1p8zst5k8jrR_XiWQ@mail.gmail.com>
I agree with the approach, but think that if CIF2->CIF1 is to be mentioned at all,
a full convention for conversion for legacy processing should be described.
Cheers
Simon
From: James Hester <jamesrhester@gmail.com>
To: ddlm-group <ddlm-group@iucr.org>
Sent: Monday, 24 April 2017, 0:45
Subject: [ddlm-group] Treatment of CIF2 unicode characters with CIF1 equivalents
Dear DDLm-group (aka COMCIFS technical committee)
There has been some lively discussion on the cif-developers mailing list of late which you may review at http://www.iucr.org/__data/iucr/lists/cif-developers/ .According to section 2.2.7.4.13 - 17 of International Tables Vol G,
by default Greek and some other non-ASCII characters can be represented
in text datavalues using a backslash notation
<backslash><ascii character>, e.g. \a is alpha. Different
markup conventions are possible on a per-dictionary or per-definition
basis. In CIF2, these characters can be represented natively, but legacy
CIF applications presented with a datavalue containing non-ASCII values
may not be prepared to typeset or present them appropriately. On the
other hand, it would seem inefficient to define separate Unicode-aware
datanames for every text value simply to avoid legacy problems.
Proposal: add the following paragraph to Vol G section 2.2.7.4. Note that "meets the requirements of paragraph 2.2.7.4.13" means that this paragraph only applies in those cases for which the CIF1 markup conventions would apply.
(2.2.7.4.18)
Whenever an application is required to convert a datavalue from a CIF2
datafile containing code points outside the ASCII range to a datavalue
containing only ASCII codepoints, the appropriate markup as per
paragraphs 2.2.7.4.13-16 should be substituted, provided that the
relevant definition meets the requirements of paragraph 2.2.7.4.13. If
no markup is defined for the Unicode code point, no CIF1 equivalent
value exists and application behaviour is undefined.Please comment.
James.
--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
F +61 (02) 9717 3145
M +61 (04) 0249 4148
ddlm-group mailing list
ddlm-group@iucr.org
http://mailman.iucr.org/cgi-bin/mailman/listinfo/ddlm-group
_______________________________________________ ddlm-group mailing list ddlm-group@iucr.org http://mailman.iucr.org/cgi-bin/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
- Follow-Ups:
- References:
- Prev by Date: [ddlm-group] Treatment of CIF2 unicode characters with CIF1equivalents
- Next by Date: Re: [ddlm-group] Treatment of CIF2 unicode characters withCIF1 equivalents
- Prev by thread: [ddlm-group] Treatment of CIF2 unicode characters with CIF1equivalents
- Next by thread: Re: [ddlm-group] Treatment of CIF2 unicode characters with CIF1equivalents
- Index(es):