The information in this article applies to:
SYMPTOMSIn an SGML-tagged document opened Microsoft Word 6.0 for Windows, underscores appear in the place of some characters. CAUSE
Any character that the SGML converter does not recognize is converted to an
underscore (_).
Filled diamonds (#168) RESOLUTIONInsert the character that did not convert from the Wingdings font set. To insert the character, use the following steps:
The ISO Character Entity declaration statement in your ENTM.CAT file should look like the following: PUBLIC "-//Microsoft Corp//ENTITIES for MS Wingdings//EN" "WINGDING.PUB" MORE INFORMATIONThe converter can always convert any character below 127 in the ANSI character set. And if you reference the ISO character sets WINGDING.PUB, WINGDING.CCF, and WINSYM.CCF in your DTD, the following symbols in a Word document can be converted to character entities in the SGML instance: Characters above 127 in the ANSI character setWhen the SGML instance is converted to Word, the character entity is converted to the referenced character and marked with the currently open style. For example, the "e" with the acute accent in the word "resume" is converted to "resumé" in the SGML instance. When the file is opened in Word, the correct character displays. Symbol characters are converted to SYMBOL fields in Word. For example, the copyright symbol is converted to the following SYMBOL field: {SYMBOL 211 \f "SYMBOL" \s 12 \h}If your DTD uses any of the following items, examine SKELETON.dtd (usually located in the C:\WINWORD\SGMLCONV\SAMPLE directory) to see how to construct a DTD that will work with SGML Author:
Q154264 SGML Author Support Policy REFERENCES"Microsoft SGML Author System Administrator's Guide," pages 118-120 Additional query words: 1.0 sgmlword KB_SGMLAUTHOR 6.0 winword ASCII WordBasic err=123 import imported dash underline line mark word6 glyph glyphs markup
Keywords : kbinterop kbsgml kbformat |
Last Reviewed: January 7, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |