Meyer:
is it possible to read out the value of \tx (or \txx ... ) for
calculations if bodyfont and fontsize is given? \the\tx doesn't work.
Does \showbodyfontenvironment help?
Hraban
Thank you, Hraban,
I know this table. But I think it's too complicated for me to extract
from
> On 12 Apr 2025, at 10:14, Thomas Meyer wrote:
>
>
>
> Am 11.04.25 um 12:19 schrieb Henning Hraban Ramm:
>> Am 11.04.25 um 10:03 schrieb Thomas Meyer:
>>> is it possible to read out the value of \tx (or \txx ... ) for
>>> calculations if bodyfont
Am 11.04.25 um 12:19 schrieb Henning Hraban Ramm:
Am 11.04.25 um 10:03 schrieb Thomas Meyer:
is it possible to read out the value of \tx (or \txx ... ) for
calculations if bodyfont and fontsize is given? \the\tx doesn't work.
Does \showbodyfontenvironment help?
Hraban
Thank you, H
Am 11.04.25 um 10:03 schrieb Thomas Meyer:
is it possible to read out the value of \tx (or \txx ... ) for
calculations if bodyfont and fontsize is given? \the\tx doesn't work.
Does \showbodyfontenvironment help?
H
Hi folks,
is it possible to read out the value of \tx (or \txx ... ) for
calculations if bodyfont and fontsize is given? \the\tx doesn't work.
\setuplayout[grid=yes]
\setupbodyfont[libertinus,12pt]
\setupinterlinespace[1.25\bodyfontsize]
\starttext
\samplefile{
odern \setupbodyfont[pagella]TeX Gyre Pagella \rma TeX Gyre
Pagella}
\footnote{\rma Latin Modern \setupbodyfont[pagella]TeX Gyre Pagella \rma TeX
Gyre Pagella}
\stoptext
%
You have to add "keep" to \setupbodyfont to ensure \tx and \txx are kept
when you switch the font, i.e. in your e
he initial quotation
mark" to "rewrite your prose." ;-)
https://i.imgur.com/ne991lZ.jpeg
TX
On Wed, Jul 10, 2024 at 11:35 PM vm via ntg-context
wrote:
>
>
> On 11/07/2024 01:55, Thangalin wrote:
> >
> > Any other ideas?
>
> Yes, change/edit the text to avoid th
ing. 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
t
e way 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
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
but can be made 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 typesetti
e we're preparing a bid for extra math symbols
> as needed 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 wel
just
>like all these emoji. We welcome input and as an example 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 typ
ason the \tex {widerandomhat} was
introduced,
\useMPlibrary[newmath]
\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 t
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
cause
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 an
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 a
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 [
> >
for all points 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 = t
xis [
sx = 2mm, sy = 2mm,
nx = 80, ny = 40,
tx = 15, ty = 15,
list = {
[
connect = true,
color = "darkblue",
close = true,
points = {data.
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
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 auto
ertain 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' fro
> $ 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/te
t lacks 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: undefin
the reason 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
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: module
uthor}} {
\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
y one
Anyway, here is an alternative:
\startsetups[MySectionTocEntry]
\doifsomething{\structurelistuservariable{author}} {
\startalignment[middle]
\darkblue \tx \structurelistuservariable{author}
\stopalignment
}
\stopsetups
\setuplist[chapter][after=\s
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
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
unately '\the' displays values with trailing 0s, 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):
{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
st and realized 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 curio
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
around but
%D 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 {\getbuff
\eTD \bTD[nc=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]
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 \eTR
\eTABLE
\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 their
;> \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 th
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 is of
\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}
>
> but
\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
nce reasons once per font instance)
you can play with these:
\setuplow [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 der
\sx and \sxx so that you 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 def
le font switch and that one 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 compat
it 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
>
>
>
> -
ition 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 | PRAGM
get
/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 --> /F
eam: 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)
"
\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
=\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
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
fails: 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 oth
pace. Nevertheless I can't find
anywhere in the manual or on the wiki 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 c
origin
> \pdfhorigin 1 true in
>
>
> \registerctxluafile ...ua.registercode("#1","#2")}
>
> l.35 \registerctxluafile{back-pdf}{1.001}
>% some code will move to lpdf-*
> ?
>
>
> Jannik
>
> Am 02.08.201
dfhorigin
\pdfhorigin 1 true in
\registerctxluafile ...ua.registercode("#1","#2")}
l.35 \registerctxluafile{back-pdf}{1.001}
% some code will move to lpdf-*
?
Jannik
Am 02.08.2013 um 21:58 schrieb Hans Hagen :
>
annot 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[&qu
om 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,"d
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
dos{canta}{>'aeide} \dos{diosa}{je`a} \dos{del ...
> > ?
>
> Replace \ix with \switchtobodyfont[9pt] or better use a relative size like
> \tx or \txx.
>
> Wolfgang
>
>
> ___
> If yo
dos{canta}{>'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 wel
:\rightorleftpageaction rl]
[]
[width=\marginwidth,
align={lohi,middle},
foregroundstyle=\tx]
{\floatuserdataparameter{text}}
\flushlayer
[extrafiguretextlayer:\rightorleftpageaction rl]
\stopsetups
\defineoverlay
tfx 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}
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 to
type1 uses standard tex 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
On Tue, Jan 22, 2013 at 8:58 PM, Marco Patzer wrote:
> Hi,
>
> can I somehow set up that files within TEXMFHOME are preferred to
> files found in the distribution? Or is there another variable which
> is more suitable than TEXMFHOME for this purpose?
Doesn't it already have the highest priority?
ntage over the plain-TeX method, kindly
> offered by Michael Rogers, in that it uses the same font as that for he main
> text,...
It uses 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
solutio
\lower0.23pt\hbox{$\scriptstyle{#3}$}}$}
>>
>> but this would probably have 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 \
gt;>
>>> \def\lomihi#1#2#3{${\scriptstyle{#2}}\limits_{#1}^{\lower0.23pt\hbox{$\scriptstyle{#3}$}}$}
>>>
>>> but this would probably have to be adjusted for each font and size.
>>
>>
>> You can use \framed:
>>
>>
>> \defineframed[lohim
se \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]
\def
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
___
If your question is of interest to
[foregroundstyle=small]{text}
\framed[foregroundstyle=italic]{text}
\framed[foregroundstyle=smallitalic]{text}
\stoptext
or
\starttext
\scratchtoks\emptytoks
\appendtoks\tx\to\scratchtoks % check if the style attribute contains “small”
\appendtoks\it\to\scratchtoks % check i
ote:
> >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
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
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-fo
ormal (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
t; type-imp-*.mkiv which are also included in TeXLive:
>
> * Latin Modern
> * Euler
> * Asana
> * Palatino (px)
> * Times (tx)
> * Utopia (mathdesign)
> * Charter (mathdesign)
> * Garamond (mathdesign)
> * Antykwa Torunska
> * Iwona
> * Kurier
> * Xits
>
} {\rm d} x
\stopformula
\stoptext
Cheers,
Tim
2012/5/25 Hans Hagen :
> 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 s
* 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 are not working.
Does anyone know if Millenial will be supported
1 - 100 of 219 matches
Mail list logo
