Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(bericht): the PDF is A4-only, with column widths tuned to hardcoded German headers

Open
  • Is something wrong?
#404 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
40/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
desktop, documentation

Research direction

Start with IncidentReportDocument.cs and AttachmentCaptionSection.cs to trace where A4 is selected, then read RolesSection.cs for the seven column widths and German headings. Check IncidentSettings for where a paper-size choice could live, and Formatting.cs for the shared date format; the issue also references #350 for UI string mechanisms. Done means supporting A4/Letter and fitting column widths to measured header text, while accounting for the report’s German strings.

Written by the indexing model from the issue text.

Description

enhancement i18n

From a portability review of main (ecb341b). Small and mechanical; grouped here because both halves live in LageBuch.Documents.

A4 is hardcoded

src/LageBuch.Documents/IncidentReportDocument.cs:56   page.Size(PageSizes.A4);
src/LageBuch.Documents/Sections/AttachmentCaptionSection.cs:32   page.Size(PageSizes.A4);

Margins are 1.5f, Unit.Centimetre. There is no Letter path and no setting. RolesSection.cs sizes its seven columns explicitly against "A4 portrait", so the page size is not purely a container — the column widths are tuned to it.

The section and column headings are hardcoded German arrays

e.g. RolesSection.cs:10 — ["Funktion", "Name", "Abschnitt", "Funkrufname", "Handynummer", "Von", "Bis"], plus "Einsatzdokumentation", "Einsatztagebuch (ETB)", "Kräfteübersicht", "Atemschutzüberwachung", "CO-Messprotokoll", "Angehängte Dateien", "Gesamtstärke: ", and the footer "Seite {n} / {total}". Roughly 42 distinct German literals across the assembly.

The PDF is also where the one de-DE CultureInfo in the codebase surfaces — Formatting.Timestamp (Formatting.cs:9,11, dd.MM.yyyy HH:mm) is shared by the report and the UI.

Why file it separately from #350

#350 is about the mechanism for UI strings. The report has two things the UI does not: column widths that are coupled to the chosen strings and the chosen page size, and an output that leaves the machine and gets filed. Whatever #350 decides, someone still has to re-fit RolesSection's seven columns when the headers change length — that work is specific to this assembly and worth knowing about before the i18n approach is chosen, not after.

Concretely: a paper-size setting (A4/Letter) on IncidentSettings, and the column widths derived from measured header text rather than tuned constants.

Dominant language
C#
Stars
1
Forks
3
Avg merge
4h 34m
Merged PRs (30d)
182

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeForFire/lagebuch

All issues in CodeForFire/lagebuch

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.