walkero
/
harfbuzz
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
harfbuzz/src/hb-ot-shape-complex-myanmar.hh

172 lines
4.7 KiB
C++
Raw Normal View History

[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
/*
* Copyright © 2018 Google, Inc.
*
* This is part of HarfBuzz, a text shaping library.
*
* Permission is hereby granted, without written agreement and without
* license or royalty fees, to use, copy, modify, and distribute this
* software and its documentation for any purpose, provided that the
* above copyright notice and the following two paragraphs appear in
* all copies of this software.
*
* IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE TO ANY PARTY FOR
* DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
* ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN
* IF THE COPYRIGHT HOLDER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
* DAMAGE.
*
* THE COPYRIGHT HOLDER SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING,
* BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
* FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS
* ON AN "AS IS" BASIS, AND THE COPYRIGHT HOLDER HAS NO OBLIGATION TO
* PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
*
* Google Author(s): Behdad Esfahbod
*/
Rename hb-*private.hh to hb-*.hh Sorry for the noise, downstream custom builders. Please adjust.
2018-08-26 07:36:36 +02:00
#ifndef HB_OT_SHAPE_COMPLEX_MYANMAR_HH
#define HB_OT_SHAPE_COMPLEX_MYANMAR_HH
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
Rename hb-*private.hh to hb-*.hh Sorry for the noise, downstream custom builders. Please adjust.
2018-08-26 07:36:36 +02:00
#include "hb.hh"
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
Rename hb-*private.hh to hb-*.hh Sorry for the noise, downstream custom builders. Please adjust.
2018-08-26 07:36:36 +02:00
#include "hb-ot-shape-complex-indic.hh"
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
/* buffer var allocations */
#define myanmar_category() indic_category() /* myanmar_category_t */
#define myanmar_position() indic_position() /* myanmar_position_t */
/* Note: This enum is duplicated in the -machine.rl source file.
* Not sure how to avoid duplication. */
enum myanmar_category_t {
OT_As = 18, /* Asat */
OT_D0 = 20, /* Digit zero */
OT_DB = OT_N, /* Dot below */
OT_GB = OT_PLACEHOLDER,
OT_MH = 21, /* Various consonant medial types */
OT_MR = 22, /* Various consonant medial types */
OT_MW = 23, /* Various consonant medial types */
OT_MY = 24, /* Various consonant medial types */
OT_PT = 25, /* Pwo and other tones */
OT_VAbv = 26,
OT_VBlw = 27,
OT_VPre = 28,
OT_VPst = 29,
OT_VS = 30, /* Variation selectors */
OT_P = 31, /* Punctuation */
OT_D = 32, /* Digits except zero */
};
static inline void
set_myanmar_properties (hb_glyph_info_t &info)
{
hb_codepoint_t u = info.codepoint;
unsigned int type = hb_indic_get_categories (u);
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
unsigned int cat = type & 0x7Fu;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
indic_position_t pos = (indic_position_t) (type >> 8);
/* Myanmar
Update the links and revive the dead ones
2018-04-12 11:10:45 +02:00
* https://docs.microsoft.com/en-us/typography/script-development/myanmar#analyze
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
*/
if (unlikely (hb_in_range<hb_codepoint_t> (u, 0xFE00u, 0xFE0Fu)))
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_VS;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
switch (u)
{
case 0x104Eu:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_C; /* The spec says C, IndicSyllableCategory doesn't have. */
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x002Du: case 0x00A0u: case 0x00D7u: case 0x2012u:
case 0x2013u: case 0x2014u: case 0x2015u: case 0x2022u:
case 0x25CCu: case 0x25FBu: case 0x25FCu: case 0x25FDu:
case 0x25FEu:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_GB;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x1004u: case 0x101Bu: case 0x105Au:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_Ra;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x1032u: case 0x1036u:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_A;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x1039u:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_H;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x103Au:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_As;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x1041u: case 0x1042u: case 0x1043u: case 0x1044u:
case 0x1045u: case 0x1046u: case 0x1047u: case 0x1048u:
case 0x1049u: case 0x1090u: case 0x1091u: case 0x1092u:
case 0x1093u: case 0x1094u: case 0x1095u: case 0x1096u:
case 0x1097u: case 0x1098u: case 0x1099u:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_D;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x1040u:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_D; /* XXX The spec says D0, but Uniscribe doesn't seem to do. */
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x103Eu: case 0x1060u:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_MH;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x103Cu:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_MR;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x103Du: case 0x1082u:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_MW;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x103Bu: case 0x105Eu: case 0x105Fu:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_MY;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x1063u: case 0x1064u: case 0x1069u: case 0x106Au:
case 0x106Bu: case 0x106Cu: case 0x106Du: case 0xAA7Bu:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_PT;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x1038u: case 0x1087u: case 0x1088u: case 0x1089u:
case 0x108Au: case 0x108Bu: case 0x108Cu: case 0x108Du:
case 0x108Fu: case 0x109Au: case 0x109Bu: case 0x109Cu:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_SM;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0x104Au: case 0x104Bu:
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_P;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
case 0xAA74u: case 0xAA75u: case 0xAA76u:
/* https://github.com/roozbehp/unicode-data/issues/3 */
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
cat = OT_C;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
break;
}
if (cat == OT_M)
{
switch ((int) pos)
{
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
case POS_PRE_C: cat = OT_VPre;
pos = POS_PRE_M; break;
case POS_ABOVE_C: cat = OT_VAbv; break;
case POS_BELOW_C: cat = OT_VBlw; break;
case POS_POST_C: cat = OT_VPst; break;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
}
}
[ubsan] Use unsigned int instead enum where needed (#1270) Actually the check is right, On -myanmar.hh, on that particular switch, OT_C is indic_category_t but OT_D is myanmar_category_t so we are mixing the types in one variable. And on -arabic.cc, step can goes one number higher than step_t enum in the loop so we are actually using it as an unsinged int.
2018-10-18 09:36:37 +02:00
info.myanmar_category() = cat;
[myanmar] Add dump-myanmar-data
2018-02-14 06:38:15 +01:00
info.myanmar_position() = pos;
}
Rename hb-*private.hh to hb-*.hh Sorry for the noise, downstream custom builders. Please adjust.
2018-08-26 07:36:36 +02:00
#endif /* HB_OT_SHAPE_COMPLEX_MYANMAR_HH */