Hi,
is there a way to end (flush) footnotes of a chapter before the next
chapters starts?
Please have a look at this double-page spread below, please:
http://werksatz.com/attachments/spread.pdf
Footnote no. 37 should be the first footnote that is printed under the
footnote line of
ISO/IEC 14496-22:2009
Information technology -- Coding of audio-visual objects -- Part 22:
Open Font Format
http://standards.iso.org/ittf/PubliclyAvailableStandards/c052136_ISO_IEC_14496-22_2009(E).zip
From pdf:
NOTE This specification is based on the OpenType®ii font
format
The fonts (linlibertine and gentium) I installed (and which worked) on
my ubuntu minimals don't work any more. I can't see any difference
between the appropriate files on my mac (where they work) and the linux
machine. Maybe somebody can point out the problem based on the message
below -- I
!pdfTeX error: pdftex (file uplr8a.pfb): cannot open Type 1 font file for
readi
ng
== Fatal error occurred, no output PDF file produced!
TeXExec | runtime: 2.115894
What is uplr8a.pfb ?
Is it on your fontpath ?
--
luigi
Thanks for the hint. uplr8... are Palatino fonts, and I have palatino
as the math-font in my typescript.
Copying them from the mac to the linux setup (where they have gone? with
an update? -- my Mac version is old!) did the trick.
Thanks again, Jörg
luigi scarso wrote:
!pdfTeX error: pdftex
Hans Hagen a écrit :
Alain Delmotte wrote:
I have downloaded a great part of the documentation (59 files or so).
But if I understood well, there has been big changes between Mark II
and Mark IV/Lua.
The documentation seems more linked to MkII.
Is mk.pdf the file to use (in conjonction with
Hi,
I've been trying to use the \overrightarrow command within a metapost graphic,
but it doesn't work. Math mode does work, for example \vec works like
expected. Outside of metapost, \overrightarrow works as expected.
To illustrate the problem, I've created the following simple testcase:
Hello all,
For some reason, the snippet below outputs 'ThOMAS' instead of 'THOMAS.'
This seems to be font dependent; at least Adobe Jenson Pro and Adobe
Garamond Pro produce 'Th,' while the other fonts that I've tried produce
'TH', as expected. I don't know whether the bug exists in the fonts
Hello,
I've a little feature request:
It would be nice, to have a command line option like --setvalue x=y or
similar for the context command to define a variable for the job.
Modes are already very nice, but often I need just one value for
conditional compiling a document instead of many binary
Aditya Mahajan wrote:
\let\normaloverrightarrow\overrightarrow
\unexpanded\def\overrightarrow{\normaloverrightarrow}
ok, i made them all unexpandable
-
Hans Hagen | PRAGMA ADE
Derek CORDEIRO wrote:
\usemodule[simplefonts]
Question for wolfgang ... do you enable node mode?
in basemode, it might be that ligatures are loaded after smallcaps (and
base mode is static) and then it's the order of features in the font
that determines what happens,
if so, then maybe we
Derek CORDEIRO wrote:
That does not work for me at all. The following does work with generating
the same ThOMAS
another test:
\definefontfeature[default] [default] [mode=node]
\definefontfeature[smallcaps][smallcaps][mode=node]
\definefontfeature[oldstyle] [oldstyke] [mode=node]
Hans
Barry Schwartz wrote:
Hans Hagen pra...@wxs.nl skribis:
could it be a bug in the font? i.e. a Th ligature showing up in
smallcaps? if so, then simplefonts should disable ligatures in smallcaps
I'm looking at AGaramondPro-Regular in fontforge and it has the lookup
for small caps well above the
On Fri, Sep 18, 2009 at 11:31 PM, Hans Hagen pra...@wxs.nl wrote:
Derek CORDEIRO wrote:
That does not work for me at all. The following does work with generating
the same ThOMAS
another test:
\definefontfeature[default] [default] [mode=node]
Hans Hagen pra...@wxs.nl skribis:
Barry Schwartz wrote:
Hans Hagen pra...@wxs.nl skribis:
could it be a bug in the font? i.e. a Th ligature showing up in
smallcaps? if so, then simplefonts should disable ligatures in smallcaps
I'm looking at AGaramondPro-Regular in fontforge and it
Am 18.09.2009 um 19:57 schrieb Hans Hagen:
Question for wolfgang ... do you enable node mode?
No.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist :
Barry Schwartz wrote:
If base mode uses the traditional TeX mechanism for ligatures, I don't
see any way the font can be blamed.
sure
Hans
-
Hans Hagen | PRAGMA ADE
Hans Hagen pra...@wxs.nl skribis:
Barry Schwartz wrote:
If base mode uses the traditional TeX mechanism for ligatures, I don't
see any way the font can be blamed.
Ant does the same thing, I believe, using the OT tables and heuristics
to run the TeX processor. That's okay, as long as the
Hans Hagen pra...@wxs.nl skribis:
but even then, if a font is not clear about issues, then one can get
unwanted side effects (the frac feature for instance is often quite
bugged and can only be applied selectively)
Yeah, I think trying to be fancy with contextual substitutions is a
bit like
Please tell me this isn't in a FAQ. :) Is there support for ActualText
tags so that searching and extraction will work with OpenType fonts
and Unicode? If so, do discretionary hyphens get treated as 00AD
instead of 002D?
20 matches
Mail list logo
