MacLink Minus

[Charles Dyer]

On 19 Jul 2007, at 11:23:52, Andrew Brown wrote:

> On 19 Jul 2007, at 12:13, Charles Dyer wrote:
>
>> 1 I've never used v14 of MacLink, but certainly v12 and earlier  
>> did translate WP files, including WP 5.1, without complaint. I  
>> just used that version to translate a bunch of assorted WP files.  
>> Worked fine.
>
> It doesn't complain, I do ;-)

What was the problem?

>
>> 2 WP 3.5e is sensitive to file extensions. It'll read WP 5.x  
>> files... if it recognises them. A .WP5 extension is usually best.
>
> No go with this file. MacLink recognises it, but not WP3.5e.  
> Changing file type and creator enabled WP to see it, but it closed  
> the window as soon as the file opened.

I've never seen that problem with 3.5e. Usually either WP will  
recognise the file, and will work with it, or it won't recognise the  
file.

>
>> 3 some WP 5.x features are not supported with WP 3.5e. There is a  
>> folder called 'ReadMes' which is installed in the WP 3.5e folder  
>> automatically. One file in there is named 'About Conversions'. I'd  
>> have a look at the WordPerfect 5.0-5.2 Import section of that file.
>
> Yes, the "active Mac font" has to have the characters that are  
> normally thrown away, but there's no indication on how to make a  
> font active in a file that does not yet exist.

That would be a problem.

>
>> 5 WP 3.5e is over a decade old. It will never be updated. Corel  
>> did a truly magnificent job of trashing the reputation of WP on  
>> Macs, to the extent that they couldn't give WP away. Literally.
>
> WP used to be excellent, rather like FrameMaker.

And it was excellent. Before Corel got hold of it.