I noticed that there is some use of std::string in the codebase. I think GooString is historical, but it does provide some number conversion facilities that are a little less straightforward with std::string. For the most part GooString has met my needs for pdftohtml, and where it hasn't, I've extended it, because for consistency it seems like a good choice -- don't know if that's right or wrong. It's a good question.
--josh On 11/3/11 10:43 PM, "Alec Taylor" <[email protected]> wrote: >Good evening, > >Why should I use GooString instead of std::string? > >I've been very careful so far with my patches to only using GooString. >But I was wondering if there is a specific added feature set (i.e. >UTF16) which can only be achieved with your custom GooString library. > >Thanks for all information, > >Alec Taylor >_______________________________________________ >poppler mailing list >[email protected] >http://lists.freedesktop.org/mailman/listinfo/poppler > _______________________________________________ poppler mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/poppler
