Re: kpathsea in xdvipdfmx source files
Daniel Greenhoe <[email protected]>
| Newsgroups | gmane.comp.tex.miktex |
|---|---|
| Message-ID | <CAF=Ssq5P7CUmgMOddkseuHMvqM0HpRDVXsUZj4te5B6VnnWW=Q@mail.gmail.com> |
> To be able to > build a self-contained format like pdf from it xdvipdfmx must be > able to find quite a lot things which can be stored in the texmf > trees (and so are found with kpathsea): Thank you Ulrike for your explanation of kpathsea. That was helpful. > Why don't you try TeXLive first? Thank you also for this suggestion. I have wget working on downloading TeXLive now from ftp://www.ctan.org/tex-archive/systems/texlive/tlnet/ But it is still with some anguish that I perhaps leave MikTeX behind after using it all these years just because I can't solve what should be a straightforward problem. I just can't understand why the example I sent out before would fail on my system but work perfectly on some (or all) other people's systems. Might you have any guesses why that might be, or how to go about debugging it without debugging xdvipdfmx at the c source file level? I only started trying to do this out of desperation. I really have a ton of other work waiting that I would prefer to be spending time on (which of course is my problem ... not anyone else's). Dan On Fri, Aug 5, 2011 at 3:11 PM, Ulrike Fischer <[email protected]> wrote: > Am Fri, 5 Aug 2011 07:28:12 +0800 schrieb Daniel Greenhoe: > >> I am trying to compile the source files for xdvipdfmx, but am having >> problems with references to labels containing kpse_.... >> Are these references to kpathsea? >> >> If so, can someone help me better understand this? From what I >> understand, kpathsea is to help with path searching. Why is it's >> presence required in xdvipdfmx? I would think that xdvipdfmx should be >> a straight forward utility that converts from one device independent >> format (xdv) to another (pdf). Why would it need any help from >> non-ANSI-C library functions? > > xdv/dvi->pdf is by no way a "straight" and simple conversion. An xdv > doesn't contain all the needed ressources but only references > ("links"). It's like making a pdf from a html file. To be able to > build a self-contained format like pdf from it xdvipdfmx must be > able to find quite a lot things which can be stored in the texmf > trees (and so are found with kpathsea): the configuration file, > .map-files, fonts referenced in the xdv/dvi (.vf, .pfb, otf, ttf > ...) and pictures. > > Run xdvipdfmx -vv to see all the ressources it searches and uses. > >> I want to compile a bare-bones version of xdvipdfmx for a win32 >> environment for the purpose of debugging xdvipdfmx, because xdvipdfmx >> doesn't work properly on my system when using pstricks with XeLaTeX. > > > Why don't you try TeXLive first? You can install it beside miktex, > you only need to change the PATH variable to switch between the > systems. > > -- > Ulrike Fischer > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > MiKTeX-Users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/miktex-users > ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ MiKTeX-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/miktex-users