If you do not have access to a Windows computer: No recent versions of Microsoft Word for calendar 2013 template word 2007 the Mac can open files created in any version of WordPerfect.
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.
Wpd (so i put that in the third line).
Take a deep breath, and then read the rest of this page so that you understand this crucial, central, and absolutely essential point.Do not overwrite the copies of the files that are now in new Storage folder!) Right-click on the file named "WordPerfect Text g" in the TextConv folder and choose Merge from the pop-up menu.These filters include the most effective versions of the Word conversion filters for wpdos.1, wpdos.1 equations, and wpdos.x and later.If this happens, press Enter or Insert once only, and then do nothing while the macro works, and the Insert Symbol dialog repeatedly opens.If you dont have Microsoft Word installed on your computer (or even if you do you can view WordPefect files using Corels free software called WordPerfect Lightening, a viewer.Now press Alt-F4 to close the Microsoft Visual Basic editor. Important: Change the file extension.DOC no matter what version of Word you have.A note on files that Microsoft refers to as "security risks Microsoft no longer distributes the files in this set of filters because it has designated them as possible "security risks." This does not mean that they in fact are security risks; they probably present.The following VBA code can be adapted to detect whether a newly-opened file was created by WordPerfect; it should work in Word 2003, 2007, and 2010, but it is entirely undocumented, and it may not work in future versions.I have over a hundred that i needed to get done in a batch, or without clicking each individual file.If you routinely open WordPerfect files in LibreOffice, you can use this macro code to detect whether a newly-opened file was created in WordPerfect, and, if so, run other macros to make changes in the file.The only solution I know of is to save the files from wpdos.x into wpdos.1 format and try again.To solve this problem, download this self-extracting archive of five Microsoft fonts that shipped with older versions of Microsoft Office but are no longer widely available.
I have not tested this.
Sub ifWordPerfect wpVer 0 wpString "not a WordPerfect document." fVer leVersion If InStr(UCase(fVer UCase WordPerfect Then If InStr(fVer, "6.x Then wpVer 6 wpString "created by WordPerfect.x or later." ' Call myWP6SubRoutine Else wpVer 5 wpString "created by WordPerfect.x." ' Call myWP5SubRoutine End.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"tion marks, em dashes, en dashes.Problems with WP files opened in Word 2003, 2007, 2010, 2013 or 2016 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.If you continue to use this site I will assume that you are okay with this.If you want to automate Word in the same way that you now automate wpdos.1, you will need to write new Word macros.A Word XP (Word 2002 Word 2003, 2007, 2010, 2013, and 2016 macro for cleaning up imported WP files You can avoid most problems with fonts in WP files imported into Word if you use the method described elsewhere on this page.Warning: If your WP files include equations or cross-references to footnotes: When you try to print your document, your equations will be numbered, or you will see "Error!