Re: [poppler] poppler::ustring encoding issue

2018-03-14 Thread suzuki toshiya
Dear Adam, The 2nd option, iconv + GlobalParams::textEncoding solution might be something like: https://github.com/mpsuzuki/poppler/commit/80f088c4a94b151ddb90e05147a8dc4565e01d89 ? Regards, mpsuzuki suzuki toshiya wrote: > Oops, I'm quite sorry for my mistake which make people confused as > if

Re: [poppler] poppler::ustring encoding issue

2018-03-14 Thread Albert Astals Cid
El dimecres, 14 de març de 2018, a les 18:17:47 CET, suzuki toshiya va escriure: > Dear Adam, > > The 2nd option, iconv + GlobalParams::textEncoding solution might be > something like: > https://github.com/mpsuzuki/poppler/commit/80f088c4a94b151ddb90e05147a8dc456 > 5e01d89 ? Seems a bit too

Re: [poppler] poppler::ustring encoding issue

2018-03-14 Thread suzuki toshiya
Dear Jeroen, Adam, Sorry for long latency about this issue. I would try to draft the solutions suggested by Adam. Yet I'm not sure what I'm seeing now is same trouble with you. In my case, the testing PDF is:

Re: [poppler] poppler::ustring encoding issue

2018-03-14 Thread suzuki toshiya
Oops, I'm quite sorry for my mistake which make people confused as if my bits are in github.com/freedesktop. The right places are: sample PDF file https://github.com/mpsuzuki/poppler/blob/cpp-textlist-encoding-issue/cpp/tests/HereIsUSASCII.pdf a easiest (and oversimplified) fix for this issue