Hi Dom I thought this might be interesting in light of the recent work you've been doing on PdfString:
http://en.wikipedia.org/wiki/C++0x#New_string_literals It's going to be a while before those types start seeing use in user code, but it's probably worth thinking about how to cleanly support them now. Ideally if the PoDoFo headers see that __cpp0x (or whatever the c++0x typedef is) is defined they should be able to enable a couple of new functions and conversion operators for those types. The main difference between pdf_utf16be and char16_t appears to be endianness. pdf_udf16be is always big endian, whereas char16_t has the endianness of the host platform (IMO a mistake, and one I really hope they'll fix before finalizing C++0x). It's great to see that the C++ folks have realized that char* and std::string are inadequate, and that a language really can't get by with only an encoding-less byte string type. It's a pity they didn't call the new types uchar32 and uchar16, though, to make it explicit that they're unicode code points rather than a character in any unspecified 16 bit or 32 bit encoding (as char is for 8 bit characters). There's already support for these types in gcc as of April 18 2008. -- Craig Ringer ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Podofo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/podofo-users
