Font size / page size setting for printing

[carlobeltrame]

Fixes #4650

A5 / A6 (bigger relative font size): Nuxt A5 Client A5 A4 / A5 (normal, same as on prod): Nuxt A4 Client A4 A4 / A3 (smaller relative font size): Nuxt A3 Client A3

Please feedback on:

• UI design of the new option
• Currently, we use A4 page sizes but many users print this on A5. I took the easy way out and left the page size default at A4 (so I don't have to change all font sizes in both print) and just labeled it as "Normal (for printing on A4 or A5)" in the UI. So when the user selects the font size "Bigger (for printing on A6)", the PDF actually uses a page size of A5, and we rely on the users' printers to scale this down. Is this fine? Do users think more in terms of page size or in terms of font size? Should I do the tedious work and change all font sizes in both prints, so that we can be honest to the users?
• Any bugs in the pdfs. I already had to adjust the picasso time column font size in nuxt print and the auto-scaling font size on picasso schedule entries in client print already.

[BacLuc]

The space problem for small blocks get worse on the picasso:

Nuxt A5:

And the 07:00 is over the line.

If for whatever reason you use 2 zeros for the relative time from block start, it always wraps: I didn't write many blocks who were longer than 10h...? But the problem persist for people who use absolute times.

Here it is completely off:

Material list looks good:

ThematicArea looks good:

Client A5 Picasso looks good:

Here the user can use 2 digit hours in the block:

A3:

I don't know what you would want to print on A3, maybe the picasso? This works, looks a little empty.

UI Design: Good that it's hidden and does not clutter the ui for not advanced users. Not so discoverable...but you have to weigh the 2 options.

[BacLuc]

What we also have to discuss:

How much value do we get vs additional maintenance effort?

Do we need tests for the other font sizes? How do we test the other font sizes?

How much priority does it get when it breaks?

[carlobeltrame]

The space problem for small blocks get worse on the picasso

True, but if you are using this advanced feature, you probably can also set the picasso to portrait mode and maybe even split it in two parts using the date filters, so it's less of a problem.

And the 07:00 is over the line.

Fixed in 10724c5

I don't know what you would want to print on A3, maybe the picasso? This works, looks a little empty.

How much value do we get vs additional maintenance effort?

I could also imagine dropping the A3 option, and just supporting the A6 one for now. I agree A4/A3 is only useful for the picasso, if at all. It does improve the "space problem for small blocks" which you mention on the A6 version, but nobody has explicitely asked for reducing the font size as far as I am aware (although when users claim they can create a better readable picasso in excel, this usually just boils down to a smaller font size).

I implemented this because I see the A6 variant as a valid use case for which we can't provide any workarounds at the moment. And if it's just setting the page size plus 1-2 workarounds for the smaller paper size, I feel like the maintenance burden is not so high.

Do we need tests for the other font sizes? How do we test the other font sizes?

~~I now added basic e2e tests just checking for the number of pages in the A6 variant. 28461de~~ The e2e tests turned out to be extremely flaky in firefox for some reason... I removed them again and added snapshot tests in the pdf module (9c6cda3). In print, we don't have any logic tests at all so far...

[github-actions[bot]]

💥 Feature branch deployment failed

Name	Link
🕒 Last attempted at	Fri Oct 03 2025 20:53:17 GMT+0200
🔨 Latest commit	9c6cda39616e8b86199ed6a4eababaeeb155171d
🔍 Latest deploy log	https://github.com/ecamp/ecamp3/actions/runs/18230958764/job/51914087760

---