How do I make the first one have the same exact
> formtating as the real footnote?
Footnotes apply the \tx style to the number in the running text and to
get the same text size with \high you need \tx before the argument.
Another solution is to create your own \high command where you set the
text s
to superscript text, but if
you compile this, you can see the first "1" and second "1" have entirely
different formatting. How do I make the first one have the same exact
formtating as the real footnote?
Footnotes apply the \tx style to the number in the running text and t
OWcell
\name{h} \location{3,5} \shape{76} \text{$a$ is equal \\ to $b$}
\connection[bt]{f}
\stopFLOWcell
\startFLOWcell
\name{f} \location{2,6} \shape{loop} \text{stop}
\stopFLOWcell
\stopFLOWchart
\placefigure
[here][fig:bigger]
{Which is bigger?}
cted macro:\triggergroupedcommand {\setsmallbodyfont \tf }
and
\tx=protected macro:\currentxfontsize \plusone \ifmmode \scriptstyle
\orelse \ifconditional \c_font_inherit_scale \font_scale_inherit_x
\else \font_scale_defined_x \fi \al ways\let \tx \txx
Thus in contrast \tx and \txx do respect the current sty
Calling "\bf\tfa TEXT" for example leaves the TEXT not in bold because \tfa
does not respect the current style. As does \small, etc.
Shown by looking at the meaning of for example \small:
\small=protected macro:\triggergroupedcommand {\setsmallbodyfont \tf }
and
\tx=prote
to work, but does not adapt to \quotation{normal}
\type{\footnote} style/format customizations
\footnote[e]{E E E E}%
\high{\tx{,}}
\note[a]
\stoptext
It would be great if there were a command that treated a (some command like)
\note as a \footnote-equivalent command for typesetting purposes
ed in
> modern explorative and daring math thesis. When symbols are
> really used, and
> we have proof of that, it should be possible to get them un
> \UNICODE, just
> like all these emoji. We welcome input and as an example of
> currently faked
> symbol
of currently faked
>symbols we added some to the distribution as easter eggs. One example:
>
>Mikael got contacted by a stressed student working on a thesis on
>probability. This student needed to typeset the characteristic function of
> a
>random variable \i
math]
\startformula
E[\ee^{\ii tX}] = \widerandomhat{f_{X}}(t)\mtp{,}
E[\ee^{\ii t(X_1+X_2)}] = \widerandomhat{f_{X_1} \ast
f_{X_2}}(t)\mtp{.}
\stopformula
Naturally, it is automatically scaled, just like the ordinary wide hat
\startformula
\widehat{a+b+c+d+e+f}
On 10/21/2022 12:59 AM, Leah Neukirchen via ntg-context wrote:
Hi,
playing around with \definebodyfontenvironment with latest LMTX,
I found this possibly buggy behavior:
\definebodyfontenvironment[12pt][small=6pt] % x=6pt works here
\setupbodyfont[12pt]
\starttext
normal {\tx tx} {\small small
On 10/21/22 00:59, Leah Neukirchen via ntg-context wrote:
> Hi,
>
> playing around with \definebodyfontenvironment with latest LMTX,
> I found this possibly buggy behavior:
>
> \definebodyfontenvironment[12pt][small=6pt] % x=6pt works here
> \setupbodyfont[12pt]
> \st
Hi,
playing around with \definebodyfontenvironment with latest LMTX,
I found this possibly buggy behavior:
\definebodyfontenvironment[12pt][small=6pt] % x=6pt works here
\setupbodyfont[12pt]
\starttext
normal {\tx tx} {\small small}
\stoptext
With \definebodyfontenvironment[12pt][x=6pt] I can
there are platform changes). She's also working on cmake based
installation helpers.
One of the things we did was pruning the fonts that are part of the
installation. With a few exceptions the type one fonts were dropped,
which is most noticeable for math. There is no need for px and tx fonts
On 7/27/2022 7:03 AM, Aditya Mahajan via ntg-context wrote:
Very nice presentation! Lots of new features to play with.
latest upload has eperimental x scaling (as we have with text \tx \txx
whuch can come in handy when one needs to squeeze some math into some place
\usemodule[article-basic
as attached
>> file)
>>
>>> Le 6 janv. 2022 à 20:00, Hans Hagen via ntg-context a
>>> écrit :
>>>
>>> Hi,
>>>
>>> Maybe this is of interest to critical users:
>>>
>>> \setupsynchronize [paralleltext] [col
On 1/6/2022 10:36 PM, Henning Hraban Ramm via ntg-context wrote:
Am 06.01.22 um 20:00 schrieb Hans Hagen via ntg-context:
Hi,
Maybe this is of interest to critical users:
\setupsynchronize [paralleltext] [color=darkblue]
% \setupsynchronize [paralleltext] [style=\tx,color=darkred
On 1/6/2022 10:36 PM, Henning Hraban Ramm via ntg-context wrote:
Am 06.01.22 um 20:00 schrieb Hans Hagen via ntg-context:
Hi,
Maybe this is of interest to critical users:
\setupsynchronize [paralleltext] [color=darkblue]
% \setupsynchronize [paralleltext] [style=\tx,color=darkred
aralleltext] [color=darkblue]
>> % \setupsynchronize [paralleltext] [style=\tx,color=darkred]
>> % \setupsynchronize [paralleltext] [style=\txx,color=darkgreen]
>>
>> \starttext
>>
>> \dorecurse{10}{%
>> \paralleltext
>> {[een allereerste zinnetje
Am 06.01.22 um 20:00 schrieb Hans Hagen via ntg-context:
Hi,
Maybe this is of interest to critical users:
\setupsynchronize [paralleltext] [color=darkblue]
% \setupsynchronize [paralleltext] [style=\tx,color=darkred]
% \setupsynchronize [paralleltext] [style=\txx,color=darkgreen]
I played
his is of interest to critical users:
>
> \setupsynchronize [paralleltext] [color=darkblue]
> % \setupsynchronize [paralleltext] [style=\tx,color=darkred]
> % \setupsynchronize [paralleltext] [style=\txx,color=darkgreen]
>
> \starttext
>
> \dorecurse{10}{%
>\par
Hi,
Maybe this is of interest to critical users:
\setupsynchronize [paralleltext] [color=darkblue]
% \setupsynchronize [paralleltext] [style=\tx,color=darkred]
% \setupsynchronize [paralleltext] [style=\txx,color=darkgreen]
\starttext
\dorecurse{10}{%
\paralleltext
{[een
Another problem. Maybe that's related?
Running the file with the --luatex flag gives me this error message:
tx-context | redirect luametatex -> luatex: luatex --luaonly
"C:/context/tex/texmf-win64/bin/mtxrun.lua" --script mtx-context --luatex debug
--redirected
mtxrun
ollowing in order to obtain
> > a line plot of the values in the 'data.csv' file? Also is it possible to
> > have the 'labels' be the identical for all points in a given list?
> >
> > \startMPcode
> >
> >draw lmt_axis [
> >
> >
in a given list?
\startMPcode
draw lmt_axis [
sx = 2mm, sy = 2mm,
nx = 80, ny = 40,
tx = 15, ty = 15,
list = {
[
connect = true,
color = "darkblue",
close = true,
, sy = 2mm,
nx = 80, ny = 40,
tx = 15, ty = 15,
list = {
[
connect = true,
color = "darkblue",
close = true,
points = {data.csv},
option results in:
╰─► context --autopdf test.tex
lua error : function call:
...TX/tex/texmf-context/scripts/context/lua/mtx-context.lua:488:
attempt to call a nil value (global 'filenewsuffix')
Without autopdf things work as expected.
ok. new upload
(the installer for windows arm64 should now
On 8/30/2021 7:27 PM, Rik Kabel via ntg-context wrote:
The corrected upload (2021.08.30 16:23) still has an issue. The
--autopdf option results in:
╰─► context --autopdf test.tex
lua error : function call:
...TX/tex/texmf-context/scripts/context/lua/mtx-context.lua:488: attempt
to call a nil
The corrected upload (2021.08.30 16:23) still has an issue. The
--autopdf option results in:
╰─► context --autopdf test.tex
lua error : function call:
...TX/tex/texmf-context/scripts/context/lua/mtx-context.lua:488: attempt
to call a nil value (global 'filenewsuffix')
Without autopdf things
>> API:
>>
>> $ context --forcecld --permitloadlib testlabel.lua
>> ...
>> fatal lua error:
>> registered function call [1542]:
>> ...tx/tex/texmf-context/tex/context/base/mkiv/l-package.lua:348: error
>> loading module 'lpeglabel' from file './lpeglabel.
$ cat testlabel.lua
> require("lpeglabel")
>
> The ConTeXt binary cannot load the library because it lacks certain Lua
> API:
>
> $ context --forcecld --permitloadlib testlabel.lua
> ...
> fatal lua error:
> registered function call [1542]:
> ...tx/tex/texmf-c
ks certain Lua API:
$ context --forcecld --permitloadlib testlabel.lua
...
fatal lua error:
registered function call [1542]:
...tx/tex/texmf-context/tex/context/base/mkiv/l-package.lua:348: error
loading module 'lpeglabel' from file './lpeglabel.so':
./lpeglabel.so: undefined symbol: lua_gettop
...
for
not supporting it is sound. It sucks because end users don't care about
such technical minutiae and can't readily unravel such font discrepancy
issues when encountered.
TX
___
If your question is of interest to others
like:
test.tex
\startluacode
package.cpath = package.cpath .. ";d:/Lukas/Lua/54/?.dll"
require "MyLib"
\stopluacode
But I'm still getting errors like:
"
...
token call, execute:
...TX/tex/texmf-context/tex/context/base/mkiv/l-sandbox.lua:180: m
}} {
\startalignment[middle]
\darkblue \tx \structurelistuservariable{author}
\stopalignment
}
\stopsetups
\setuplist[chapter][after=\setups{MySectionTocEntry}]
Julian
On 9/2/21 9:02 pm, mf wrote:
Il 09/02/21 10:49, jbf ha scritto:
I wonder if someone can assist me with the final
Anyway, here is an alternative:
\startsetups[MySectionTocEntry]
\doifsomething{\structurelistuservariable{author}} {
\startalignment[middle]
\darkblue \tx \structurelistuservariable{author}
\stopalignment
}
\stopsetups
\setuplist[chapter][after=\setups
ed testing and discovered what is certainly a
bug. Here’s a new example:
#
# \setbreakpoints [compound]
#
# \definelinenumbering
#[original]
#[style=\tx\ss,distance=-1ex,step=5,location=inleft,start=10,color=darkred]
#
# \definelinenumbering
# [translation]
#[style=\tx\ss,distance=-1e
’s bonus
question. But I have continued testing and discovered what is certainly a bug.
Here’s a new example:
\setbreakpoints [compound]
\definelinenumbering
[original]
[style=\tx\ss,distance=-1ex,step=5,location=inleft,start=10,color=darkred]
\definelinenumbering
[translation]
[sty
but using
\switchtobodyfont[small] instead of \tfx.
\tf.. \bf.., etc. only change the text font; \switchtobodyfont changes
the entire font family, including math.
Only \tx and \txx (and the combinations \tfx etc.) ignore math.
\starttext
xxx \m{xxx}
{\tfc xxx \m{xxx}}
{\tfx xxx \m{xxx
, and
% so the result must be converted to a string and truncated in lua.
\startluacode
userdata = userdata or {}
userdata.fontsize = function ()
local fs
fs = font.getfont(font.current()).specification.size
fs = tostring(fs/2^16):gsub("%.?0+$","") .. "pt"
{change}{\inmargin{\tx #1}{\red
#2\par}}}
\def\ChangeD#1#2{\change{#1+#2}\doifmode{change}{\inmargin{\tx #1}{\red
#2\par}}}
\starttext
\ChangeV{V. 1.0}{Fertig!}
\input knuth
\ChangeD{2018-12-22}{Fertig!}
\ChangeD{2018-12-23}{Letzter Fehler beseitigt.}
\input knuth
\ChangeD{2018-12-23
lized that while scaling down seems broken,
> > scaling up works as expected:
> \tx (or \tfx, \bfx etc.) and \txx are ignored in some cases unlike the
> other size switches (\tfa etc.).
Out of curiosity, why
User 19087 schrieb am 16.01.19 um 21:56:
I'm having trouble scaling down symbols and emojis. For a while I
assumed these don't scale with the current font size. Then I scoured
the mailing list and realized that while scaling down seems broken,
scaling up works as expected:
\tx (or \tfx, \bfx
in a more modern way.
%D
%D \startbuffer
%D \basegrid
%D [nx=8,ny=5,
%Ddx=.5,dy=.25,
%Dunit=cm,scale=2,factor=1,
%Doffset=1ex,xstep=2,ystep=1,
%Dalign=middle,style=\tt\tx]
%D \stopbuffer
%D
%D \typebuffer
%D
%D \placefigure
%D {An example of a grid.}
%D {\getbuffer}
\startuseM
Hi,
On 27 August 2017 at 19:24, Pablo Rodriguez wrote:
> Dear Mojca,
>
> [I beg your pardon, if you aren’t the maintainer of the ConTeXt Suite
> distribution. In that case I address this message to whom it might
> concern :-).]
>
> After reading some messages about PDF/A and PDF/X, I remembered
=3] TCP\eTD \bTD[nc=3] UDP
\eTD \eTR
\bTR \bTD Vermittlungsschicht \eTD \bTD[nc=3] IPv4\eTD \bTD[nc=3] IPv6
\eTD \eTR
\bTR \bTD Sicherungsschicht\eTD \bTD[nc=6] Ethernet \eTD \eTR
\bTR \bTD Bitübertragungsschicht \eTD \bTD[nc=2] 100BASE-TX\eTD
\bTD[nc=2] 100BASE-T\eTD \bTD[nc=2] 1000BASE-T \eTD
\bTR \bTD Vermittlungsschicht \eTD \bTD[nc=3] IPv4\eTD \bTD[nc=3] IPv6
\eTD \eTR
\bTR \bTD Sicherungsschicht\eTD \bTD[nc=6] Ethernet \eTD \eTR
\bTR \bTD Bitübertragungsschicht \eTD \bTD[nc=2] 100BASE-TX\eTD
\bTD[nc=2] 100BASE-T\eTD \bTD[nc=2] 1000BASE-T \eTD \eTR
\eTABLE
\stoptext
If I
\NC[nx=3] TCP \NC[nx=3] UDP \NR
\NC Vermittlungsschicht\NC[nx=3] IPv4 \NC[nx=3] IPv6 \NR
\NC Sicherungsschicht \NC[nx=6] Ethernet \NR
\stopXTABLEbody
\startXTABLEfoot
\NC Bitübertragungsschicht \NC[nx=2] 100BASE-TX \NC[nx=2] 100BASE-T
\NC[nx=2] 1000BASE-T \NR
Bitübertragungsschicht \NC[nx=2] 100BASE-TX \NC[nx=2] 100BASE-T \NC[nx=2]
1000BASE-T \NR
\stopxtable
\stoptext
On 03/08/2017 04:39 PM, Henri Menke wrote:
> I quickly came up with something myself. Unfortunately, it involves
> overloading of the original xtables. Perhaps there is a better way but it
> wor
] IPv6 \NC\NR
\NC Sicherungsschicht \NC[nx=6] Ethernet \NC\NR
\NC Bitübertragungsschicht \NC[nx=2] 100BASE-TX \NC[nx=2] 100BASE-T \NC[nx=2]
1000BASE-T \NC\NR
\stopxtable
\stoptext
On 03/08/2017 04:29 PM, Henri Menke wrote:
> Dear devs,
>
> Natural Tables are quite handy but the
;> \NC Sicherungsschicht \NC[nx=6] Ethernet \NC\NR
>> \NC Bitübertragungsschicht \NC[nx=2] 100BASE-TX \NC[nx=2] 100BASE-T
>> \NC[nx=2] 1000BASE-T \NC\NR
>> \stopTABLE
>>
>> \stoptext
>
> Because that's not a natural table. You're confusing the old TABL
Sitzungsschicht\NC\NR
\NC Transportschicht \NC[nx=3] TCP \NC[nx=3] UDP \NC\NR
\NC Vermittlungsschicht\NC[nx=3] IPv4 \NC[nx=3] IPv6 \NC\NR
\NC Sicherungsschicht \NC[nx=6] Ethernet \NC\NR
\NC Bitübertragungsschicht \NC[nx=2] 100BASE-TX \NC[nx=2] 100BASE-T \NC[nx=2]
1000BASE-T
] IPv6 \NC\NR
\NC Sicherungsschicht \NC[nx=6] Ethernet \NC\NR
\NC Bitübertragungsschicht \NC[nx=2] 100BASE-TX \NC[nx=2] 100BASE-T \NC[nx=2]
1000BASE-T \NC\NR
\stopTABLE
\stoptext
___
If your question
\footnote{bar}
\stoptext
which crashes with this output:
8<-----
tx-context | run 1: luatex
--fmt="/usr/local/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en"
--jobname="tt"
--lua="
hi,
in a pristine standalone context (installed yesterday) under ubuntu I see
a seemingly consistent crash of luatex if the document contains footnotes
minimal example:
\starttext
foo\footnote{bar}
\stoptext
which crashes with this output:
8<-----
On 10/17/2016 08:33 PM, Hans Hagen wrote:
>> [...]
>> If this isn’t a bug, what am I missing here?
>
> that the x/xx sized are automatic adaptions of tf bf sl it ..., so: \bf
> \tx is the same as \bfx:
>
> test {\bf \tx test} test {\bfx test}
>
&g
\tfx Smaller2 \tfxx Smaller2
\stoptext
I can set a different value for a, but not for x or xx. The values for x
and xx seem to be hardcoded.
If this isn’t a bug, what am I missing here?
that the x/xx sized are automatic adaptions of tf bf sl it ..., so: \bf
\tx is the same as \bfx:
test
tuplow [down=.48\exheight]
\setuphigh[up=.86\exheight]
e.g. use other values, but if your ex and em are bad you can expect many
other issues (so best use decent fonts)
for such cases. However, as these are derived relative scales they
are normally not compatible with \tx and txx size
u can say:
>
> \setuplow [style=\sx]
> \setuphigh[style=\sx]
>
If I do this, this will not get attached to the font; right? For
instance, if I define two bodyfonts 'myfonta' and 'myfontb', a
is unrelated to any other
font setting.
I'll add two new commands: \sx and \sxx so that you can say:
\setuplow [style=\sx]
\setuphigh[style=\sx]
for such cases. However, as these are derived relative scales they are
normally not compatible with \tx and txx sizes.
Hans
an dit being 8 bit fonts you also need a
> virtual font definition file (like the px, tx and mathdesign fonts have)
> ... no big deal (one time job) but someone has to do it
> (so far no one needed fourier i guess)
>
> Hans
>
>
>
>
file (like the px, tx and mathdesign fonts
have) ... no big deal (one time job) but someone has to do it
(so far no one needed fourier i guess)
Hans
-
Hans Hagen | PRAGMA ADE
/T (Gehnehmiger Unterschrift)
/Type /Annot
%% Object stream: object 187, index 57; original object ID: 495
<<
/Action /Exclude
/Fields [
(Einrichter Name)
(Einrichters Unterschrift)
]
/Type /SigFieldLock
("Einrichter Name" is another Text Field --> /FT /Tx
object 187, index 57; original object ID: 495
<<
/Action /Exclude
/Fields [
(Einrichter Name)
(Einrichters Unterschrift)
]
/Type /SigFieldLock
("Einrichter Name" is another Text Field --> /FT /Tx [...] /Subtype
/Widget [...] /T (Einrichter Name)
"Einri
\startsetups[s:footer]
\startembeddedxtable[frame=off,distance=5pt,bodyfont=6pt,option=stretch]
\startxrow
\startxcell Filename: \stopxcell
\startxcell[distance=1cm] \outputfilename.pdf \stopxcell
\stopxrow
\stopembeddedxtable
\stopsetups
\setupheader[style=\tx
=stretch]
\startxrow
\startxcell Filename: \stopxcell
\startxcell[distance=1cm] \outputfilename.pdf \stopxcell
\stopxrow
\stopembeddedxtable
\stopsetups
\setupheader[style=\tx]
\setupfooter[style=\tx]
\setupfootertexts[\setups{s:footer}][][][\setups{s:footer}]
\startchapter
On 08/08/2015 04:18 PM, Wolfgang Schuster wrote:
[...]
All I can tell at the moment is that the problem is related to the “x”
font size.
\starttext
\startxtable
\startxrow
\startxcell[foregroundstyle=\txx] % this fails: foregroundstyle=\tx
\CONTEXT
=\tx
\CONTEXT
\stopxcell
\stopxrow
\stopxtable
\stoptext
Wolfgang,
I’m afraid that compilation also crashes with font commands in
foregroundstyle:
\definefontfamily[newtimes][serif][TeX Gyre Termes]
\setupbodyfont[palatino, 12pt]
\setuphead[section
: foregroundstyle=\tx
\CONTEXT
\stopxcell
\stopxrow
\stopxtable
\stoptext
BTW: Can you avoid using fonts which aren’t available on all systems.
Wolfgang
___
If your question is of interest to others
that tells me that
\setsmallbodyfont differs from \tx in this way (let alone *why* it
differs). Maybe I should expect that any command that has bodyfont in
its name is intended for long-term changes, and other commands aren't?
Sorry if I'm being slow on the uptake.
Documentation like
http
schrieb Hans Hagen pra...@wxs.nl:
function nodepool.pdfsetmatrix(rx,sx,sy,ry,tx,ty)
local t = copy_node(pdfsetmatrix)
if type(rx) == string then
t.data = rx
else
t.data = formatters[%s %s %s %s](rx or 1,sx or 0,sy or 0,ry or 1) --
todo: tx ty
end
return t
end
On 8/2/2013 9:05 PM, Jannik Voges wrote:
No problem. Pdf is attached.
ok, i see the problem ... will try to fix it (cannot upload from where i
am now)
you can try this in back-pdf.lua:
function nodepool.pdfsetmatrix(rx,sx,sy,ry,tx,ty)
local t = copy_node(pdfsetmatrix)
if type(rx
)
you can try this in back-pdf.lua:
function nodepool.pdfsetmatrix(rx,sx,sy,ry,tx,ty)
local t = copy_node(pdfsetmatrix)
if type(rx) == string then
setfield(t,data,rx)
else
setfield(t,data,formatters[%s %s %s %s](rx or 1,sx or 0,sy or 0,ry
or 1)) -- todo: tx ty
to fix it (cannot upload from where i am now)
you can try this in back-pdf.lua:
function nodepool.pdfsetmatrix(rx,sx,sy,ry,tx,ty)
local t = copy_node(pdfsetmatrix)
if type(rx) == string then
setfield(t,data,rx)
else
setfield(t,data,formatters[%s %s %s %s](rx or 1,sx or 0,sy
)}
l.35 \registerctxluafile{back-pdf}{1.001}
% some code will move to lpdf-*
?
Jannik
Am 02.08.2013 um 21:58 schrieb Hans Hagen pra...@wxs.nl:
function nodepool.pdfsetmatrix(rx,sx,sy,ry,tx,ty)
local t = copy_node(pdfsetmatrix)
if type(rx
}{'aeide} \dos{diosa}{je`a} \dos{del ...
?
Replace \ix with \switchtobodyfont[9pt] or better use a relative size like \tx
or \txx.
Wolfgang
___
If your question is of interest to others as well, please add an entry
] or better use a relative size like
\tx or \txx.
Wolfgang
___
If your question is of interest to others as well, please add an entry to
the Wiki!
maillist : ntg-context@ntg.nl /
http://www.ntg.nl/mailman/listinfo
:\rightorleftpageaction rl]
[]
[width=\marginwidth,
align={lohi,middle},
foregroundstyle=\tx]
{\floatuserdataparameter{text}}
\flushlayer
[extrafiguretextlayer:\rightorleftpageaction rl]
\stopsetups
\defineoverlay
a} {\tfw a}
\stoptext
Why isn't the x font size set to 0.9?
because the x sizes are defined for sizes
\definefontsize
[w]
\setupbodyfontenvironment
[12pt]
[x=2pt]
\setupbodyfontenvironment
[default]
[w=0.2]
\starttext
\ruledhbox{xxx {\tfx tfx} {\tx tx} {\txx txx} {\tfw tfw
Hi,
I found a typo in the current beta (2013-05-21)
meta-pdf.lua, line 169
168 function mps.translate(tx,ty)
169 mpscode(f_translate(tx,ty)
170 end
Regards, Peter
___
If your question is of interest
encoding, it
should work as virtual otf .. you then only need to make a file like
tx-math.lfg as vectors are already built-in.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27
the math font, which is worse. I should have wrapped the arguments
with \hbox and thrown in a \tx or \txx. Or waited a little longer for the good
solution. :)
Best,
Michael
This e-mail message (including any attachments) is for the sole use of
the intended
to be adjusted for each font and size.
You can use \framed:
\defineframed[lohimi][align=flushleft,location=middle,frame=off,foregroundstyle=\tx]
\starttext
text \lohi{1}{2} text \lohimi{1\\2\\3} text
\stoptext
Wolfgang
Hi Wolfgang,
Though you actually replied to Michael Rogers' mail
=flushleft,location=middle,frame=off,foregroundstyle=\tx]
\starttext
text \lohi{1}{2} text \lohimi{1\\2\\3} text
\stoptext
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki
\framed:
\defineframed[lohimi][align=flushleft,location=middle,frame=off,foregroundstyle=\tx]
\starttext
text \lohi{1}{2} text \lohimi{1\\2\\3} text
\stoptext
Neat trick.
===
Wolfgang,
The next beta has:
\starttext
\definelow [MyLow] [style=\txx]
\definehigh [MyHigh] [style=\txx
][align=flushleft,location=middle,frame=off,foregroundstyle=\tx]
\starttext
text \lohi{1}{2} text \lohimi{1\\2\\3} text
\stoptext
Neat trick.
===
Wolfgang,
The next beta has:
\starttext
\definelow [MyLow] [style=\txx]
\definehigh [MyHigh] [style=\txx]
\definelowhigh
=smallitalic]{text}
\stoptext
or
\starttext
\scratchtoks\emptytoks
\appendtoks\tx\to\scratchtoks % check if the style attribute contains “small”
\appendtoks\it\to\scratchtoks % check if the style attribute contains “italic”
\framed[foregroundstyle=\the\scratchtoks]{text}
\stoptext
Wolfgang
Hi Mojca,
This is the status with 2012.05.30 11:26:
[HIGH] The integral signs in PX-fonts now work correctly. Only the
distance between the integral sign and the bounds are to big.
[HIGH] TX, XITS, Antykwa and Iwona have the same problem. (It's OK in
Asana and Euler).
[MID] The Kurier-font
makes
assumes opentype logic).
Hans
On 1-6-2012 17:05, Tim Steenvoorden wrote:
Hi Mojca,
This is the status with 2012.05.30 11:26:
[HIGH] The integral signs in PX-fonts now work correctly. Only the
distance between the integral sign and the bounds are to big.
[HIGH] TX, XITS, Antykwa and Iwona
:26:
[HIGH] The integral signs in PX-fonts now work correctly. Only the
distance between the integral sign and the bounds are to big.
[HIGH] TX, XITS, Antykwa and Iwona have the same problem. (It's OK in
Asana and Euler).
[MID] The Kurier-font is not working at all (math and text).
[MID
included in TeXLive:
* Latin Modern
* Euler
* Asana
* Palatino (px)
* Times (tx)
* Utopia (mathdesign)
* Charter (mathdesign)
* Garamond (mathdesign)
* Antykwa Torunska
* Iwona
* Kurier
* Xits
Compiling the example in the attachment I found than Euler and all
Mathdesign derivatives
(12pt) size this becomes 1040448 for px as well as
tx. Both fonts (when looking at them with \showfont[pxex.tfm] etc have
the same shapes.
Concerning the rest of the parameters, only for this case irrelevant
differ a bit.
% name px tx
% RadicalRuleThickness 46399 44040 2359
(px)
* Times (tx)
* Utopia (mathdesign)
* Charter (mathdesign)
* Garamond (mathdesign)
* Antykwa Torunska
* Iwona
* Kurier
* Xits
Compiling the example in the attachment I found than Euler and all
Mathdesign derivatives are not working.
Does anyone know if Millenial will be supported by TeXLive
} {\rm d} x
\stopformula
\stoptext
Cheers,
Tim
2012/5/25 Hans Hagen pra...@wxs.nl:
On 25-5-2012 00:43, Aditya Mahajan wrote:
It's more complicated because tx-fonts behaves correctly.
indeed, and I always thought that these fonts were similar in setup
Hans
On 25-5-2012 00:43, Aditya Mahajan wrote:
It's more complicated because tx-fonts behaves correctly.
indeed, and I always thought that these fonts were similar in setup
Hans
-
Hans Hagen
it) in asana-math.lfg. After that, you can at least use
asana math as a work around.
Euler and Stix fonts work OK, and surprisingly so is txfonts! I thought
that px- and tx-fonts were handled identically. Why does the bug only
appear with px-fonts?
Comparing the two files, I noticed
a bit, but never recovered
properly back.
something math_operator_size and/or DisplayOPeratorMinHEight
It's more complicated because tx-fonts behaves correctly.
Aditya
___
If your question is of interest to others
integrals and
sums. To fix asana, change
DisplayOperatorMinHeight = more,
to
DisplayOperatorMinHeight = 0,
(or just comment it) in asana-math.lfg. After that, you can at least use
asana math as a work around.
Euler and Stix fonts work OK, and surprisingly so is txfonts! I thought
that px- and tx
,
to
DisplayOperatorMinHeight = 0,
(or just comment it) in asana-math.lfg. After that, you can at least use
asana math as a work around.
Euler and Stix fonts work OK, and surprisingly so is txfonts! I thought
that px- and tx-fonts were handled identically. Why does the bug only
appear
}}
\def\tfxx{\orgtfxx\dosetcurrentfontsize{xx}}
Is the difference intentional? Or is Hans willing to incorporate the change in
a next beta?
this is intentional as tx and txx are only meant for (nested) \high an
\low implementations while \tfa are for heads and such
Hans
' process is also(!) called, if normal transparency
('tr') or text ('tx') is used. You can imagine that the 'cleanup
code' has unwanted side effects here. :-)
A change of the 'appendaction' order has no impact.
I simply added
commands.writestatus('mtr_process',table.serialize(prescript
1 - 100 of 206 matches
Mail list logo
