[Poppler-bugs] [Bug 97449] New: PDFDoc::setDocInfoStringEntry() should treat value consisting of just the unicode marker as an empty string

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=97449

            Bug ID: 97449
           Summary: PDFDoc::setDocInfoStringEntry() should treat value
                    consisting of just the unicode marker as an empty
                    string
           Product: poppler
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: poppler-bugs at lists.freedesktop.org
          Reporter: jakubkucharski97 at gmail.com

A frontend like glib during string conversion from UTF8 to UTF16-BE inserts the
unicode marker and when the input string is empty, then the output consists of
just the unicode marker which prevents PDFDoc::setDocInfoStringEntry() from
detecting that in reality it's an empty string. It may potentially occur in
other places, so I think it should be fixed in PDFDoc::setDocInfoStringEnty(),
not in the callers, since converting an empty string to just the unicode marker
seems like a valid behavior to me and in a sense such a string is really empty.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/poppler-bugs/attachments/20160823/bda08e3d/attachment.html>