Bug#880610: xterm -report-fonts spawns another xterm

[積丹尼 Dan Jacobson]

Package: xterm
Version: 330-1
File: /usr/bin/xterm

I did
$ xterm -report-fonts
and voila it spawns another xterm in the process.

What if
$ xterm -version
did the same?

You see I was reading
https://unix.stackexchange.com/questions/96962/how-can-i-find-the-default-font-resource-xterm-is-using

Because I want to tell you that of
$ unicode 絶 絕|grep U+
U+7D76 CJK UNIFIED IDEOGRAPH-7D76
U+7D55 CJK UNIFIED IDEOGRAPH-7D55

I can see the first, but not the second.

$ xrdb -q|grep font:
*VT100.font:-misc-fixed-medium-r-normal--18-*-*-*-*-*-iso10646-1

Bug#880551: xterm: corrections to man page

[G. Branden Robinson]

At 2017-11-02T04:55:25-0400, Thomas Dickey wrote:
> thanks - someone reported a problem with the same macro in ncurses.
> (I'll have to make a script to check for other instances, since I've
> used bullets in a lot of places - I've a to-do item for that anyway).

Yeah, I've noticed those.  When I read over the ncurses man pages I get
all kinds of ideas... ;-)

> For the rest, I'll pick through in case there's something I find
> that's an unnecessary groffism (but likely will just apply most/all of the
> change).

I tried not to introduce any; I know you're concerned with broad
portability, especially to legacy systems.

