WD97: InsertSymbol Result Not Translated Between Mac and ANSI

Last reviewed: March 3, 1998
Article ID: Q181292
The information in this article applies to:
  • Microsoft Word 97 for Windows

SYMPTOMS

If you run a Microsoft Visual Basic for Applications macro (Sub procedure) that inserts a character, a different character may be inserted when the macro is run on the Macintosh than when it is run on Windows.

CAUSE

Word currently does not support conversion of Macintosh CharNum values to equivalent ANSI values, and vice versa.

When a Visual Basic for Applications macro that includes the InsertSymbol method is exchanged between Word 98 Macintosh Edition or later versions for the Macintosh and Word 97 or later versions for Windows, the numeric value of the CharNum or CharacterNumber command is not translated from its Macintosh character set value to its ANSI equivalent, and vice versa.

WORKAROUND

Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:

   http://www.microsoft.com/support/supportnet/refguide/default.asp

Edit the macro on the target platform, replacing the character value with the value that gives correct results. In the following example, replace the number 203 with 192. (ANSI 192, Capital A Grave, is the equivalent of Macintosh character 203.)

The following macro statements insert the Capital A Grave character:

   ' Word for Windows statement
   Selection.InsertSymbol CharacterNumber := 192, Font:= "(normal text)"

   ' Macintosh Word statement
   Selection.InsertSymbol CharacterNumber := 203, Font:= "(normal text)"

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The following Word 98 Macintosh Edition sample macro statement, which inserts the character Capital A Grave (Macintosh character 203) in a Word document, is transferred unchanged to Word 97 for Windows:

   Selection.InsertSymbol CharacterNumber := 203, Font:= "(normal text)"

If the preceding statement is run in Word 97 for Windows, a CE Diaeresis (ANSI 203) is inserted instead of the intended Capital A Grave.

REFERENCES

For more information about getting help with Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q163435
   TITLE     : VBA: Programming Resources for Visual Basic for
               Applications


Additional query words: conversion converted converts transfer transfers
translation translate charnum symbol
Keywords : kbdta kbdtacode word97 OffVBA
Version : WINDOWS:97
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbnofix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.