Quote:
Originally Posted by frabjous
Interesting. I have noticed that XeLaTeX does sometimes do strange things with how it encodes characters and embeds fonts. Just as a point of comparison, do you have the same problem if you generate using plain LaTeX 2e with type 1 fonts?
|
I tried a few things, here are the results:
- Using LaTeX 2e with type 1 fonts, the same behaviour: double-tapping selects from previous punctuation mark to next.
- Using LaTeX 2e with type 1 fonts, I tried enclosing a single word between two punctuation marks, double-tapping recognizes the word and brings up the definition.
- As mentioned, using XeLaTeX double-tapping selects from previous punctuation mark to next.
- Using XeLaTeX with OTF fonts embedded as type 1, double-tapping a word enclosed between two punctuation marks selects the word but does not recognize it as a word or bring up the definition.
Quote:
Originally Posted by WillAdams
The problem is likely caused by the spaces being omitted when the .pdf is built --- instead they're encoded in as positional information which the .pdf renderer is ignoring.
If memory serves, you can get it to insert the spaces by adding:
\XeTeXinterchartokenstate=1
to your document preamble.
William
|
I would agree with you 100%, the problem is the handling of spacing between characters/words.
I looked up the command you mentioned, it enables you to insert tokens between different characters. However I'm not quite sure how to use it to solve my problem, or even if these interchartokens can solve my problem.
Thank you both for you replies
