Re: [ddlm-group] Treatment of CIF2 unicode characters with CIF1equivalents
- To: Group finalising DDLm and associated dictionaries <firstname.lastname@example.org>
- Subject: Re: [ddlm-group] Treatment of CIF2 unicode characters with CIF1equivalents
- From: James Hester <email@example.com>
- Date: Wed, 26 Apr 2017 17:43:00 +1000
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;h=mime-version:in-reply-to:references:from:date:message-id:subject:to;bh=Z3/bUJCt/SOkaA9hdTouKgMTOfpf1p04WBuY+Zp4lVM=;b=PU4FfKHgdqeZRkDW+aN68yzNm1IQh6n+189rvC3HhaH8U1QmRFKhZYqybzI9Yys1XBeK+rxjxyOmijcmTr0xvS4FD/eVzPBVu/KBhYVz1w5ibpd4c9iAcfiRxYHpEvBj/Py+xhvXVg2KoqeWd5+l9PiGUIJ2eFb3Ue7dj3PwJa9KbsHaMqBAWEIgqnp2vEPw0pF7docql4d12M/67CdpYdg/k3XX29kPeQak9/2xEFfBv9qZ058eG83pggP7DiZDVvgAuIhabQ1D/0DlQMhHlPax8uFmJRmL2T99Rkn4pqjxtMtY6aEjuWC4yG71sup7+sCju5RawJQ3cSQnK+IfqA==
- In-Reply-To: <MWHPR04MB0512E5C58F2EFDB1B3C26B9FE01F0@MWHPR04MB0512.namprd04.prod.outlook.com>
- References: <CAM+dB2fj5b9wvBk2JZU4ATX-4qjJkKJfY1p8zst5k8jrR_XiWQ@mail.gmail.com><MWHPR04MB0512E5C58F2EFDB1B3C26B9FE01F0@MWHPR04MB0512.namprd04.prod.outlook.com>
Comments inserted below:
Although the kind of transformation described by the James’s proposed rule is appropriate under the conditions the rule describes, I am a bit apprehensive about adding the specific proposed text to Vol G. In particular,
(1) I am inclined to think it inappropriate to assert rules for *applications* in a chapter presenting specifications for the CIF *format*, except to the extent that such rules can be construed as de facto specifications for details of the format or its intended interpretation.
(2) The proposed rule comes awfully close to comingling syntax with semantics, and I think the more separation we can maintain between those, the better.
(3) I’m not convinced that such a provision is needed at all, inasmuch as it seems to follow directly from the principle that CIF data values will be interpreted according to their items’ definitions.
Evidently we’re talking about the next edition of Vol G, and it is unclear to me exactly how that edition will need to be changed to cover CIF 2.0. Inasmuch as I imagine it will incorporate at least some of the content of the CIF 2.0 specification paper, however, I observe that appendix A.2 of that paper addresses exactly this area already, in the context of a more complete discussion of format conversions such as the current proposal considers. Since we already have applicable text, I suggest we use that as context and starting point, instead of drafting something new from scratch. (Hyperlink for the paper: http://journals.iucr.org/j/iss
From: ddlm-group [mailto:ddlm-group-bounces@iuc
r.org] On Behalf Of James Hester
Sent: Sunday, April 23, 2017 6:46 PM
To: ddlm-group <firstname.lastname@example.org>
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/iuc
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).
According to section 22.214.171.124.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 126.96.36.199. Note that "meets the requirements of paragraph 188.8.131.52.13" means that this paragraph only applies in those cases for which the CIF1 markup conventions would apply.
(184.108.40.206.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 220.127.116.11.13-16 should be substituted, provided that the relevant definition meets the requirements of paragraph 18.104.22.168.13. If no markup is defined for the Unicode code point, no CIF1 equivalent value exists and application behaviour is undefined.
Email Disclaimer: www.stjude.org/emaildisclaimer
Consultation Disclaimer: www.stjude.org/consultationdis
ddlm-group mailing list
_______________________________________________ ddlm-group mailing list email@example.com http://mailman.iucr.org/cgi-bin/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
- [ddlm-group] Treatment of CIF2 unicode characters with CIF1equivalents (James Hester)
- Re: [ddlm-group] Treatment of CIF2 unicode characters withCIF1 equivalents (Bollinger, John C)
- Prev by Date: Re: [ddlm-group] Treatment of CIF2 unicode characters with CIF1equivalents
- Next by Date: Re: [ddlm-group] Treatment of CIF2 unicode characters with CIF1equivalents
- Prev by thread: Re: [ddlm-group] Treatment of CIF2 unicode characters withCIF1 equivalents
- Next by thread: Re: [ddlm-group] Treatment of CIF2 unicode characters with CIF1equivalents