# 11x17 half/half layout #4

Closed
opened this Issue Oct 20, 2018 · 21 comments

Projects
None yet
3 participants
Contributor

### anarcat commented Oct 20, 2018

 Hi! Those calendars seem to be designed towards a single-page, 8.5x11 (or A4 in metric) but I would like to print a more classic "split in half" calendar (with a spiral binding in the middle) which is usually built with a larger 11x17" (or A3 in metric) sheet split in half. The biggest advantage is that there is more room in the calendar part of the sheet to write stuff down. In the "small landscape" layout, there is not much room for people to write notes in the calendar, and I'd like to make that better. It would also mean writing the events directly in the calendar grid instead of below the grid. Have you considered working on such a layout? How much work would be involved in porting this? Thanks!
Contributor

### gambhiro commented Oct 21, 2018

 Hello there, interesting idea. The origin of this class is that I produce wall calendars with it. So the examples are all about that sort of layout, where you want an image and the days on the wall, but not for taking notes or making schedules. Implementing a different layout is certainly possible. There is a command that gets called for every month to do page layout. This is empty at the start, and will do nothing if not redefined, so there are no assumptions about how it should lay out the elements. Each layout design redefines this command to specify how the pages should be produced. Two pages per month (one side photo, one side notes) are not a problem either. Could you add an image of a good example of the layout you have in mind? A photo would be best. I don't have time to design it now but I'm happy to give guidance or I might come back to it later.
Contributor

### anarcat commented Oct 22, 2018

 This is pretty much what I'm trying to replicate: I would describe this as a "two-page wall calendar with a spiral binding in the middle, photo on top, grid below, about A3 sized". I also want the "holidays" to be inline, directly in the grid boxes, as a small note so there's still room for hand-written stuff. Here's another example which show that aspect better: It's pretty much "two pages per month", but I couldn't find such an example in the docs. Did I miss something? I must admit my experience with Latex graphic layout gymnastic are limited and it's where I generally give up angrily whenever I try to make sense of things. :) I would be very happy to try if you give me a few hints to get started though. So far I'm down to using ODT or PDF templates and it hurts just to think about going that route. :/
Contributor

### gambhiro commented Oct 22, 2018

 Thanks for the images and description. It looks useful too. I would like to give it a go sometime. Do you need this by some particular time, for printing a personal calendar for example?
Contributor

### anarcat commented Oct 22, 2018

 yeah, i want to print this for the new year, and would like proof-reading samples by early December. No pressure though, I can always fallback to doing the stuff myself, either in LaTeX (unlikely, TBH) or (more likely) as SVG templates. one thing that's tricky in that layout is that it needs to be printed recto-verso and my mind melts just to think how it would actually lay out in a PDF document. Maybe it would be easier (and require less post-processing) to print it on A4 (US legal) instead and just join those instead of cutting a A3/11x17. thank you so much for your consideration!

Contributor

