[XeTeX] Conflict between xunicode and fontspec?

[Peter Dyballa]

Am 07.02.2008 um 16:47 schrieb Ulrike Fischer:

> So the problem is not the input but the output encoding: the default
> encoding eu1 from fontspec doesn't contain the necessary commands  
> to map
> the commands like \^{u} to the correct single glyph "ugrave".

This would explain why at sudden it fails to copy from the PDF file:  
fontspec was changed in an unwanted and unexpected way – besides  
probably not so many will write with LaTeX macros but use the proper  
characters.

Below is just the input, contents of the LaTeX source file, and the  
output I could copy from the PDF file.

>
>> The change has come ... from this in the source Ḃạȳḵ
>> ÝŶŸƳÝẎỴỲỶȲɎỸ ǵğǧģĝġʛɠḡǥɢɡ to that from
>> PDF: Ḃạȳḵ ÝŶŸ￿ÝẎỴỲỶȲ￿Ỹ
>> ǵğǧģĝġ￿￿ḡ￿￿￿! Fontspec only used with Monaco.
>
> ?? Not quite sure what this should mean.




I was thinking (and I think I also experienced this) xdv2pdf and  
xdvipdfmx were inserting a mapping from accented characters to their  
Unicode positions, just as Vladimir Volovich's cmap packages tries to  
handle this with pdfTeX, so that copying from the PDF file resulted  
in fully composed Unicode strings. At least today I cannot copy  
composed Unicode characters from any PDF file.

--
Greetings

   Pete

It's not the valleys in life I dread so much as the dips.
				– Garfield