[bug #59531] configure: warn people of Ghostscript bug: `lh` glyph is shifted horizontally

[G. Branden Robinson]

Update of bug #59531 (project groff):

                  Status:                    None => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #5:

[comment #3 comment #3:]
> And the gs people confirmed.  The bug was introduced in gs version 9.00 –
ten(!) years ago, and nobody cared enough or noticed the issue to submit a bug
report, including myself...
> 
> As soon as a new gs release x.y appears with this bug fixed I suggest that
groff's `configure.ac` script gets modified to emit a warning if a gs version
in the range [9.00,x.y[ is used.

Thanks, Werner.  I've done this, [9,00,9.54).

[comment #4 comment #4:]
> Version 9.54.0 of ghostscript has fixed it.

Thanks, Bjarni!


commit ebc2637532ff35b1261f6d7cc207f122dc4f2e26
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sun May 16 19:18:42 2021 +1000

    [configure]: Warn of buggy Ghostscript versions.
    
    * m4/groff.m4 (GROFF_GHOSTSCRIPT_VERSION_CHECK): Add new autoconf macro
      to check if Ghostscript version.  Versions 9.00 <= x < 9.54 suffer
      from a rendering glitch that affects the AT&T troff (and groff)
      special character \(lh; see
      <https://bugs.ghostscript.com/show_bug.cgi?id=703187>.  Store the
      result of the check.
    
      (GROFF_GHOSTSCRIPT_VERSION_NOTICE): Add new macro to report the
      problem detected by GROFF_GHOSTSCRIPT_VERSION_CHECK to the user.
    
    * configure.ac: Call the macros in appropriate places.
    
    Fixes <https://savannah.gnu.org/bugs/index.php?59531>.
    
    I did not name GROFF_GHOSTSCRIPT_VERSION_NOTICE consistently with other
    groff autoconf macros of similar purpose; I find the existing names,
    ending in "_CHECK", confusing because these don't perform checks except
    in a trivial sense (effectively of a single Boolean variable).  Instead
    they are wrappers around a lengthy parameter to AC_MSG_NOTICE.
    
    By contrast, GROFF_GHOSTSCRIPT_VERSION_CHECK does the actual ugly
    business of calling `gs -v`, munging the resulting string, and
    comparison.  (I tried AX_COMPARE_VERSION but couldn't get it to work,
    and in any case the Ghostscript versioning scheme is simple and sane.)
    
    I'm open to feedback on writing more idiomatic autoconf macros.


    _______________________________________________________

Reply to this item at:

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

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