Bug#1041094: Xserver.1: some remarks and editorial fixes for the manual

2025-03-29 Thread Alan Coopersmith

I have included portions of this in the upstream MR:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1875

The first line too long fix cannot be applied upstream as the upstream source
substitutes the font path at build time, so it doesn't appear expanded
as it does in this patch.

The second line too long issue was already handled by a previous commit in
this MR.

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#1095446: exa.4: Some remarks and a patch with editorial changes for this man page

2025-03-29 Thread Alan Coopersmith

I have submitted this upstream as part of
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1875

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#726063: Xserver(1): Too long line in the manual and some minor changes

2025-03-29 Thread Alan Coopersmith

I have included portions of this in the upstream MR:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1875

The line too long fix cannot be applied upstream as the upstream source
substitutes the font path at build time, so it doesn't appear expanded
as it does in this patch.

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#1072500: Xserver.1: some remarks and editorial changes for this man page

2025-03-29 Thread Alan Coopersmith

I have included portions of this in the upstream MR:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1875

The first line too long fix cannot be applied upstream as the upstream source
substitutes the font path at build time, so it doesn't appear expanded
as it does in this patch.

The second line too long issue was already handled by a previous commit in
this MR.

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#667983: Bug #667983: xorg.conf(5): Three ".RE" in the same line, unprotected period in abbreviations and ellipses

2025-03-29 Thread Alan Coopersmith

The "Three ".RE" in the same line" issue was fixed upstream by
https://gitlab.freedesktop.org/xorg/xserver/-/commit/321873f8045139edd47b526a765f8b1c66f53cd4
which is included in the xorg-server 1.12.0 and later releases.

The "macro `TP7' not defined (possibly missing space after `TP')"
issue was fixed upstream by
https://gitlab.freedesktop.org/xorg/xserver/-/commit/85b831f701d085e514afcf8a5ce9b11f8a57984e
which is included in the xorg-server 1.10.0 and later releases.

I've submitted the remaining fix for "unprotected period in ellipses" upstream
in https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1875

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#755809: xorg.conf.5 man page mentions an incorrect "Enable" option for Monitors

2025-03-29 Thread Alan Coopersmith

I've included the latest patch from this bug in the upstream merge request
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1875

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#919143: Bug #919143: xorg.conf.5: Some formatting and word corrections in the manual

2025-03-29 Thread Alan Coopersmith

I've included fixes from this patch in the upstream merge request
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1875

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#1095449: inputtestdrv.4: Some remarks and a patch with editorial changes for this man page

2025-03-29 Thread Alan Coopersmith

I have submitted this upstream as part of
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1875

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#919137: cvt1: Some adjustments in the man page

2025-03-29 Thread Alan Coopersmith

I've submitted this patch upstream in
https://gitlab.freedesktop.org/xorg/lib/libxcvt/-/merge_requests/18

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#869252: Xserver.1: Fix two warnings and some textual and formatting issues

2025-03-29 Thread Alan Coopersmith

I have included portions of this in the upstream MR:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1875

The first line too long fix cannot be applied upstream as the upstream source
substitutes the font path at build time, so it doesn't appear expanded
as it does in this patch.

The second line too long issue was already handled by a previous commit in
this MR.

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#1101570: twm.1: Some remarks and a patch with editorial changes for this man page

2025-03-29 Thread Bjarni Ingi Gislason
Package: twm
Version: 1:1.0.10-1+b1
Severity: minor
Tags: patch

   * What led up to the situation?

 Checking for defects with a new version

