[XeTeX] xdvipdfm and Omega dvi files

Pablo Rodríguez oinos at web.de
Wed Aug 23 23:57:58 CEST 2006

Jonathan Kew wrote:
> On 23 Aug 2006, at 4:15 pm, Pablo Rodríguez wrote:
>> Trying to use xdvipdfmx 0.3 with an Omega generated dvi file, gives me
>> the following error:
>> xdvipdfmx culturalibre
>> culturalibre.dvi -> culturalibre.pdf
>> [1otf_load_Unicode_CMap(GenR101, 0)
>> ** ERROR ** Could not open TrueType font file "GenR101"
>> Output file removed.
>> As far as I can remember, it worked fine with version 0.1.
>> GenR101 is a TrueType font and has a .ttf extension (just in case  
>> it helps).
> Uh oh -- sorry, you've run into an unfinished fragment of the  
> program. :(
> The font-reading code has undergone some significant changes since  
> 0.1, and not everything is 100% done or tested. As I don't use .ttf  
> fonts via Omega (or standard TeX) myself, I hadn't run into this  
> particular situation, but it is a case where I know the support is  
> incomplete; there's a "FIXME" comment in the code right there!

Thanks for the reply, Jonathan.

What I have discovered is that xdvipdfmx inserts two pdfproducers in a
file (xdvipdfmx and the other set in the source file) in the final PDF
document. dvipdfmx only includes dvipdfmx as producer in the PDF field.

I don't know whether users should be able to change the producer field
in the final PDF document, but xdvipdfmx should generate only one
producer in the PDF document fields.

Many thanks for your help,


More information about the XeTeX mailing list