Would something like this make you happy? That's what I've been using for years.
Put it in your preamble. And of course, change the parindent size to somheting
you like.
\makeatletter
\renewcommand\@makefntext[1]{%
\vspace{2pt}%
\setlength\parindent{-1.8em}%
\setlength\leftskip{1.8em}%
On 5 Jun 2011, at 21:09, Peter Dyballa wrote:
>
> Am 05.06.2011 um 21:54 schrieb Philip TAYLOR (Webmaster, Ret'd):
>
>> So why doesn't it ?!
>
> Phil,
>
> it does! It passes all \special{}s without touching them into the output
> file. Whether you're using the xetex or the xelatex command pl
I don't think I really understand this, but never mind :
I have a solution (TikZ) which I also need for another
part of the project (fitting text to a path), so I'll just go with it !
** Phil.
--
Subscriptions, Archive, and List information, etc.:
Am 05.06.2011 um 21:54 schrieb Philip TAYLOR (Webmaster, Ret'd):
So why doesn't it ?!
Phil,
it does! It passes all \special{}s without touching them into the
output file. Whether you're using the xetex or the xelatex command
plays no role: you have only access to the xetex engine's trans
Peter Dyballa wrote:
Am 05.06.2011 um 21:24 schrieb Philip TAYLOR (Webmaster, Ret'd):
So how is it, I am forced to ask, that an add-on package can achieve
something that the underlying
engine cannot ? This seems very odd to me.
The fontspec package does not use PDF specials which TiKZ/PG
Am 05.06.2011 um 21:24 schrieb Philip TAYLOR (Webmaster, Ret'd):
So how is it, I am forced to ask, that an add-on package can achieve
something that the underlying
engine cannot ? This seems very odd to me.
The fontspec package does not use PDF specials which TiKZ/PGF uses.
That's my sim
Peter Dyballa wrote:
Am 05.06.2011 um 14:06 schrieb Philip TAYLOR (Webmaster, Ret'd):
What am I missing, please ?
Mac OS X's deprecated xdv2pdf.
And yet, Tikz/PGF can achieve transparency using the default driver
(xdvipdfmx (0.7.8)),
as Matthew Skala kindly pointed out and went on to de
Am 05.06.2011 um 14:06 schrieb Philip TAYLOR (Webmaster, Ret'd):
What am I missing, please ?
Mac OS X's deprecated xdv2pdf.
--
Greetings
Pete
Don't force it; get a larger hammer.
– Anthony's Law of Force
By all means, Alessandro : ZIP all the files and
send them direct as an attachment.
Philip Taylor
Alessandro Ceschini wrote:
Sorry Phillip, but I can't find the way to post an attach here.
I can't just copy all the .tex file in a mail, it's just too long!
But, if you don't mind, I coul
Sorry Phillip, but I can't find the way to post an attach here.
I can't just copy all the .tex file in a mail, it's just too long!
But, if you don't mind, I could send it to you via your mail.
Obviously, if your enthusiasm has recovered, of course.
--
Alessandro Cesch
Alessandro Ceschini wrote:
Will the prologue suffice?
Different people differ in their expectations. If I ask someone to
help me, I try to give them all of the information that they will
need in order to (a) replicate the problem, and (b) endeavour to
find a solution. Someone else may think
IIRC, the fontspec manual mentions that font transparency through font
loading commands is only available on Macs because it requires the
xdv2pdf driver.
-Andy
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo
Hi Gareth!
Thank you so much! I will take closer look at this tomorrow. Apparently the
Code2000 font has many drawbacks.
Best regards,
Jargal
-Original Message-
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/06/11 09:53, Жаргал Бадагаров wrote:
> > Hello members,
> >
>
Will the prologue suffice?
\documentclass[a4paper, 12pt, openany, draft]{book}
\usepackage{fontspec}
\defaultfontfeatures{Mapping=tex-text}
\setmainfont{Garamond Premier Pro}
\usepackage{polyglossia}
\setmainlanguage{french}
\setotherlanguages{dutch, english, german, latin, italian, spanish}
\seto
Alessandro Ceschini wrote:
My source is frenchb.ldf!
Please take a look at this piece of code from frenchb.ldf dealing with
footnotes:
OK, two comments.
1) The use of ten inches appears to be as a sentinel, rather than
the actual value intended for real use.
2) When I suggested you post yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/06/11 09:53, Жаргал Бадагаров wrote:
> Hello members,
>
>
> My name is Jargal. I am interested in the Mongolian Vertical Script Support
> in MacOS. I have found a 2005 presentation of XETEX made in Uhan, where it is
> said that Mongolian had
I can't take time to absorb that, but it looks as if it wants to force the
indentation at the start of a footnote to be 1.5em, which ought to be OK
(rather more than I would have, but no matter just now).
Just before the first line of your text (after you've loaded all your
packages and so on)
> To be honest, I wouldn't worry about the \makeatletter nonsense; it
> really
> isn't at the heart of your problem. If you are getting an \hbox that
> is
> overfull
> by over 381pt (5.27"), the numbers have all but disappeared, and the
> text
> appears to be cut, then John Was's suggestion that
Alessandro Ceschini wrote:
I'm sorry, Phillip, the problem is that I don't know much about the
\makeatletter programming environment. I just deal with normal Latex
commands, so that's really Arabic for me. The only thing I can tell you
is I get loads of warning messages like this:
Overfull \hb
That huge overfull \hbox is surely because you have specified 10 inches as
the indentation. Try 10pt instead of 10in (leaving everything else as
given), and see what happens.
John
- Original Message -
From: "Alessandro Ceschini"
To: "Customizing footnote markers"
Sent: 05 June 201
> doesn't seem calculated to encourage further help. Perhaps if you
> were to tell us in what way "it doesn't work", and and/or attach
> a minimal source document that demonstrates the problem, there
> would be a greater probability of someone getting to the root of
> your problem.
I'm sorry, Phi
John Was wrote:
I'm sure '10in' is a mistake - rather 10pt?
And try replacing
\hbox to \parindentFFN {}
with
\hbox to \parindentFFN{\hfill}
Why, John ? An \hbox can be empty, surely ?
(no space after FFN).
Again, why, John ? \parindentFFN is a control word, and
therefore soaks up th
Forgive my bluntness, but
It doesn't work, anyhow.
doesn't seem calculated to encourage further help. Perhaps if you
were to tell us in what way "it doesn't work", and and/or attach
a minimal source document that demonstrates the problem, there
would be a greater probability of someone g
I'm sure '10in' is a mistake - rather 10pt?
And try replacing
\hbox to \parindentFFN {}
with
\hbox to \parindentFFN{\hfill}
(no space after FFN).
I would also replace
\@thefnmark.~#1
with
\@thefnmark.\kern 0.5em #1
Otherwise the ~ will give a variable space after each footnote-cue, wher
So should it look like this:
\makeatletter
\newdimen\parindentFFN
\parindentFFN=10in
\renewcommand \@makefntext [1]%
{%
\leavevmode \hbox to \parindentFFN {}\@thefnmark.~#1%
}
\makeatother
It doesn't work, anyhow.
--
Alessandro Ceschin
I'd be curious to know what kind of a book could support a ten-inch indentation
before the footnote-cue...
John
- Original Message -
From: Philip TAYLOR (Webmaster, Ret'd)
To: Customizing footnote markers
Cc: Alessandro Ceschini
Sent: 05 June 2011 16:21
Subject: Re: [XeTeX
Alessandro Ceschini wrote:
Well, it looks to me as if the expansion of @makefntext tries
to perform an assignment to \parindentFFN (even though
you omitted an explicit assignment operator); surely this is
not what you intended ?
I intended to have an indentation before the footnote marke
> Well, it looks to me as if the expansion of @makefntext tries
> to perform an assignment to \parindentFFN (even though
> you omitted an explicit assignment operator); surely this is
> not what you intended ?
I intended to have an indentation before the footnote marker.
--
Alessandro Ceschini wrote:
As I wrote: "look in frenchb.ldf to find the french settings." The
definition of \@makefntext above is a simple example. Adjust it to
your need.
Since what I'm lacking here is indentation I tried to put together the
following collage by pasting a piece of code
Thank you for your further comments, Mathew :
msk...@ansuz.sooke.bc.ca wrote:
The default driver for XeTeX is xdvipdfmx; you're probably already using
it, so that's most likely not your problem.
Yes, this is a XeTeX-specific question (I need non-TeX fonts), so I am using
the XeTeX default dri
> As I wrote: "look in frenchb.ldf to find the french settings." The
> definition of \@makefntext above is a simple example. Adjust it to
> your need.
Since what I'm lacking here is indentation I tried to put together the
following collage by pasting a piece of code from frenchb.ldf.
\makeatlett
On Sun, 5 Jun 2011, Philip TAYLOR (Webmaster, Ret'd) wrote:
> Thank you for your prompt response, Mathew. In fact, I am using the default
> driver (I am not aware how I might alter this), and was simply relying on it
> to "do the right thing". If you could tell me how to identify the driver, and
Hello members,
My name is Jargal. I am interested in the Mongolian Vertical Script Support in
MacOS. I have found a 2005 presentation of XETEX made in Uhan, where it is said
that Mongolian had not yet obtained a full support of all its features.
Do you know if it has been being developed so fa
msk...@ansuz.sooke.bc.ca wrote:
Transparency depends very much on the output driver and its settings. I
have used it successfully with xdvipdfm, by way of the "opacity" optin in
TikZ; but the resulting output files are version 1.5 PDFs which not every
printer supports. If you're using some ot
On Sun, 5 Jun 2011, Philip TAYLOR (Webmaster, Ret'd) wrote:
> However, experimenting with all possible values from "00" to "FF"
> for the transparency byte seems to have zero effect, in that the
> second element laid down completely obscures whatever lies
> beneath it. What am I missing, please ?
Will Robertson's "/X/?/TEX reference guide/" reads (in part)
color=RRGGBB[TT]
Triple pair of hex values to specify the colour in RGB space, with an
optional
value for the transparency.
However, experimenting with all possible values from "00" to "FF"
for the transparency byte seems to have z
36 matches
Mail list logo
