| Copyright | Will Thompson and Iñaki García Etxebarria |
|---|---|
| License | LGPL-2.1 |
| Maintainer | Iñaki García Etxebarria |
| Safe Haskell | Safe-Inferred |
| Language | Haskell2010 |
GI.HarfBuzz.Flags
Description
Synopsis
- data BufferDiffFlagsT
- = BufferDiffFlagsTEqual
- | BufferDiffFlagsTContentTypeMismatch
- | BufferDiffFlagsTLengthMismatch
- | BufferDiffFlagsTNotdefPresent
- | BufferDiffFlagsTDottedCirclePresent
- | BufferDiffFlagsTCodepointMismatch
- | BufferDiffFlagsTClusterMismatch
- | BufferDiffFlagsTGlyphFlagsMismatch
- | BufferDiffFlagsTPositionMismatch
- | AnotherBufferDiffFlagsT Int
- data BufferFlagsT
- = BufferFlagsTDefault
- | BufferFlagsTBot
- | BufferFlagsTEot
- | BufferFlagsTPreserveDefaultIgnorables
- | BufferFlagsTRemoveDefaultIgnorables
- | BufferFlagsTDoNotInsertDottedCircle
- | BufferFlagsTVerify
- | BufferFlagsTProduceUnsafeToConcat
- | BufferFlagsTProduceSafeToInsertTatweel
- | BufferFlagsTDefined
- | AnotherBufferFlagsT Int
- data BufferSerializeFlagsT
- data GlyphFlagsT
- data OtColorPaletteFlagsT
- data OtMathGlyphPartFlagsT
- data OtVarAxisFlagsT
Flags
BufferDiffFlagsT
data BufferDiffFlagsT Source #
Flags from comparing two BufferT's.
Buffer with different BufferContentTypeT cannot be meaningfully
compared in any further detail.
For buffers with differing length, the per-glyph comparison is not
attempted, though we do still scan reference buffer for dotted circle and
.notdef glyphs.
If the buffers have the same length, we compare them glyph-by-glyph and report which aspect(s) of the glyph info/position are different.
Since: 1.5.0
Constructors
| BufferDiffFlagsTEqual | equal buffers. |
| BufferDiffFlagsTContentTypeMismatch | buffers with different
|
| BufferDiffFlagsTLengthMismatch | buffers with differing length. |
| BufferDiffFlagsTNotdefPresent |
|
| BufferDiffFlagsTDottedCirclePresent | dotted circle glyph is present in the reference buffer. |
| BufferDiffFlagsTCodepointMismatch | difference in |
| BufferDiffFlagsTClusterMismatch | difference in |
| BufferDiffFlagsTGlyphFlagsMismatch | difference in |
| BufferDiffFlagsTPositionMismatch | difference in |
| AnotherBufferDiffFlagsT Int | Catch-all for unknown values |
Instances
BufferFlagsT
data BufferFlagsT Source #
Flags for BufferT.
Since: 0.9.20
Constructors
| BufferFlagsTDefault | the default buffer flag. |
| BufferFlagsTBot | flag indicating that special handling of the beginning of text paragraph can be applied to this buffer. Should usually be set, unless you are passing to the buffer only part of the text without the full context. |
| BufferFlagsTEot | flag indicating that special handling of the end of text
paragraph can be applied to this buffer, similar to
|
| BufferFlagsTPreserveDefaultIgnorables | flag indication that character with Default_Ignorable
Unicode property should use the corresponding glyph
from the font, instead of hiding them (done by
replacing them with the space glyph and zeroing the
advance width.) This flag takes precedence over
|
| BufferFlagsTRemoveDefaultIgnorables | flag indication that character with Default_Ignorable
Unicode property should be removed from glyph string
instead of hiding them (done by replacing them with the
space glyph and zeroing the advance width.)
|
| BufferFlagsTDoNotInsertDottedCircle | flag indicating that a dotted circle should not be inserted in the rendering of incorrect character sequences (such at <0905 093E>). Since: 2.4.0 |
| BufferFlagsTVerify | flag indicating that the |
| BufferFlagsTProduceUnsafeToConcat | flag indicating that the |
| BufferFlagsTProduceSafeToInsertTatweel | flag indicating that the |
| BufferFlagsTDefined | All currently defined flags: Since: 4.4.0 |
| AnotherBufferFlagsT Int | Catch-all for unknown values |
Instances
BufferSerializeFlagsT
data BufferSerializeFlagsT Source #
Flags that control what glyph information are serialized in bufferSerializeGlyphs.
Since: 0.9.20
Constructors
| BufferSerializeFlagsTDefault | serialize glyph names, clusters and positions. |
| BufferSerializeFlagsTNoClusters | do not serialize glyph cluster. |
| BufferSerializeFlagsTNoPositions | do not serialize glyph position information. |
| BufferSerializeFlagsTNoGlyphNames | do no serialize glyph name. |
| BufferSerializeFlagsTGlyphExtents | serialize glyph extents. |
| BufferSerializeFlagsTGlyphFlags | serialize glyph flags. Since: 1.5.0 |
| BufferSerializeFlagsTNoAdvances | do not serialize glyph advances, glyph offsets will reflect absolute glyph positions. Since: 1.8.0 |
| BufferSerializeFlagsTDefined | All currently defined flags. Since: 4.4.0 |
| AnotherBufferSerializeFlagsT Int | Catch-all for unknown values |
Instances
GlyphFlagsT
data GlyphFlagsT Source #
Flags for GlyphInfoT.
Since: 1.5.0
Constructors
| GlyphFlagsTUnsafeToBreak | Indicates that if input text is broken at the beginning of the cluster this glyph is part of, then both sides need to be re-shaped, as the result might be different. On the flip side, it means that when this flag is not present, then it is safe to break the glyph-run at the beginning of this cluster, and the two sides will represent the exact same result one would get if breaking input text at the beginning of this cluster and shaping the two sides separately. This can be used to optimize paragraph layout, by avoiding re-shaping of each line after line-breaking. |
| GlyphFlagsTUnsafeToConcat | Indicates that if input text is changed on one
side of the beginning of the cluster this glyph
is part of, then the shaping results for the
other side might change.
Note that the absence of this flag will NOT by
itself mean that it IS safe to concat text.
Only two pieces of text both of which clear of
this flag can be concatenated safely.
This can be used to optimize paragraph
layout, by avoiding re-shaping of each line
after line-breaking, by limiting the
reshaping to a small piece around the
breaking position only, even if the breaking
position carries the
|
| GlyphFlagsTSafeToInsertTatweel | In scripts that use elongation (Arabic, Mongolian, Syriac, etc.), this flag signifies that it is safe to insert a U+0640 TATWEEL character before this cluster for elongation. This flag does not determine the script-specific elongation places, but only when it is safe to do the elongation without interrupting text shaping. Since: 5.1.0 |
| GlyphFlagsTDefined | All the currently defined flags. |
| AnotherGlyphFlagsT Int | Catch-all for unknown values |
Instances
OtColorPaletteFlagsT
data OtColorPaletteFlagsT Source #
Flags that describe the properties of color palette.
Since: 2.1.0
Constructors
| OtColorPaletteFlagsTDefault | Default indicating that there is nothing special to note about a color palette. |
| OtColorPaletteFlagsTUsableWithLightBackground | Flag indicating that the color palette is appropriate to use when displaying the font on a light background such as white. |
| OtColorPaletteFlagsTUsableWithDarkBackground | Flag indicating that the color palette is appropriate to use when displaying the font on a dark background such as black. |
| AnotherOtColorPaletteFlagsT Int | Catch-all for unknown values |
Instances
OtMathGlyphPartFlagsT
data OtMathGlyphPartFlagsT Source #
Flags for math glyph parts.
Since: 1.3.3
Constructors
| OtMathGlyphPartFlagsTExtender | This is an extender glyph part that can be repeated to reach the desired length. |
| AnotherOtMathGlyphPartFlagsT Int | Catch-all for unknown values |
Instances
OtVarAxisFlagsT
data OtVarAxisFlagsT Source #
Flags for OtVarAxisInfoT.
Since: 2.2.0
Constructors
| OtVarAxisFlagsTHidden | The axis should not be exposed directly in user interfaces. |
| AnotherOtVarAxisFlagsT Int | Catch-all for unknown values |