Bring the enum class and its values in line with PDFium naming conventions: drop the FX_ prefix, switch values from SCREAMING_SNAKE to CamelCase, and spell out BRK as Break/Common.Minor nit: should be
```suggestion
Bring the enum class and its values in line with PDFium naming conventions by dropping the FX_ prefix, switching values from SCREAMING_SNAKE to CamelCase, and spelling out BRK as Break/Common.
```
And then wrap.
enum class LineBreakType : uint8_t {
kUnknown = 0x00,
kDirectBreak = 0x1A,
kIndirectBreak = 0x2B,
kCommonIndirectBreak = 0x3C,
kCommonProhibitedBreak = 0x4D,
kProhibitedBreak = 0x5E,
kHangulSpaceBreak = 0x6F,
};
LineBreakType GetLineBreakTypeFromPair(FX_BREAKPROPERTY curr_char,
FX_BREAKPROPERTY next_char);Can this go inside a struct, or a class or something of that sort, leaving it in the global namespace may not be best.
#define FX_LBPB LineBreakType::kProhibitedBreakNot needed for this CL, but a general point: I noticed another one of your CLs that replaces these with constexprs. No need to rework anything here, but maybe consider chaining CLs together in future to avoid rebase/merge conflicts if one lands before the other.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |