bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #59962] soelim(1) man page uses pic diagram--should it?


From: Helge Kreutzmann
Subject: [bug #59962] soelim(1) man page uses pic diagram--should it?
Date: Sun, 2 May 2021 11:13:42 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #4, bug #59962 (project groff):

Hello Branden,
thanks for working on improving the (soelim) man pages.

I manually inserted the version from git as of this morning into our toolchain
for testing purposes. As #59222 is closed, I report all I noticed while
quickly reviewing the newly generated man page. Please apologize if some is an
artefact due to the manual process (but I do hope there is none).

1. The headings of soelim are now all lower case instead of upper case (e.g.
Name, Synopsis, Description instead of NAME, SYNOPSIS, DESCRIPTION)

2. The markup is partially strange. Usually program names are in B<>, but now
they are in I<> (with an additional \\% at the beginning, but I don't complain
about the latter). In a KDE konsole this looks strange (underlined instead of
bold), in a VT visually this does not matter.

3. Usually B<> is not additionally quoted, I noticed that it is now in the new
version, e.g. \\[lq]B<...>\\[rq].

4. Regarding the picture, the toolchain of manpages-l10n still does not
integrate it but tells me it is in a separate file. This is a little
unfortunate, but right now I do not have the time to debug this. And the
downside is only the missing translation. Therefore please close this bug for
now. If I ever investigate this further, I would open (if necessary) a new
bug.

5. The line graphics was changed. On my system, the arrows are displayed fine
in a VT, but not the lines. Both display fine in a KDE konsole. Maybe you want
to keep the previous line and just use the arrows? (But most users probably
will use a terminal program in a graphical environment, so this really is very
minor)

So I would suggest to address 1. and 2. (and maybe 3./5.) and then close this
bug.

Thanks again for your work.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59962>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]