A place for those passionate about port, and for those new to it. We hold lots of Port tastings: please join us!
https://www.theportforum.com/
I have FreebooterScript on my computer, which is sufficiently silly for this purpose.JacobH wrote:Almibar Pro
Fixed.JacobH wrote:Should the font selected for the place-mat have, in effect, built in negative kerning, in that some of the glyphs go over the y-axis, then there may be a clash between some letters and the lines on the question and other pages.
For example, the J in Jannon T Moderne Pro Italic overlaps the y-axis (in red) quite considerably:
[!]
Fixed. Also a workaround added to circumvent a bug in Adobe Distiller.jdaw1 wrote:Except the distance of items of Names from the waterboxes.
jdaw1 wrote:• Data is mostly in two arrays, PeopleData and PortData, and is decanted from there into the parameter arrays. For large tastings this can be easier, as it keeps together the relevant items of Titles, Overtitles, FillTexts, etc.
Given our habit of late changes to line-ups, attendance, etc I think the logistics of having these bound will prove to be extremely challenging.jdaw1 wrote:At some tastings there can be insufficjent table space for the TN sheets. So, for very formal tastings, such as the Olympic tasting, there should be A6 tasting booklets, properly bound.
If the binding is expensive per unit, agreed. But if it the the first item that costs most, each subsequent being relatively cheap, we could have some binders for un-named people, much as we currently do with TN sheets.DRT wrote:Given our habit of late changes to line-ups, attendance, etc I think the logistics of having these bound will prove to be extremely challenging.
Much less smart, as the pages would not be named with wines.DRT wrote:with a second sticker listing the wines and attendees that could be placed inside the front cover as a title page?
Your response doesn't address my point, which is logistics, not cost.jdaw1 wrote:If the binding is expensive per unit, agreed. But if it the the first item that costs most, each subsequent being relatively cheap, we could have some binders for un-named people, much as we currently do with TN sheets.DRT wrote:Given our habit of late changes to line-ups, attendance, etc I think the logistics of having these bound will prove to be extremely challenging.
Seconded.RAYC wrote:I would say tht TN sheets are better printed on standard A4 rather than heavy gsm cartridge paper - allows them to be folded and put in jacket for return home!
Agreed, except that DRT’s comment applies also to this.RAYC wrote:However, i did think the use of cartridge paper for placemats was very good, and i must admit i prefer the use of A3 to 2xA4.
I can probably print A3 myself on similar quality paper. Happy to give a trial run for the next tasting. (when is the next tasting, btw....?)jdaw1 wrote:Agreed, except that DRT’s comment applies also to this.RAYC wrote:However, i did think the use of cartridge paper for placemats was very good, and i must admit i prefer the use of A3 to 2xA4.
All good, and happily not needing any enhancements to the placemat code.RAYC wrote:I can probably print A3 myself on similar quality paper. Happy to give a trial run for the next tasting. (when is the next tasting, btw....?)
Happily settransfer can fade the circles, as illustrated by the following code.jdaw1 wrote:• With one wine per A6 sheet, should each sheet have a copy of the glasses tasting circle. Small, or A6-fillingly big? It might be tricky to have that faded, but if possible, should it be faded? (Technical question in comp.lang.postscript.)
Code: Select all
%!
/SquaresForm
<<
/FormType 1
/BBox [ 0 0 60 60 ]
/Matrix matrix identmatrix
/PaintProc
{
pop
0 setgray 0 dup 60 dup rectfill
0.5 setgray 12 dup 36 dup rectfill
0.75 setgray 24 dup 12 dup rectfill
}
>> def % /SquaresForm
<< /PageSize [84 228] >> setpagedevice
12 12 translate
SquaresForm execform
0 72 translate
gsave
{/null exec 0.2 mul 0.8 add} dup 0 currenttransfer put settransfer
SquaresForm execform
grestore
0 72 translate
SquaresForm execform
showpage Easiest for me would be to print to A6. Would that be difficult for the printers?uncle tom wrote:Easiest way would be for each page to be printed four up on an A4 sheet.
Saying what? One or two lines of tasting title; name of person; that’s it? For simplicity of collation the person name could be omitted from the internal pages.uncle tom wrote:I would suggest that the front cover be colour printed on 250 gsm card
For short print runs, the printers use laser printers - printing A4 avoids the need to re-config the paper tray, and I'm not sure if the machines can handle paper smaller than A5.Easiest for me would be to print to A6. Would that be difficult for the printers?
Title of event, date, venue, logo etc. - the cover could be personalised..Saying what? One or two lines of tasting title; name of person; that’s it? For simplicity of collation the person name could be omitted from the internal pages.
The functional benefit is to overcome the lack of table space for A4 sheets.My take is that this seems to be a lot of effort for no functional benefit over A4 tasting sheets
The few tastings where this has been a problem, folding an A4 sheet into thirds (or smaller) has done the trick for me.uncle tom wrote:The functional benefit is to overcome the lack of table space for A4 sheets.My take is that this seems to be a lot of effort for no functional benefit over A4 tasting sheets
Error. Works in Adobe distiller, not in Ghostscript nor in Preview. See PostScript, and output from Adobe Distiller, Ghostscript, and Apple Preview.jdaw1 wrote:(Works in Adobe Distiller; works in GhostScript; but settransfer ignored by Apple Preview. So good in the important two of the three.)
I looked at the pages; my comment was "ooh, a Graham's mini-vertical - yes please!"jdaw1 wrote:Please inspect and comment upon the tasting-note pages in www.jdawiseman.com/2012/20120731_circles_on_TNs.pdf
I think this was to test the concept of the faded circle backgrounds, rather than the A6 format itself.uncle tom wrote:This looks like a regular A4 tasting sheet to me - I can't see how it could be guillotined to A6..
That would help the printers make sure they don't screw up..Should pages of the booklet be numbered?
I think this is the most sensible comment so far in this discussion.RAYC wrote:My take is that this seems to be a lot of effort for no functional benefit over A4 tasting sheets and very little aesthetic benefit. Particularly when 50%+ will never be used.
PhilW wrote:I looked at the pages; my comment was "ooh, a Graham's mini-vertical - yes please!"
uncle tom wrote:This looks like a regular A4 tasting sheet to me - I can't see how it could be guillotined to A6..
Correct: that example was just to test the faded replica of the glasses-page circle.RAYC wrote:I think this was to test the concept of the faded circle backgrounds, rather than the A6 format itself.
Thank you for testing.RAYC wrote:I was worried tht the backgrounds looked too dark on screen, but printed out they are sufficiently faded that they would not be a distraction from the handwriting.
So like the ordinary old-fashioned TN sheets, featuring just one port. OK.RAYC wrote:As an alternative, I would suggest that on each page you could just keep the "G63" motif in big and bold lettering in top left corner and then incorporate the small "Graham 1963" lettering across the top of the page.
Some printers’ printers can auto-rearrange pages for guillotining. It is much much easier for me to supply a PDF of A6 pages. Tom, please ask your printer. And I prefer single sided.RAYC wrote:Guillotining to A6 will require careful thought about page layout, assuming the pages of the booklet will be double sided (which i think they should be)
Yes.RAYC wrote:Should pages of the boolet be numbered?
This is a very good argument.DRT wrote:If it is for guests of the type and number that attended our most recent tasting I think they will go largely unused, and if not produced to a very high standard will appear rather naff and not worthy of a keepsake to remember the event. Personally, I would rather that our guests remember us for our Port and our company rather than our prowess at publishing fancy (or naff) tasting note booklets.
It is very easy to add parametersjdaw1 wrote:Yes.RAYC wrote:Should pages of the boolet be numbered?
Code: Select all
/TastingNotesPaperType /A6 def
/GlassesOnTastingNotePages [ [ 0 ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] ] def
/TastingNotesColumnHeadings [ ] def
/TastingNotesColumnRelativeWidths [ ] def
/TastingNotesCirclesBehind true def
/TastingNotesReplaceNameWithPageNum true def
/VoteRecorderPaperType /A4 def
/HeaderCenterText [{TypeOfPagesBeingRendered /TastingNotes ne {(Graham: a small vertical)} if}] def
/HeaderRightText [{TypeOfPagesBeingRendered /TastingNotes eq
{(Graham: a small vertical)}
{(www) {-0.092 Kern} (.) {-0.092 Kern} (ThePortForum.com, www) {-0.092 Kern} (.jdawiseman.com)}
ifelse}
] def
/ExternalLinks [
(http://www.theportforum.com/viewtopic.php?p=51617#p51617) (Thread on ThePortForum.com)
(http://www.jdawiseman.com/2012/20120818_A6_TN_pages_test.pdf) (Latest version this placemat)
] defjdaw1 wrote:This change has had a consequence that might not have been anticipated. The WaterCounts, on the glasses pages, avoid overlapping the name. Previously, for all people the boxes avoided the widest name. I.e., everybody’s boxes were laid out identically. That is no longer true: boxes are now personalised. So ‟Jim” might have fewer wider rows of boxes than ‟Commander James Bond”, who might have shorter rows, but more of them.
Good job!jdaw1 wrote:This change has had a consequence that might not have been anticipated. The WaterCounts, on the glasses pages, avoid overlapping the name. Previously, for all people the boxes avoided the widest name. I.e., everybody’s boxes were laid out identically. That is no longer true: boxes are now personalised. So ‟Jim” might have fewer wider rows of boxes than ‟Commander James Bond”, who might have shorter rows, but more of them.
[url=http://www.theportforum.com/viewtopic.php?p=51632#p51632]Here[/url] PhilW wrote:Placemats updated here.
Observe that PhilW has used different URLs for the two versions, ‘a’ and ‘b’.[url=http://www.theportforum.com/viewtopic.php?p=51634#p51634]Here[/url] PhilW wrote:Updated here and emailed to you as .ps file.
Thoughts?[url=http://www.theportforum.com/viewtopic.php?p=51640#p51640]Here[/url] jdaw1 wrote:I have tended to have one name for my placemat files, repeatedly overwritten as updated. You have done versioning. Hmm, a question for elsewhere, but do people need versioning?
[url=http://www.theportforum.com/viewtopic.php?p=51650#p51650]Here[/url] PhilW wrote:Habitual due to software releases etc, where source is under version control, but releases (and release candidates) get revision numbers. Not expected to be part of the postscript.
Form (b) has two awkwardnesses. First, what if the requested length overlaps a circle. Second, the array needs to be of huge length to cope with all cases. I could avoid this by renaming to /WaterCountMaxRowLengths, with the last item applying to all subsequent rows. Would that be OK? Would this second form be materially more useful than a single integer WaterCountMaxRowLength?PhilW wrote:Water box formatting
Currently the designer can specify the desired number of water tick boxes, but cannot control the number of bozes per row. In some layouts it would be more aesthetically pleasing to have a 'clump' of boxes rather than a long single line, even if they would fit. Two suggested 'simple' options:
(a) Add a parameter to control the maximum boxes per line, e.g.
/WaterCountTarget 10 def % already provided
/WaterCountRowMax 6 def
(b) Add an optional array parameter to specify the number of bozes per line, e.g.
/WaterCountTarget 10 def % already provided
/WaterCountRows [4 3 2 1] def
What about something likePhilW wrote:Packing style selection
Currently the code allows the designer to specify a preferred ordered list of packing styles; User-specified layout can also be used. An additional feature which could be useful in some situations would be the ability to specify on a per-page basis, which of
the list should be used (rather than the program automatically determining this). An example would be a two-page user-specified layout where the style on each page is to be different, e.g.
/PermittedPackingStyles [
[ [2 5] [0 4] [4 4] [2 3] ] % desired layout for glasses page 1
[ [1 1] [0 2] [4 2] [2 1] ] % desired layout for glasses page 2
] def
/EnforcePackingStyles [ 1 2 ] def
n.b. for consistency with other naming, the above variables might perhaps be better renamed as /PackingStylesPermitted and /PackingStylesEnforce
Code: Select all
/PermittedPackingStyles [ {SheetNum 0 eq {/This} {/None} ifelse} ! ]Code: Select all
/PermittedPackingStyles [ {[/This /That /None] SheetNum get} ! ] defYes, that sounds good and second form more useful imo.jdaw1 wrote:I could avoid this by renaming to /WaterCountMaxRowLengths, with the last item applying to all subsequent rows. Would that be OK? Would this second form be materially more useful than a single integer WaterCountMaxRowLength?
Would be fine, so can ignore this one; I tried something similar which was rejected by the parser so thought that might not be allowed for some semantic reason I was missing, but the semantic error was user-basedjdaw1 wrote:What about something likeCode: Select all
/PermittedPackingStyles [ {SheetNum 0 eq {/This} {/None} ifelse} ! ]
+WaterCountMaxRowLengths done.PhilW wrote:Yes, that sounds good and second form more useful imo.jdaw1 wrote:I could avoid this by renaming to /WaterCountMaxRowLengths, with the last item applying to all subsequent rows. Would that be OK? Would this second form be materially more useful than a single integer WaterCountMaxRowLength?
[url=http://www.theportforum.com/viewtopic.php?p=46131#p46131]Here[/url] jdaw1 wrote:I do agree that it would be neater if the two A1s touched. But how should that be expressed that in the parameter?
Done.[url=http://www.theportforum.com/viewtopic.php?p=46214#p46214]Here[/url] jdaw1 wrote:So [ [0 2] [2 2 3 2] [4 2 3 2] [6 2] [0 1] [3 1] [6 1] [0 0] [3 0] [6 0] ] would make the two A1s touch.
Much of this information isn’t available. Yes, there are headers defined, into which we typically put some of this, but not in a structured way. ‟Tasting Name”, ‟Date”, and ‟Location” will need extra parameters unless reproducing headers is sure to be satisfactory. Attendees are known to the code; as are the ‟Wines” (with the information spread around Circlearrays, Titles, Belowtitles, Abovetitles, and Overtitles). So it seems that this request doesn’t fit the mojo of the rest of the code.DRT wrote:Tasting Name:
Date:
Location:
Attendees:
Wines:
I am unlikely to lose sleep as a result of this suggestion being rejectedjdaw1 wrote:it seems that this request doesn’t fit the mojo of the rest of the code.
PhilW, in the PM quoted [url=http://www.theportforum.com/viewtopic.php?p=52243#p52243]here[/url], wrote:
- Layout was enforced since with minor margin change the default layout was sometimes varying from that intended (rows of 1-2-1-2-1 wanted, default varied between this and 2-2-1-2).
Excepting unity these are in pairs of rationalised reciprocals.jdaw1, in the [url=http://www.jdawiseman.com/papers/placemat/placemat.ps]code[/url], wrote:Code: Select all
% /PseudoHexagonal trivia: fix the number of glasses at eight, and vary the page's usable Height/Width ratio. At which ratios does the number of rows change? % 2 -> 3 0.44444444 4 9 div = 4/9 % 3 -> 4 0.68572971 7 sqrt 1 sub 5 mul 12 div = (Sqrt(7)-1) * 5/12 % 4 -> 3 0.70562062 35 sqrt 15 sqrt add 2 mul 21 sqrt sub 3 sub 17 div = ( (Sqrt(35)+Sqrt(15))*2 - Sqrt(21) - 3 ) / 17 % 3 -> 5 1 1 = 1 % 5 -> 4 1.41719214 35 sqrt 15 sqrt sub 2 mul 3 sub 21 sqrt add 4 div = ( (Sqrt(35)-Sqrt(15))*2 - 3 + Sqrt(21) ) / 4 % 4 -> 5 1.45830052 7 sqrt 1 add 2 mul 5 div = (Sqrt(7)+1) * 2/5 % 5 -> 8 2.25 9 4 div = 9/4
I like too.RAYC wrote:http://vintuswines.com/blog/2012/09/ An intersting approach to placemants by Noval - i like!
Round glass bases on a rectangularly divided tasting mat - where the divisions are too small to hold the base of the glass? Hmmm. Not as much to my taste as the current tasting mats we use.RAYC wrote:http://vintuswines.com/blog/2012/09/ An intersting approach to placemants by Noval - i like!
In [url=http://www.theportforum.com/viewtopic.php?p=52657#p52657]the review of the tasting [i]Mon 15 Oct 2012, The Bung Hole, Delaforce 1958 and friends[/i][/url], jdaw1 wrote:People liked the circle watermarks on the TN sheets. The code has just been changed such that these default to being present.
