> follow the alignment of the english translation, > which usually has the description on a separate line, > starting at offset 10
On one hand, the 10 offset is very enticing as usually Bulgarian is longer than English though I take pride in how terse (while still correct) I can get the translation. On the other: 10 means that very often the translation will need to leave the first line empty. The 24 offset I used allowed me to start at the same line more often and make the translation take less vertically. I will think about which width to use. Skipping the first line creates visual regularity but this is at the cost of a lot of vertical space and forces you to scroll. Thanx and kind regards: al_shopov На чт, 18.06.2026 г. в 13:43 Pádraig Brady <[email protected]> написа: > On 18/06/2026 12:28, Pádraig Brady wrote: > > So in summary for languages that have similar horizontal width > > as english, I would follow the alignment of the english translation, > > which usually has the description on a separate line, > > starting at offset 10. For example see: > > > $ TERM= cksum --help | grep -A1 -- --check; ruler > > -c, --check > > read checksums from the FILEs and check them > > 123456789¹123456789²123456789³123456789⁴123456789⁵123456789⁶123456789⁷12 > > Thunderbird messes with spaces and newlines, > which I've readjusted hopefully correctly above. > > > Now there are a few exceptions like `[ --help` > > where a single line is best, but again following > > the english alignment is best where possible. > > You also asked about option matching logic. > Bascially again follow the english lead here, > and ensure there is a single translation per option. > For details on how this is all wired together see: > https://www.pixelbeat.org/docs/tty_links/ > > cheers, > Padraig >
