double quotes to show up correctly in text,
perhaps does more
liga=yes, % Enables ligatures.
itlc=yes, % Activates italic correction.
mark=yes, % Used for positioning diacritical marks (accents, dots, etc.)
relative to base characters.
mkmk=yes, % positions diacritical marks
does more
liga=yes, % Enables ligatures.
itlc=yes, % Activates italic correction.
mark=yes, % Used for positioning diacritical marks (accents, dots, etc.)
relative to base characters.
mkmk=yes, % positions diacritical marks relative to other marks
locl=yes,
ccmp=yes
,
perhaps does more
liga=yes, % Enables ligatures.
itlc=yes, % Activates italic correction.
mark=yes, % Used for positioning diacritical marks (accents, dots, etc.)
relative to base characters.
mkmk=yes, % positions diacritical marks relative to other marks
locl=yes,
ccmp
shape + \framed +
\getshapetext (and several precautions regarding offsets, thicknesses,
spacings, dimensions, box positioning...)
It's not used in this case, but I discovered that \placelocalfootnotes
and \reference \at \in etc... are fully functional with \getshapetext
:-)
The resul
layout
> > output meets already some of the requirements (see comments in the code).
> > Among the ones to still be implemented are:
> >
> > • solid setting (no extra spacing between characters)
> > https://www.w3.org/TR/jlreq/#fig1_8 if no requirement for line-ad
he code).
> > Among the ones to still be implemented are:
> >
> > • solid setting (no extra spacing between characters)
> > https://www.w3.org/TR/jlreq/#fig1_8 if no requirement for line-adjustment
> > https://www.w3.org/TR/jlreq/#term.line-adjustment
> > • al
the Kihon-hanmen (optimizing the code below
> in this regard)
> • positioning and realm of headings
> https://www.w3.org/TR/jlreq/#fig3_1_9 https://www.w3.org/TR/jlreq/#fig3_1_15
> et al, and https://www.w3.org/TR/jlreq/#fig3_1_4
> • positioning of yokugo-ruby https://www.w3.o
] https://www.w3.org/TR/jlreq/#positioning_of_punctuation_marks
*
positioning and realm of headings
https://www.w3.org/TR/jlreq/#fig3_1_9
https://www.w3.org/TR/jlreq/#fig3_1_15 et al, and
https://www.w3.org/TR/jlreq/#fig3_1_4
*
positioning of yokugo-ruby https://www.w3.org/TR
anmen (optimizing the code
below in this regard)
*
positioning and realm of headings
https://www.w3.org/TR/jlreq/#fig3_1_9
https://www.w3.org/TR/jlreq/#fig3_1_15 et al, and
https://www.w3.org/TR/jlreq/#fig3_1_4
*
positioning of yokugo-ruby https://www.w3.org/TR/jlreq/#fig2
the lines to the Kihon-hanmen (optimizing the code below in this
regard)
positioning and realm of headings https://www.w3.org/TR/jlreq/#fig3_1_9
https://www.w3.org/TR/jlreq/#fig3_1_15 et al, and
https://www.w3.org/TR/jlreq/#fig3_1_4
positioning of yokugo-ruby https://www.w3.org/TR/jlreq
\usetikzlibrary[calc, intersections, through, backgrounds, arrows,
shapes.geometric, fadings, decorations.pathreplacing, shadings,
shapes.geometric, patterns, fit, positioning, shapes.symbols, chains]
17 \usemodule[pgfmath]
18 %\usemodule[filter]
19
20
21 \startsection[title={Problemes de
array so when that one is wrong (could be a side effect of some bad
metric in the font file like units, possibly reported in the log) you
can get wrong positioning
Hans
-
Hans Hagen
nted it out. Very
well put nevertheless. But its main argumentative conclusion was the
challenging part rather than cementing/positioning/establishing/ one
Then I thought, heck, let's see if chatgtt is aware of the relatively
recent findings about the printing methods used by Gutenberg and so
fort
Thanks for your reply Pablo. I didn't see it till just now because for
some reason it ended up in my junk folder, along with a number of other
ConTeXt messages. You will probably have seen my reply to the list with
the three solutions, now we have four!
Yep, I know that A4 is the default page
Hi,
I've experimented this morning with the solutions suggested by Wolfgang
and Alan in reply to my post.
The solution is really quite simple as suggested by Wolfgang i.e.
\centerbox{..}. I have applied this to the code and I now have three
different solutions to my initial problem. The Joy
gt; > > thinking that this would be the easiest way to position it where I
> > > wanted. However to position in the centre of the page I would need
> > > to know the size of the combination and use this to calculate the x
> > > and y values for positioning o
the combination and use this to calculate the x
> > and y values for positioning of the layer. I have looked at the
> > Wiki page on image size of combinations but still cant figure out
> > how to do it. Any suggestions on how to go about this or is their a
> > better way?
> >
On 3/16/23 17:59, Keith McKay via ntg-context wrote:
> Hi,
>
> I would like to position a combination of images where the centre of the
> combination coincides with the centre of the text area of a page.
Hi Keith,
I think the following sample might achieve what you want:
\showframe
\setupex
be the easiest way to position it where I wanted.
However to position in the centre of the page I would need to know the
size of the combination and use this to calculate the x and y values
for positioning of the layer. I have looked at the Wiki page on image
size of combinations but still cant
position in the centre of the page I would need to know the size of the
combination and use this to calculate the x and y values for positioning
of the layer. I have looked at the Wiki page on image size of
combinations but still cant figure out how to do it. Any suggestions on
how to go about
ryone,
> > >
> > > I’ve recently had to typeset a document that gave me some headaches
> > > with the floats. The floats where jumping around, appearing in a
> > > different order than in the source file, tables ended up split up at
> > > weird point
ping around, appearing in a
> > different order than in the source file, tables ended up split up
> > at weird points, some positioning keys had not the intended effect
> > (e.g. top), «page» moved the float more than seemed necessary for
> > me... I know, TeX’s float positioning
1 or a float appearing before it
is placed in the source (with the exception of the top issue), then
you've probably found a bug.
> some positioning keys had not the intended effect (e.g. top)
I've had mixed results with some of the positioning keys too, but "top"
should g
positioning keys had not the intended effect (e.g. top), «page»
moved the float more than seemed necessary for me... I know, TeX’s float
positioning algorithm should be rather reliable and stable, and it’s
quite possible that I’m messing things up in my setups–especially since
my source files
it up at weird points, some
> positioning keys had not the intended effect (e.g. top), «page» moved the
> float more than seemed necessary for me... I know, TeX’s float positioning
> algorithm should be rather reliable and stable, and it’s quite possible that
> I’m messing things up in my
Hi everyone,
I've recently had to typeset a document that gave me some headaches with the
floats. The floats where jumping around, appearing in a different order than in
the source file, tables ended up split up at weird points, some positioning
keys had not the intended effect (e.g
- subprescript
- prime
and each comes with spacing and positioning properties cf opentype and
our own additions for the pre/prime)
there is some magick wrt subscripts as these often are indices (which is
why we have for instance ^^^ and ___ too)
What you can do is:
$\primed{a}^2$
which basically makes
zlibrary[intersections]
\usetikzlibrary[patterns]
\usetikzlibrary[bending]
\usetikzlibrary[arrows.meta]
\usetikzlibrary[shapes.geometric]
\usetikzlibrary[plotmarks]
\usetikzlibrary[shapes]
\usetikzlibrary[trees]
\usetikzlibrary[animations]
\usetikzlibrary[quotes]
\useti
omposition
cpsp Capital Spacing
dlig Discretionary Ligatures
frac Fractions
hlig Historical Ligatures
kern Kerning
liga Standard Ligatures
lnum Lining Figures
mark Mark Positioning
mkmk Mark to Mark Positioning
onum Oldstyle Figures
pnum Proportional Figures
salt
tures
frac Fractions
hlig Historical Ligatures
kern Kerning
liga Standard Ligatures
lnum Lining Figures
mark Mark Positioning
mkmk Mark to Mark Positioning
onum Oldstyle Figures
pnum Proportional Figures
salt Stylistic Alternates
smcp Small Capitals
ss01 Stylistic
ore alien stuff to m-oldmath in due time
>
> We paid a lot of attention to details of positioning, sizing and spacing
> of glyphs. We do have some documents in the making that describe this
> (some are in the ontarget namespace) and the second half of this year we
> use for w
upport for \over simply because it is too fragile wrt
spacing (one can \usemodule[oldmath] to get it back
-- we might move some more alien stuff to m-oldmath in due time
We paid a lot of attention to details of positioning, sizing and spacing
of glyphs. We do have some documents in the making tha
t; > 1. I want the baseline grid to evenly (vertically) divide the text
>> > area, but my code produces a smaller height of the first line and an
>> > additional space at the bottom.
>>
>> You did not set footerdistance to zero. So, that takes up some space.
.
> 2. The number of columns is 21.5, that is the first column
is 0.5 units
> wide and the rest are 1 unit wide.
I believe that columns has to be an integer. Why do you want
fractional columns? Columns are useful because you can say:
\setlayer[name][line=2,column=3]{
t are 1 unit wide.
>
> I believe that columns has to be an integer. Why do you want fractional
> columns? Columns are useful because you can say:
>
> \setlayer[name][line=2,column=3]{}
>
> for absolute positioning of layers. So, you can always use:
>
> \setlayer[name][line=2,co
st are 1 unit wide.
I believe that columns has to be an integer. Why do you want fractional
columns? Columns are useful because you can say:
\setlayer[name][line=2,column=3]{....}
for absolute positioning of layers. So, you can always use:
\setlayer[name][line=2,column=3,x=0.5\measured{base}]{..
>
> Dear list,
>
> Years ago I stumbled upon the work of Jean-Luc Doumont.
He typesets all his documents using TeX, although his modified Version
> called Quantum. The whole idea of his fascinating approach is that the page
> is quantized in 2 dimensions and that all positioni
k, "Theorems, Maps, and
Trees" all paragraphs are typeset as complete rectangles! See a sample here:
https://www.principiae.be/book/pdfs/TM&Th-samplepages.pdf
> The whole idea of his fascinating approach is that the page is quantized in 2
> dimensions and that all positionin
Dear list,
Years ago I stumbled upon the work of Jean-Luc Doumont. He typesets all his
documents using TeX, although his modified Version called Quantum. The
whole idea of his fascinating approach is that the page is quantized in 2
dimensions and that all positioning, even graphical elements
the test suite: you can define a kern
pair positioning feature than you enable for just that font
Thanks Hans, here's the working MWE:
---
\mainlanguage[it]
% from http://www.pragma-ade.com/context/latest/cont-tst.zip
% file doc
On 4/5/2022 1:45 PM, mf via ntg-context wrote:
It's defined in typo-fkr.lua, but I can't understand what parameters to
pass and whether it's the right macro. It looks like it's not.
look at the extension examples in the test suite: you can define a kern
pair positioning fea
On Tuesday, March 29, 2022 4:18 AM Michael Urban via ntg-context wrote:
> Is there a simple way to accomplish this?
Aside from the other solution using makeup, a simpler way might be to just use
the 'page' option for positioning the float. The following MWE achieves the
same result
index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
\defineprocessor[special][style=italic]
In the periti case it is the \it command that clearly interferes
with correct alphabetic positioning in the sub entry list.
Placing +periti in the key does not overcome that problem.
In the ‘special ki
;> text after.
>>
>> text before \index{animals+‘special kinds’} text after. Or alternatively,
>> \index[animals+special]{animals+‘special kinds’}
>>
>> The setup for my register is a pretty standard one. The processor is not for
>> the 'periti' case ab
pregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
\defineprocessor[special][style=italic]
In the periti case it is the \it command that clearly interferes
with correct alphabetic positioning in the sub entry list. Placing
+periti in the key does not overcome that problem.
\setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
>
> \defineprocessor[special][style=italic]
>
> In the periti case it is the \it command that clearly interferes with
> correct alphabetic positioning in the sub entry list. Placing +periti in
> the key does not overco
processor is not
for the 'periti' case above but I use it for book titles.
\setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
\defineprocessor[special][style=italic]
In the periti case it is the \it command that clearly interferes with
correct alphabetic positioning in the
Hello again List,
Now I’m making diagrams using MetaFun. The MetaFun manual describes an “origin”
option for positioning textext’s and label’s on the baseline. However, this
dose not appear to be happening with the code in the manual (below). In fact,
the diagram in the manual dose not show
: \immediate\csname
> openout\endcsname\pgfutil@auxout\jobname.pgf\relax
> tex/generic/pgf/utilities/pgfutil-plain.def:
> \pgfutil@IfFileExists{\jobname.pgf}{\input \jobname.pgf\relax}{}
> tex/generic/pgf/utilities/pgfutil-plain.def: \immediate\csname
> openout\endcsname\pgfutil@
\pgfutil@IfFileExists{\jobname.pgf}{\input \jobname.pgf\relax}{}
tex/generic/pgf/utilities/pgfutil-plain.def: \immediate\csname
openout\endcsname\pgfutil@auxout\jobname.pgf
The file handle \pgfutil@auxout is used in the macro \pgfutil@writetoaux which
gets used in the driver files to write absolute pos
#x27; are wrong in English, too.
sure, i know that, but i was more refering to the fact that the visual
rendering (even publisher specs) became 'use the english ones', shape
and location wise (high/low) .. the dutch seem to care less about it
than germans, french, czech etc (same
with somewhat weird
properties, parsing preferably in a robust way, positioning in a
superscript like position (before or after a script), i fpossible
intercepting interference etc. And ... all that is resembled in unicode
math as well as all these math fonts out there.
But it is not the way i want
Thanks Hans!
On Sun, 12 Sept 2021 at 19:02, Hans Hagen wrote:
> On 9/12/2021 6:54 PM, Sylvain Hubert via ntg-context wrote:
> > Dear List,
> >
> > The following code draws a circle at the center of the page, ignoring
> > the "shifted" part.
> >
> > \startuniqueMPgraphic{concept}
> > draw fullcir
On 9/12/2021 6:54 PM, Sylvain Hubert via ntg-context wrote:
Dear List,
The following code draws a circle at the center of the page, ignoring
the "shifted" part.
\startuniqueMPgraphic{concept}
draw fullcircle scaled 1cm shifted (10cm,10cm);
\stopuniqueMPgraphic
\defineoverlay[concept][\uniqueM
Dear List,
The following code draws a circle at the center of the page, ignoring the
"shifted" part.
\startuniqueMPgraphic{concept}
draw fullcircle scaled 1cm shifted (10cm,10cm);
\stopuniqueMPgraphic
\defineoverlay[concept][\uniqueMPgraphic{concept}]
\setupbackgrounds[page][background=concept]
\
o big. For big documents, would it
make sense to simply read and write zipped tuc files?
normally they are not that large but when you enable for instance
mechanisms that need positioning they can grow large .. zipping makes
for less bytes but still large files and the overhead for serialization
s
early in
\MKII\ we had a positioning mechanism available. At that time we had
\DVI\ output and specials were used to track positions. A script
calculated the positions that were then fed back into the second run.
Later Taco wrote \DVIPOS\ which sped up the analysis between runs. When
\PDFTEX
not bad considering that a lots of features are used: thousands of mp
> images, a bunch of external images, many fonts, plenty of buffers,
> positioning, color, hyperlinks, backgrounds etc. This document uses plenty of
> lua so that is why we gain a lot with luajittex.
>
> In lmtx
used: thousands of
mp images, a bunch of external images, many fonts, plenty of buffers,
positioning, color, hyperlinks, backgrounds etc. This document uses
plenty of lua so that is why we gain a lot with luajittex.
In lmtx where we dropped jit and have a less performing backend we
expect to
l? Because it seems it's there.
depends on what you consider (non) hdpi ... the positioning of glyphs
depends on font scale, rounding of stems and such (hints in fonts but
these get less relevant with high res displays), caching, inter glyph
corrections (that pdftex/luatex/...) put in the
as well? Because it seems it's there.
>
> depends on what you consider (non) hdpi ... the positioning of glyphs
> depends on font scale, rounding of stems and such (hints in fonts but
> these get less relevant with high res displays), caching, inter glyph
> corrections (that pdft
On 1/8/2021 12:39 AM, Vedran Miletić wrote:
It's whatever ConTeXt standalone has. I don't have any extra Lua installed:
--credits should mention the lua version
Should I see it on non-HiDPI as well? Because it seems it's there.
depends on what you consider (non) hdpi ...
Dear list,
I have a problem with LMTX when I try to place a tikz drawing at an absolute
location on the page. Here is a minimal failing example.
===
\usemodule[tikz]
\starttext
\starttikzpicture[remember picture, overlay]
\draw (current page.center) circle [radius=20mm];
\sto
authors. The titles
will be simply 'Foreword' and 'Preface', obviously.
*Foreword Author name*
*Preface Author name*
I am using \hskip 1cm to separate the authors' names from either of
those two words. But this does not give me the kind of exact
positionin
ither of
those two words. But this does not give me the kind of exact positioning
I need to get the two author names directly underneath each other in the
list. I have tried various alternatives to \hskip, but none of them can
give me the correct proportional distance. The distance is obvi
this does not give me the kind of exact positioning
I need to get the two author names directly underneath each other in the
list. I have tried various alternatives to \hskip, but none of them can
give me the correct proportional distance. The distance is obviously
being controlled by the fact that '
ich also explains an alternative
method to set title of chapters (toward the end of that chapter), which is
useful if you need absolute positioning.
Aditya
___
If your question is of interest to others as well, please
\stopoverlay}
>>
>> \starttext
>> \startchapter[title={This is a test}]
>> \stopchapter
>>
>> \stoptext
>>
>> Overlays don't allow tuning the location...for that you need layers. See the
>> chapter on ornaments in the details manual, w
n't allow tuning the location...for that you need layers. See the
chapter on ornaments in the details manual, which also explains an alternative
method to set title of chapters (toward the end of that chapter), which is
useful if you need abso
Thanks Aditya. The 'quick and simple' explanation below helps me to
grasp some concepts I had not been clear about earlier. While you say
that overlays 'don't allow tuning' for positioning, is this only in
terms of absolute positioning?
It would be so helpful if we co
{This is a test}]
\stopchapter
\stoptext
Overlays don't allow tuning the location...for that you need layers. See the
chapter on ornaments in the details manual, which also explains an alternative
method to set title of chapters (toward the e
What is the simplest way to build a page based on positioning of external
images? Some of these images are page-sized (so take up an entire page, though
I might want to overlay some other text boxes and MP graphics). I’ve been
trying to find a good explanation/introduction into layers (which I
Gerben Wierda schrieb am 17.05.2020 um 16:52:
What is the simplest way to build a page based on positioning of external
images? Some of these images are page-sized (so take up an entire page, though
I might want to overlay some other text boxes and MP graphics). I’ve been
trying to find a
manual) and Ralph Hancock, is used for mark
positioning by a number of Hebrew fonts. Its guidelines govern their glyph
classes and chaining substitution rules. The fonts I know of that
explicitly implement it are SBL Hebrew, Ezra SIL, Keter YG, Keter Aram
Tsova.
On Tue, Apr 28, 2020 at 2:21 PM Hans
On Thu, 9 Apr 2020 20:44:16 +0200
Geert Dobbels wrote:
> Hello,
>
> Maybe I did not understand the problem, but doesn't the code below
> give you the expected result?:
Hmm, unfortunately no. Using [top,force] just causes context to
break the text flow at the place where the image is specified.
Hello,
Maybe I did not understand the problem, but doesn't the code below give
you the expected result?:
\setupexternalfigures[location={local,default}]
\starttext
\dorecurse{3}{\input{knuth}}
\placefigure[force]{cow}{\externalfigure[cow][width=150mm]}
\input{knuth}
\placefigure[force,page]{
On Mon, 6 Apr 2020 16:53:33 +0200
Tomas Hala wrote:
> You can try the work around below, it is based on computation of
> additional measures for special instance of figure.
Thank you, this is helpful indeed, at least as a workaround.
--
Regards,
Alexey Kryukov
Moscow State University
Faculty
Hi Alexey,
# Yes, I tried leftpage/rightpage: this removes the blank page, but may
# cause images to be reordered (so that e. g. 3 goes before 2), which is
# completely unacceptable IMO.
Yes, you are right.
But -- I do not know why -- your code you attached gives on my computer (TL2019)
the 1-3-
Hi Tomas,
thank you for your answer.
Yes, I tried leftpage/rightpage: this removes the blank page, but may
cause images to be reordered (so that e. g. 3 goes before 2), which is
completely unacceptable IMO.
Also, this doesn't help with the text flow at the page where the first
image is positione
Hi Alexey,
I do not how free are you in decision where figures should be located
but I tried with "leftpage" and "rightpage" instead of "page" and
it seems to be ok.
\placefigure[rightpage]{one more cow}{\externalfigure[cow][width=150mm]}
\placefigure[leftpage]{cow again}{\externalfigure[cow][wid
Hi all,
Suppose I have the following document:
\setupexternalfigures[location={local,default}]
\starttext
\dorecurse{3}{\input{knuth}}
\placefigure[top]{cow}{\externalfigure[cow][width=150mm]}
\input{knuth}
\placefigure[page]{one more cow}{\externalfigure[cow][width=150mm]}
\placefigure[page]{co
gt;
> \stoptext
>
> does not show the historic ligature in « st » and in « ct »: how can I get
> them?
For these your font needs the hlig feature, which Lucida doesn't seem to have.
$ otfinfo -f "$(mtxrun --find-file LucidaBrightOT.otf)"
liga Standard Ligatures
mark
rate overlay to better control the positioning. Perhaps a bit
> overthought, but it works for me ...
Here’s my approach. Right/left stuff and placement is good, but I get always
the extra contents of the previous chapter, i.e. “Another Fancy Story” gets the
subtitle/quote from “My Fancy Story
rate overlay to better control the positioning. Perhaps a bit
> overthought, but it works for me …
Thank you, looks interesting. I’ll try to adapt that before=\directsetup
approach to my project.
Best, Hraban
__
in a separate overlay to better control the positioning. Perhaps
a bit overthought, but it works for me ...
\setupheadertexts [][{\it\getmarking[section]}]
[{\it\getmarking[chapter]}][]
\startsetups section:epigraph
\doifelsebuffer{SectionEpigraph}
{\getbu
brings in creating a new union. The code is from Denis Roegel,
who quickly responded when I was unable to piece together a working
example from his 2005 TUGboat article:
https://www.tug.org/TUGboat/tb26-1/tb82roegel.pdf
I've resorted to layers with explicit positioning for now, as wel
gt;>
>>
>>> On Aug 21, 2019, at 9:25 PM, Jon Wong >> <mailto:jhannw...@gmail.com>> wrote:
>>>
>>> Hi all,
>>>
>>> Sorry, my solution didn’t work.
>>>
>>> My purpose of using \startnarrower is to have some par
ext inside
>> the \framed. Unfortunately, it seems \framed doesn’t take paragraphs.
>>
>> \startframedtext doesn’t have as many border options as \framed.
>>
>> Should I use overlays? Or layers? It seems layers require absolutely
>> positioning, and
amed.
>
> Should I use overlays? Or layers? It seems layers require absolutely
> positioning, and can’t be logically contained inside a \startnarrower?
>
> Regards
> Jon
>
>
>> On Aug 21, 2019, at 8:53 PM, Jon Wong wrote:
>>
>> Hi all,
>>
>
seems layers require absolutely
positioning, and can’t be logically contained inside a \startnarrower?
Regards
Jon
> On Aug 21, 2019, at 8:53 PM, Jon Wong wrote:
>
> Hi all,
>
> I got some progress!
>
> \setupnarrower[left=2cm, right=2cm] % what does middle do, actua
; 12 by default. Use the "ampersand replacement" option.
> >>
> >> \usemodule[tikz]
> >> \usetikzlibrary[matrix,decorations.pathreplacing, calc, positioning,fit]
> >> \starttext
> >>
> >> \starttikzpicture[>=stealth,thick,baseli
alignment character but has catcode
>> 12 by default. Use the "ampersand replacement" option.
>>
>> \usemodule[tikz]
>> \usetikzlibrary[matrix,decorations.pathreplacing, calc, positioning,fit]
>> \starttext
>>
>> \starttikzpicture[>=stealth,th
t; \usetikzlibrary[matrix,decorations.pathreplacing, calc, positioning,fit]
> \starttext
>
> \starttikzpicture[>=stealth,thick,baseline,
> every right delimiter/.append style={name=rd},
> ]
> \matrix [matrix of math nodes,
> left delimiter=(,
> right delimiter=),
In ConTeXt the ampersand is not an alignment character but has catcode
12 by default. Use the "ampersand replacement" option.
\usemodule[tikz]
\usetikzlibrary[matrix,decorations.pathreplacing, calc, positioning,fit]
\starttext
\starttikzpicture[>=stealth,thick,baseline,
every ri
Hi,
If I compile the following code, the result is not the one expected.
\usemodule[tikz]
\usetikzlibrary[matrix,decorations.pathreplacing, calc, positioning,fit]
\starttext
\starttikzpicture[>=stealth,thick,baseline,
every right delimiter/.append style={name=rd},
]
\matrix [matrix of math no
only use one core
- the 30 min on linux is probably due to swapping
- the 8 gig in general is a side effect of the way this font is using
pair positioning (half a billion pairs due to classes where most pairs
are dummies)
The font files are here:
http://tug.org/~hvoss/Sparks-Bar-Medium.otf
V integer value: 91 <-> 0 in font
descriptor dictionary.
yes, but most of these are bogus and heuristically derived (could be the
subset or whole font) and quite certainly not used in rendering
(positioning happens at the pdf level)
we'll see what magic taco has embrained ...
right from the start and one has to keep adapting ...
> (scaling, positioning, decoupled representations, colors) ... a bit of a
> gamble
Many thanks for your reply, Hans.
I find suprising that /Rect entriess aren’t calculated the same way when
no dimension is specified.
, positioning, decoupled representations, colors) ... a bit of a
gamble
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69
her values than the ones besides opbd, the
values for optical bounds aren’t reliable for accurate glyph
positioning. Sorry, but otherwise there is no need for optical margins
in OpenType (standard protrusion would be all that is needed).
Kerning might be selectively applied, such as in:
\st
1 - 100 of 459 matches
Mail list logo
