pango-Text-Processing {RGtk2} | R Documentation |
Functions to run the rendering pipeline
pangoItemize(context, text, start.index, length, attrs, cached.iter = NULL)
pangoItemizeWithBaseDir(context, base.dir, text, start.index, length, attrs, cached.iter = NULL)
pangoItemCopy(item)
pangoItemNew()
pangoItemSplit(orig, split.index, split.offset)
pangoReorderItems(logical.items)
pangoContextSetFontMap(object, font.map)
pangoContextGetFontMap(object)
pangoContextGetFontDescription(object)
pangoContextSetFontDescription(object, desc)
pangoContextGetLanguage(object)
pangoContextSetLanguage(object, language)
pangoContextGetBaseDir(object)
pangoContextSetBaseDir(object, direction)
pangoContextGetMatrix(object)
pangoContextSetMatrix(object, matrix)
pangoContextLoadFont(object, desc)
pangoContextLoadFontset(object, desc, language)
pangoContextGetMetrics(object, desc, language = NULL)
pangoContextListFamilies(object)
pangoGetMirrorChar(ch)
pangoUnicharDirection(ch)
pangoFindBaseDir(text, length = -1)
pangoBreak(text, analysis)
pangoGetLogAttrs(text, level, language)
pangoFindParagraphBoundary(text, length = -1)
pangoShape(text, analysis, glyphs)
GObject +----PangoContext
The Pango rendering pipeline takes a string of Unicode characters and converts it into glyphs. The functions described in this section accomplish various steps of this process.
PangoContext
PangoContext
structure stores global information
used to control the itemization process.
PangoItem
PangoItem
structure stores information about
a segment of text. It contains the following fields:
offset
length
num_chars
analysis
PangoAnalysis
] the properties of the segment.
PangoAnalysis
PangoAnalysis
structure stores information about
the properties of a segment of text. It has the following
fields:
font
PangoFont
] the engine for doing rendering-system-dependent processing.level
language
PangoLanguage
] extraAttrs
PangoLogAttr
PangoLogAttr
structure stores information
about the attributes of a single character.
isLineBreak
isMandatoryBreak
isCharBreak
isWhite
isCursorPosition
isWordStart
isWordEnd
isSentenceBoundary
isSentenceStart
isSentenceEnd
backspaceDeletesCharacter
is.cursor.position
is
set). In some languages, the full grapheme
(e.g. letter + diacritics) is considered a
unit, while in others, each decomposed
character in the grapheme is a unit. In the
default implementation of pangoBreak
, this
bit is set on all grapheme boundaries except
those following Latin, Cyrillic or Greek base
characters.
PangoDirection
PangoDirection
type represents a direction in the
Unicode bidirectional algorithm; not every value in this
enumeration makes sense for every usage of PangoDirection
;
for example, the return value of pangoUnicharDirection
and pangoFindBaseDir
cannot be PANGO_DIRECTION_WEAK_LTR
or PANGO_DIRECTION_WEAK_RTL
, since every character is either
neutral or has a strong direction; on the other hand
PANGO_DIRECTION_NEUTRAL
doesn't make sense to pass
to pango\Log2vis\Get\Embedding\Levels()
.
The PANGO_DIRECTION_TTB_LTR
, PANGO_DIRECTION_TTB_RTL
values come from an earlier interpretation of this
enumeration as the writing direction of a block of
text and are no longer used; See the Text module of the
CSS3 spec for how vertical text is planned to be handled
in a future version of Pango. The explanation of why
PANGO_DIRECTION_TTB_LTR
is treated as PANGO_DIRECTION_RTL
can be found there as well.
ltr
rtl
ttb-ltr
PANGO_DIRECTION_RTL
.ttb-rtl
Derived by RGtkGen from GTK+ documentation
http://developer.gnome.org/doc/API/2.0/pango/pango-Text-Processing.html