> > Make them test instead simply for "n" (nroff mode, as opposed to
> > troff mode), since that appears to be the intention.
> > 
> > 02. Use the \(ha, \(ga, and \(ti character escapes instead of ^`~
> > literals, since these produce full-sized spacing glyphs instead of
> > small ones intended as combining characters on troff output devices.
> > 
> > 03. Use \- character escape in (especially in examples) when an ASCII
> > "hyphen-minus" is intended; ensures that the correct glyph can be
> > cut and pasted from the man page both from TTY and PDF output
> > devices.
> 
> :-)
> 
> It would have been nice if groff hadn't reversed common usage here.

I didn't realize that was the case.  My battered old copy of _Unix Text
Processing_ (Dougherty, O'Reilly) doesn't really cover these matters.
(Its explanation of \- is simply "the minus sign in the _current_ font",
emphasis in original.)  There simply isn't much discussion of spacing
vs. combining glyphs.

Also, I noted that your definition of NS and NE complains about groff
not offering DS and DE (display start and end).  As far as my limited
awareness goes, displays were never part of anyone's man macros; they
were part of both ms and mm, though.

GNU roff's man has EX and EE, but notes that not all legacy systems' man
macros had them.  However, the GNU folks seemed to believe they did not
originate these macros themselves.

Let me know if I can be of any help.

-- 
Regards,
Branden


signature.asc
Description: PGP signature

Bug#880551: xterm: corrections to man page

[Thomas Dickey]

On Thu, Nov 02, 2017 at 02:20:54AM -0400, G. Branden Robinson wrote:
> Package: xterm
> Version: 327-2 (but I prepared the diff against xterm-330)
> Severity: normal
> Tags: upstream
> 
> Hi Thomas,
> 
> Here's a patch for various markup bugs and inconsistencies in the xterm
> man page.
> 
> 01. The local macro definitions for bP and NS were testing the values of
> registers which were likely to be undefined; e.g.
>   "./xterm-330/xterm.man:64: warning: number register `.I' not defined"

thanks - someone reported a problem with the same macro in ncurses.
(I'll have to make a script to check for other instances, since I've
used bullets in a lot of places - I've a to-do item for that anyway).

For the rest, I'll pick through in case there's something I find
that's an unnecessary groffism (but likely will just apply most/all of the
change).

> Make them test instead simply for "n" (nroff mode, as opposed to
> troff mode), since that appears to be the intention.
> 
> 02. Use the \(ha, \(ga, and \(ti character escapes instead of ^`~
> literals, since these produce full-sized spacing glyphs instead of
> small ones intended as combining characters on troff output devices.
> 
> 03. Use \- character escape in (especially in examples) when an ASCII
> "hyphen-minus" is intended; ensures that the correct glyph can be
> cut and pasted from the man page both from TTY and PDF output
> devices.

:-)

It would have been nice if groff hadn't reversed common usage here.


-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Bug#880551: xterm: corrections to man page

[G. Branden Robinson]

Package: xterm
Version: 327-2 (but I prepared the diff against xterm-330)
Severity: normal
Tags: upstream

Hi Thomas,

Here's a patch for various markup bugs and inconsistencies in the xterm
man page.

01. The local macro definitions for bP and NS were testing the values of
registers which were likely to be undefined; e.g.
  "./xterm-330/xterm.man:64: warning: number register `.I' not defined"
Make them test instead simply for "n" (nroff mode, as opposed to
troff mode), since that appears to be the intention.

02. Use the \(ha, \(ga, and \(ti character escapes instead of ^`~
literals, since these produce full-sized spacing glyphs instead of
small ones intended as combining characters on troff output devices.

03. Use \- character escape in (especially in examples) when an ASCII
"hyphen-minus" is intended; ensures that the correct glyph can be
cut and pasted from the man page both from TTY and PDF output
devices.

04. Apply font markup to "Control characters may be specified as ^char
(e.g., ^c or ^u)", consistently with the ensuing discussion.

05. Minor style fix: "the feature is built in" vs. "the program's
built-in features".

06. Remove no-op zero-width space character escapes from the xfontsel
example.

07. Add linebreaks after sentences that had only one space between them
and the succeeding sentence, so the roff system recognizes them as
separate sentences and pads ("adjusts") the line appropriately.

08. Remove trailing whitespace from the ends of input lines.

09. Convert several uses of bare `` and '' to use the page's local
string defines, for consistency with the rest of the page.

10. Remove boldfacing from portions of code examples; these escapes
changed the font family back to Times from Courier.  If this change
is unacceptable, I can come up with one that will stay within the
Courier family, but it will only work for groff.  I don't know of
a portable way to do what I think is desired here.

11. Remove trailing "\n\" from the BtnUp select-end example; it didn't
seem necessary and the \ was syntactically meaningful to
roff so it didn't get rendered as expected and caused a warning:
  "./xterm-330/xterm.man:5033: warning: number register `.' not defined"
It also turned off fill mode outside of the examples for a few
paragraphs, making the output ugly.

12. "etc" is an abbreviation that gets a period.

13. Join two really short input lines about triple-clicking.

14. Use the local AQ string definition instead of bare 's in printf
examples, for correct appearance and more successful cut and
pasting.

15. In the big default charClass table, use a dingbat asterisk at the
end of the C comment for symmetry with the beginning, which already
uses one.

16. Rewrite the upper half of the charClass table so it depicts the
actual (printable) glyphs in \x80-\xff.  What was there was largely
incomprehensible to me.

17. Use character escape '\e' instead of '\\' in resource translation
examples.  '\\' does not render as desired and makes the examples
wrong.  (\(rs would be more strictly correct than \e, but is a
groffism; \e is not an invariant glyph reference but instead means
"whatever the current roff escape character is"; fortunately, most
man pages do not change the escape character.  Traditional roff does
not have a character escape for the "reverse solidus".)

18. The translation examples also don't need zero-width spaces (\&) at
the ends of the input lines; this is a no-op.  Remove them.

19. Unindent the examples for the VT100 and Tektronix default
translations by one space since some of the lines are very wide.
One space was all the room available given the existing alignment.
If desired, I can prepare a patch to step the font size down by
a point or two, though this will not help TTY-like devices.

20. Fix missing word: "you could add a binding [to] shifted keys".

-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xterm depends on:
ii  libc6   2.24-11+deb9u1
ii  libfontconfig1  2.11.0-6.7+b1
ii  libice6 2:1.0.9-2
ii  libtinfo5   6.0+20161126-1+deb9u1
ii  libutempter01.1.6-3
ii  libx11-62:1.6.4-3
ii  libxaw7 2:1.0.13-1+b2
ii  libxft2 2.3.2-1+b2
ii  libxinerama12:1.1.3-1+b3
ii  libxmu6 2:1.1.2-2
ii  libxpm4 1:3.5.12-1
ii  libxt6  1:1.1.5-1
ii  xbitmaps1.1.1-2

Versions of packages xterm recommends:
ii  x11-utils  7.7+3+b1

Versions of packages xterm suggests:
pn  xfonts-cyrillic  

-- no debconf information

-- 
Regards,
Branden