[bug #64684] [nroff] would like support for option clusters

[Dave]

Follow-up Comment #1, bug#64684 (group groff):

Nit: -a is not a recognized nroff option, so that specific command would fail
anyway.


___

Reply to this item at:

  

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

[bug #56015] [PATCH] [grotty] should handle bullet character more intelligently

[Dave]

Update of bug#56015 (group groff):

 Summary: [grotty] should handle bullet character more
intelligently => [PATCH] [grotty] should handle bullet character more
intelligently

___

Follow-up Comment #8:

If we're all in agreement about dropping \[pc] and \[md] as bullet fallbacks:

* Since the two ".if c" calls setting them up don't do what's expected anyway,
it seems that the code block Jeff quoted can be ripped out of tty.tmac
wholesale.
* Comment #2 posits that .fchar is the correct mechanism for handling this
situation.  While it has issues as well, it's used to define a plethora of
other fallback characters in tty.tmac, so if .fchar is deemed inadequate as a
mechanism to define grotty fallbacks, that issue goes far beyond the bullet,
and this bug is limited to the bullet's rendering.

So what _should_ be the fallback on terminals where no bullet is available?

Since few if any modern terminal emulators support overstriking (see comment 1
in bug #62983), and grotty output is far likelier to be put on a screen than
on a printer, I think this fallback shouldn't involve overstriking, which
rules out an overstruck "o" and "+", which is what tty.tmac currently defines
(once the aforementioned code block is removed) and is one of Jeff's
suggestions.

That leaves the asterisk as the one idea that everyone in this thread can get
behind: Jeff, Branden, and I have all endorsed it (respectively in the
[comment #0 original submission], comment #1, and comment #5).

In light of all the above, I submit the following patch for feedback.

diff --git a/tmac/tty.tmac b/tmac/tty.tmac
index 2a28a7dd2..0ebd77a2c 100644
--- a/tmac/tty.tmac
+++ b/tmac/tty.tmac
@@ -8,15 +8,7 @@
 .
 .po 0
 .
-.if !'\*[.T]'utf8' \{\
-.  ie c\[pc] \
-.tr \[bu]\[pc]
-.  el \
-.if c\[md] \
-.  tr \[bu]\[md]
-.\}
-.
-.fchar \[bu] \z+o
+.fchar \[bu] *
 .fchar \[14] 1/4
 .fchar \[12] 1/2
 .fchar \[34] 3/4




___

Reply to this item at:

  

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

[bug #65215] .MT/.ME and .UR/.UE should result in hyperlink for pdf output

[Dave]

Update of bug#65215 (group groff):

 Open/Closed:Open => Closed 


___

Reply to this item at:

  

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

[bug #56015] [grotty] should handle bullet character more intelligently

[Dave]

Follow-up Comment #7, bug#56015 (group groff):

Jeff and I agree that \[pc] and \[md] are both poor choices for a bullet. 
Branden leads off comment #1 with "I'm a +1 on this" but then proposes a code
snippet designed to replace the bullet (if none exists) with, in order of
preference, \[pc], \[md], or asterisk, two of which Jeff explicitly opposed in
his initial report.  (I say "designed to" rather than "does" because we now
know ".if c" tests do nothing useful in grotty contexts.  But that's a
resolvable coding issue.)  So Branden, can you clarify whether you're willing
to take \[pc] and \[md] out of consideration as replacement bullet characters?


___

Reply to this item at:

  

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

[bug #56015] [grotty] should handle bullet character more intelligently

[Dave]

Update of bug#56015 (group groff):

  Item Group: Incorrect behaviour => Rendering/Cosmetics
  Status:   Need Info => Confirmed  

___

Follow-up Comment #6:

Branden put this bug in Need Info status with comment #2, presumably based on
his stated need to research the history of the change cited in that comment. 
That history was unveiled a couple months later in comment #3, and if any
further info is required, it's not clear what it is.

As comment #5 notes, the two ".if c" statements are useless in tty.tmac.  But
these long predate the comment #2-referenced commit: the first dates back to
James Clark's creation of the file in
[http://git.savannah.gnu.org/cgit/groff.git/commit/?id=b04d345ed commit
b04d345ed] in 1992, and the second to Werner's
[http://git.savannah.gnu.org/cgit/groff.git/commit/?id=fbd6cbb8a commit
fbd6cbb8a] in Apr 2000.  The comment #2-referenced commit merely wrapped these
conditionals in a further test for non-UTF8 terminals, the purpose of which I
think is clear from the associated email thread linked in comment #3.  But
this additional test is not the source of the issue Jeff Conrad is reporting;
if anything, this additional test keeps that issue from being more widespread.


___

Reply to this item at:

  

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

[bug #65215] .MT/.ME and .UR/.UE should result in hyperlink for pdf output

[Deri James]

Update of bug#65215 (group groff):

  Status: In Progress => Fixed  

___

Follow-up Comment #1:

Fixes committed.

commit d71f9264f8c187aee1161f27cda7d42c4ad7065e
Author: Deri James 
AuthorDate: Fri Jan 26 15:47:28 2024 +

.MT/.ME and .UR/.UE hyperlinking for pdf output

Our documentation groff_man.7 documents that these requests are
for hyperlinks. The .pdfhref W command expects the hotspot text
to be passed as a parameter, but these pairs of requests enclose
the required text. To solve this conundrum if the given
hyperlink text to the .pdfhref request is the single pipe
character "|" then mark all following text sent for output as
the hotspot, terminate the hotspot on receipt of \X'pdf:
markend' escape. This new facility is only available using -T
pdf, not using -T ps and the pdfmark macros. Note the advice in
the gropdf man page to use \X'pdf: marksuspend' and \X'pdf:
markrestart' to protect any headers and footers becoming part of
the hotspot in case the hyperlinked text crosses a page
boundary.

* tmac/an.tmac: add code to use .pdfhref W for these hyperlinks
and protect against crossing page boundaries.

* tmac/pdf.tmac: if the given text for a hyperlink consists of
a single pipe character "|", start the hotspot and only
terminate when \X'pdf: markend' is received.



___

Reply to this item at:

  

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

[bug #65215] .MT/.ME and .UR/.UE should result in hyperlink for pdf output

[Deri James]

URL:
  

 Summary: .MT/.ME and .UR/.UE should result in hyperlink for
pdf output
   Group: GNU roff
   Submitter: deri
   Submitted: Fri 26 Jan 2024 01:27:39 PM UTC
Category: Macro man
Severity: 1 - Wish
  Item Group: Rendering/Cosmetics
  Status: In Progress
 Privacy: Public
 Assigned to: deri
 Open/Closed: Open
 Discussion Lock: Any
 Planned Release: None


___

Follow-up Comments:


---
Date: Fri 26 Jan 2024 01:27:39 PM UTC By: Deri James 
These macros are meant to produce hyperlinks (according to groff_man(7)).







___

Reply to this item at:

  

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