If you are doing XSL-FO processing, then the font currently being used may not contain all special characters. With HTML, when a system viewing an HTML file does not have a screen font installed for a given encoding, in may not display all characters. If you are using Windows, you can use the Character Map application to investigate whether a given font has a certain Unicode character. If the font in use does not have a given character, it may not show up in the display or may display as #.
#EMBEDDED LUCIDA SANS UNICODE PDF#
For example, a PDF file that does not contain embedded fonts relies on the system to supply requested fonts. The output medium may not have a font loaded that can display a special character.
#EMBEDDED LUCIDA SANS UNICODE FULL#
For example, old browsers may not recognize the full range of numerical character references in Unicode. Then the downstream viewer or processor must be able to handle such entities.
If the output encoding does not include the character, the XSLT processor should convert it to a numerical character entity. If the DTD is not available, the processor may continue processing the document as a well-formed document, but it will not be able to resolve the named character entities. Most XSLT processors do not do full validation, but they do load the entities defined in the DTD. That's because the named entities are defined in the DTD, and the processor will not know what the names mean unless it can load the DTD. If you are using named character entities, the DocBook XML DTD must be available to the processor. Also, if you intend to enter a hexadecimal value, be sure to include the x prefix or it will be interpreted as a decimal value. If you enter a numerical character reference wrong, the number may resolve to a range in Unicode that does not have printable characters. If you misspell a named entity, it will not resolve. If only one entity is not resolving, it may simply be entered wrong. However, some browsers do not support all of these space characters, and may display a placeholder character instead of the intended space. In HTML output, these characters will pass through the stylesheet and be rendered in the output encoding for the HTML file. If you need to customize the width of any of those special space characters, you can change the stylesheet parameters that are defined in that module. The length unit used for the leaders is em, which scales to the current font size. So the print stylesheet uses a set of templates in the stylesheet module fo/spaces.xsl to convert them to fo:leader elements of different lengths. However, many print fonts do not support all of the characters in that range. For example, the characters in the Unicode range to represent spaces of different widths. Not all of these characters may work in the various output forms. Used to prevent a line break, as for example, after the hyphen in a word that contains its own hyphen.
Used to allow a line break in a word without generating a hyphen. Space equal to the narrow punctuation of a font. One-sixth of an EM SPACE, similar to thin space. One-fourth of an EM SPACE, called a mid space. One-third of an EM SPACE, called a thick space. Usually a space equal to the type size in points. Space that may not be broken at the end of a line.