([[\luaescapestring{#1}]])}}
\PrintTheThing{a \em b {c}}
\stoptext
I wonder whether there is a proper way in the Lua code to avoid
[[\luaescapestring{}]] in \ctxlua.
BTW, [[\luaescapestring{}]] in \ctxlua works better for me, since in my
real world document, I’m using str:match() to check
Dear list,
I have the following sample:
\starttext
\startluacode
function document.print_the_thing(str)
context(str)
end
\stopluacode
\unexpanded\def\PrintTheThing#1{%
\ctxlua{document.print_the_thing([[\luaescapestring{#1}]])}}
\PrintTheThing{a \em b {c}}
\stoptext
I
On 4/6/2024 1:38 PM, Wolfgang Schuster wrote:
Henning Hraban Ramm schrieb am 06.04.2024 um 12:23:
Am 06.04.24 um 11:43 schrieb madiazm.eo...@gmail.com:
Hi everyone,
I'm a bit puzzled because I usually don't get an em-dash when I type
tree hyphens. If I use the command \emdash, no problem
Henning Hraban Ramm schrieb am 06.04.2024 um 12:23:
Am 06.04.24 um 11:43 schrieb madiazm.eo...@gmail.com:
Hi everyone,
I'm a bit puzzled because I usually don't get an em-dash when I type
tree hyphens. If I use the command \emdash, no problem but when I use
the hyphens some days it works
Am 06.04.24 um 11:43 schrieb madiazm.eo...@gmail.com:
Hi everyone,
I'm a bit puzzled because I usually don't get an em-dash when I type tree
hyphens. If I use the command \emdash, no problem but when I use the hyphens
some days it works... and somedays I see three small hyphens.
I tried
Hi everyone,
I'm a bit puzzled because I usually don't get an em-dash when I type tree
hyphens. If I use the command \emdash, no problem but when I use the hyphens
some days it works... and somedays I see three small hyphens.
I tried it on overleaf and of ContextOnWeb with the same inconsistency
.
\enableexperiments[fonts.compact]
\definefontfamily[mainface][rm][TeX Gyre Termes]
[it={style:regular, features:{default,slanted}},
sl={style:regular, features:{default,slanted}}]
\setupbodyfont[mainface]
\starttext
\startstyle[style=italic]normal {\em emphasized} normal\stopstyle
\stoptext
[mainface][rm][TeX Gyre Termes]
[it={style:regular, features:{default,slanted}},
sl={style:regular, features:{default,slanted}}]
\setupbodyfont[mainface]
\starttext
\startstyle[style=italic]normal {\em emphasized} normal\stopstyle
\stoptext
The only way to mask the effect is to create a new
umulate, like
> [...]
> which you will now wikify...
Many thanks for your reply, Hans.
I will wikify this, once I figure out where it can fit in the wiki (in
due time, since ConTeXt is more and more complex for me lately and my
free time is less and less these days).
I only used \enableexpe
On 3/10/2024 9:32 AM, Pablo Rodriguez via ntg-context wrote:
On 3/9/24 16:04, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
[...]
\enableexperiments[fonts.compact]
Which seeems weird to me. Or at least, I thought I read that Hans
enabled it by
On 3/9/24 16:04, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
>> [...]
>>\enableexperiments[fonts.compact]
>>
>> Which seeems weird to me. Or at least, I thought I read that Hans
>> enabled it by default in LMTX.
>
> AFAIR Hans uses the setting in
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
On 3/8/24 19:09, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
[...]
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
[...]
I get b and d in italic which
On 3/8/24 19:09, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
>> [...]
>> LMTX gets b, c and d in slanted form.
>>
>> LuaTeX gets only b and c in slanted form.
> [...]
> I get b and d in italic which is the expected output.
Sorry, my LuaTeX is getting
},
it={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d
},
it={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d
: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d\\
\stopTEXpage
\stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only
=doublesided, location={header, inmargin}]
\setupmargindata[inmargin][location=inner,
style={\ssx\setupinterlinespace[line=2.8ex]}]
\setupmarginframed[inmargin][align=right]
\setupbodyfontenvironment[default][em=italic]
% Use Theano Didot as Ancient Greek font
\definefallbackfamily[mainface][serif
possibilities_for_linebreaking_between_character
> > ) and eventually more, which I didn't test.
> > It might be useful to define three scripts nihongo_loose, nihongo_strict
> > and nihongo_very_strict which each implement one of the 3 cases described
> > here: ht
; ) and eventually more, which I didn't test.
>
> It might be useful to define three scripts nihongo_loose, nihongo_strict
> and nihongo_very_strict which each implement one of the 3 cases described
> here: https://www.w3.org/TR/jlreq/#addendum_a
>
> According the *line gap* (
t be useful to define three scripts nihongo_loose, nihongo_strict and
> nihongo_very_strict which each implement one of the 3 cases described here:
> https://www.w3.org/TR/jlreq/#addendum_a
>
> According the line gap (Otared uses \setupwhitespace[big], which is exceeding
is common that the line gap for the kihon-hanmen is set to a value
between half-em spacing and the one em spacing of the character frame
used for the kihon-hanmen. Half-em spacing can be chosen in cases
where the line length is short, but one em spacing or close to it is
more appropriate when the l
g/TR/jlreq/ :
It is common that the line gap for the kihon-hanmen is set to a value between
half-em spacing and the one em spacing of the character frame used for the
kihon-hanmen. Half-em spacing can be chosen in cases where the line length is
short, but one em spacing or close to it is more approp
]
\setuppagenumbering[alternative=doublesided, location={header, inmargin}]
\setupmargindata[inmargin][location=inner,
style={setupinterlinespace[line=2.8ex]}]
\setupmarginframed[inmargin][align=right]
\setupbodyfontenvironment[default][em=italic]
\definefallbackfamily[mainface][rm][Theano
Didot
]
[TeX Gyre Pagella]
\setupbodyfont[mainface, 11pt]
\setupbodyfontenvironment[default][em=italic]
\starttext
Socrate est descendu au Pirée et affirme sa satisfaction du culte rendu Ã
cette nouvelle déesse par les Thraces; néanmoins, {\em il ne nous dit rien
des prières} qu'il a lui-même
with
setupinterlinearspace[1.3ex] was the right way (I read somewhere that vertical
spaces should be measured in ex and horizontal spaces in em; maybe it's not
widely accepted).
I tried setting my interlinearspace to 3ex and it looked much better, but I
must compare it with a onehalfspacing
n ex and
> horizontal spaces in em; maybe it's not widely accepted).
As far as I know, em is defined by the width of the capital 'M' and ex
is defined by the height of the lowercase 'x'.
With your requirements, I think it is easier to set line spacing to one
and a half line with 1.5em, such
with
setupinterlinearspace[1.3ex] was the right way (I read somewhere that vertical
spaces should be measured in ex and horizontal spaces in em; maybe it's not
widely accepted).
I tried setting my interlinearspace to 3ex and it looked much better, but I
must compare it with a onehalfspacing
somewhere that vertical
spaces should be measured in ex and horizontal spaces in em; maybe it's not
widely accepted).
I tried setting my interlinearspace to 3ex and it looked much better, but I
must compare it with a onehalfspacing of wordprocessors to be sure it is not
such different.
Sorry
description like /em/, /\em/, /bf/, /\bf/,
/\sc,/ does produce the suggested result. The wiki and mail repository
are full of examples with the former style names.
Using /style=cap/ (which would change the number as well) also results
in a failed compilation, while using /style=bolditalic/ works
iki
(https://wiki.contextgarden.net/Commands_with_optional_arguments).
It seems that the command has to be defined as unexpanded, such as in:
\setupinteraction[state=start]
\setupattachments[method=hidden]
\usemodule[database]
\starttext
\unexpanded\def\ItemContents#1#2#3{\doiftext{#2}
/bidi.pdf;
"Flowcharts","charts-mkiv.pdf",
Faking a command such as \cA, \cB and \cC (for contents of columns A, B
or C) I would like to create a source document with an enumeration that
contains:
\doiftext{\cB}
{\item {\em\cA}\attachment[file=\cB]%
\doiftext{\cC}{
his):
\definefontfamily[mainface][rm][DejaVu Sans]
[sl≃style:bf]
\setupbodyfont
[mainface, 100pt]
\starttext
\startTEXpage[offset=1ex]
a {\em b}
\stopTEXpage
\stoptext
Many thanks for your help again,
Pablo
][DejaVu Sans]
[sl={style:tf, features:{default,slanted}}]
\setupbodyfont[maf, 8pt]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX
:{default,slanted}}]
\setupbodyfont[maf, 8pt]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text
]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text (or not at all).
Using MkIV text is slanted fine
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text (or not at all).
Using MkIV text is slanted fine, independent from font size.
Could anyone confirm the issue?
Many
Mikael, Wolfgang:
This is in reference to the prior
Re: redefine space to be the same as \␣ similar to knuthian approach
> Maybe your system is broken?
>
> >
> > > 2. The example below results in a correct output for \TEX.
> > >
> >
> > Not in my end with any font other than latin modern
>
chapter at the end of a book. It
produces headings that indicate the pages for which the notes apply.
Perhaps you can adapt it to your needs:
In the environment file:
\definemarking [notePage] \startsetups noteHeadingsText {\em
Notes for page
\doifelse{\fetchmark[notePage
[url(http://wiki.contextgarden.net)] versió
\contextversionnumber, \goto{\texenginename}[url(http://www.luatex.org)] versió
\texengineversion\space i \goto{PGF/Ti{\em
k}Z}[url(http://sourceforge.net/projects/pgf/)]) sota un entorn
\goto{GNU/Linux}[url(https://www.linuxfoundation.org)] (\goto{Artix
Linux}[
er, \goto{\texenginename}[url(http://www.luatex.org)] versió
\texengineversion\space i \goto{PGF/Ti{\em
k}Z}[url(http://sourceforge.net/projects/pgf/)]) sota un entorn
\goto{GNU/Linux}[url(https://www.linuxfoundation.org)] (\goto{Artix
Linux}[url(https://artixlinux.org)]). La revisió d'aquest document és
we still need something like
\defineactivecharacter ʿ {\high{c}}
\defineactivecharacter ʾ {\kern.07 em
\high{\rotate[rotation=180,location=high]{c}}}
or better
\definecharacter ʿ {\high{c}}
\definecharacter ʾ {\kern.07 em \high{\rotate[rotation=180,location=high]{c}}}
The upshot is that we need
On Fri, 19 May 2023, Jeroen via ntg-context wrote:
> Many thanks. Is there a proper way to add some space (a couple of pt or em)
> to the left and the right of the text itself so the frame does not get so
> close to the text?
\framed[loffset=0.2ex, roffset=0.2ex]{...}
Also s
Many thanks. Is there a proper way to add some space (a couple of pt or em)
to the left and the right of the text itself so the frame does not get so
close to the text?
Op vr 19 mei 2023 om 14:10 schreef Wolfgang Schuster via ntg-context <
ntg-context@ntg.nl>:
> Jeroen via ntg-context s
ee: Not-so-short Intro to ConTeXt (J.
>>> Ataz-Lopez;English, page 114))
>>> • $ mtxrun (mtxrun is the ConTeXt TDS Runner Tool) command from a
>>> terminal window it has has a large number of options for finding the fonts
>>> installed, and for querying their c
finding the fonts
>> installed, and for querying their characteristics (see: Fonts out of ConTeXt
>> (Hans Hagen, pg 52 and ff))
>> Em
>>
>> On 2023-04-25 08:50, Werner Schmidt via ntg-context wrote:
>> Hi conTeXt folks,
>>
>> may I ask again. How c
Xt (_J.
> Ataz-Lopez;English, page 114))
> * $ MTXRUN (mtxrun is the _ConTeXt TDS Runner Tool_) command from a
> terminal window it has has a large number of options for finding the fonts
> installed, and for querying their characteristics (SEE: _Fonts out of ConTeXt
> _(Hans Hagen
the
fonts installed, and for querying their characteristics (SEE: _Fonts out
of ConTeXt _(Hans Hagen, pg 52 and ff))
Em
On 2023-04-25 08:50, Werner Schmidt via ntg-context wrote:
> Hi conTeXt folks,
>
> may I ask again. How could I debug the font typesetting of PDF files with
> conTeXt?
&
},
translators={foo,bar,baz}
]
{\em authors} \\
\commalistsentence[\structureuservariable{authors}][{ \crlf },{ \crlf }]
{\em translators} \\
\processcommacommand[\structureuservariable{translators}]\dosomethingtwo
\doloopoverlist {\structureuservariable{translators}} {
(#1) \\
}
\stopchapter
\stoptext
apter.
>
>
>
>
> \stopbuffer
>
> \startxmlsetups xml:testsetups
> \xmlsetsetup{#1}{*}{-}
> \xmlsetsetup{#1}{document|chapters|chapter|content|emph}{xml:
> *}
> \stopxmlsetups
>
> \xmlregistersetup{xml:testsetups}
>
> \startxmlsetup
txmlsetups xml:chapter
\xmlfunction {#1} {chapter}
%\xmlflush {#1}
\stopxmlsetups
\startxmlsetups xml:chapter:content
\xmltext {#1} {content}
\stopxmlsetups
\startxmlsetups xml:emph
{\em \xmlflush {#1}}
\stopxmlsetups
\startluacode
function xml.functions.
\xmltext {#1} {content}
\stopxmlsetups
\startxmlsetups xml:emph
{\em \xmlflush {#1}}
\stopxmlsetups
\startluacode
function xml.functions.chapter (t)
local ch_id = t.at.ch:id
local ch_id = t.at["ch:id"]
local metadata = xml.filter (t,
'../../topics/topic[
xml:chapter:content
\xmltext {#1} {content}
\stopxmlsetups
\startxmlsetups xml:emph
{\em \xmlflush {#1}}
\stopxmlsetups
\startluacode
function xml.functions.chapter (t)
local ch_id = t.at.ch:id
local metadata = xml.filter (t,
'../../topics/topic[@t:id=="%s"
ps
>
> \startxmlsetups xml:chapters
> \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:chapter
> \xmlfunction {#1} {chapter}
> \xmlflush {#1}
> \stopxmlsetups
>
> \startxmlsetups xml:chapter:content
> \xmltext {#1} {content}
>
}
\stopxmlsetups
\startxmlsetups xml:chapter
\xmlfunction {#1} {chapter}
\xmlflush {#1}
\stopxmlsetups
\startxmlsetups xml:chapter:content
\xmltext {#1} {content}
\stopxmlsetups
\startxmlsetups xml:emph
{\em \xmlflush {#1}}
\stopxmlsetups
\startluacode
function
this is all settled down, we can improve
specific font related issues based on {\em realistic} user mwe's as we go.
Concerning large operators .. it worked before so ... the main reason
why in e.g. euler it failed was a configuration option (euler fonts will
be fixed too) which is a side effect of more
[footnote]
[numberconversion=set 2]
\setupnotation [footnote]
[align=hanging]
\setupwhitespace [medium]
\setupbodyfont [libertinus]
\showframe
\starttext
\quotation{{\em Cantharides}} is the reported message from Sir Francis
Drake upon
stopbuffer
\startxmlsetups xml:xhtml
\xmlsetsetup{\xmldocument}{*}{-}
\xmlsetsetup{\xmldocument}{html|p|em}{xml:*}\stopxmlsetups
\startxmlsetups xml:html
\startdocument
\xmlflush{#1}
\stopdocument\stopxmlsetups
% Paragraphs are followed by a paragraph break, but only if
mldocument}{*}{-}
\xmlsetsetup{\xmldocument}{html|p|em}{xml:*}\stopxmlsetups
\startxmlsetups xml:html
\startdocument
\xmlflush{#1}
\stopdocument\stopxmlsetups
% Paragraphs are followed by a paragraph break, but only if not
nested.\startxmlsetups xml:p
\xmlfunction{#1}{p}
\par\sto
the
following code to add them (and add en and em dash substitution as well).
%% start
\startluacode
fonts.handlers.otf.addfeature {
name = "v1", -- these character substitutions will be applied to
venetian-301-demi-bt
type = "ligature&
enetian 301 Italic
Venetian301BT-Bold.otf Venetian 301 Bold
venetian-301-demi-bt.ttfVenetian Dm BT Demi
They each had the fi and fl ligatures, but at different character positions
depending on which file, and they weren't recognised by default. So I used the
following code to add them
environment file for the project contains the definitions. e.g.
\definesynonyms[abbreviation][abbreviations][\infull]
\setupsynonyms[abbreviation][synonymstyle=\em] \abbreviation[adjp]
{adjp.} {adjectival phrase}
All dictionary components (A-Z) call on the main environment file where
the above
the following number on the
same line and to convert /\em/ and such to taggable macros that I define
in my environment. The result is ConText source that can be further
edited (if necessary) and inserted where needed/./ I have not extended
it to multiple bibliographies in a single document
An: 'mailing list for ConTeXt users'
Betreff: process list items differently depending on position in list
Hi,
I need to process a comma separated list, and adapt the formatting according to
the position of an item in the list (example below). Expected output would be:
{\bf foo
}, {\em bar
Hi,
I need to process a comma separated list, and adapt the formatting according to
the position of an item in the list (example below). Expected output would be:
{\bf foo
}, {\em bar} and baz.
Is that possible? Can I somehow get the position of an item in the list? (My
understanding
.
There are a couple of problems with the speech bubbles that could use
fixing. First, the ability to have a fixed offset for the tail (e.g.,
2 em from the left and 2 em from the right). Second, when the speech
bubble is too short (e.g., a single emoji), the tail gets mangled.
Here's a screenshot
rl{#1}}[url(https://#1)]\autoinsertnextspace}
>>> \define[1]\Email{\goto{\hyphenatedurl{#1}}[url(mailto:#1)]\autoinsertnextspace}
>>> \define[1]\WebQR{\inouter[scope=local]{\barcode[alternative=qr code,
>>> text={#1}, width=10mm]}\Web{#1}}
>>> \
]\WebQR{\inouter[scope=local]{\barcode[alternative=qr code, text={#1},
width=10mm]}\Web{#1}}
\define[1]\WebArrow{\symbol[wingdings 3][barb1right]~{\em\hyphenatedurl{#1}}}
So I guess you’d like something like:
\define[1]\Link{\goto{\symbol[wingdings
3][barb1right]}[url(https://#1)]\autoinsertnextspace
de[alternative=qr code,
> text={#1}, width=10mm]}\Web{#1}}
> \define[1]\WebArrow{\symbol[wingdings 3][barb1right]~{\em\hyphenatedurl{#1}}}
>
> So I guess you’d like something like:
>
> \define[1]\Link{\goto{\symbol[win
[wingdings
3][barb1right]~{\em\hyphenatedurl{#1}}}
So I guess you’d like something like:
\define[1]\Link{\goto{\symbol[wingdings
3][barb1right]}[url(https://#1)]\autoinsertnextspace}
Hraban
___
If your question
usemodule[ipsum]
\showframe
\setuplayout[
width=100mm,
rightmargin=50mm,
rightmargindistance=6mm,
]
\setupbodyfontenvironment[11pt][
em=italicface,
text=11pt,
small=8pt,
interlinespace=14pt,
]
\definebodyfontenvironment[8pt][interlinespace=8pt]
\setupbodyfont[rm,11pt]
\define\PlaceFoot
of this code
(I've enriched the didascalies for people who are fresh beginners):
\mainlanguage[la] % Définition du latin comme langue principale du
document/Latin as main language.
\setupbodyfontenvironment[default][em=italic]
\setuplayout[header=2cm, footer=2cm] % Paramétrage de la page
]
\definetypeface [jun-pr-lib] [rm] [serif] [jun-pr-lib] [default]
\stoptypescript
% some tracking stuff
\enabletrackers[fonts.missing=replace]
\enabledirectives[logs.errors]
% text, we use lib-fb-jun first, then jun-pr-lib
\starttext
\setupbodyfont[lib-fb-jun]
{\em emph. lib-fb-jun
] [name]
> \definefontsynonym [Serif] [JunicodeRoman] [fallbacks=preferlibertine]
> \stoptypescript
>
> \starttypescript [jun-pr-lib]
>\definetypeface [jun-pr-lib] [rm] [serif] [jun-pr-lib] [default]
> \stoptypescript
>
> % some tracking stuff
>
> \enabletrackers[fo
erif] [JunicodeRoman] [fallbacks=preferlibertine]
> \stoptypescript
>
> \starttypescript [jun-pr-lib]
> \definetypeface [jun-pr-lib] [rm] [serif] [jun-pr-lib] [default]
> \stoptypescript
>
>
> % some tracking stuff
>
> \enabletrackers[fonts.missing=replace]
> \enable
]
\stoptypescript
% some tracking stuff
\enabletrackers[fonts.missing=replace]
\enabledirectives[logs.errors]
% text, we use lib-fb-jun first, then jun-pr-lib
\starttext
\setupbodyfont[lib-fb-jun]
{\em emph. lib-fb-jun: \Uchar61125 \char64259 \utfchar{"eec5} (three glyphs)}
lib-fb-jun: \Uchar
numéro des pages, etc.
\mainlanguage[la] % Définition du latin comme langue principale du document.
\setupbodyfontenvironment[default][em=italic]
\setuplayout[header=2cm, footer=2cm] % Paramétrage de la page;
\setuplinenumbering[step=2] % La sortie PDF comportera une numérotation
commandes stipulant les marges, les en-têtes, le numéro des pages, etc.
\mainlanguage[la] % Définition du latin comme langue principale du document.
\setupbodyfontenvironment[default][em=italic]
\setuplayout[header=2cm, footer=2cm] % Paramétrage de la page;
\setuplinenumbering[step=2] % La sortie
Marco
Thanks a lot. It works. Such a solution had briefly crossed my mind but I
had left it aside, hoping there was some feature I had missed.
Em qua., 29 de dez. de 2021 10:40, Marco Patzer via ntg-context <
ntg-context@ntg.nl> escreveu:
> On Wed, 29 Dec 2021 08:29:34 -0300
> Yo
Hi all:
In the example below:
\setuppagenumbering[alternative=doublesided, location={footer,right},page=no]
\newdimen\Margin
\Margin=2cm
\newdimen\MarginRaise
\MarginRaise=56ex
\setuptexttexts[margin][][\setups{text a}][\setups{text b}][]
\setuptext[leftstyle=\sc,rightstyle=\em
=12cm,margin=2.5cm]
\setupmargindata[inmargin][style={\tfx\em}, location=outer,align=flushouter]
just use \inouter or define a new margindata class (see typo-mar.mkxl
line 360 etc to see what is defined in what way)
\starttext
\chapter{Introduction}
\input{tufte}
\input{tufte}\inmargin
Hi all:
I send this minimal example:
\mainlanguage [es]
\definefontfamily [mainface] [serif] [Gentium]
\setupbodyfont[mainface]
\setuppagenumbering[alternative=doublesided, location={footer,right}]
\setuplayout[textwidth=12cm,margin=2.5cm]
\setupmargindata[inmargin][style={\tfx\em}, location
gt;header=empty,
>footer=chpaterfooter,
>sectionsegments=chapter,
>before={\setups[chapter:before]},
>after={\setups[chapter:after]}]
>
> \startsetups chapter:before
> \page[left]
> \noheaderandfooterlines
> \startalignment[left,nothyphen
\startalignment[flushright,nothyphenated]
\startnarrower[4*left]
\em \getbuffer[chapter:quote]
\stopnarrower
\stopalignment
\page[right]
\stopsetups
\starttext
\startbuffer [chapter:quote]
If you think good architecture is expensive, try bad architecture\crlf
{\tf Brian Foote
[chapter]
[page=,
header=empty,
footer=chpaterfooter,
sectionsegments=chapter,
before={\setups[chapter:before]}]
\startsetups chapter:before
\page[left]
\noheaderandfooterlines
\startalignment[left,nothyphenated]
\startnarrower[4*left]
\em \getbuffer[chapter:quote
,
header=empty,
footer=chpaterfooter,
sectionsegments=chapter,
before={\setups[chapter:before]},
after={\setups[chapter:after]}]
\startsetups chapter:before
\page[left]
\noheaderandfooterlines
\startalignment[left,nothyphenated]
\startnarrower[4*left]
\em \getbuffer[
as
a result. Look at the definition. If the current fontalternative is it \it it
will give a \tf result. It is sensitive to the current state in a similar way
that \em and \emph are, but it will always give an italic or roman result.
If we leave the comparisons between \em and \italicface aside
> \startsetups chapter:before
> \page[left]
> \noheaderandfooterlines
> \startalignment[left,nothyphenated]
> \startnarrower[4*left]
> \em \getbuffer[chapter:quote]
> \stopnarrower
> \stopalignment
> \resetsetups[quote:text]
>
]
\startnarrower[4*left]
\em \getbuffer[chapter:quote]
\stopnarrower
\stopalignment
\resetsetups[quote:text]
\page[right]
%\noheaderandfooterlines % I want the enumber in the footer here
\blank[force,2*big]
\stopsetups
\startsetups chapter:after
\blank[3*big
t},
color=blue,
]
\MyStyle[
color=blue,
]
\MyStyle[
text={test \em test},
]
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherl
t;> as a result. Look at the definition. If the current fontalternative is it
>> \it it will give a \tf result. It is sensitive to the current state in a
>> similar way that \em and \emph are, but it will always give an italic or
>> roman result.
>>
>
> If we leave
state in a similar way that \em and \emph are, but it
will always give an italic or roman result.
If we leave the comparisons between \em and \italicface aside and talk
only about the results from \italicface we have a common ground.
You're right the results from \italicface aren't
Wolfgang (off-list),
It is simply wrong to say that \italicface as defined gives only \it or
\bi as a result. Look at the definition. If the current fontalternative
is it \it it will give a \tf result. It is sensitive to the current
state in a similar way that \em and \emph
?
\setupbodyfontenvironment
[default]
[em=italicface] %same with italic for this example
\definehighlight
[emIt]
[style=italic]
\definehighlight
[emIf]
[style=italicface]
\definehighlight
[emEm]
[style=\em
expected to see no difference in the line before and
line after the hairline the example below, but see that italicface
adapts to nesting, while italic does not:
Are there other places where this makes a difference?
\setupbodyfontenvironment
[default]
[em=italicface] %same
the hairline the example below, but see that italicface
adapts to nesting, while italic does not:
Are there other places where this makes a difference?
\setupbodyfontenvironment
[default]
[em=italicface] %same with italic for this example
\definehighlight
to nesting,
while italic does not:
Are there other places where this makes a difference?
\setupbodyfontenvironment
[default]
[em=italicface] %same with italic for this example
\definehighlight
[emIt]
[style=italic]
\definehighlight
' for an unscaled unit (kind of the
internal one, also used at the lua end), 'ex', 'em', 'px' as relative
units (the handy ones), 'mu' for math (sort of relative and adaptive
too), which leaves 'cm', 'mm' (popular and valid SI), 'pt' (natural to
typesetting), 'bp' (related to postscript and pdf, the unit
John Quincy\quad 2\par
\stopIndex
\startIndex{b}
Beagle\quad 1, 2\par
\reference[breedingprograms]{breeding programs}breeding
programs\quad 2
\stopIndex
\startIndex{c}
Coton de Tulear\quad 2.\par
\quad {\em See also under} \in[do
ss] [sans] [modern] [default]
\definetypeface [ka] [tt] [mono] [modern] [default]
\definetypeface [ka] [mm] [math] [modern] [default]
\definetypeface [ka] [hw] [handwriting] [comicsans] [default]
\stoptypescript
\setupbodyfont[ka,rm,18pt]
\setupbodyfontenvironment[default][em=italicface]
\de
\makeupwidth,corner=round]
The poems of St John of the Cross have been important for me in
recent years. This is John’s prayer from a verse in his Spiritual
Canticle:\footnote{John of the Cross, {\em Spiritual Canticle},
stanza 32. }
\startblockquote
You looked with love upon me, and deep
1 - 100 of 1278 matches
Mail list logo