### gambhiro commented Oct 26, 2018

 Checkout the notes-page branch and take a look at doc/examples/cal-photo-and-notes.tex. Link to the pdf: cal-photo-and-notes.pdf Also see screenshots below. Looking quite good I think! Is this the sort of thing you had in mind? Try to adapt the example and let me know if you get stuck. I would agree that it is not the most straightforward to understand where to manipulate which part of the calendar. I recommend cloning the notes-page branch, and copying the example and its asset files (data, photos and fonts folders) to the project root, then compiling the document there. This is in order to make sure the wallcalendar.cls, .lua scripts and i18n/ files are loaded from the local folder, not from the system folders (from TeXLive for example). If you compile directly in the doc/examples folder, latex will not tell you that these files are missing, it will instead load them from the system folders and then error out with obscure messages. I usually have symlinks setup in doc/examples which point back to ../../wallcalendar.cls and so on, but copying is more clear in terms of you knowing what is happening. cd wallcalendar cp doc/examples/cal-photo-and-notes.tex . cp -r doc/examples/data . cp -r doc/examples/photos . cp -r doc/examples/fonts . Then compile: lualatex -interaction=nonstopmode -halt-on-error ./cal-photo-and-notes.tex How are you planning to produce your calendar? It can be printed on a home printer, an inkjet on thicker (120-150gsm) glossy paper can produce nice results. But you also have to trim and bind, so taking the PDF (with cropmarks, use the showtrims option) to a printing shop might be better. The first page have to be a title page (or empty) so that the following pages are photo and notes as facing pages. The facing photo and note pages don't have to be rotated. If the printer can do two-sided print (also called duplex print) then select Duplex over long edge. Or else the pages have to be turned manually in which case it will depend on the machine. I assumed you would want to print on A4 sheets, so the spacing is tweaked for looking good at that size. The effective calendar size have to be smaller because you want to cut the photo pages such that the edge of the photo extends ~3mm over the margin (called bleed image cut), and so the bleed space and trim marks also have to fit on that A4 sheet. The devil is in the details, several parts have to be aligned and tweaked by hand to match up. The images have to be cropped to the correct aspect ratio, and include them that way. The days can have a background photo (like the Bombadil image in the example) but this is done manually by positioning extra \node elements over the calendar. With the showtrims option enabled:
Contributor

### anarcat commented Oct 26, 2018

 On 2018-10-26 08:15:52, Gambhiro wrote: Checkout the notes-page branch and take a look at doc/examples/cal-photo-and-notes.tex. Link to the pdf: [cal-photo-and-notes.pdf](https://github.com/profound-labs/wallcalendar/blob/notes-page/doc/examples/cal-photo-and-notes.pdf) Also see screenshots below. Looking quite good I think! Oh wow, awesome! :) It looks gorgeous, thanks! Is this the sort of thing you had in mind? I'll have to try out a print first, but that's pretty much it, yes!! Try to adapt the example and let me know if you get stuck. Will do! And I will definitely provide feedback, either as comments here or as a pull request. :) I would agree that it is not the most straightforward to understand where to manipulate which part of the calendar. This also depends how it's printed. It's very different if printed on A3 and cut than A4... I still have to wrap my head around this, I'm not a printer. :p I recommend cloning the notes-page branch, and copying the example and its asset files (data, photos and fonts folders) to the project root, then compiling the document there. It's pretty much how I proceeded here already because wallcalender is not included in the texlive distribution in Debian. :( [...] How are you planning to produce your calendar? It can be printed on a home printer, an inkjet on thicker (120-150gsm) glossy paper can produce nice results. But you also have to trim and bind, so taking the PDF (with cropmarks, use the showtrims option) to a printing shop might be better. I'll bring this to a print shop. I don't have a good color printer here. The first page have to be a title page (or empty) so that the following pages are photo and notes as facing pages. The facing photo and note pages don't have to be rotated. If the printer can do two-sided print (also called duplex print) then select Duplex over long edge. Or else the pages have to be turned manually in which case it will depend on the machine. I assumed you would want to print on A4 sheets, so the spacing is tweaked for looking good at that size. Okay. I'm in north america, so this will likely be US Legal (8.5x11 inches), unfortunately, but I can probably figure that out. The effective calendar size have to be smaller because you want to cut the photo pages such that the edge of the photo extends ~3mm over the margin (called bleed image cut), and so the bleed space and trim marks also have to fit on that A4 sheet. The devil is in the details, several parts have to be aligned and tweaked by hand to match up. The images have to be cropped to the correct aspect ratio, and include them that way. Good to know, thanks! The days can have a background photo (like the Bombadil image in the example) but this is done manually by positioning extra \node elements over the calendar. I'm probably not going to be using that feature, but good to know. ![cal-photo-and-notes pdf_078](https://user-images.githubusercontent.com/1586232/47573012-383f4f00-d934-11e8-906e-fc41bcf22ef2.png) With the showtrims option enabled: ![cal-photo-and-notes pdf_079](https://user-images.githubusercontent.com/1586232/47573026-3e353000-d934-11e8-9007-ac5fd0d15e36.png) That looks just gorgeous. Thanks! I wonder though, I'm not sure I need the notes section below, is that easy to get rid of? Thanks for all that hard work, it's really appreciated and unblocked a huge worry I had about the project. By the way, I tried to figure out how you created the moonphases CSV file, and ended up going down a crazy rabbit hole with astronomy calculations. I figured it would be useful for other purposes because I have grand goals for the project: I want to include more than moon phases and stuff like the best time to watch saturn or whatever... I just got the moon phases so far: https://gitlab.com/anarcat/undertime/blob/master/moonphases.py ... aaaand I did it the wrong way too. But anyways, I figured that might be useful for you as well. :) The output is not *exactly* a CSV file, but it should be easy to post-process. Thanks again!
Contributor

### anarcat commented Oct 27, 2018

There's a typo in the .tex file:

! LaTeX Error: File mountains-crop' not found.

That's easy to fix with:

--- a/doc/examples/cal-photo-and-notes.tex
+++ b/doc/examples/cal-photo-and-notes.tex
@@ -201,7 +201,7 @@
minimum width=\calPaperWidth + 6mm,
minimum height=\calPaperHeight + 6mm,
] {%
-        \includegraphics[height={\calPaperHeight + 6mm}]{mountains-crop}%
+        \includegraphics[height={\calPaperHeight + 6mm}]{green-mountains-crop}%
};

