[XeTeX] XDV viewer
Alastair M. Paterson
TheDoc at WadiZaytoon.org
Wed Feb 27 11:19:36 CET 2008
The problem was with a font not being displayed correctly in a PDF
viewer so I was wondering where the problem was coming from i.e. in the
stage to the XDV part of in the XDV to PDF conversion, but that issue
has been solved thanks to JK so viewer no longer necessary!
Alastair
Moritz Angermann wrote:
>Hi
>
>I'm not in for questionining the usefulness, but JK has a point here
>and I'd be interesting to see what your intended use is too.
>
>Apart from that:
>One could always write one though.
>After I've been looking though the xdv2png and dvipdfmx, to implement
>the missing opcodes 251 to 254 in dvipng.
>
>If you are familiar with fontconfig, freetype, kpathsea and your
>windowing toolkit on windows it should be straight forward :)
>
>The hardest part for me to extend dvipng is the way it has been
>written. Especially adding new font types to the font numbering
>system. But I'm making slow progress.
>
>kindest regards,
> Moritz
>On 2/27/08, Jonathan Kew <jonathan_kew at sil.org> wrote:
>
>
>> On 27 Feb 2008, at 3:55 am, Alastair M. Paterson wrote:
>>
>> > Hi!
>> >
>> > Does anyone know of a .xdv file viewer that can be used with Windows?
>>
>>
>>AFAIK, the only way to visualize an .xdv file (on any platform) is by
>> converting it to PDF.
>>
>> Think of .xdv as a purely internal format that happens to be used to
>> communicate between two stages of the overall process. The fact that
>> it's possible to capture this internal data into a file is an
>> irrelevant detail of the implementation.
>>
>>
>> >
>> > I need to see the output of this file (produced by MikTeX) without
>> > converting it to PDF.
>>
>>
>>Why do you need this?
>>
>>
>> JK
>>
>>
>> _______________________________________________
>> XeTeX mailing list
>> postmaster at tug.org
>> http://tug.org/mailman/listinfo/xetex
>>
>>
>>
>
>
>
>
More information about the XeTeX
mailing list