[bug #61829] [libdriver] unhelpful diagnostics when font nonexistent

[G. Branden Robinson]

Update of bug #61829 (project groff):

                  Status:             In Progress => Fixed                  
             Open/Closed:                    Open => Closed                 
         Planned Release:                    None => 1.23.0                 

    _______________________________________________________

Follow-up Comment #1:


commit e5e72144155b9fb66d398cf51711c5368729065e
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sun Jan 16 17:54:48 2022 +1100

    [libdriver]: Update diagnostic messages.

    * src/libs/libdriver/printer.cpp (printer::find_font): Describe the
      problem encountered instead of saying lamely "sorry, I can't
      continue".

      (printer::set_char_and_width, printer::set_numbered_char):
      Characterize input as "invalid", not "bad"; see commit bb7512b5, 17
      September.  When referring to font mounting position, say so.

      (printer::set_char_and_width): Describe required input character as
      "ordinary", not "ascii".  Apart from the incorrect casing, doing so
      better aligns with our terminology in groff_char(7), groff_out(5), our
      Texinfo manual, and other diagnostic messages; moreover, the use of
      "ascii" is potentially confusing to those whose environments use
      another encoding, like UTF-8 or IBM code page 1047.

    Fixes <https://savannah.gnu.org/bugs/?61829>.



    _______________________________________________________

Reply to this item at:

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

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