Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(18)

Side by Side Diff: third_party/lcms2-2.6/src/cmscgats.c

Issue 2545553002: Make LCMS2 source files utf-8 (Closed)
Patch Set: Created 4 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « no previous file | third_party/lcms2-2.6/src/cmstypes.c » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 //------------------------------------------------------------------------------ --- 1 //------------------------------------------------------------------------------ ---
2 // 2 //
3 // Little Color Management System 3 // Little Color Management System
4 // Copyright (c) 1998-2012 Marti Maria Saguer 4 // Copyright (c) 1998-2012 Marti Maria Saguer
5 // 5 //
6 // Permission is hereby granted, free of charge, to any person obtaining 6 // Permission is hereby granted, free of charge, to any person obtaining
7 // a copy of this software and associated documentation files (the "Software"), 7 // a copy of this software and associated documentation files (the "Software"),
8 // to deal in the Software without restriction, including without limitation 8 // to deal in the Software without restriction, including without limitation
9 // the rights to use, copy, modify, merge, publish, distribute, sublicense, 9 // the rights to use, copy, modify, merge, publish, distribute, sublicense,
10 // and/or sell copies of the Software, and to permit persons to whom the Softwar e 10 // and/or sell copies of the Software, and to permit persons to whom the Softwar e
(...skipping 240 matching lines...) Expand 10 before | Expand all | Expand 10 after
251 251
252 {"MEASUREMENT_SOURCE", WRITE_STRINGIFY}, // Illumination used for spectr al measurements. This data helps provide 252 {"MEASUREMENT_SOURCE", WRITE_STRINGIFY}, // Illumination used for spectr al measurements. This data helps provide
253 // a guide to the potential for issues of paper f luorescence, etc. 253 // a guide to the potential for issues of paper f luorescence, etc.
254 254
255 {"PRINT_CONDITIONS", WRITE_STRINGIFY}, // Used to define the character istics of the printed sheet being reported. 255 {"PRINT_CONDITIONS", WRITE_STRINGIFY}, // Used to define the character istics of the printed sheet being reported.
256 // Where standard conditions have been defined (e .g., SWOP at nominal) 256 // Where standard conditions have been defined (e .g., SWOP at nominal)
257 // named conditions may suffice. Otherwise, detai led information is 257 // named conditions may suffice. Otherwise, detai led information is
258 // needed. 258 // needed.
259 259
260 {"SAMPLE_BACKING", WRITE_STRINGIFY}, // Identifies the backing mater ial used behind the sample during 260 {"SAMPLE_BACKING", WRITE_STRINGIFY}, // Identifies the backing mater ial used behind the sample during
261 // measurement. Allowed values are “black? “white ? or {"na". 261 // measurement. Allowed values are "black" "white " or "na".
262 262
263 {"CHISQ_DOF", WRITE_STRINGIFY}, // Degrees of freedom associate d with the Chi squared statistic 263 {"CHISQ_DOF", WRITE_STRINGIFY}, // Degrees of freedom associate d with the Chi squared statistic
264 264
265 // below properties are new in recent specs: 265 // below properties are new in recent specs:
266 266
267 {"MEASUREMENT_GEOMETRY", WRITE_STRINGIFY}, // The type of measurement, e ither reflection or transmission, should be indicated 267 {"MEASUREMENT_GEOMETRY", WRITE_STRINGIFY}, // The type of measurement, e ither reflection or transmission, should be indicated
268 // along with details of the geometry and the ape rture size and shape. For example, 268 // along with details of the geometry and the ape rture size and shape. For example,
269 // for transmission measurements it is important to identify 0/diffuse, diffuse/0, 269 // for transmission measurements it is important to identify 0/diffuse, diffuse/0,
270 // opal or integrating sphere, etc. For reflectio n it is important to identify 0/45, 270 // opal or integrating sphere, etc. For reflectio n it is important to identify 0/45,
271 // 45/0, sphere (specular included or excluded), etc. 271 // 45/0, sphere (specular included or excluded), etc.
272 272
273 {"FILTER", WRITE_STRINGIFY}, // Identifies the use of physic al filter(s) during measurement. Typically used to 273 {"FILTER", WRITE_STRINGIFY}, // Identifies the use of physic al filter(s) during measurement. Typically used to
274 // denote the use of filters such as none, D65, R ed, Green or Blue. 274 // denote the use of filters such as none, D65, R ed, Green or Blue.
275 275
276 {"POLARIZATION", WRITE_STRINGIFY}, // Identifies the use of a phys ical polarization filter during measurement. Allowed 276 {"POLARIZATION", WRITE_STRINGIFY}, // Identifies the use of a phys ical polarization filter during measurement. Allowed
277 // values are {"yes? “white? “none?or “na? 277 // values are "yes" "white" "none" or "na"
278 278
279 {"WEIGHTING_FUNCTION", WRITE_PAIR}, // Indicates such functions as: the CIE standard observer functions used in the 279 {"WEIGHTING_FUNCTION", WRITE_PAIR}, // Indicates such functions as: the CIE standard observer functions used in the
280 // calculation of various data parameters (2 degr ee and 10 degree), CIE standard 280 // calculation of various data parameters (2 degr ee and 10 degree), CIE standard
281 // illuminant functions used in the calculation o f various data parameters (e.g., D50, 281 // illuminant functions used in the calculation o f various data parameters (e.g., D50,
282 // D65, etc.), density status response, etc. If u sed there shall be at least one 282 // D65, etc.), density status response, etc. If u sed there shall be at least one
283 // name-value pair following the WEIGHTING_FUNCTI ON tag/keyword. The first attribute 283 // name-value pair following the WEIGHTING_FUNCTI ON tag/keyword. The first attribute
284 // in the set shall be {"name" and shall identify the particular parameter used. 284 // in the set shall be {"name" and shall identify the particular parameter used.
285 // The second shall be {"value" and shall provide the value associated with that name. 285 // The second shall be {"value" and shall provide the value associated with that name.
286 // For ASCII data, a string containing the Name a nd Value attribute pairs shall follow 286 // For ASCII data, a string containing the Name a nd Value attribute pairs shall follow
287 // the weighting function keyword. A semi-colon s eparates attribute pairs from each 287 // the weighting function keyword. A semi-colon s eparates attribute pairs from each
(...skipping 2478 matching lines...) Expand 10 before | Expand all | Expand 10 after
2766 2766
2767 _cmsAssert(hIT8 != NULL); 2767 _cmsAssert(hIT8 != NULL);
2768 2768
2769 if (Formatter == NULL) 2769 if (Formatter == NULL)
2770 strcpy(it8->DoubleFormatter, DEFAULT_DBL_FORMAT); 2770 strcpy(it8->DoubleFormatter, DEFAULT_DBL_FORMAT);
2771 else 2771 else
2772 strncpy(it8->DoubleFormatter, Formatter, sizeof(it8->DoubleFormatter)); 2772 strncpy(it8->DoubleFormatter, Formatter, sizeof(it8->DoubleFormatter));
2773 2773
2774 it8 ->DoubleFormatter[sizeof(it8 ->DoubleFormatter)-1] = 0; 2774 it8 ->DoubleFormatter[sizeof(it8 ->DoubleFormatter)-1] = 0;
2775 } 2775 }
OLDNEW
« no previous file with comments | « no previous file | third_party/lcms2-2.6/src/cmstypes.c » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698