How to deal with unicode characters? #7

Activity

1. ShabbyX commented on Jan 23, 2017

   

   ShabbyX

   on Jan 23, 2017

   Owner

   More actions

   I should look into it. I see in 8ec4ac9 that the original author of libpandoc had changed the interface from wchar_t * to char *, adding a comment that all strings should be encoded as UTF-8. There's no explanation as to why!
2. Phyks commented on Jul 8, 2017

   

   Phyks

   on Jul 8, 2017

   Contributor

   More actions

   👍 for this issue. It seems that whatever accentuated character I am feeding in libpandoc, I get the character with code 65533 as output.

   Typically, input "é" gives "�".
3. ShabbyX commented on Jul 10, 2017

   

   ShabbyX

   on Jul 10, 2017

   Owner

   More actions

   This is doable, if I simply duplicate everything and change all CStrings to CWStrings. But that would get quite ugly. I'll see if I can refactor some stuff to do this less dirty (having a newborn doesn't help finding time either!!)
4. Phyks commented on Jul 10, 2017

   

   Phyks

   on Jul 10, 2017

   Contributor

   More actions

   Ok I'll try to have a look at this hack around CWStrings. No problem, thanks for this lib!