🚀 go-pugleaf

The preferable choice for us is to open the WP-documents in WP and
convert them to Word 2.0 or 6. The reason is that during the import
process Word uses font substitution for the extended characters that
Windows ANSI (Word) has and WP (ASCII) doesn't have cause of it's
backwards-compability (I guess) to DOS ASCII.
You will notice this if You import a WP-document into Word, cause
extended characters will be separatley formatted with a "WP
Multilingual" font. In Sweden this problem is big 'cause our alphabet
doesn't end with a "Z",  We've got three characters more. I have
addressed this question to this group some weeks ago and from the
replies I noticed that this is a problem in many countries like for
example France, England, etc.

Best Regards

Sven Ostlind
E-Mail: Sven.Ostlind@mbox325.swipnet.se


fchow@direct.ca (Francis J. Chow) wrote:

>In article <4vqfcl$rc0@news-2.ccinet.ab.ca>, iq@incentre.net (Mike Brown -- Interquest Business Solutions Inc.) says:
>>
>>I have been having problems with a client who uses both
>>WinWord 6.0c and WPWin 6.x(6-point-something).. Documents
>>created in WPWin can't be imported correctly into WinWord
>>and vice-versa.  The WPWin doc have .WPD extensions, and the
>>WinWord docs have .DOC extensions.
>>


>To go from Word 6.0c to WPWin 6.1, you can open the document with WordPerfect
>and have WordPerfect convert it. Alternatively, you can save the Word
>document in WPDOS 5.1 format, and then open it with WPWin 6.1.

>To go from WPWin 6.1 to Word 6.0c, save the document in WPDOS 5.1 format,
>then open it with Word and have Word convert it. (I haven't tried saving
>it in Word 2.0 format using WPWin 6.1.)