[bug #51568] gropdf: Bug when string '\e014' is in the input

[G. Branden Robinson]

Update of bug #51568 (project groff):

                  Status:                    None => Fixed                  
             Assigned to:                    None => deri                   

    _______________________________________________________

Follow-up Comment #8:

Reported fixed in git HEAD.

commit eaf4526d8c3d52a46f95bdfc06ac692f9d5b424f
Author: Deri James <address@hidden>
Date:   Fri Aug 4 00:56:22 2017 +0100

    See bug at: https://savannah.gnu.org/bugs/?51568
    
    * src/devices/gropdf/gropdf: Further 'fix' to handle those octal
    characters. See comment #5 - thank you Bjarni.

commit 6a241192be60d0cc1a2ab5464281e297b2c0243d
Author: Deri James <address@hidden>
Date:   Mon Jul 31 17:02:02 2017 +0100

    See bug at: https://savannah.gnu.org/bugs/?51568
    
    * src/devices/gropdf/gropdf: previous 'fix' was too narrow, all
    '\' characters should be escaped. Also there was an unwanted
    interaction with code in routine 'do_t'. Sometimes, do_C, when
    the named glyph is mapped to a chr < 32, this is encoded as
    octal \nnn, so in this case the '\' must not be escaped.

commit 67c3d46d452ce05082839920a8058091a8797583
Author: Deri James <address@hidden>
Date:   Tue Jul 25 16:43:54 2017 +0100

            If input text contained string which could be interpreted as
            escaped octal (\ddd) a pdf viewer would interpret as an octal
            character.  See bug at: https://savannah.gnu.org/bugs/?51568
    
            * src/devices/gropdf/gropdf: protect text which resembles \ddd
            by escaping with extra '\'.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51568>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/