ThePortForum.com

[url=http://www.theportforum.com/viewtopic.php?p=45355#p45355]Here[/url] RAYC wrote:Placemats printed.

• ‘Purist’ (the printed version is the final version);
• ‘Near-Purist’ (later uploads must be of something that would print the same to paper);
• Other (detail).

DRT wrote:but do wonder what sort of geek would find it necessary to print a set of placemats for a tasting that had already happened.

jdaw1 wrote:

DRT wrote:but do wonder what sort of geek would find it necessary to print a set of placemats for a tasting that had already happened.

That’s not quite the point, I think. The online placemats are part of the record of the tasting. Records are important. (Some might recall that DRT and I are meant to be writing a book based on various records relating to port.)

To what extent can we retrospectively change this ‘record’? My view is slightly, not so much as to change the print, and only very soon after the tasting. It isn’t quite purist, but nearly so.

SushiNorth wrote:Are our placemats being stored and backed up?

jdaw1 wrote:I could add a page listing all the placemats, so that all are archived.

jdaw1 wrote:

jdaw1 wrote:I could add a page listing all the placemats, so that all are archived.

Done. Henceforth the British Library will find all these.

SushiNorth wrote:Is this list intended to include all TPF Tastings, and if so would it be useful to DL the ones that we've done in NYC for inclusion in that archive?

• At DRT’s request, HeaderRightText no longer depends on any other parameters, making it easier to move it to the top.
• Based on a suggestion of PhilW, BackgroundTextsGlassesPaintCode changed from 25% black to 6¼% black.  
• When RAYC prints, he prints the placenames to card. This is stiff enough to require one fold rather than three, so PlaceNamesFirstAndThirdFoldsFromEdge should be set to zero. I promised to add a feature that checked this parameter’s equality to zero, and if so, not to print the lines and instructions. Except that this was already being checked in just this manner. So, no change to software required. But note to self: if RAYC is to print then set /PlaceNamesFirstAndThirdFoldsFromEdge 0 def.
• I noticed that the ‘which shipper’ sheet still had the instruction ‟Record points, not rank.” These words have been moved to the parameter VoteRecorderInstruction.
• RAYC requested a sheet on which corks and cork fragments could be put, both for photography and for observation by others. This has not yet been done, whilst I ponder the range of variations that might be wanted.

• All placemats now include a link to this thread.

jdaw1 wrote:[*]Based on a suggestion of PhilW, BackgroundTextsGlassesPaintCode changed from 25% black to 6¼% black.

PhilW wrote:increasing the line width by 40%

jdaw1 wrote:

• RAYC requested a sheet on which corks and cork fragments could be put, both for photography and for observation by others. This has not yet been done, whilst I ponder the range of variations that might be wanted.

• /CorkDisplay true def, saying whether or not to bother.
• /GlassesClusteredOnCorkDisplay GlassesClusteredOnDecantingNotes def, saying which glasses go there;
• CorkDisplayMinWidth and CorkDisplayMinHeight, being minimum sizes.

jdaw1 wrote:

jdaw1 wrote:

• RAYC requested a sheet on which corks and cork fragments could be put, both for photography and for observation by others. This has not yet been done, whilst I ponder the range of variations that might be wanted.

I think that parameters needed are as follows:

• /CorkDisplay true def, saying whether or not to bother.
• /GlassesClusteredOnCorkDisplay GlassesClusteredOnDecantingNotes def, saying which glasses go there;
• CorkDisplayMinWidth and CorkDisplayMinHeight, being minimum sizes.

Then the code works out how many can go on each sheet. Each is a rectangle, surrounded by the Circlearrays text, very small, and containing, larger but not very large, the various title-like texts. Sheets would be discretely titled ‟The Corks”.

Does that work?

jdaw1 wrote:

• RAYC requested a sheet on which corks and cork fragments could be put, both for photography and for observation by others. This has not yet been done, whilst I ponder the range of variations that might be wanted.

On a PC the specification of NotePad++ looks encouraging user feedback welcomed

PhilW wrote:The value "/NonDecanterLabelGlassesNumCopies 1 def" appears a few lines below the comment "% Non-Glasses Pages %". Changing this value to zero appears to stop the glasses pages from being printed. Is this as intended, or what is this variable intended to control?

PhilW wrote:Also, perhaps a trivial detail but - is there a setting to define the width of any exclusion area on the glasses sheets between the outer ring of text as defined by circlearrays and the inner text defined by titles, belowtitles? In a couple of cases experimenting I found that the inner text can (virtually) meet the outer, and therefore by allowing optionally configurable decrease of the effective inner circle size (in which the title/belowtitle are sized and placed) by a small degree (say <=5%, configurable, or a fixed amount e.g. 1mm) might help clarity?

PhilW wrote:

On a PC the specification of NotePad++ looks encouraging user feedback welcomed

I use Notepad++ daily and find it is an excellent context-sensitive-highlighting text editor for use with many languages including postscript (though I hadn't used it for that particular language before today, I use it for several others regularly); highly recommended.

jdaw1 wrote:

PhilW wrote:The value "/NonDecanterLabelGlassesNumCopies 1 def" appears a few lines below the comment "% Non-Glasses Pages %". Changing this value to zero appears to stop the glasses pages from being printed. Is this as intended, or what is this variable intended to control?

This might be slightly mis-placed, but does what it seems to do. Why, oh why? Because several page types, including decanter labels and pre-pour and sticky-labels, contain extracts from the glasses pages. If there are no glasses pages, there cannot be sticky labels. But what if!? Then have glasses pages, and show 0 copies of them.

jdaw1 wrote:

PhilW wrote:Also, perhaps a trivial detail but - is there a setting to define the width of any exclusion area on the glasses sheets between the outer ring of text as defined by circlearrays and the inner text defined by titles, belowtitles? In a couple of cases experimenting I found that the inner text can (virtually) meet the outer, and therefore by allowing optionally configurable decrease of the effective inner circle size (in which the title/belowtitle are sized and placed) by a small degree (say <=5%, configurable, or a fixed amount e.g. 1mm) might help clarity?

They can indeed touch. Such a parameter could be added, though I think it should be expressed a proportion of one of the radii (Radii, RadiiCirclearrayBaseline, or RadiiCirclearrayInside). Suggest a name for the parameter. (Edit: though the boundaries of the Titles etc are separately constrained if there are decanter labels, and of course common sizing will also shrink some.)

PhilW wrote:In that case I wouldn't suggest it was mis-placed, but perhaps a change of name to something like "/InhibitGlassesPagePrinting" for clarity?

PhilW wrote:If I've understood the current variables correctly - Radii being the radius to the outside of the circlearray text, and RadiiCircleArrayInside to be the radius to the inside of the circlearray text - then I'd suggest RadiiCirclearrayInsideMargin with default either zero (to print as current) or 0.025 (to provide a 2.5% (radially) gap).

jdaw1 wrote:You should delight that, at no effort to yourself, TPF’s finest minds are keeping me in check. Express joy.

AHB wrote:

jdaw1 wrote:You should delight that, at no effort to yourself, TPF’s finest minds are keeping me in check. Express joy.

This is true. I apologise for my earlier, churlish comment. My thanks and appreciation go to those able to contribute meaningfully to this thread and keep Julian challenged and in check.

RAYC wrote:if it's ready in time, i can try next month for the GC-SW-QH tasting. But i appreciate this is non-essential!

In the [url=http://www.theportforum.com/viewtopic.php?p=45591#p45591]GC/SW/QH triple vertical[/url] thread, jdaw1 wrote:Updated draft of the placemats.

• +Cork display sheets, as requested.

jdaw1 wrote:The manual has not yet been updated, but will be soon.

jdaw1 wrote: I hope that people appreciate that this functionality diminished my cellar by a very fine bottle of T77. The sacrifices one makes.

jdaw1 wrote:I have an algorithm problem.

We need a known number of cork-display rectangles, this being computed using CorkDisplayNumCopies and CorkDisplaySpaceForNumExtras. We need to compute how many rows and columns go on each page, subject to CorkDisplayMinWidth and CorkDisplayMinHeight.

So the code loops over /Portrait and /Landscape, computing available space, and loop over numbers of rows and columns:
• Preferring possibilities that meet the CorkDisplayMinWidth and CorkDisplayMinHeight constraints.
• Within those, preferring those requiring as few pages as possible.
• Within those, preferring those for which each rectangle has maximal area.

It’s not bad, but the area preference is wrong, because it has no bias towards rectangles being of the ratio implied by the minima (tall and thin being unhelpful, for example). So, relabelling the minima as H and W, both positive, I want to maximise over positive h and w a function f[h,w,H,W] satisfying:
• f[h,w,H,W] = f[w,h,W,H];
• ∂f[h,w,H,W]/∂h > 0;
• ∂f[h,w,H,W]/∂w > 0;
• w/W > h/H ⇔ ∂f[h,w,H,W]/∂h > ∂f[h,w,H,W]/∂w, equality implying equality.
What should be f[!]? I’m stumped. Suggestions please.

jdaw1 wrote:What should be f[!]? I’m stumped. Suggestions please.

RAYC wrote:I suggest the formation of a working group chaired by AHB

jdaw1 wrote:In a sheet for displaying corks, what should be the default minimum space required per cork? Three inches across? And how much vertical space? (The algorithm will be efficient about space usage, but the minima are important.)

PhilW wrote:f(h,w)=wh/(ah+bw)

jdaw1 wrote:So you prefer a portrait display to landscape? I am surprised.

jdaw1 wrote:

PhilW wrote:f(h,w)=wh/(ah+bw)

An excellent form. It doesn’t quote solve the problem as asked, but if one is instead differentiating with respect to Ln[h] and Ln[w], so considering proportionate increases, it works well.

f[h,w,H,W] = h w /( W h + H w ), or ”“1 if the denominator is ≤0.

This is increasing in both h and w. It can be rearranged to be a constant times a function of (h/H) and (w/W), and is faster increasing in the smaller of these.

Thank you. To be implemented at the next opportunity.

jdaw1 wrote:Think not of the paper, but of the rectangle to hold the cork or cork pieces. That rectangle could be landscape, even on a portrait page (e.g., two columns and four rows). Should the rectangle be portrait or landscape?

jdaw1 wrote:To be implemented at the next opportunity.

/CDSizeScore  % http://www.ThePortForum.com/viewtopic.php?t=175&start=205
	CDHeightOneCork CDWidthOneCork mul
	CorkDisplayMinWidth 0 gt  CorkDisplayMinHeight 0 gt  and
	{
		CorkDisplayMinWidth CDHeightOneCork mul  CorkDisplayMinHeight CDWidthOneCork mul  add  dup 0 gt {div} {pop pop -1} ifelse
	} if  % positive minima
def  % /CDSizeScore

PhilW wrote:You might perfectly validly say "don't set values !"

jdaw1 wrote:Thank you for the clear bug report. Please re-test.