Software that makes placemats

[Andy Velebil]

For the purposes of testing this you could force the software to output CMYK or RGB somewhere on the sheet.

Did DRT just get all computer technical and stuff. Julian what have you done to him?

[jdaw1]

For the purposes of testing this you could force the software to output CMYK or RGB somewhere on the sheet.

Brilliant. Done. Old files replaced.

[PhilW]

For the purposes of testing this you could force the software to output CMYK or RGB somewhere on the sheet.

Brilliant. Done. Old files replaced.

Surely the best approach would be a CMYK to RGB colour-space conversion performed in post-script?

[flash_uk]

On my HP Officejet Pro 8600 Plus at home, RGB is considerably darker and sharper. Will bring the prints to the next tasting we attend together.

Wow! That is very surprising. Thank you for testing.

Maybe I'll just check that I got them the right way round.

OK, retested with the updated pdfs. Same result, RGB darker and sharper.

Will also test on a Samsung Multi-function laser printer in the office tomorrow.

[jdaw1]

I now have GhostScript installed and so tried it myself using the first file that I generated for this set of placemats. (I sent a different file to my friend based off a known-to-be-good version from the FTLOP 1985 Horizontal in January.)

Works fine with the new scan converter.

Glenn: are you able to update your GhostScript to the latest? Please would you be willing to /InlineTitlesAttemptMinimiseNumContours true def, and test whether new GhostScript is still painfully slow? Thank you.

This is not urgent.

Edit: also /InlineTitlesMaxNumberContours 20 def.

[Glenn E.]

I now have GhostScript installed and so tried it myself using the first file that I generated for this set of placemats. (I sent a different file to my friend based off a known-to-be-good version from the FTLOP 1985 Horizontal in January.)

Works fine with the new scan converter.

Glenn: are you able to update your GhostScript to the latest? Please would you be willing to /InlineTitlesAttemptMinimiseNumContours true def, and test whether new GhostScript is still painfully slow? Thank you.

This is not urgent.

Edit: also /InlineTitlesMaxNumberContours 20 def.

I don't believe that I have GhostScript installed on my current computer. I have gone back to using ps2pdf.com because you fixed the issue that was causing that website to fail.

Glenn

[jdaw1]

Bug report re Mac Preview’s setlinewidth and clip’ping

FYI.

This is the text of a bug report re Mac Preview 10.0 (944.4) under macOS High Sierra 10.13.3. Please suggest improvements: whatever makes it more likely to be fixed.

Mac Preview mis-displays PDF files. Both setlinewidth and clip'ping regions are seriously mis-displayed, which is most inconvenient for those using macOS to produce beautiful files.

A PDF file has been made from the hand-written PostScript file at
www.jdawiseman.com/papers/bugs/201803_P ... lip_bug.ps
Because this is handwritten, it can be read and understood by a human, who can then see what it is meant to do, and compare to what actually happens.

It was distilled with Distiller XI Pro 11.0.23 (01/11/2017) to make
www.jdawiseman.com/papers/bugs/201803_P ... ip_bug.pdf

The PostScript was opened in Mac Preview 10.0 (944.4) under macOS High Sierra 10.13.3, and at 1200* screenshotted to make

Observe error: red stroke of the (S) is much thinner than it should be.

The distilled PDF was opened in Mac Preview 10.0 (944.4) under macOS High Sierra 10.13.3, and at 1200* screenshotted to make

Two errors: red stroke of the (S) is much thinner than it should be. Also the painting of the triangle clipped to the (S) is not correctly clipped: some green and black spills out of the S.

The same distilled was PDF opened in Adobe Acrobat Reader DC 2018.011.20038, and at 1200* screenshotted to make

This shows correctly.

The text of this report is also at www.jdawiseman.com/papers/bugs/201803_P ... ip_bug.txt

Any or all files might be updated or improved to show the bug better. Check for latest.

Summary: Preview badly mis-displays the PDF, and also (though to a lesser extent) the PostScript.

Mac Bug 38317613 https://bugreport.apple.com/web/?problemID=38317613
Also at https://groups.google.com/forum/#!topic ... O_tFq3dyDM

[jdaw1]

In 'Table of Contents', Preview’s navigation dysfunctional

This is the text of a bug report re Mac Preview 10.0 (944.4) under macOS High Sierra 10.13.3.

Download and open
http://www.jdawiseman.com/2018/20180102_Ideally1878.pdf
View > Table of Contents (or, equivalently, command-option-3)
Click on the arrow next to “Vote recorders (pp35-39, A4)” to make visible its sub-items.

Click on “Wine of the Night? (p37, A4)”. The black focus jumps from there up a few lines. Click on “What is it? (p39, A4)”. Again focus jumps.

In a previous version of Preview (no, I don't know precisely, but about two OS's ago) one could navigate through the Table of Contents using up and down arrows. Attempt same. Observe jumping about. This user interface isn't working.

Please fix.

The text of this bug report, perhaps updated or improved, is also at
http://www.jdawiseman.com/papers/bugs/2 ... ntents.txt