\node (title-bg) [

I've also tried to tweak the size to follow the US Letter standard, and I think I have succeeded... The images need to be re-cropped as well, I think. But I need to process my own images anyways, so I've postponed this for now:

diff --git i/doc/examples/cal-photo-and-notes.tex w/doc/examples/cal-photo-and-notes.tex
index f83965f..b0be036 100644
--- i/doc/examples/cal-photo-and-notes.tex
+++ w/doc/examples/cal-photo-and-notes.tex
@@ -4,8 +4,12 @@
eventsCsv = ./data/holidays.csv,
markDefaultsCsv = ./data/mark_defaults.csv,
imageFolder = ./photos/,
-  paperWidth = 282mm,% 297mm - 15mm
-  paperHeight = 195mm,% 210mm - 15mm
+  % A4
+  %paperWidth = 282mm,% 297mm - 15mm
+  %paperHeight = 195mm,% 210mm - 15mm
+  % US Letter
+  paperWidth = 262mm,% 279mm - 15mm
+  paperHeight = 201mm,% 216mm - 15mm
topMargin = 12mm,
trimSpace = 15mm,
%showtrims,
@@ -195,7 +199,7 @@
\mbox{}

-  \put(\LenToUnit{-3mm},\LenToUnit{-3mm}){%
+  \put(\LenToUnit{-18mm},\LenToUnit{-3mm}){%
\begin{tikzpicture}
\node (bg) [
minimum width=\calPaperWidth + 6mm,

So now I need to shove my images in there.

I would also like to figure out how just remove the notepad (? is that how you call the dotted lines below the grid?) to get more space for the grid.

I did try to mess around:

Line 1364 in a5779cf

 \TypesetCoffin\@wall@notesPageWrap%

but couldn't figure it out...

Anyways, when I get a little further I'll let you know, thanks so much! :)

Contributor

### gambhiro commented Oct 27, 2018

Contributor

### anarcat commented Oct 27, 2018 • edited

Contributor

### gambhiro commented Oct 27, 2018

 I'll have a better look at your comments later, just wanted to quickly respond to the cropping question. Very manual: I open the image in GIMP, and set "Fixed aspect ratio" on the Rectangle Select tool. It takes integers, so you can use the inch numbers (11x8.5) multiplied up: 110:85. Then select the area and crop. It also helps to put guides on the edges by selecting all (Ctrl + A) and using Image > Guides > New Guides from Selection.
Contributor

### anarcat commented Oct 27, 2018

 Excellent, thanks! That was one of the last pieces missing. :)
Contributor

### anarcat commented Oct 27, 2018

 Ah, and I found a problem with months that span over 6 distinct weeks, like september 2019:
Contributor

### anarcat commented Oct 27, 2018

 as for the "back" of the calendar, I've used the following patch: anarcat@94273a8. Basically, I just include an external file and use normal LaTeX markup. I'm wondering why it fallsback on the modern font instead of the font used in the rest of the calendar, but that's a minor issue i can probably figure out on my own.
Contributor

Contributor

### anarcat commented Oct 28, 2018

 On 2018-10-28 00:52:27, Gambhiro wrote: Your undertime tool is neat, I had that scheduling promblem several times too. I hope that tool is useful for you! :) Let me know how it can be improved... Thanks for pointing out moonphases.py, I didn't know about the ephem library. I need to produce lists of moon phases regularly as well, I will remember this tip. Just a warning, I found out about PyEphem before I knew Skyfield. So if you ever work on this, you should see if Skyfield does what you want first, since it's much better designed, as explained in the comments on top of the moonphases.py file. **Title page positioning** [...] **Calendar size and spacing** [...] Thanks for those tips! That should get me out of the woodwork. :) **Custom holidays** You can specify your event notes either at the top in the class options,  eventsCsv = ./data/holidays.csv,  Or use this command to draw them when setting \SetEvents{September}, just like the moon phases (which only don't show text because the note column is empty in the csv).  \parseMonthMarksDayTextInlineUsing{./data/moonphases-2018.csv}%  I see, I didn't realize it was the same mechanism! That's cool. That said, I have used a symlink because I wanted to avoid needless diffs with you... [...] **Typefaces** [...] Thanks for those tips! I must admit I'm not very familiar with the graphic elements of LaTeX and those are very useful! **Credits** Truly not necessary. I'm glad that it benefits someone else too. Link to the package's github page if you wish. Good luck with the photo project! I hope the above lets you continue. It does! I think it unblocks *everything* I was having trouble with. :) One last thing I'm juggling with is how to keep my changes (e.g. the colophon) private... I wonder if I could just move all of the .tex file, data/ photos/ and all the good stuff in another repository and point at the .cls file somehow. I googled around to see how to change the TeX search path but I couldn't figure it out... Nor could I figure out how to "install" your stuff directly. But it's probably something I can figure out on my own. I will definitely link to the Github project in the credits then. I can send you a copy of the PDF if you want. ;) Thanks again for the stellar support!
Contributor

Contributor

### norbusan commented Nov 10, 2018 • edited

 Thanks @gambhiro for this nice extension CASE CLOSED!!! I forgot to update the holidays.csv which still refers to 2018 ... Sorry for the noise! ================= original request ========== I just tried to adjust your example for 2019. I copied all the files and can compile the original document without any problem and obtain the same output as yours. Then I changed 2018 to 2019 in some places in the document and tried to compile it, but get strange errors: ! Package pgf Error: No shape named cal09-2018-09-10 is known. See the pgf package documentation for explanation. Type H for immediate help. ... l.246 ... and notes, put photo=full page]{September} ? i checked several times but there is no 2018 mentioned anymore. I attach the 2019 file (as .txt file to get support for it) Do you have any idea? Thanks Norbert calendar2019.txt
Contributor

### gambhiro commented Nov 10, 2018

 @anarcat Thanks for the feature request, it was a good feature to add to the class. The notes-page branch is now merged to master. @norbusan Good to head the class being used, I'm glad you found the error.

Contributor

### anarcat commented Nov 10, 2018

 @norbusan i had trouble with those when the events wouldn't be updated to follow the new year. check those CSV files... @gambhiro thanks for all the good work!! :) i've got the first prints of the calendar done which I'll get to see soon, i'm quite excited about all this :)