On 2022-05-29 21:16, Apostolos Syropoulos via XeTeX wrote:
[...] The two files differ as follows:
28,29c28,29
< \node[inner sep=0pt] (light) at (1,2.1)
< {\includegraphics[scale=0.1]{TRAIN-crop.pdf}};
---
\node[inner sep=0pt] (light) at (5.2,3.5)
{\includegraphics[scale=0.
Hello,
On 2022-01-12 16:41, Niemann, Hartmut wrote:
Hello!
I observed a strange thing when experimenting with colored text.
\usepackage{bookmark}
\section{\color{red}Two}
There is a pdf bookmark for each section, but the second one is “redTwo”
instead of “Two”.
Is there a way to avoid
Hello,
the properties of the PNG file "Zaborowski_MBC_page19y42_a.png"
are (retrieved by display from ImageMagicks):
png:IHDR.width=112 pixels
png:IHDR.height=42 pixels
png:pHYs.x_res=984 pixels/m ≈ 25 dpi
png:pHYs.y_res=276 pixels/m ≈ 7 dpi
The image has different resolutions in the x
.
xelatex --no-pdf test
xdvipdfmx test
The last command will show an error, what it is?
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Hello,
On 29.08.2015 19:16, M. Lin wrote:
Hi,
I have problem with pdf output when I running xetex. There is no any
errors, but it does not produce pdf file.
This is normal, when there is no material to be shipped out, e.g.:
\documentclass{article}
\begin{document}
\end{document}
Therefore,
On 04.08.2014 19:50, Stefan Solbrig wrote:
>> Turns out we've also been bit by this problem... please see my
>> questions below.
>>
>> On 2014-08-04 01:55, Heiko Oberdiek wrote:
>>> On 04.08.2014 01:27, Gildas Hamel wrote:
>>>> I append th
TeX programs (XeTeX, *dvipdfm*, pdfTeX, LuaTeX,
bmpsize, ...) could agree on the same algorithm, which
values resolution are used in which order. Then the images
would have the same size on all TeX systems.
Yours sincerely
Heiko Oberd
orts three level.
Probably xindy can support more.
Usually two levels should be enough,
a further level for emergencies.
But IMHO four levels indicate a much too
complex index both for the writer and
the reader.
Yours sincerely
Heiko Oberdiek
--
\documentclass{article}
\usepackage{hyperref}
\usepackage{bookmark}
\bookmarksetup{
depth=subsubsection,
numbered,
}
\setcounter{tocdepth}{2}
\begin{document}
\tableofcontents
\section{Chapter heading}
\subsection{Drug name}
\subsubsection{Individual section}
\end
PDF.
There are other less invasive options:
pdftk old.pdf cat output new.pdf
Or use another PDF library for reading/writing. When the file
is written, PDF object compression of PDF-1.5 must be disabled.
Yours sincerely
Heiko Oberdiek
--
an EPS file.
It is much better to generate an EPS file in the first place
(setting an option to create EPS instead of PS in the driver/program
that generates the PostScript, ...).
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
inventor)
* LuaTeX: \pdf@filemoddate of package `pdftexcmds' (also plain TeX)
* XeTeX: not available (!)
Again \pdf@filemoddate can be used for the differnt engines (pdfTeX/LuaTeX),
but in case of XeTeX you are out of luck. You have to resort the shell
escape feat
XeTeX, just a few more bytes for the PDF version could
be added to the intermediate file. And the driver side (xdvipdfmx)
just need a function to read it from there.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
.
would be useful.
Example to generate uncompressed PDF:
xe(la)tex --output-driver="xdvipdfmx -V4 -z0"
But the most annyouning bug is the broken/crappy/unspecified interface
to transfer binary bytes to PDF output structures.
Yours sincerely
Heiko Oberdiek
Am 08.06.2012 02:27, schrieb Karl Berry:
Martin Scharrer has added clipping to xetex.def.
...
https://groups.google.com/forum/#!msg/comp.text.tex/pOR3Zv39TUA/02hiqt8TP94J
And Joseph, evidently. That is great! Longstanding issue with XeTeX.
As far as I know, xetex.def is mainta
s features higher than the version number would support.
pdfTeX only warns or throws an error message, if the
feature in question is in control of the engine.
Example: \pdfobjcompresslevel.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archiv
not necessarily mean that
the output file contains a ligature glyph. It could be
a fake ligature at TeX level that get replaced by something
else, e.g. by using virtual fonts.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information,
he rectangle with "a" and "b".
The rule in between is higher than "b".
* Page 3: xdvipmx only makes a tiny link spot at the left lower corner,
no link with dvipdfmx.
BTW, setting the width of the invisible rules from 0pt to 1mm
does not make a difference.
Yours s
On Wed, Feb 29, 2012 at 12:24:11AM +0100, Zdenek Wagner wrote:
> 2012/2/28 Ross Moore :
> >
> > On 29/02/2012, at 8:44 AM, Heiko Oberdiek wrote:
> >
> >> ...
> >
> > BTW, what about the /CreationDate and /ModificationDate ?
> > Surely these shoul
On Wed, Feb 29, 2012 at 09:57:04AM +1100, Ross Moore wrote:
> On 29/02/2012, at 8:44 AM, Heiko Oberdiek wrote:
>
> > Hello,
> >
> > the entries in the information dictionary can be controlled
> > at TeX macro level except for /Producer:
> >
> > % xetex
/hyperref: pdfproducer={XeTeX ...} does not work.
* hyperxmp is at a loss, it *MUST* know the value of the
/Producer, because the setting in the XMP part has to be
the same.
Please fix this issue in xdvipdfmx.
Yours sincerely
Heiko Oberdiek
--
IK pdfparcolumns works only with pdfTeX.
Because pdfTeX supports multiple color stacks.
Also LuaTeX should work with package `luacolor',
because LuaTeX supports attributes.
XeTeX and other (dvips, ...) offer neither
multiple color stacks nor attributs.
On Wed, Dec 21, 2011 at 04:37:08PM +0100, Ulrike Fischer wrote:
> Am Wed, 21 Dec 2011 15:26:16 +0100 schrieb Heiko Oberdiek:
>
> >> but of course I am put off by the fact that it warns me that it
> >> cannot find a free read register.
>
> > Unless you are
font\rm=cmr10
\rm
\hologo{XeTeX}
\font\lm=[lmroman10-regular]
\lm
\hologo{XeTeX}
...
The logo uses U+018E if the font has this glyph otherwise
the reversed E is constructed.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Wed, Dec 07, 2011 at 06:30:39AM +0800, Daniel Greenhoe wrote:
> On Wed, Dec 7, 2011 at 5:46 AM, Heiko Oberdiek
> wrote:
> > You have to compile twice at least.
>
> I compiled at least 8 times using "xelatex Heiko.tex". I still get the
> same error: the text e
e (see attachments). Did I do something wrong?
Yes, not reading the screen messages/.log file.
You have to compile twice at least.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
zref@savepos
\zref@labelbyprops{tl@a\thetlcount}{posy}%
\box\tl@box
}%
}
\begin{document}%
xyz\footnote{%
\begin{tltabular}{l}
abc\\
def\\
ghj\\
klm\\
\end{tltabular}%\\
}
xyz\footnote{%
\begin{tltabular}{l}
abc\\
On Thu, Dec 01, 2011 at 06:06:13PM +, Philip TAYLOR wrote:
> Heiko Oberdiek wrote:
>
> >Because they are solving those problems for you and others now
> >and in the future. That is one of the main reasons for a package,
> >providing an easier interface for tricky
On Thu, Dec 01, 2011 at 05:38:04PM +0100, Zdenek Wagner wrote:
> 2011/12/1 Heiko Oberdiek :
> > On Thu, Dec 01, 2011 at 04:51:14PM +0100, Zdenek Wagner wrote:
> >
> >> 2011/12/1 Philip TAYLOR :
> >> >
> >> >
> >> > Heiko Oberdiek wro
On Thu, Dec 01, 2011 at 04:47:30PM +, Philip TAYLOR wrote:
> Heiko Oberdiek wrote:
>
> >It's your choice to use low level internals. Higher level interfaces
> >are already written and some can also be used with plain TeX:
> >
...
> >\input graphicx.sty
.
eXpicfile and \XeTeXpdffile for the end user.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Thu, Dec 01, 2011 at 04:51:14PM +0100, Zdenek Wagner wrote:
> 2011/12/1 Philip TAYLOR :
> >
> >
> > Heiko Oberdiek wrote:
> >
> >> No, it's a whatsit. It is *not* discarded, but it isn't a box.
> >
> >
> > Right, so why isn
On Thu, Dec 01, 2011 at 03:58:10PM +0100, Zdenek Wagner wrote:
> 2011/12/1 Heiko Oberdiek :
> > On Thu, Dec 01, 2011 at 11:49:30AM +, Philip TAYLOR wrote:
> >
> >> Typesetting a restaurant menu, I have run into two problems :
> >> one I can work around, one
On Thu, Dec 01, 2011 at 03:03:32PM +, Philip TAYLOR wrote:
> Heiko Oberdiek wrote:
>
> >D.E. Knuth, "The TeXbook": "Chapter 15: How TeX Makes Lines into Pages":
> >
> >| Whenever TeX is moving an item from the top of the "recent
> >|
introduces a significant
> >right shift for all text that follows it on the current
> >page; concealed within a \centerline, all is well yet
> >concealed within braces the artifact remains (so it
> >is not a scoping issue).
Make a minimal example that show
Solution, for example: put \XeTeXpicfile ... in an \hbox.
> Problem 2 (completely intractable) : XeTeX claims to be unable to find
> "TAR-2.pdf",
Already answered (\XeTeXpdffile).
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
n the PDF output.
If someone want's this issue fixed, make a feature request
for XeTeX/xdvipdfmx to provide a real "\pdfliteral direct"/
"direct mode for colors" without breaking text sections.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Wed, Nov 30, 2011 at 10:58:23AM +1100, Ross Moore wrote:
> On 30/11/2011, at 10:32 AM, Heiko Oberdiek wrote:
>
> > or
> > 00c4\\
> > A0308\\
> > A\textcolor{red}{0308}
> >
> > As you can see, this problem is not related to color,
>
Hi Ross,
On Wed, Nov 30, 2011 at 06:23:54AM +1100, Ross Moore wrote:
> Hi Heiko,
>
> On 29/11/2011, at 9:29 AM, Heiko Oberdiek wrote:
>
> > The same also works in XeLaTeX:
> >
> > \documentclass{minimal}
> > \usepackage{fontspec}
> > \usepackage{co
%%
\IfXeTeXTextCharNumExists{"018E}{yes}{no}
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Tue, Nov 29, 2011 at 07:40:13AM +, Jonathan Kew wrote:
> On 28 Nov 2011, at 08:06, Heiko Oberdiek wrote:
>
> > \catcode`\{=1
> > \catcode`\}=2
> > \catcode`\^=7
> > \showboxdepth=1
> > \showboxbreadth=1
> > \tracingonline=1
> >
ontsize{100pt}{100pt}\selectfont
\noindent
00e4\\
a0308\\
a\textcolor{red}{0308}
\end{document}
stream
q 1 0 0 1 72 769.89 cm 0 G 0 g 0 G 0 g 0 G 0 g BT /F1 99.626 Tf 0 -63.86
Td[<00a0>]TJ 0 -99.63 Td[<001c00ee>]TJ 0 -99.62 Td[<001c>]TJ ET 1 0 0 RG 1
0 0
; \moo
> \textcolor{red}{}
> \end{document}
>
> I'm not much of an expert in the inner workings of TeX and I know
> absolutely nothing about Lua (is that a derivative of LISP?) so I
> can't comment on whether the luacolor package could be ported to
> XeTeX.
On Mon, Nov 28, 2011 at 07:19:48AM +, Jonathan Kew wrote:
> On 28 Nov 2011, at 06:59, Heiko Oberdiek wrote:
>
> > On Mon, Nov 28, 2011 at 03:07:07PM +1030, Andrew Moschou wrote:
> >
> >> 2011/11/28 Zdenek Wagner
> >>
> >>> Put it into an \h
this measure the ".notdef"
> glyph?
No, the problem is rather that a existing glyph can have width zero
(not likely in your case) and that there is a warning in the .log file.
See my examples.
Yours sincerely
Heiko Oberdiek
--
Subsc
18e\expandafter}%
\expandafter\endgroup
\ifdim\lastkern=1sp
\immediate\write16{glyph does not exist}%
\else
\immediate\write16{glyph does exist}%
\fi
\csname @@end\endcsname\end
Disadvantage: There is a warning in the .log file for missing gly
mp;\vfill\hbox{#}\vfill\cr E\cr e\cr}
\end{document}
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
river xetex.def scales the images by a separate
scale operation except for PostScript images. In the latter case
\special{PSfile="myimage.eps" ...} is used with the restriction
of integer numbers (bounding box for size and the final width/height
with unit pt or bp).
Yours sincerely
Heiko Oberd
siteCommand{\=}{EU1}{y}{%
\leavevmode
\begingroup
\sbox0{016b}%
\sbox2{02c9}%
\sbox4{y}%
\rlap{%
\hbox to \wd4{%
\hfill
\raisebox{\dimexpr\ht0-\ht2\relax}{02c9}%
\hfill
}%
}%
y%
\endgr
is 498.9bp x 708.66bp
or 176mm x 250mm that is the correct size for B5.
If your memoir comes from the stone age (before XeTeX and its support),
then update. Otherwise a minimal example and the command line call
help in finding the cause of your problem.
Yours sinc
ooperation of
> macro package authors, in that macros designed to directly generate binary
> PDF streams and send them out via \special cannot be expected to work
> unchanged - they're assuming that the argument of \special{...} expands to
> a string of 8-bit bytes, not a string of Unicode characters, and that's
> not true in xetex.
Thus xdvipdfmx knows that it can only get UTF-8, not arbitrary 8-bit.
If it then allows a syntax in its supported specials that allows
arbitrary 8-bit, then also the macro package authors would be happy. :-)
Currently this is not the case.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
vipdfmx finds a way for specifying arbitrary
byte strings (at least for PDF strings(/streams)) -- it is a
requirement of the PDF specification. Or we have to conclude
that 8-bit is not supported and that means US-ASCII.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
X macro package to generate
> arbitrary binary data (byte streams) and expect these to be passed
> unchanged to the output. I suspect that's what Heiko's macros probably do,
> and it worked in pdftex where "tex character" == "byte", but it's
> problematic when "tex character" == "Unicode character".
Yes, that's the problem. PDF is a binary format, not a Unicode text format.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
iour of 8-bit characters in destination strings
are unspecified and undocumented. It makes more sense to address
the problem upstream first.
> > pdfTeX is fine, because it doesn't reencode the strings.
> > Also \pdfescapestrin
\BenutzedieSprache{Englisch}
No, wait, without spaces???
\Befehlsnamensstart Benutze die Sprache\Befehlsnamenende{Englisch}
;-))
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Fri, Nov 04, 2011 at 07:31:02AM +1100, Ross Moore wrote:
> On 04/11/2011, at 1:58 AM, Heiko Oberdiek wrote:
>
> > Hello,
> >
> > to get more to the point, I start a new thread.
>
> Yes. very good idea.
>
> > As we have learned, the PDF specification
oTo%
/D(foobar)%
>>%
>>%
}%
% ABC%
\vrule width4bp height2bp depth2bp\relax
\special{pdf:eann}%
\hss
}%
}%
}
\end
The annotation apperas, if there are characters inbetween (ABC).
Yours sincerely
Heiko Oberdiek
--
the PDF file still contains:
/D
Only the other way worked:
\special{pdf:dest ...}
\special{pdf:ann ... /D(änchør) ...}
Result:
* Even for nice short names the size is doubled and increased
by two bytes.
* Assymetrical behaviour of \special commands
On Wed, Nov 02, 2011 at 01:30:53PM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
> Heiko Oberdiek wrote:
>
> >XeTeX can't write byte strings.
>
> Is this a XeTeX or an (x)dvipdfmx limitation, Heiko?
AFAIK both.
Your
> I do not understand the question. There /is/ no "encoding" in a
> byte string; it is a byte string, by definition. What am I missing ?
That XeTeX can't write byte strings.
Yours sincerely
Heiko Oberdiek
--
Subscriptio
vers much more encodings than you can think of.
But the tools inbetween apply restrictions (plain TeX,
LaTeX, XeTeX, xdvipdfmx, ...).
And for example, XeTeX adds the restriction that
arbitrary 8-bit bytes cannot be written. A severe
restriction when dealing with binary
On Wed, Nov 02, 2011 at 11:42:38AM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
> Heiko Oberdiek wrote:
> >On Wed, Nov 02, 2011 at 11:14:54AM +, Philip TAYLOR (Webmaster, Ret'd)
> >wrote:
> >
> >>Heiko Oberdiek wrote:
> >>
> >>>
On Wed, Nov 02, 2011 at 11:14:54AM +, Philip TAYLOR (Webmaster, Ret'd)
wrote:
> Heiko Oberdiek wrote:
>
> >If the OP needs funny stuff as labels
>
> Heiko, you are, I believe, a native German speaker
> (please correct me if I am mistaken). In your
> person
t;meaning" in the string/name contents
consisting of bytes, not characters.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
s, because they are
generated automatically, then the it can be made safe
by converting to hex strings (package pdfescape
and others), for example.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
loats is that the numbering
might get out of order, because the floating algorithm does not know
about the non-floats.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
1 %
\catcode`\}=2 %
\catcode`\#=6 %
\countdef\C=0 %
\C=1 %
\countdef\X=255 %
\X=7 %
\chardef\I=1 %
\let\A=\advance
\let\S=\shipout
\let\H=\hbox
\let\N=\ifnum
\let\F=\fi
\def\P{%
\S\H{}%
\A\C\I
\N\C>\X
\let\P\relax
\F
\P
}
\P
\end
Yours sincerely
ptionsToPackage{options}{something}
\usepackage{anything}
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
if the loaded packages is too old.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
s option list. And the package documentation
needs to be checked, if options of this package might overwrite
each other.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
you mean with *both*?
It is a bug in polyglossia that xkeyval has to be loaded manually
before polyglossia, because polyglossia has
forgotten \RequirePackage{xkeyval}.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
pdfTeX you
specify the number followed by "0 R". But in dvipdfm(x)/XeTeX the
objects are referenced by name without "0 R":
\special{pdf: object @extgs << /GSko @opoff /GSop @opon >>}
\special{pdf: put @resources << /ExtGState @extgs >>}
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
articular that content streams, which define the visible contents
| of the document, may not contain indirect references (see Section 3.7.1,
| "Content Streams").
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Tue, Aug 30, 2011 at 12:19:51PM +0200, Oleg Parashchenko wrote:
> Hello again,
>
> On Fri, 26 Aug 2011 12:32:14 +0200
> Heiko Oberdiek
> wrote:
>
> ...
> > * \pdfobj useobjnum/pdfobj: Objects can be constructed by
> > \special{pdf:obj
fobj: Objects can be constructed by
\special{pdf:object ...}
\special{pdf:put ...}
\special{pdf:close ...}
\special{pdf:stream ...} (dvipdfmx)
\special{pdf:fstream ...} (dvipdfmx)
Yours sincerely
Heiko Oberdiek
--
Subscriptions,
;>>>}
See the PDF specification for the contents of dictionary /Trans.
It works in AR5/Linux. In AR7/Linux and AR8/Linux the effects
are active in full screen mode only.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and Lis
eXoutputencoding" is missing.
Is there a way to write arbitrary binary data in files
and \special commands? Or is this limited to 7bit or UTF-8?
Yours sincerely
Heiko Oberdiek
^1 For the example the workaround would be using the
filter ASCII85Decode (or ASCIIHexDecode). But that blows
On Mon, May 16, 2011 at 07:57:14AM -0500, msk...@ansuz.sooke.bc.ca wrote:
> On Mon, 16 May 2011, Heiko Oberdiek wrote:
> > take some actions arising specials. But these actions might
> > have effects on the whole document. Sometimes this is good
> > to avoid missing object d
nown limited set of specials should be not to difficult.
But supporting it for more general cases can increase the work to
the work of a large software project.
For example, the set of specials for page 4 of the example should
consist of 2.1, 3.2, 4.1. In this case 2.2 and 3.1 do not harm,
because the values of the same dict key are the same. bit 3.2
adds an additional value in the dict that is not needed. In this
case it might be tolerable.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Wed, May 11, 2011 at 12:44:25PM +0200, Martin Schröder wrote:
> is there a way to switch a font to outline rendering with OTF/fontspec?
>
> I know I can hack this in PDF, but a fontspec feature would be nicer. :-)
Without fontspec, see package `pdfrender'.
Yours sincerely
eX can't delete files. Thus again the
`shell escape' feature is needed. But depending on the
driver the image files must not be deleted. For example,
DVI driver usually only embed the image file name references,
but not the images.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
t)
for encoding.
Additional fill bytes at the end and line breaks may cost some more
bytes.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
ld be written
in TeX^1. But the result would have to be written in temporary
external files and be input as image via \includegraphics.
But I don't see the point of this exercise, you have such
a converter already in a much more efficient programming
language than TeX.
Yours sincerely
Heiko
On Thu, Feb 10, 2011 at 08:07:26PM +, Arash Zeini wrote:
> "! No room for a new \count .
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom
No room for a new `thing'
In short: \usepackage{etex}
Yours sincerely
H
27;t know the internals of xesearch.sty, but do you really need
the meaning \relax? Or it is just the usual side effect of TeX's
\csname?
In \xs@@F@Test you are using:
\expandafter\ifx\csname\xs@String @cs@xs@words\endcsname\relax
Perhaps you can replace it by \ifcsname ...\endcsname?
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
side a group?
Then local macro definition (labels, ...), changed counters, ...
will occupy save positions.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
gt;
> ./a.tex:7: Extra \else.
> \@hyper@@anchor ...g {Ignoring empty anchor}\else
Thanks, will be fixed in 6.82b.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
s
slide, note, overlay and page. In 2011/02/05 v6.82a I have now
implemented some support for class `slides' for options
`pdfpagelabels' and `pageanchor'.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
the software,
than try to get a fixed version or to get your money back.
The file matrix.pdf seems fixable if at least the first entry
of the xref table is fixed:
* Replace "0 n" by "65536 f" in the line
"0003
,Subtype=/Movie,Movie=<...
> l.28 \end{frame}
>
> ?
>
> What am I doing wrong?
Nothing.
Package `multimedia' does not support dvipdfm(x)/XeTeX.
Either pdfTeX or pdfmark based drivers are supported.
dvipdfm(x)/XeTeX is a different class o
very helpful. And thanks to Michiel for only using fontspec.
Analysis: polyglossia/arabic redefines \...@arabic. For destination names
the original version is the better choice, because it is expandable
and generates ASCII digits.
Thus I have fixed hyperref in this sens
g the fonts. But then there is no time left for
analyzing/fixing the problem. If TL 2010 provides
alternatives, then I think it's probably a very easy
and fast job to provide a `more minimalized' example.
Yours sincerely
Heiko Oberdiek
--
S
ng fonts that are
available on TeX Live 2010, please?
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
ne as it
> does in case of section{}, also tried putting lines with labels and still it
> did not work.
Quite unclear about the problem. Probably you are here mixing several
issues, perhaps completetely unrelated to \nameref?
Yours sincerely
Heiko Oberdiek
-
rticle}
\begin{document}
X\textsuperscript{A}{\scriptsize A}{\tiny A}
Normalsize: A
{\Huge
X\textsuperscript{A}{\scriptsize A}{\tiny A}
}
\end{document}
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://t
rsion is done automatically without the need for
manual uses of \texorpdfstring{?}{'}.
Yours sincerely
Heiko Oberdiek
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
;def}
\end{document}
Works without problems with TL 2010 (restricted shell escape).
abc&def.eps is automatically converted to abc&def-eps-converted-to.pdf.
TL 2010 loads package `epstopdf' in `graphics.cfg' and enables
restricted shell escape by default.
Your
ngs ... -sOutputFile=%o %i -c quit"
to
D "rungs ... '-sOutputFile=%o' -f '%i' -c quit"
Unhappily single quotes will not work in Windows, AFAIK.
At least double quotes can/should be used:
D "rungs ... \"-sOutputFile=%o
se,
pdfpagelabels=true,
]
{hyperref}
\hypersetup{
pdftitle={Document Preparation for Classical Languages},
pdfauthor={David J.Perry},
pdfsubject={Creating text in classical, biblical, and medieval studies},
pdfkeywords={Latin, Greek, Hebrew, classics, medieval, biblical,
fonts,
On Sun, Sep 26, 2010 at 08:21:28AM +0530, Shrisha Rao wrote:
> El sep 26, 2010, a las 4:47 a.m., Peter Dyballa escribió:
>
> > The correct Xe(La)TeX logos can be produced with metalogo or hologo (HO =
> > Heiko Oberdiek) packages.
>
> Yes and no, respectively, at lea
1 - 100 of 131 matches
Mail list logo
