bugGNU troff - Bugs: bug #61407, Remove spurious error messages...

 
 

bug #61407: Remove spurious error messages generated by pdf.tmac

Submitter:  Bjarni Ingi Gislason <bjarniig>
Submitted:  Mon 01 Nov 2021 12:22:31 AM UTC
 
Category:  Macro - others/general Severity:  2 - Minor
Item Group:  Warning/Suspicious behaviour Status:  In Progress
Privacy:  Public Assigned to:  deri
Open/Closed:  Open Planned Release:  None
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

( Jump to the original submission )

Sat 26 Mar 2022 04:51:49 PM UTC, comment #10: 

Now that these warnings are suppressed except for users who explicitly enable them, does it make sense to snip out the parts of the documentation instructing users to ignore the warnings?  Such text appears in at least INSTALL.REPO and src/devices/gropdf/pdfmom.1.man.

Dave <barx>
Project Member
Mon 07 Mar 2022 09:12:19 AM UTC, comment #9: 

Commit 557bc055 applies a temporary Band-aid to the problem by hiding the warnings unless an (undocumented) environment variable is set.

Dave <barx>
Project Member
Fri 17 Dec 2021 10:44:33 AM UTC, comment #8: 

This patch seems to be intended for bug #58206.

Dave <barx>
Project Member
Thu 16 Dec 2021 10:27:25 AM UTC, comment #7: 

As discussed in the mailinglist (https://lists.gnu.org/archive/html/groff/2021-12/msg00000.html) hereby the patch I used to get pdfpic.tmac to work.

(file #52513)

Anonymous
Sun 28 Nov 2021 09:19:40 AM UTC, comment #6: 

Comment #4 indicates this isn't a mom-specific issue.  Updating fields accordingly.

Dave <barx>
Project Member
Wed 03 Nov 2021 06:31:34 PM UTC, comment #5: 

comment #4:

> I believe the transparent node message occurs when pdf.tmac calls .asciify in order to "clean" the text to use in the bookmark text, and it includes nodes which can't be converted back text. Last time I looked this message could not be suppressed with a -W number.
>
> However, Keith's clever sanitise.tmac, which he has recently included in Groff, takes a different approach, it "cleans" the text in pure roff code rather than asciifying after groff has converted the input to nodes. I need to investigate whether .sanitise could be used as a replacement for .asciify.


Ooh, that sounds nice.  I'd like to get rid of these diagnostic messages but neither adding a warning category for them nor just discarding standard error output feels right to me.

Better still, if we can phase out .asciify in favor of .sanitize, we'll seem a lot more "hip" and "with it" to all those crazy kids doing the Unicode boogaloo.

Assigning to Deri and marking "in progress"; please further change those if I'm getting carried away.

G. Branden Robinson <gbranden>
Project Administrator
Wed 03 Nov 2021 06:00:27 PM UTC, comment #4: 

I believe the transparent node message occurs when pdf.tmac calls .asciify in order to "clean" the text to use in the bookmark text, and it includes nodes which can't be converted back text. Last time I looked this message could not be suppressed with a -W number.

However, Keith's clever sanitise.tmac, which he has recently included in Groff, takes a different approach, it "cleans" the text in pure roff code rather than asciifying after groff has converted the input to nodes. I need to investigate whether .sanitise could be used as a replacement for .asciify.

Deri James <deri>
Project Member
Wed 03 Nov 2021 04:18:14 PM UTC, comment #3: 

"...can't transparently output node at top level" and "...can't translate character code nnn to special character 'c'in transparent throughput" (point 2) are spurious insofar as they have no impact on pdf output, nor the generation of pdf outlines.  The warnings are emitted by troff when the gropdf driver is being used.  So far, no one has come up with a solution to getting rid of them.  I suspect it isn't possible except by suppressing stderr, which is no solution at all.

Peter Schaffter <PTPi>
Project Member
Wed 03 Nov 2021 10:50:53 AM UTC, comment #2: 

Are the errors being reported in point 2) legitimate errors?  If so, their root causes should be fixed.  If not, perhaps the code generating them should be changed to not emit spurious error messages.  Suppressing stderr seems like the least desirable approach, unless there are constraints making all other approaches unworkable.

Dave <barx>
Project Member
Mon 01 Nov 2021 12:38:35 AM UTC, comment #1: 

  Point 1) is not a part of master branch and has nothing to do with "automake.mom" or "transparently output".

Bjarni Ingi Gislason <bjarniig>
Mon 01 Nov 2021 12:22:31 AM UTC, original submission:  

Remove default error messages from mom-files.

1) Error message from "doc/automake.mom"

  Fix in "doc/doc.am" with something like

.ms.ps:
        $(GROFF_V)$(MKDIR_P) `dirname $@` \
        && $(DOC_GROFF) $(GROFF_PAPER_FLAG) -Tps -ms 2>&1 $< >$@ | \
                                                     ****        ***
+        if test $< = ms.ms ; then \
+          sed -f <filter>  >&2 ; \
+        fi

  With file <filter> containing

/^error: can't transparently output node at top level$/d

2) Error messages from "contrib/mom/*.mom"

  Fix in "contrib/mom/mom.am" with something like

.mom.pdf:
        $(GROFF_V)$(MKDIR_P) `dirname $@` \
        && LC_ALL=C $(MOMPDFMOM) 2>&1 $< >$@ | \
                                 ****        ***
+        sed -f <filter>  >&2

  With file <filter> containing

/error: can't transparently output node at top level$/d
/error: can't translate character code /d

Bjarni Ingi Gislason <bjarniig>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #52513:  pdfpicbsd.patch added by None (488B - text/x-patch)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by gbranden (Posted a comment)
  • -email is unavailable- added by deri (Posted a comment)
  • -email is unavailable- added by PTPi (Posted a comment)
  • -email is unavailable- added by barx (Posted a comment)
  • -email is unavailable- added by barx (mom maintainer)
  • -email is unavailable- added by bjarniig (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    Follow 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-12-16 None Attached File- Added pdfpicbsd.patch, #52513
    2021-11-28 barx CategoryNone Macro - others/general
        Severity3 - Normal 2 - Minor
        Item GroupFeature change Warning/Suspicious behaviour
        Summary[mom] Remove default error messages from mom-files. Remove spurious error messages generated by pdf.tmac
    2021-11-03 gbranden StatusNone In Progress
        Assigned toNone deri
    2021-11-01 barx Carbon-Copy- Added ptpi

    Back to the top


    Powered by Savane 3.9