Text that is too long in Ledger Map

Done (24/10/2026): your choices are applied in the code: 58 texts use the short version, 62 are removed, and 4 undecided texts are unchanged. Each card now shows the screen Before and After.

Every text of 100 characters or more that explains a button, page, pop-up or message, with a one-line version for each. Each is measured where it appears, to show which break the two-line rule. Names and numbers in the examples are made up.

Your choices

For each text, choose: Keep as is in the app, Use short version, or Remove it entirely. Choices are saved in this browser. When done, copy them and paste them to me.

Proposed rule: one line, about 70 characters at most. Say what the thing does. Leave out how and why. Key details go in the Keyboard shortcuts pop-up (Ctrl+K).

Now: the text as the app shows it Short version: the one-line replacement Each screenshot is the real Ledger Map screen, built from its code with made-up data, in a 1280 px wide window; the text is outlined in red. Line counts are counted in that screenshot. The text boxes use the same width and text size; on a phone they are narrower.

Where they are

How this list was made

Every text in the app, the admin panel, the server and the Windows app was read. A text is on this list when it is 100 characters or more. Its line count was then measured in the real screen, so you can see which really break the two-line rule.
About 60 more texts have 80–99 characters. They are not on this list. Most fill two lines, and some wrap to three in narrow places such as the shortcut list.
“Read aloud only” texts are not on screen. Screen readers read them when a row gets focus.
“Development builds only” texts never reach customers.