Software that makes placemats

[JacobH]

I notice Almibar Pro is currently available for $7.99 which might be helpful for testing swash handling:

B.gif (5.27 KiB) Viewed 27060 times

...

[jdaw1]

Almibar Pro

I have FreebooterScript on my computer, which is sufficiently silly for this purpose.

[jdaw1]

Bonus question. The voting sheets and decanting-note sheets have grey straight lines on them. Currently the text is imperfectly fitted to the centre of these lines. So the text, deliberately, might overlap the near half of a line.

Should the fitting be to the centre, or to the edges of the lines?

[jdaw1]

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.

Except the distance of items of Names from the waterboxes.

[jdaw1]

Except the distance of items of Names from the waterboxes.

Fixed. Also a workaround added to circumvent a bug in Adobe Distiller.

As ever, please use the latest version.

[DRT]

This looks like an elegant solution. Collecting most of the relevant data first into two arrays to then be used by the more complicated stuff is just one step closer to a Placemat Wizard.

Edit by JDAW:

• 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.

[jdaw1]

Uncle Tom has suggested another feature for the software, on which comment would be welcomed.

At some tastings there can be insufficient table space for the TN sheets. So, for very formal tastings, such as the Olympic tasting, there should be A6 tasting booklets, properly bound. Much of this is easily acomodated: /TastingNotesPaperType /A6 def already works; and /GlassesOnTastingNotePages [ GlassesOnSheets {{[ exch ]} forall} forall ] def would put one port on each of the A6 tasting-note sheets.

So, questions:

• Would each tasting booklet require a cover sheet? Saying what?

• With one wine per A6 sheet, I think the pages should be less cluttered. The column titles (currently ‟Times”, ‟Eye”, ‟Nose”, ‟Mouth”, ‟Score”) can be zapped with /TastingNotesColumnHeadings [] def and /TastingNotesColumnRelativeWidths [] def, which would also remove the vertical dashed lines. Would there be any other changes to the required page layout?

• 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.)

• Other suggestions.

[DRT]

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.

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.

As an alternative, we could purchase a relatively large batch of these and simply produce a sticker that could be applied to the front cover with the name and date of the tasting, perhaps with a second sticker listing the wines and attendees that could be placed inside the front cover as a title page?

[jdaw1]

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.

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.

with a second sticker listing the wines and attendees that could be placed inside the front cover as a title page?

Much less smart, as the pages would not be named with wines.

[DRT]

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.

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.

Your response doesn't address my point, which is logistics, not cost.

A printer will require a significant amount of time to print, bind and deliver these to us. That time scale will be impacted by what is meant by "properly bound". My suggestion was intended to circumvent those difficulties, not to save money.

[RAYC]

binding is a bit OTT in my opinion. Printing in booklet form can be done on most printers, and A6 is small enough to be stapled.

However, I must say i do not find the space on the sheets, or the A4 format, to be a problem.

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!

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.

Other suggestions? clipboards...?

[jdaw1]

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!

Seconded.

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.

Agreed, except that DRT’s comment applies also to this.

[RAYC]

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.

Agreed, except that DRT’s comment applies also to this.

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]

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....?)

All good, and happily not needing any enhancements to the placemat code.

I think we need Tom to enlarge upon his suggestion.

[jdaw1]

Technicals

• 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.)

Happily settransfer can fade the circles, as illustrated by the following code.

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 

(Works in Adobe Distiller; works in GhostScript; but settransfer ignored by Apple Preview. So good in the important two of the three.)


Forthcoming Placemat Feature
This suggests a more general feature, a boolean TastingNotePagesBackgroundCircles, and a real TastingNotePagesBackgroundCirclesFadingFactor, being both >0 and ≤1, and defaulting to 0.2. These would produce, on the TN pages, a diagonal stripe of circles, tightly fitted” , one for each wine on that TN page. If there’s only one wine ‟tightly fitted” would typically be the width of the page.

”  Tightly fitted? What if there are two pages of TNs, one holding five ports, one holding six? Should the circles be compelled to be the same size? I say not, as they are so faint, and as one typically sees only one TN page at a time.

[uncle tom]

Spiral binding is quite cheap to have done, and works better with a small format than other binding methods, as the pages are easier to lay flat.

