GhostScript Font Sizes

[abenson]

Is there a trick to getting the font sizes (fine, large, very large, etc) working with GhostScript? I see 0.10 reverted the GhostScript for this issue, but even after removing/adding the printer for it, the font sizes still won't change.

Switching to a different printer driver, like HP Color LaserJet PS, does print correctly, but I don't want to do that since it doesn't support modern characters, like '€'.

Side note: I really appreciate the work you've done to bring WordPerfect back. I grew up with WP 5.1 for DOS and still keep 5.1+ setup in DOSBOX, but native 8c is a game-changer.

[emendelson]

Until this gets sorted out, download this .ALL file:

https://www.dropbox.com/s/i96hvmnjlqt4c4l/wp51gscr.all?dl=0

Install the driver named Ghostscript Color PS (wpdos.org) (or the Mono PS one if you prefer). It should support font size changes and prints the euro at WP character 4,72 (and, unlike the DOS version, the euro will appear in the editing screen).

This is the driver that I put together for the vDosWP and DOSBoxWP systems. It seems to work well in WP Unix also.

EDIT: unless you've changed the printer file location setting, you'll need to move the .ALL file to /opt/wp80/shlib10/

[abenson]

I appreciate it. I'll be bringing this over to my DOS setups, as well. Thanks!

[taviso]

Hmm I'm confused what the change there is - I thought this issue was fixed.

Does it not work if you just delete and re-install the existing printer?

There was a release with a different .ALL file before I noticed this problem, so if you installed a printer then it might be broken - but if you delete it (Select Printer, Delete) and then reinstall it it should work!

[abenson]

I just tried again and now it works.

I feel dumb, I don't know what I did differently before. I appreciate the help from both of you, in any case.

[emendelson]

And I wasted time and bandwidth by not checking this myself and jumping in with something irrelevant. You can of course use Tavis's ALL file with WPDOS also, and ignore the one that I linked.

[taviso]

It wasn't your fault @abenson! WordPerfect extracts the PRS file from the ALL file and stores it separately, so you likely installed the printer from a release where it was broken and then upgraded - not realizing you had the outdated PRS file!

At the moment I can only partially generate these .ALL files, some steps require manual changes, but I hope to fix that one day so tracking changes will be easier!

[taviso]

No problem :)

I'll close this issue, although I guess I should create an issue to look into a way to automatically update PRS files when the corresponding ALL file changes!

[abenson]

I found the root cause. I was able to recreate my same issue on my other computer.

I'm building a custom package for Void just for ease a management and synchronization. One of two things happened.

1. The tag/hash for v0.10 changed at some point and I had a broken version of it cached.
2. I really screwed up my package when messing with the update and somehow had a bad copy of the file cached.

So in the end, I thought I had v0.10 installed but the cached tarball did not have the right gscript.all file, so even deleting it would copy the broken one over.

Again, I appreciate the help!