Download - Multivac!

Table 4.8 Control characters and their meaning in TextflowsUnicode character entity name equiv. Textflowoptionmeaning within Textflows in Unicode-compatible fontsU+0020 SP, space space align words and break linesU+00A0 NBSP, nbsp (none) (no-break space) space character which will not break linesU+0009 HT, hortab (none) horizontal tab: will be processed according to the ruler,tabalignchar, and tabalignment optionsU+002D HY, hyphen (none) separator character for hyphenated wordsU+00AD SHY, shy (none) (soft hyphen) hyphenation opportunity, only visible at line breaksU+000BU+2028VT, verttabLS, linesepnextline(next line) forces a new lineU+000AU+000DU+000D andU+000AU+0085U+2029LF, linefeedCR, returnCRLFNEL, newlinePS, parasepnextparagraph(next paragraph) Same effect as nextline; in addition, theparindent option will affect the next line.U+000C FF, formfeed return PDF_fit_textflow( ) will stop, and return the string _nextpage.Glyph name references. A font may contain glyphs which are not directly accessiblebecause the corresponding Unicode values are not known in advance (e.g. PUA assignments)or because they do not even have Unicode values in the font. Although allglyphs in a font can be addressed via the glyphid encoding, this is very cumbersome anddoes not fit Unicode workflows. As a useful facility glyph name references can be used.These are similar to character references, but use a slightly different syntax and refer tothe glyph by name (note that the first period character is part of the syntax, while thesecond is part of the glyph name in the examples):&.T.swash;&.orn.15;Glyph name references will not be converted by default; you must explicitly set thecharref parameter or option to true if you want to use glyph name references in contentstrings:p.set_parameter("charref", "true");Glyph name references are useful for alternate forms (e.g. swash characters, tabular figures)and glyphs without any specific Unicode semantics (symbols, icons, and ornaments).The general syntax is &.; where name is a glyph name which will be substitutedas follows:> Font-specific glyph names from OpenType fonts (but not OpenType CID fonts) canbe used for content strings (since these are always related to a particular font);> Glyph names used in encodings can be used for content strings;> Names from the Adobe Glyph List (including the uniXXXX and u1XXXX forms) pluscertain common »misnamed« glyph names will always be accepted for contentstrings and hypertext strings.90 Chapter 4: Unicode and Legacy Encodings