I have many PDFs giving Preview this problem, including:
http://www.jdawiseman.com/2017/20171219_1977s.pdf
http://www.jdawiseman.com/2017/20171130 ... _1970s.pdf
http://www.jdawiseman.com/2017/20171129_Calem.pdf
http://www.jdawiseman.com/2017/20171102_1970s.pdf
http://www.jdawiseman.com/2017/20171019_mature.pdf
http://www.jdawiseman.com/2017/20171010 ... mpbell.pdf
http://www.jdawiseman.com/2017/20170928_Bring.pdf
http://www.jdawiseman.com/2017/20170907_SQVP_Blind.pdf
http://www.jdawiseman.com/2017/20170809_Blind.pdf
http://www.jdawiseman.com/2017/20170801_Emergency.pdf
http://www.jdawiseman.com/2017/20170713_Blind.pdf
http://www.jdawiseman.com/2017/20170621 ... yHouse.pdf
http://www.jdawiseman.com/2017/20170600_Portugal.pdf
http://www.jdawiseman.com/2017/20170608_1967s.pdf
http://www.jdawiseman.com/2017/20170524 ... mebody.pdf
http://www.jdawiseman.com/2017/20170510 ... quired.pdf
http://www.jdawiseman.com/2017/20170426_DFW.pdf
http://www.jdawiseman.com/2017/20170419_emergency.pdf
http://www.jdawiseman.com/2017/20170406_1955s.pdf
http://www.jdawiseman.com/2017/20170322_blind.pdf
http://www.jdawiseman.com/2017/20170309 ... tangle.pdf
http://www.jdawiseman.com/2017/20170301 ... uctory.pdf
http://www.jdawiseman.com/2017/20170204_CUTwC.pdf
http://www.jdawiseman.com/2017/20170204 ... rkusen.pdf
http://www.jdawiseman.com/2017/20170201 ... it_hen.pdf
http://www.jdawiseman.com/2017/20170104 ... Bottle.pdf

Mac Bug report 38358147 https://bugreport.apple.com/web/?problemID=38358147

[jdaw1]

Apple Preview ignores many pdfmark settings

This is the text of a bug report re Mac Preview 10.0 (944.4) under macOS High Sierra 10.13.3.

mark {Catalog} << /PageLayout /TwoPageLeft >> /PUT pdfmark
This PostScript command, which is echoed in the PDF, causes a two page layout in which the first page is not shown by itself. Two pages, without title page. Heeded by Adobe reader; ignored by Preview.


mark /Action << >> /Color [0 0 0] /F 0 /Title () /OUT pdfmark
mark /Action << >> /Color [0 0 0] /F 2 /Title (\247 Re-ordered) /OUT pdfmark
The “/F 2” sets the Outline (= Table of Contents) entry to be bold. Heeded by Adobe reader; ignored by Preview.

Code: Select all

mark
	/Rect [ ... ]
	/Subtype /Polygon
	/BS  << /Type /Border  /W 1  /S /S >>
	/Subj (A string)
	/ModDate ParametersVersionDateTimeAdobeFormat
	/F 64 128 add  % ReadOnly + Locked. PDFReference16.pdf page 574
	/Vertices [ ... ]
	/Color [ 0.6 0.6 1.0 ]
/ANN pdfmark

Adds a non-printing polygon to show the boundary of something. Heeded by Adobe reader; ignored by Preview.

The first two of these bugs can be seen by opening
http://www.jdawiseman.com/2018/20180102_Ideally1878.pdf
and the third in
http://www.jdawiseman.com/2016/20161215_White_Horse.pdf

Please could these and other settings be heeded.

This text, perhaps updated, will appear at
http://www.jdawiseman.com/papers/bugs/2 ... ttings.txt

Apple bug 38391355 https://bugreport.apple.com/web/?problemID=38391355

[PhilW]

In the latest placemats, why are the "1963" over the shipper different sizes?

Draft of the placemats.

In the above, the 1963 over Ck and Mz are clearly smaller than those over G and D; perhaps some form of proportion since the Mz and Ck are in a smaller font than G and D (being maximised to fit within circles), but it would look better if all the 1963s were the same size font. I don't know how the font size decision for the over-print of the year was determined (I haven't looked, to be fair); perhaps some additional form of control might already provide the capability to enforce a common font size for the 1963s since they are all the same and in the same size area, but if not then perhaps it might be a worthwhile addition.

[jdaw1]

In the above, the 1963 over Ck and Mz are clearly smaller than those over G and D; perhaps some form of proportion since the Mz and Ck are in a smaller font than G and D (being maximised to fit within circles), but it would look better if all the 1963s were the same size font. I don't know how the font size decision for the over-print of the year was determined (I haven't looked, to be fair); perhaps some additional form of control might already provide the capability to enforce a common font size for the 1963s since they are all the same and in the same size area, but if not then perhaps it might be a worthwhile addition.

It was wrong. I will investigate whether it was a user error or a programmer failure (same person; different roles) and suggest a plan, or just effect it.

[jdaw1]

Instead of

Code: Select all

/OvertitleMaxFontSizeProportionTitles 0.125 def

it would have been better to do

Code: Select all

/OvertitleMaxFontSizeProportionTitles 0.166666666 def
/FontSizesRatioAboveBelowOverMin 999 def

So it could be a user error.

But I think a change of default for FontSizesRatioAboveBelowOverMin would be advisable, from

Code: Select all

/FontSizesRatioAboveBelowOverMin 2 sqrt sqrt def

to

Code: Select all

/FontSizesRatioAboveBelowOverMin 999 def

So it could be a programmer error.

A reminder: if font sizes are closer in ratio than FontSizesRatioAboveBelowOverMin (or, mutatis mutandis, FontSizesRatioTitlesMin, then they are set to be the same. It is, in ratio terms, the minimum difference in font size. These two parameters prevent there being many font sizes that differ only slightly.

Objections?

[jdaw1]

Code: Select all

/FontSizesRatioAboveBelowOverMin 999 def

Done.