🚀 go-pugleaf

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.)

In article <4vqlv7$rtd@orb.direct.ca>, Francis J. Chow <fchow@direct.ca> 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.

This is only true if you have obtained CVWW6X.EXE from the Corel web/ftp
site and installed it.  It adds filters for Word 6 reading and writing
to 6.1.  I haven't tried to do so,  but I have heard it can be used with
6.0a also.  If you have no way to get it,  let me know and I will email
you a uuencoded (or base64 encoded) copy.

>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.)

The Micro$oft ftp site has a filter for Word 6 that allows you to read
(not write) WP 6.1 format.  I don't recall the name and I do not have a
copy on hand.
-- 
Rich Greenberg            
N6LRT   TinselTown, USA   Play: richgr@netcom.com               310-649-0238
Pacific time.    I speak for myself & my dogs only.        VM'er since CP-67
Canines: Val(Chinook,CGC), Red(Husky,(RIP)), Shasta(Husky)

iq@incentre.net (Mike Brown -- Interquest Business Solutions Inc.)
wrote:
>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.

>Is there a magic incantation that I need to chant?  Is there
>a utility (shareware, freeware, commercial) that will do
>this? Is there a patch to either of the products that will
>help?

This is a Word 6 document import/export filter for WordPerfect 6.1 (I
don't know of an equivalent for WP 6.0):
ftp://ftp.corel.com/pub/WordPerfect/WordPerfect/WP61WIN/cvww6x.exe

This is a WordPerfect 6 document import (no export) filter for Word
6.0:
http://www.microsoft.com/msword/FreeStuff/Converters/wpcnv.exe

Of course, don't expect perfect conversions from either of them.

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.)

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.)

iq@incentre.net (Mike Brown -- Interquest Business Solutions Inc.)
wrote:

>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.

>Is there a magic incantation that I need to chant?  Is there
>a utility (shareware, freeware, commercial) that will do
>this? Is there a patch to either of the products that will
>help?

MS has an update that will let Word6 read WP6.1 files, but it cannot
write to WP6.1 (I forget the name)

WP already reads Word6. If you want to write to Word6, you need the
conversion filter. (Again, I forget the name)

That said, there is no really "clean" way to convert between the two,
as I have found when I did some test conversions a while back (the
powers-that-be wanted us to standardize on Word--I convinced 'em this
was a BAD idea, although I may have gotten away with it because my
group doesn't share documents with any other part of the company). As
near as I can tell, converting Word6 to WP6.1 is easier than the other
way around. Word6 has some really SCREWY ways of handling headers and
footers and tables and columns and . . . .

JMHO

Lin