00001 /********************************************************************** 00002 * cbf_ascii -- write plain ASCII values * 00003 * * 00004 * Version 0.6 13 January 1999 * 00005 * * 00006 * Paul Ellis (ellis@ssrl.slac.stanford.edu) and * 00007 * Herbert J. Bernstein (yaya@bernstein-plus-sons.com) * 00008 **********************************************************************/ 00009 00010 /********************************************************************** 00011 * NOTICE * 00012 * Creative endeavors depend on the lively exchange of ideas. There * 00013 * are laws and customs which establish rights and responsibilities * 00014 * for authors and the users of what authors create. This notice * 00015 * is not intended to prevent you from using the software and * 00016 * documents in this package, but to ensure that there are no * 00017 * misunderstandings about terms and conditions of such use. * 00018 * * 00019 * Please read the following notice carefully. If you do not * 00020 * understand any portion of this notice, please seek appropriate * 00021 * professional legal advice before making use of the software and * 00022 * documents included in this software package. In addition to * 00023 * whatever other steps you may be obliged to take to respect the * 00024 * intellectual property rights of the various parties involved, if * 00025 * you do make use of the software and documents in this package, * 00026 * please give credit where credit is due by citing this package, * 00027 * its authors and the URL or other source from which you obtained * 00028 * it, or equivalent primary references in the literature with the * 00029 * same authors. * 00030 * * 00031 * Some of the software and documents included within this software * 00032 * package are the intellectual property of various parties, and * 00033 * placement in this package does not in any way imply that any * 00034 * such rights have in any way been waived or diminished. * 00035 * * 00036 * With respect to any software or documents for which a copyright * 00037 * exists, ALL RIGHTS ARE RESERVED TO THE OWNERS OF SUCH COPYRIGHT. * 00038 * * 00039 * Even though the authors of the various documents and software * 00040 * found here have made a good faith effort to ensure that the * 00041 * documents are correct and that the software performs according * 00042 * to its documentation, and we would greatly appreciate hearing of * 00043 * any problems you may encounter, the programs and documents any * 00044 * files created by the programs are provided **AS IS** without any * 00045 * warranty as to correctness, merchantability or fitness for any * 00046 * particular or general use. * 00047 * * 00048 * THE RESPONSIBILITY FOR ANY ADVERSE CONSEQUENCES FROM THE USE OF * 00049 * PROGRAMS OR DOCUMENTS OR ANY FILE OR FILES CREATED BY USE OF THE * 00050 * PROGRAMS OR DOCUMENTS LIES SOLELY WITH THE USERS OF THE PROGRAMS * 00051 * OR DOCUMENTS OR FILE OR FILES AND NOT WITH AUTHORS OF THE * 00052 * PROGRAMS OR DOCUMENTS. * 00053 **********************************************************************/ 00054 00055 /********************************************************************** 00056 * The IUCr Policy * 00057 * on * 00058 * the Use of the Crystallographic Information File (CIF) * 00059 * * 00060 * The Crystallographic Information File (Hall, Allen & Brown, * 00061 * 1991) is, as of January 1992, the recommended method for * 00062 * submitting publications to Acta Crystallographica Section C. The * 00063 * International Union of Crystallography holds the Copyright on * 00064 * the CIF, and has applied for Patents on the STAR File syntax * 00065 * which is the basis for the CIF format. * 00066 * * 00067 * It is a principal objective of the IUCr to promote the use of * 00068 * CIF for the exchange and storage of scientific data. The IUCr's * 00069 * sponsorship of the CIF development was motivated by its * 00070 * responsibility to its scientific journals, which set the * 00071 * standards in crystallographic publishing. The IUCr intends that * 00072 * CIFs will be used increasingly for electronic submission of * 00073 * manuscripts to these journals in future. The IUCr recognises * 00074 * that, if the CIF and the STAR File are to be adopted as a means * 00075 * for universal data exchange, the syntax of these files must be * 00076 * strictly and uniformly adhered to. Even small deviations from * 00077 * the syntax would ultimately cause the demise of the universal * 00078 * file concept. Through its Copyrights and Patents the IUCr has * 00079 * taken the steps needed to ensure strict conformance with this * 00080 * syntax. * 00081 * * 00082 * The IUCr policy on the use of the CIF and STAR File processes is * 00083 * as follows: * 00084 * _________________________________________________________________ * 00085 * * 00086 * * 1 CIFs and STAR Files may be generated, stored or transmitted, * 00087 * without permission or charge, provided their purpose is not * 00088 * specifically for profit or commercial gain, and provided that * 00089 * the published syntax is strictly adhered to. * 00090 * * 2 Computer software may be developed for use with CIFs or STAR * 00091 * files, without permission or charge, provided it is distributed * 00092 * in the public domain. This condition also applies to software * 00093 * for which a charge is made, provided that its primary function * 00094 * is for use with files that satisfy condition 1 and that it is * 00095 * distributed as a minor component of a larger package of * 00096 * software. * 00097 * * 3 Permission will be granted for the use of CIFs and STAR Files * 00098 * for specific commercial purposes (such as databases or network * 00099 * exchange processes), and for the distribution of commercial * 00100 * CIF/STAR software, on written application to the IUCr Executive * 00101 * Secretary, 2 Abbey Square, Chester CH1 2HU, England. The * 00102 * nature, terms and duration of the licences granted will be * 00103 * determined by the IUCr Executive and Finance Committees. * 00104 * * 00105 * _________________________________________________________________ * 00106 * * 00107 * In summary, the IUCr wishes to promote the use of the STAR File * 00108 * concepts as a standard universal data file. It will insist on * 00109 * strict compliance with the published syntax for all * 00110 * applications. To assist with this compliance, the IUCr provides * 00111 * public domain software for checking the logical integrity of a * 00112 * CIF, and for validating the data name definitions contained * 00113 * within a CIF. Detailed information on this software, and the * 00114 * associated dictionaries, may be obtained from the IUCr Office at * 00115 * 5 Abbey Square, Chester CH1 2HU, England. * 00116 **********************************************************************/ 00117 00118 #ifdef __cplusplus 00119 00120 extern "C" { 00121 00122 #endif 00123 00124 #include "cbf.h" 00125 #include "cbf_ascii.h" 00126 #include "cbf_tree.h" 00127 #include "cbf_file.h" 00128 00129 #include <stdlib.h> 00130 #include <string.h> 00131 #include <ctype.h> 00132 #include <limits.h> 00133 00134 00135 /* Write an ascii value */ 00136 00137 int cbf_write_ascii (const char *string, cbf_file *file) 00138 { 00139 static const char missing [] = { CBF_TOKEN_WORD, '?', '\0' }; 00140 00141 int end; 00142 00143 unsigned int column; 00144 00145 const char *c; 00146 00147 char delim; 00148 00149 00150 /* Check the arguments */ 00151 00152 if (!string) 00153 00154 string = missing; 00155 00156 else 00157 00158 if (*string != CBF_TOKEN_WORD && 00159 *string != CBF_TOKEN_SQSTRING && 00160 *string != CBF_TOKEN_DQSTRING && 00161 *string != CBF_TOKEN_SCSTRING && 00162 *string != CBF_TOKEN_NULL) 00163 00164 return CBF_ARGUMENT; 00165 00166 00167 /* Get the current column */ 00168 00169 cbf_failnez (cbf_get_filecoordinates (file, NULL, &column)) 00170 00171 00172 /* Do we need to start a new line? */ 00173 00174 if (column) 00175 00176 if (*string == CBF_TOKEN_SCSTRING) 00177 00178 cbf_failnez (cbf_write_character (file, '\n')) 00179 00180 else 00181 { 00182 if (*string == CBF_TOKEN_WORD || 00183 *string == CBF_TOKEN_NULL ) 00184 00185 end = column + 3; 00186 00187 else 00188 00189 end = column + 1; 00190 00191 for (c = string + 1; *c && end <= CBF_LINELENGTH; c++) 00192 00193 if (*c == '\t') 00194 00195 end = (end & ~0x07) + 8; 00196 00197 else 00198 00199 end = end + 1; 00200 00201 if (end > CBF_LINELENGTH) 00202 00203 cbf_failnez (cbf_write_character (file, '\n')) 00204 } 00205 00206 00207 /* Write the value */ 00208 00209 switch (*string) 00210 { 00211 /* Simple word? */ 00212 00213 case CBF_TOKEN_WORD: 00214 case CBF_TOKEN_NULL: 00215 00216 cbf_failnez (cbf_write_character (file, ' ')) 00217 00218 cbf_failnez (cbf_write_string (file, string + 1)) 00219 00220 break; 00221 00222 00223 /* Single line? */ 00224 00225 case CBF_TOKEN_SQSTRING: 00226 case CBF_TOKEN_DQSTRING: 00227 00228 if (*string == CBF_TOKEN_SQSTRING) 00229 00230 delim = '\''; 00231 00232 else 00233 00234 delim = '"'; 00235 00236 cbf_failnez (cbf_write_character (file, ' ')) 00237 00238 cbf_failnez (cbf_write_character (file, delim)) 00239 00240 cbf_failnez (cbf_write_string (file, string + 1)) 00241 00242 cbf_failnez (cbf_write_character (file, delim)) 00243 00244 break; 00245 00246 00247 /* Multiple lines? */ 00248 00249 case CBF_TOKEN_SCSTRING: 00250 00251 cbf_failnez (cbf_write_character (file, ';')) 00252 00253 end = 1; 00254 00255 for (c = string + 1; *c; c++) 00256 { 00257 if (*c == ';' && end == 0) 00258 00259 cbf_failnez (cbf_write_character (file, '\\')) 00260 00261 cbf_failnez (cbf_write_character (file, *c)) 00262 00263 if (*c == '\n') 00264 00265 end = 0; 00266 00267 else 00268 00269 end = 1; 00270 } 00271 00272 cbf_failnez (cbf_write_string (file, "\n;\n")) 00273 00274 end = 0; 00275 00276 break; 00277 } 00278 00279 00280 /* Flush the buffer */ 00281 00282 return cbf_flush_characters (file); 00283 } 00284 00285 00286 #ifdef __cplusplus 00287 00288 } 00289 00290 #endif 00291