Re: MS Word question

Chris <chrissypete2@xxxxxxx> wrote in news:1176828781.740591.298420
@e65g2000hsc.googlegroups.com:

I have created a macro that searches for the word temp and then
replaces it that way, but it doesn't always work due to variations in
the temperature reading and the keystrokes in the macro, and it
doesn't search for times when the word temperature is spelled out
elsehwere in the report.

I have tried the highlighting of the symbol first, and it does appear
as the strange symbol in the Find Window, but I am unable to get the
MSWord symbol to then appear in the Replace Window. The degree sign is
not offered in the codes section of the Find and Replace options.

I am going to see if Fonts is an option there because when I put my
cursor just after the converted degree sign, it shows up as WPMathA in
the font window. In the meantime, does anyone else know of the
solution to search for this WP degree sign/symbol and replace it with
the MSWord degree sign?


I went to google and entered "WP document symbols convert to Word"and found
this:
http://www.columbia.edu/~em36/wpdos/wptoword.html

snip - Problems with WP files opened in Word XP (Word 2002)
If Word displays empty boxes, or the wrong symbols, in place of the symbol
and typographic characters that you expect to see in your imported files,
see another section of this page.

For a general description of features that Word can and cannot import in
WordPerfect 5.x files, see this Microsoft article on the WP Converter in
Word 2002.

Word XP (Word 2002) converts WP files in one of two different ways,
depending on whether or not your system includes the special WP Windows
fonts (for example, WP TypographicSymbols) that are installed by all
versions of WordPerfect for Windows.

If the WP fonts are not present on your system when you open a WP file in
Word XP (Word 2002), then Word smoothly converts most typographic symbols,
such as curly quotation marks, dashes, section marks, etc., into the
equivalent native Windows symbols. However, many non-English characters
(such as the oe and IJ digraphs) are converted into a complex Word feature
called "fields" (described below) instead of simply being converted into
the equivalent symbols in Windows' built-in fonts.

Note: Word also uses its "field" feature (described below) to convert
almost all multinational characters and typographic symbols if you have
installed one of Microsoft's additional text converter packs for Word, and
if the converter installer added the five special fonts described elsewhere
on this page to your Windows system.

If the WP fonts are present on your system when you open a WP file in Word
XP (Word 2002), then Word converts many non-English characters (as
described in the paragraph above) and many typographic symbols (such as
curly quotation marks, em dashes, en dashes, section marks, and others)
into the complex Word "fields." You can avoid this problem by using the
method described elsewhere on this page.

Fields are Word's way of storing almost all data that it does not process
as ordinary text; when you see the current date and time in a Word
document, the underlying code is a field; the current page number in a
header or a footer is actually a field, not simply a number. When Word uses
a field to represent a symbol (like the curly quotation marks in an
imported WP document), you see a quotation mark on screen and the page; but
if you try to use Word's Find dialog to search for the oe digraph or a
quotation mark, Word won't find the symbol, because the oe digraph and the
quotation mark aren't actually present in the file - instead, Word uses a
field comprised of arcane name and number codes to tell it which font and
character to use when displaying the character that is represented by a
field.

The worst problem with Word's use of fields in imported WordPerfect files
is that Word doesn't let you manipulate these fields in the way it lets you
manipulate other fields. Most of Word's fields can be displayed by toggling
Alt-F9, but the fields that Word uses when converting symbols from WP files
are special invisible fields that cannot be displayed. This means that you
can't even search for the fields that contain the WP symbols, although you
can search for almost all other fields. If you want to replace the
unsearchable field with an ordinary Word-style quotation mark, you will
have to look very closely at your document on screen in order to find the
symbols that don't look quite right (the WP quotation mark is small and
narrow, while an ordinary Windows-style quotation mark looks more
spacious). For further details, see this article on Word 2002's handling of
WP formats.

Another section of this page offers a way to convert these fields into
ordinary characters, but the only way I have found to make these hidden
fields easily visible is to tell Word to save the imported WP file in
Microsoft Word for Windows 2.0 format (this requires the conversion filters
described elsewhere on this page); then close the file; and then reopen the
converted Word 2.0 file in Word XP. The fields are now easily visible, and
can be replaced by hand without much effort - unless, of course, you have
an enormous number of them in your file. The visible codes, when displayed
by toggling Alt-F9, look something like this: "{symbol 65\f "WP Typographic
Symbols"\s 12}" You can search for this codes in Word's Find dialog by
searching for: ^19symbol 65 \f "WP Typ (the ^19 character is the code used
in Word's Find dialog to represent the opening curly brace of a field
code).

How to avoid these problems: To avoid these problems, don't open a WP file
with typographic symbols or multinational characters directly in Word XP
(Word 2002). Use WP's Convert.exe or CV.exe program to convert the WP file
into RTF (Rich Text Format) before opening the converted file in Word, or,
if you have WPDOS 6.x, save the file directly into Rich-Text Format from
WP's Save As... dialog box. (See the section immediately below for
details.) Files converted by this method will show the correct, searchable
characters that Word normally uses for quotation marks and dashes and other
symbols.

How to fix these problems in files opened in Word XP (Word 2002): The
simplest way to fix these problems (if you have not avoided them) is to
install and use the special Word macro described elsewhere on this page.


.

Relevant Pages

  • Re: MS Word question
    ... see this Microsoft article on the WP Converter in ... depending on whether or not your system includes the special WP Windows ... However, many non-English characters ... quotation mark, Word won't find the symbol, because the oe digraph and the ...
    (sci.med.transcription)
  • Re: Serial port read troubles
    ... and converting the bytes into ASCII (man readable characters). ... Mac) that I can send data to correctly, but when it sends data back, I ... Windows using the same Keyspan converter. ...
    (comp.lang.basic.realbasic)
  • Re: Corrupt Word Files
    ... Naaaahhhh :-) I open Word documents all the time on external drives. ... designed for PCs and forgot that a Mac file is in two parts: ... Microsoft made a decision some years back to drop support for that converter ... Because Microsoft updated their Word 2 converter for Windows 95/Word 97, ...
    (microsoft.public.mac.office.word)
  • Re: Cannot open .docx documents in Office 2000
    ... Unfortunately the MS converter packs rely on features of Windows 2000 or higher to function. ... I know Windows ME is no longer in support, but the fact is, ...
    (microsoft.public.office.misc)
  • Re: MS Office -- About to be a nightmare -- AGAIN??!
    ... I will try that converter and hope ... If we have to have our custom software redeveloped, ... I am now in a small company that has mostly Windows 98 machines. ...
    (microsoft.public.office.misc)