On 15 Apr 2014, at 9:49 am, Khaled Hosny khaledho...@eglug.org wrote:
On Thu, Apr 10, 2014 at 12:58:23PM +0100, Philip Taylor wrote:
Why are these key XeTeX primitives (\XeTeXprotrudechars, \rpcode, etc)
not documented in /The XƎTEX reference guide/ ? Will, Khaled,
Jonathan : can you
Hallo both --
Will Robertson wrote:
I’ve been away from LaTeX development work for a while; I’ve been known to let
primitives slip through the cracks.
Thanks for letting us know — I wouldn’t be surprised if there were some more we
overlooked.
These commands are all described in the pdfTeX
Philip Taylor wrote:
Hallo both --
[long snip]
It would also (IMHO) be very helpful to document how to create
hyperlinks at the XeTeX primitive (\special) level; JK writes :
IIRC, hyperlinks are handled entirely at the pdf output driver level; there are
no xetex primitives involved.
On Fri, 25 Apr 2014, Philip Taylor wrote:
(X)DVIPDFM(X). Since (X)DVIPDFM(X) is indeed an integral part of the XeTeX
tool chain, I think that documenting how to access its functionality (with
XeLaTeX is the integrated toolchain. If you're going to insist that XeTeX
without LaTeX must be fully
2014-04-25 13:59 GMT+02:00 msk...@ansuz.sooke.bc.ca:
On Fri, 25 Apr 2014, Philip Taylor wrote:
(X)DVIPDFM(X). Since (X)DVIPDFM(X) is indeed an integral part of the
XeTeX
tool chain, I think that documenting how to access its functionality
(with
XeLaTeX is the integrated toolchain. If
On Apr 25, 2014, at 7:51 AM, Zdenek Wagner zdenek.wag...@gmail.com wrote:
2014-04-25 13:59 GMT+02:00 msk...@ansuz.sooke.bc.ca:
On Fri, 25 Apr 2014, Philip Taylor wrote:
(X)DVIPDFM(X). Since (X)DVIPDFM(X) is indeed an integral part of the XeTeX
tool chain, I think that documenting how to
msk...@ansuz.sooke.bc.ca wrote:
XeLaTeX is the integrated toolchain. If you're going to insist that XeTeX
without LaTeX must be fully documented as a separate entity, then it only
makes sense to do the same for XDVIPDFMX.
I'm sorry, what has LaTeX to do with any of this ?
Philip Taylor
On Fri, 25 Apr 2014, Philip Taylor wrote:
I'm sorry, what has LaTeX to do with any of this ?
You don't want to hear about XeLaTeX, but you write:
(X)DVIPDFM(X). Since (X)DVIPDFM(X) is indeed an integral part of the XeTeX
tool chain, I think that documenting how to access its functionality
On Fri, Apr 25, 2014 at 07:18:34PM +0930, Will Robertson wrote:
Khaled, would you be able update the copy in the xetex repo?
Just send me the updated version and I’ll commit it (a git format-patch
would be even better but not necessary).
Regards,
Khaled
msk...@ansuz.sooke.bc.ca wrote:
On Fri, 25 Apr 2014, Philip Taylor wrote:
I'm sorry, what has LaTeX to do with any of this ?
You don't want to hear about XeLaTeX, but you write:
(X)DVIPDFM(X). Since (X)DVIPDFM(X) is indeed an integral part of the XeTeX
tool chain, I think that
On Fri, 25 Apr 2014, Philip Taylor wrote:
I'm sorry, Matthew, I can only think you are confusing XeTeX with some other
system.
Just because you can invent a silly-looking command line to make invoking
XeLaTeX look more difficult than it is, doesn't make XeLaTeX stop being an
integrated tool
msk...@ansuz.sooke.bc.ca wrote:
Just because you can invent a silly-looking command line to make invoking
XeLaTeX look more difficult than it is, doesn't make XeLaTeX stop being an
integrated tool chain. However, it seems unlikely that either of us will
be able to change the other's mind on
XeTeX My-file
..
XeTeX LaTeX My-LaTeX-file
Philip that's not been true for so long I'm surprised you can remember
that far back:-) all the web2c engines load formats based on their
name, there is no intrinsic difference between say pdflatex with a
preloaded latex and pdftex with a pre loaded
David Carlisle wrote:
I don't see any reason to include the documentation in the xetex manual
texdoc dvipdfmx
provides a 5 or so page tugboat article with the details, what's to be
gained by copying that?
It just duplicates the information and is only of interest to a
minuscule fraction
2014-04-25 22:21 GMT+02:00 Philip Taylor p.tay...@rhul.ac.uk:
David Carlisle wrote:
I don't see any reason to include the documentation in the xetex manual
texdoc dvipdfmx
provides a 5 or so page tugboat article with the details, what's to be
gained by copying that?
It just
Zdenek Wagner wrote:
XeTeX can do via xdvipdfmx specials almost everything explained in the
PDF reference and pdfmark reference. Will you insist to include these
1000+ pages in the XeTeX manual?
No, Zdeněk; I am asking for /important/ facts to be documented,
not the entire known universe.
Should a \XeTeXpicfile primitive take a JPG or similar as parameter;
for a PDF, do you not want \XeTeXpdffile ?
I think you're right. Picfile used to handle with PDF images, but
apparently not anymore. Thanks.
By the way, is there a more detailed description of these primitives than
the
17 matches
Mail list logo
