Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Unknown <dog@gmail.com>
Newsgroups: comp.lang.postscript
Subject: *nix: pdftotext messes quotes; mouse-pastes OK?
Date: Wed, 9 Sep 2015 05:34:36 +0000 (UTC)
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <pan.2015.09.09.05.37.39@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 9 Sep 2015 05:34:36 +0000 (UTC)
Injection-Info: mx02.eternal-september.org; posting-host="974223c501b3e1a146fe31977db83b12"; logging-data="15444"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+LiZgbBWCuUjxfLMp5mNC8wR6mIEgnrSk="
User-Agent: Pan/0.133 (House of Butterflies)
Cancel-Lock: sha1:g768MI02lT/lb9gQ3NhaiosO/xw=
Xref: csiph.com comp.lang.postscript:2346

How does mouse-pasting from `xpdf <file.pdf>` manage to do the quote/
apostrophe correctly; when `pdftotext` can't do it: but translates the
single-quote to 3 non-ASCII-chars ?!

I'm guessing, that working backwards from the screen:
screen <-FrameBufrPixels <-Char & Font
Well yes,the mouse current X,Y position is/must be mappable to the 
corresponding char.
Whereas `pdftotext` only sees the bytes of the <File.pdf>.
Ie. the mouse works with wysiwyg, where as `pdftotext` misses out
several translation steps.

Is that right?