test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man 
page"

  [Use "grep -e ' $' -e '\\~$' " to find obvious trailing spaces.]

  ["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).

  [The fate of "test-nroff" was decided in groff bug #55941.]

   * What was the outcome of this action?

troff::377: warning: trailing space in the line
troff::646: warning: trailing space in the line
troff::731: warning: trailing space in the line
troff::761: warning: trailing space in the line

   * What outcome did you expect instead?

 No output (no warnings).

-.-

  General remarks and further material, if a diff-file exist, are in the
attachments.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.19-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages twm depends on:
ii  libc6  2.41-6
ii  libice62:1.1.1-1
ii  libsm6 2:1.2.4-1
ii  libx11-6   2:1.8.10-2
ii  libxext6   2:1.3.4-1+b3
ii  libxmu62:1.1.3-3+b4
ii  libxt6t64  1:1.2.1-1.2+b2
ii  menu   2.1.51

twm recommends no packages.

twm suggests no packages.

-- no debconf information
Input file is twm.1

Output from "mandoc -T lint  twm.1": (shortened list)

  1 input text line longer than 80 bytes: and may only be give...
  1 input text line longer than 80 bytes: may only be specifie...
  1 input text line longer than 80 bytes: only be specified in...
  6 skipping paragraph macro: PP after SH
  1 skipping paragraph macro: PP empty

-.-.

Output from "test-nroff -mandoc -t -ww -z twm.1": (shortened list)

  4 line(s) with a trailing space


Remove trailing space with: sed -e 's/  *$//'

-.-.

Change a HYPHEN-MINUS (code 0x2D) to a minus(-dash) (\-),
if it
is in front of a name for an option,
is a symbol for standard input,
is a single character used to indicate an option,
or is in the NAME section (man-pages(7)).
N.B. - (0x2D), processed as a UTF-8 file, is changed to a hyphen
(0x2010, groff \[u2010] or \[hy]) in the output.

84:information requested by the user (usually through \fI-geometry\fP
553:screen width.  The default height is 32767 - screen height.
747:convenience, the ratio 0/0 is the same as 1/2 for \fBcenter\fP and -1/1
765:programs that do not support an \fI-iconic\fP command line option or
875:keysym name; buttons are given as the keywords \fBButton1\fP-\fBButton5\fP:
1221:all of the client and \fItwm\fP-supplied windows.  Selecting an entry will

-.-.

Find a repeated word

! 410 --> if
! 826 --> of
! 1239 --> the

-.-.

Add a "\&" (or a comma (Oxford comma)) after an abbreviation
or use English words
(man-pages(7)).
Abbreviation points should be marked as such and protected against being
interpreted as an end of sentence, if they are not, and that independent
of the current place on the line.

126:The \fIscreennumber\fP is a small positive number (e.g. 0, 1, etc.)
127:representing the screen number (e.g. the last number in the DISPLAY 
environment
160:by double quote characters (e.g. "blue") and are case-sensitive.
186:(e.g. to determine whether or not to enable autoraise as shown above), a 
string
686:unquoted, signed number (e.g. 999).  This variable has an effect only
1087:integer in double quotes (e.g. "999" ).  This function has an effect only
1169:specified by the argument \fIstring\fP.  If \fIstring\fP is empty (i.e. 
""),
1173:argument \fIstring\fP.  \fIString\fP may be a number (e.g. \fB"0"\fP or

-.-.

Wrong distance (not two spaces) between sentences in the input file.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

Mark a final abbreviation point as such by suffixing it with "\&".

Some sentences (etc.) do not begin on a new line.

Split (sometimes) lines after a punctuation mark; before a conjunction.

  Lines with only one (or two) space(s) between sentences could be split,
so latter sentences begin on a new line.

Use

#!/usr/bin/sh

sed -e '/^\./n' \
-e 's/\([[

Bug#1095446: exa.4: Some remarks and a patch with editorial changes for this man page

2025-03-29 Thread Alan Coopersmith

On Sat, 8 Feb 2025 13:46:15 + Bjarni Ingi Gislason  
wrote:

  Upstream does not accept emails without subscribing, which I do not.


Upstream prefers bug reports & patches be submitted via
https://gitlab.freedesktop.org/xorg/xserver these days, not email.

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris



Bug#919140: exa.4: Minor corrections of the manual

2025-03-29 Thread Alan Coopersmith

This is a subset of the fixes in bug #1095446 and will be covered by fixing 
that.

--
-Alan Coopersmith- alan.coopersm...@oracle.com
 Oracle Solaris Engineering - https://blogs.oracle.com/solaris