Hello, Maybe this is a bug in PoDoFo - or just wrong usage of the library functions:
Reading/parsing PDF-Files which contain strings with escape sequences, e.g. (\r) or (\b), causes problem when writing these strings: the functions PdfVariant::Write() and PdfString::Write() yield a strange output - that is: (\r) becomes ( ) and (\b) becomes ) respectively. That means, the escape sequences are resolved in the output to a CR or BACKSPACE instead of maintaining the escaping with the Backslash "\". Due to this behavior, the written PDFs are corrupt (esp. due to malformed syntax produced by the \b). Is there a special function or flag to find a work-around for this behavior? I could not fix the problem with PoDoFo functions but rather had use PdfVariant::ToString() and rewrite the std::string manually to hex codes... Thank you for your help! Greetings, Amin PS: The strange encodings with low code numbers occur in a PDF where a Font Encoding remaps all present characters by a "Differences"-Mapping to codes starting at 1 - i.e. the non-printable chars will be mapped to printable characters by this encoding (cf. Pdf Spec Sect 9.6.6 Character Encoding). ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
