Update of bug #65985 (group groff):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

I see a few classes of problem:


* I get warnings from afmtodit about names already being mapped.

afmtodit: AGL name 'Delta' already mapped to groff name '*D'; ignoring AGL
name 'uni0394'

You can ignore these if they're in the form shown above, where the
ignored AGL name is 'uniXXXX' and 'XXXX' is four hexadecimal digits.
The Adobe Glyph List (AGL) has its own names for glyphs; they are often
different from groff's special character names.  The afmtodit program is
constructing a mapping from groff special character names to AGL names;
this can be a one-to-one or many-to-one mapping, but one-to-many will
not work, so afmtodit discards the excessive mappings.  The example you
see above is telling you that the groff font description that afmtodit
is writing cannot map the groff special character '*D' to both 'Delta'
and 'uni0394'.

Which, if any, such warnings you see depends on the version of the URW
fonts you are building groff against.  See the '--with-urw-fonts-dir'
option to the "configure" script, and the afmtodit(1) and groff_char(7)
man pages for more background.


That's from the "PROBLEMS" file in the root of the source tree.

Next...it looks like someone has rewritten "psselect" in Python and changed
the way it works.

On my system...


$ file $(type -p psselect)
/usr/bin/psselect: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
2.6.32, BuildID[sha1]=4839ba7efbc7003958ce0c635776aeaeb57a7da5, stripped


Someone needs to look into this.  It could be a bug in psutils.

Most or even all of the rest of the diagnostics appear to arise from grohtml's
rose-tinted expectations that the giant pipeline it constructs to pre-run
_troff_ on a document, covert it to PostScript, convert it to a raster
graphic, crop pieces out of it, and point HTML 'img' elements at those pieces
will never go wrong.

You may already be aware of issues with image cropping in bug #65961.

You might want to disable grohtml and see what diagnostics remain when
building.

Please try that and see what you see.


    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to