Customising them to each participant would be a bit of a struggle, but customising them to the event would be quite simple.

Easiest way would be for each page to be printed four up on an A4 sheet. These can then be stacked and guillotined, and the sets offered up to the spiral binder, which punches and stitches in a single action.

I am also told by my printers that for an A6 booklet, placing the comb on the long side is much to be preferred.

I would suggest that the front cover be colour printed on 250 gsm card, the inner pages on 120 gsm white paper, with the last page on plain white card.

[jdaw1]

Easiest way would be for each page to be printed four up on an A4 sheet.

Easiest for me would be to print to A6. Would that be difficult for the printers?

I would suggest that the front cover be colour printed on 250 gsm card

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.

[RAYC]

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.

I have previously tried using an A6 booklet for notes before and must admit i prefer the width of an A4 page to scribble on, so would strongly favour retention of A4 tasting note sheets even if A6 option is incorporated.

[uncle tom]

Easiest for me would be to print to A6. Would that be difficult for the printers?

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.

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.

Title of event, date, venue, logo etc. - the cover could be personalised..

[uncle tom]

My take is that this seems to be a lot of effort for no functional benefit over A4 tasting sheets

The functional benefit is to overcome the lack of table space for A4 sheets.

[RAYC]

My take is that this seems to be a lot of effort for no functional benefit over A4 tasting sheets

The functional benefit is to overcome the lack of table space for A4 sheets.

The few tastings where this has been a problem, folding an A4 sheet into thirds (or smaller) has done the trick for me.

A4 sheets on regular gsm paper (say, 75gsm) are also to be commended for folding down small for jacket pockets.

For fancy tastings, i can see an aesthetic benefit to an A6 booklet printed with card and bound.

[jdaw1]

(Works in Adobe Distiller; works in GhostScript; but settransfer ignored by Apple Preview. So good in the important two of the three.)

Error. Works in Adobe distiller, not in Ghostscript nor in Preview. See PostScript, and output from Adobe Distiller, Ghostscript, and Apple Preview.

[jdaw1]

Please inspect and comment upon the tasting-note pages in www.jdawiseman.com/2012/20120731_circles_on_TNs.pdf. The idea is that each A6 TN page would be for one port only, and could have this as a faint background.

[PhilW]

Please inspect and comment upon the tasting-note pages in www.jdawiseman.com/2012/20120731_circles_on_TNs.pdf

I looked at the pages; my comment was "ooh, a Graham's mini-vertical - yes please!"

[uncle tom]

This looks like a regular A4 tasting sheet to me - I can't see how it could be guillotined to A6..

[RAYC]

This looks like a regular A4 tasting sheet to me - I can't see how it could be guillotined to A6..

I think this was to test the concept of the faded circle backgrounds, rather than the A6 format itself.

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.

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.

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)

Should pages of the boolet be numbered?

[uncle tom]

Should pages of the booklet be numbered?

That would help the printers make sure they don't screw up..

[DRT]

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.

I think this is the most sensible comment so far in this discussion.

Who are we making these for?

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.

If they are being made for large tastings where 12 or 13 out of the 14 attendees are members of TPF they will be of very limited use as most of us either don't take/keep notes or we keep them electronically.

In both scenarios we should also consider how often this software is likely to be used:

>> How many 20+ person, 8-10 guest tastings are we likely to have in the future. I would suggest the answer is close to none.

>> How many TPFers want to carry a book home from a port tasting. I think the answer is probably close to the answer above.

So, is Julian being asked to spend lots of time creating software that will never or almost never be used?

[jdaw1]

I looked at the pages; my comment was "ooh, a Graham's mini-vertical - yes please!"

This looks like a regular A4 tasting sheet to me - I can't see how it could be guillotined to A6..

I think this was to test the concept of the faded circle backgrounds, rather than the A6 format itself.

Correct: that example was just to test the faded replica of the glasses-page circle.

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.

Thank you for testing.

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.

So like the ordinary old-fashioned TN sheets, featuring just one port. OK.

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)

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.

Should pages of the boolet be numbered?

Yes.

[jdaw1]

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.

This is a very good argument.

[jdaw1]

Should pages of the boolet be numbered?

Yes.

It is very easy to add parameters

• /TastingNotesReplaceNameWithPageNum true def
  /TastingNotesPageNumCompoundString [(Page ) {TastingSheetNum 1 add 5 string cvs}] def

which is trivial to code and has a lot of flexibility.

(Note to self: make changes at end of TastingNotesInnerLoop.)

[jdaw1]

Done, I think, in that jdawiseman.com/2012/20120818_A6_TN_pages_test.pdf was made using the following parameter changes.

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)
] def

Are the page numbers OK? IS the lightening of the TN pages (no column splits) a good idea?

Arranging multiple A6 pages onto A4 to suit the particular cutting needs of a printer is a task that I am leaving for the printer’s page management software.


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.

[jdaw1]

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.

[DRT]

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!

Which tasting is he coming to? Is he bringing Her Majesty Elizabeth the Second, by the Grace of God, of the United Kingdom of Great Britain and Northern Ireland, and of Her other Realms and Territories, Queen, Head of the Commonwealth, Defender of the Faith?

[jdaw1]

Placemats updated here.

Updated here and emailed to you as .ps file.

Observe that PhilW has used different URLs for the two versions, ‘a’ and ‘b’.

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?

Thoughts?

Edit:

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.

[PhilW]

Two suggestions for additional features:

1. 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

2. 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

[jdaw1]

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

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?

[jdaw1]

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

What about something like

Code: Select all

/PermittedPackingStyles [ {SheetNum 0 eq {/This} {/None} ifelse} ! ]

or even

Code: Select all

/PermittedPackingStyles [ {[/This /That /None] SheetNum get} ! ] def

(where This and That are to be replaced with something else)? (Neither of which need any change to the code.)

[PhilW]

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?

Yes, that sounds good and second form more useful imo.

What about something like

Code: Select all

/PermittedPackingStyles [ {SheetNum 0 eq {/This} {/None} ifelse} ! ]

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-based

[jdaw1]

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?

Yes, that sounds good and second form more useful imo.

+WaterCountMaxRowLengths done.

Easiest way to update your code would be to search for ‟WaterCountMaxRowLengths”, and splice in that line. Then search in the new code for ‟%%%”, copy from there down, and paste into same place in yours. If being pedantic also substitute line 6.

[jdaw1]

I do agree that it would be neater if the two A1s touched. But how should that be expressed that in the parameter?

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.

Done.

[DRT]

On my last trip to Porto and the Douro I purchased a notebook that I intend to use for future trips. I know of others who take the same notebook time after time to use as an immediate source of reference at tastings.

Perhaps it would be good to have the option of a Tasting Summary Sticker that included:

Tasting Name:
Date:
Location:
Attendees:
Wines:

These stickers could then be placed into notebooks in which tasting notes are to be written.

Yes, I know. It's just laziness not to write all of those things directly into the notebook. But not everything produced by the placemats programme is essential, so these would simply be for convenience of those who need them.

Default should be /TastingSummaryStickers = False

[jdaw1]

My immediate reaction is not enthusiastic.

Tasting Name:
Date:
Location:
Attendees:
Wines:

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.

But if others are enthusiastic I’ll reconsider.

[DRT]

it seems that this request doesn’t fit the mojo of the rest of the code.

I am unlikely to lose sleep as a result of this suggestion being rejected

[jdaw1]

In implementing WaterCountMaxRowLengths I forgot to re-include the parameters that control which pages hold water boxes. PhilW remarked on this bug at the Warre versus Fonseca vertical, and in the PM quoted here. It has been remedied, and is regretted.

[jdaw1]

• 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).

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

Excepting unity these are in pairs of rationalised reciprocals.

So PermittedPackingStyles being [ /PseudoHexagonal ] causes the less elegant four-row arrangement to happen with a height÷width ratio in the narrow range between ½âˆš35 + ¼√21 ”“ ½âˆš15 ”“ ¾ ≈ 1.4172, and â…–(1+√7) ≈ 1.4583.

[RAYC]

http://vintuswines.com/blog/2012/09/ An intersting approach to placemants by Noval - i like!

[jdaw1]

http://vintuswines.com/blog/2012/09/ An intersting approach to placemants by Noval - i like!

I like too.

[Alex Bridgeman]

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.

[jdaw1]

People liked the circle watermarks on the TN sheets. The code has just been changed such that these default to being present.