Garulfo schrieb am 23.12.2023 um 12:41:
Hi all,
the following minimum working example is properly typesetted with
textstyle=bold,
but it fails with textstyle=cap (ConTeXt version : 2023.09.26 18:19)
A number should have been here; I inserted '0'. (If you can't figure
out why I
needed
> On 23 Dec 2023, at 11:41, Garulfo wrote:
>
> Hi all,
>
> the following minimum working example is properly typesetted with
> textstyle=bold,
> but it fails with textstyle=cap (ConTeXt version : 2023.09.26 18:19)
>
> A number should have been here; I inserted '0
Hi all,
the following minimum working example is properly typesetted with
textstyle=bold,
but it fails with textstyle=cap (ConTeXt version : 2023.09.26 18:19)
A number should have been here; I inserted '0'. (If you can't figure out
why I
needed to see a number, look up 'weird error
Hello list,
The following example does not compile, complaining “Missing number,
treated as zero
needed to see a number, look up 'weird error' in the index to The TeXbook”:
\setuphead [chapter]
[
textstyle=cap
e read the wiki, looked at workflows-synctex.tex, searched the web, and
>> scratched my head, all to no avail. So here I am, cap in hand...
>> When I run context, I get a .synctex file which has some information in it,
>> but I can't find any invocation of synctex to return anythin
On 11/12/2023 10:26 AM, Henning Hraban Ramm wrote:
Am 12.11.23 um 00:59 schrieb Jim:
Hi,
I've read the wiki, looked at workflows-synctex.tex, searched the web,
and
scratched my head, all to no avail. So here I am, cap in hand...
When I run context, I get a .synctex file which has some
Am 12.11.23 um 00:59 schrieb Jim:
Hi,
I've read the wiki, looked at workflows-synctex.tex, searched the web, and
scratched my head, all to no avail. So here I am, cap in hand...
When I run context, I get a .synctex file which has some information in it,
but I can't find any invocation
Hi,
I've read the wiki, looked at workflows-synctex.tex, searched the web, and
scratched my head, all to no avail. So here I am, cap in hand...
When I run context, I get a .synctex file which has some information in it,
but I can't find any invocation of synctex to return anything useful. Nor
\stoptikzpicture \eTD \eTR
\eTABLE } \par \startitemize [a, columns, packed, four] \item 40\% \item 4 de 5
\item $3/4$ \item 4 a 1 \item 22\% \item $1/8$ \item 5 a 3 \item 3 de 8
\stopitemize \par Si aquestes informacions corresponguessin a mostres de peixos
ferits a la mar, calculeu quants peixo
tartitemize [4] \\item S'enlairen 5
astronautes, amb 200 kg de menjar a una estació espacial \\item Al cap de 3
dies, hi ha un relleu: se'n van 2 i en vénen 3 \\item La tripulació resultant
es queda durant 5 dies més \\item Tots els astronautes tornen. L'estació
espacial queda buida \\stopi
Thanks Hans.
I've updated the wiki. I'm wondering if there's a way to also control the
indenting? Max's solution removed any indenting, allowing the text for the
second paragraph to be flush. It looks a little strange to see text
indented next to a drop-cap. The test case is the same
rna.nl/the-book-edition-iii/>
> On 15 May 2023, at 18:18, Gerben Wierda via ntg-context
> wrote:
>
> I'd like to use a drop cap inside a \framed, but it doesn't work.
>
> Minimal example:
>
> %==
> \starttext
> \setupinitial[n=2,text=
I'd like to use a drop cap inside a \framed, but it doesn't work.
Minimal example:
%==
\starttext
\setupinitial[n=2,text=Knuth]\placeinitial\input knuth
\framed[align=flushleft]{\setupinitial[n=2,text=Knuth]\placeinitial\input knuth
}
\stoptext
version.
How could I get bold small caps with the latest version please?
TIA for any hints,
best use a font that has smallcaps (otherwise use pseudocaps \cap{..} etc)
Hans
-
Hans Hagen
LMTX via the filter module and compiling the main doc with MkIV).
> afaik tikz should work ok, so can you make a test file?
>
> Hans
Perhaps this is a good test. It's a complete example:
\setupcolors[state=start]
\definecolor[darkgreen][g=.5]
\usemodule[tikz]
\starttext
\starttikzpi
an][ match={[Pp]\\.[Mm]\\.},
replace={\cap{pm}} ]
That seems like the cleanest approach because it would work on top of XML
or any other source document. Nevertheless, here is what I tried, which
partially works:
\startbuffer[main]
“Mr. McAnulty, I presume?”
Regular text. Irregular text.
\
every XML
element to capture the replacement.
My original post asked about applying regex word substitution in a ConTeXt
way, such as:
\definereplacement[SubstMac][ match={Mc([A-Z].*)}, replace={\Mac \\1} ]
\definereplacement[SubstPostmeridian][ match={[Pp]\\.[Mm]\\.},
replace={\cap{pm}} ]
That
Hi list,
I'm looking to perform text replacements.
\definereplacement[SubstPostmeridian][
match={[Pp].[Mm].]},
replace={\cap{pm}}
]
The \replaceword command doesn't handle periods well. The translate module
doesn't seem flexible enough to cover edge cases. Consider the following
example
than the
central point of the text's bounding box. (I thought that (cap height +
descender height) / 2 was the middle, but I suppose that wouldn't account
for diacritics.)
Thanks for looking into this!
On Wed, Jun 29, 2022 at 2:24 PM Hans Hagen via ntg-context <
ntg-context@ntg.nl> wrote:
>
On 6/29/2022 8:48 PM, Thangalin wrote:
To me, it looks like the text, after a rotational transform, is being
written to the baseline rather than (cap height + descender height) / 2,
which seems to be a MetaPost conversion issue? There's another, possibly
related issue, which I'll provide
Note how the text is vertically centered above the vertical line.
To me, it looks like the text, after a rotational transform, is being
written to the baseline rather than (cap height + descender height) / 2,
which seems to be a MetaPost conversion issue? There's another, possibly
related issue
tion=]
> \starttext
> \definecolor[ffvvqq][r=1.,g=0.3333,b=0.]
> \startTEXpage
> \starttikzpicture[line cap=round,line join=round,>=triangle
> 45,x=1.0cm,y=1.0cm]
> \startaxis
> [
> x=1.0cm,y=1.0cm,
> axis lines=middle,
> ymajorgrids=true,
> xmajorgrids=
=0.]
\startTEXpage
\starttikzpicture[line cap=round,line join=round,>=triangle 45,x=1.0cm,y=1.0cm]
\startaxis
[
x=1.0cm,y=1.0cm,
axis lines=middle,
ymajorgrids=true,
xmajorgrids=true,
xmin=-3.2488079448294145,
xmax=34.87398305791419,
ymin=-7.496155590728956,
ymax=11.53265632858922,
xtick={-3.0,-
]
\usetikzlibrary[arrows]
\setuppagenumbering[location=]
\starttext
\definecolor[ffvvqq][r=1.,g=0.,b=0.]
\startTEXpage
\starttikzpicture[line cap=round,line join=round,>=triangle 45,x=1.0cm,y=1.0cm]
\startaxis
[
x=1.0cm,y=1.0cm,
axis lines=middle,
ymajorgrids=true,
xmajorgrids=true,
x
{\mathradicalparameter\c!strut}\strut#1}}
\protect
\definemathradical[MyRoot] [strut=cap,alternative=Mine]
\definemathradical[MyRootX][strut=yes,alternative=Mine]
\startformula
\sqrt[3]{4n} \ne \sqrt[3] {\vphantom{4} n}
\stopformula
\startformula
\MyRoot[3]{4n} \ne \MyRoot[3] {n}
\stopformula
\startformula
ll Goudy Regular,
> % it=name:Sorts Mill Goudy Italic,
> % ]
> % If you don't have the font above, try this:
> \setupbodyfont[heros]
>
> \setupbodyfont[mainfont,11pt]
>
> \definemeasure[CAindent][12pt]
> \setupindenting[yes,\measure{CAindent}]
>
> % Every chapter
[Sorts Mill Goudy] [
% tf=name:Sorts Mill Goudy Regular,
% it=name:Sorts Mill Goudy Italic,
% ]
% If you don't have the font above, try this:
\setupbodyfont[heros]
\setupbodyfont[mainfont,11pt]
\definemeasure[CAindent][12pt]
\setupindenting[yes,\measure{CAindent}]
% Every chapter
hen I get with
\definemeasure[CAindent][12pt]
\setupindenting[yes,\measure{CAindent}]
% Every chapter body text starts with a drop cap:
\usemodule[lettrine]
\setuplettrine[Lines=3,
Hang=.5,
Oversize=0,
Raise=0,
Findent=0pt,
his.
Hi Gerben,
this might be what you need:
% Every chapter body text starts with a drop cap:
\setupindenting[yes, medium]
\starttext
\chapter{Chapter}
\placeinitial So it was. \input knuth
\placeinitial So it was. \input knuth
\noindentation
\placeinitial So it was. \input kn
On 2021-07-18, Gerben Wierda wrote:
> PS. switching \kap and \bf has an interesting result, the first
> character of the words is not in bold. This did not happen with
> lettrine in mkii
I do not have an answer to your question, but I'd like to point out that
you can keep using lettrine with
With the following minimal example:
\definemeasure[CAindent][12pt]
% Every chapter body text starts with a drop cap:
\setupinitial[n=3,m=1,-\measure{CAindent}]]
\setupindenting[yes,\measure{CAindent}]
\starttext
\placeinitial S{\bf{\kap uppose we}} have a system for the approval of
loans. \input
#2%
{
\FramedText{{\cap\labeltext{chapter}}\space#1
\\
\bfc#2}
}
\unexpanded\def\processheadnumber#1%
{\getmarking[chapternumber]}
\setuphead
[chapter]
[style=\bfd,
align={flushleft,broad},
numbercommand=\processheadnumber,
command=\HeadTitle
Hi,
My first solution is incorrect ; with the second solution, I don't
understand why the first chapter is not numbered while the second is with
number 1.
Thanks.
Fabrice
\unexpanded\def\HeadTitle#1#2%
{
\FramedText{{\cap\labeltext{chapter}}\space#1
\\
\bfc#2}
}
\unexpanded
} \getmarking[chapternumber]
\stopsetups
\setupheadertexts
[]
[{\FramedText{{\cap\labeltext{chapter}\space\getmarking[chapternumber]}
\\
\bfc\getmarking[chapter]}}]
[]
[\FramedText{{\cap\labeltext{chapter}\space \getmarking[chapternumber]}
\\
\bfc\getmarking[chapter
On 7/9/2021 1:58 AM, Thangalin wrote:
This has come up before on the mailing list, but I was wondering if LMTX
has a more elegant solution than using a transparent/invisible capture
of the drop-cap.
Consider:
|\setupinitial[n=2, style=\tfd, location=text]
\setuphead[chapter][after
This has come up before on the mailing list, but I was wondering if LMTX
has a more elegant solution than using a transparent/invisible capture of
the drop-cap.
Consider:
\setupinitial[n=2, style=\tfd,
location=text]\setuphead[chapter][after={\placeinitial}]
\starttext
\chapter
Hello world
llowing: since last week (I guess) some math sympbols are not shown
>> either, such as \bigcap and \bigcup, even using version 2021.06.18 23:37. An
>> example is:
>> \starttext
>> $A \cup B = X \cap Y$
>> \startformula
>> A \bigcup B = X \bigcap Y
>> \stopfo
$A \cup B = X \cap Y$
\startformula
A \bigcup B = X \bigcap Y
\stopformula
\stoptext
it's a bug i introduced in the engine .. you can try a newer bin from:
https://dl.contextgarden.net/build/luametatex
Hi,
I don’t know whether the issue reported by Mikael S. is related to the
following: since last week (I guess) some math sympbols are not shown either,
such as \bigcap and \bigcup, even using version 2021.06.18 23:37. An example is:
\starttext
$A \cup B = X \cap Y$
\startformula
A \bigcup B
um 16:02:
>
> Hello,
> For the title of the chapters I use the following command.
>
> \unexpanded\def\HeadTitle#1#2%
>{\framed
> [frame=off,
>width=fit,
>align=flushleft]
>{\color[darkgray]{\tfxx\cap\bf\labeltext{chapter}}
> \bl
Fabrice Couvreur schrieb am 23.08.2020 um 16:02:
Hello,
For the title of the chapters I use the following command.
\unexpanded\def\HeadTitle#1#2%
{\framed
[frame=off,
width=fit,
align=flushleft]
{\color[darkgray]{\tfxx\cap\bf\labeltext{chapter}}
\blank#1\blank#2}
When I
Hello,
For the title of the chapters I use the following command.
\unexpanded\def\HeadTitle#1#2%
{\framed
[frame=off,
width=fit,
align=flushleft]
{\color[darkgray]{\tfxx\cap\bf\labeltext{chapter}}
\blank#1\blank#2}
When I compile my project, I have the label
Hello,
I'm attempting to typeset a short book using ConTeXt (current version:
2020.08.09 22:03).
EXAMPLE:
\setuplist[content][alternative=c]
\setuphead[title][alternative=middle,style=cap]
\setuphead[chapter][number=no]
\setuphead[section][sectionsegments=section]
\setuplist[section][width
w it crashes:
> >
> >
> \setuphead[chapter][alternative=middle,textstyle=\cap,numbercommand=\WORDS]
> >
> \setuphead[section][sectionsegments=section,align=middle,textstyle={\bf},conversion=R,numbercommand={\bf}]
> >
> \setuphead[subsection][numbercommand=,textstyle={\it},sectionseg
Jairo A. del Rio schrieb am 04.08.2020 um 06:07:
The following worked some days ago. Now it crashes:
\setuphead[chapter][alternative=middle,textstyle=\cap,numbercommand=\WORDS]
\setuphead[section][sectionsegments=section,align=middle,textstyle={\bf},conversion=R,numbercommand={\bf}]
\setuphead
-- Forwarded message -
De: Jairo A. del Rio
Date: lun., 3 de ago. de 2020 a la(s) 23:05
Subject: Re: [NTG-context] \emph not working in LMTX (bug?)
To: Wolfgang Schuster
The following worked some days ago. Now it crashes:
\setuphead[chapter][alternative=middle,textstyle=\cap
On 7/22/2020 5:43 AM, Otared Kavian wrote:
Hi Hans,
It seems that \cap is not anymore defined in the latest LMTX: the following
gives an error
\starttext
$A \cap B$
\stoptext
with current version: 2020.07.21 18:39.
Also, I would like to place a request about the reporting of errors: can we
Hi Hans,
It seems that \cap is not anymore defined in the latest LMTX: the following
gives an error
\starttext
$A \cap B$
\stoptext
with current version: 2020.07.21 18:39.
Also, I would like to place a request about the reporting of errors: can we get
back the nice reporting of errors we had
for ConTeXt's community to use it as a "new" or
an "updated" french interface, I may try to produce a 40~50 pages
documentation for the basics commands (during 2020 S2):
• \starttext
• \startchapter, \startsection, \starttitle, \startsubject,
\setuphead, \completecont
a number of you look at
this style
and cringe, but \cap{A.} I'm not looking for grammatical input, and
\cap{B.}
I'm intending this for a non-English language where the quotation dash
(though
still not most common) isn't as out of place.
\stopsection
\startsection[title=Desired rendering]
\quotedash
at
this style
and cringe, but \cap{A.} I'm not looking for grammatical input, and
\cap{B.}
I'm intending this for a non-English language where the quotation dash
(though
still not most common) isn't as out of place.
\stopsection
\startsection[title=Desired rendering]
\quotedash~Speech should
kern for one
character? The cap J in the font I am using is being set too
close to
the preceding characters and I would rather not insert a thinspace
before each. (Inserting a thinspace is sufficient, but finer control
is welcome.)
\definecharacterspacing[distantJ]
\setupcharacterspacing[distantJ
On 12/22/2019 21:34, Henri Menke wrote:
On 12/23/19 3:33 PM, Henri Menke wrote:
On 12/23/19 2:30 PM, Rik Kabel wrote:
On 12/22/2019 17:40, mf wrote:
Il 22/12/19 22:19, Rik Kabel ha scritto:
List,
Is there a way in ConTeXt to adjust the left-side kern for one
character? The cap J
On 12/23/19 3:33 PM, Henri Menke wrote:
On 12/23/19 2:30 PM, Rik Kabel wrote:
On 12/22/2019 17:40, mf wrote:
Il 22/12/19 22:19, Rik Kabel ha scritto:
List,
Is there a way in ConTeXt to adjust the left-side kern for one
character? The cap J in the font I am using is being set too close
On 12/23/19 2:30 PM, Rik Kabel wrote:
On 12/22/2019 17:40, mf wrote:
Il 22/12/19 22:19, Rik Kabel ha scritto:
List,
Is there a way in ConTeXt to adjust the left-side kern for one
character? The cap J in the font I am using is being set too close to
the preceding characters and I would rather
On 12/22/2019 17:40, mf wrote:
Il 22/12/19 22:19, Rik Kabel ha scritto:
List,
Is there a way in ConTeXt to adjust the left-side kern for one
character? The cap J in the font I am using is being set too close to
the preceding characters and I would rather not insert a thinspace
before each
Il 22/12/19 22:19, Rik Kabel ha scritto:
List,
Is there a way in ConTeXt to adjust the left-side kern for one
character? The cap J in the font I am using is being set too close to
the preceding characters and I would rather not insert a thinspace
before each. (Inserting a thinspace
On 12/23/19 10:19 AM, Rik Kabel wrote:
List,
Is there a way in ConTeXt to adjust the left-side kern for one
character?
No, kerns always come in pairs.
The cap J in the font I am using is being set too close to
the preceding characters and I would rather not insert a thinspace
before each
List,
Is there a way in ConTeXt to adjust the left-side kern for one
character? The cap J in the font I am using is being set too close to
the preceding characters and I would rather not insert a thinspace
before each. (Inserting a thinspace is sufficient, but finer control is
welcome
> small.
>
> \definesynonyms[term][terms][\deffull]
> \setupsynonyms[term][textstyle=cap]
> \placelistofterms
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maill
Space between the term (left column) and the definition (right column) is too
small.
\definesynonyms[term][terms][\deffull]
\setupsynonyms[term][textstyle=cap]
\placelistofterms
___
If your question is of interest
h actually I have never used the command completion mechanism.
>
> However I use extensively the autocompletion mechanism which is a way to
> key-in more rapidly some commands: for instance pressing alt-Cap-$ gives me
> \startformula
>
> \stopformula
>
> with the inserting poi
-Cap-$ gives me
\startformula
\stopformula
with the inserting point being between the two. The autompletion mechanism uses
a file named autocompletion.plist which can be easily edited and adapted by the
user (mine is adapted to the french keyboard layout AZERTY).
Indeed I can send you that file
}{rgb}{0.30196078431372547,0.30196078431372547,1}
\begin{tikzpicture}[line cap=round,line join=round,>=triangle 45,x=1cm,y=1cm]
\begin{axis}[
x=1cm,y=1cm,
axis lines=middle,
ymajorgrids=true,
xmajorgrids=true,
xmin=-12.678,
xmax=12.678,
ymin=-13.472,
ymax=8
}
\definecolor{zzttqq}{rgb}{0.6,0.2,0}
\definecolor{ududff}{rgb}{0.30196078431372547,0.30196078431372547,1}
\begin{tikzpicture}[line cap=round,line join=round,>=triangle 45,x=1cm,y=1cm]
\begin{axis}[
x=1cm,y=1cm,
axis lines=middle,
ymajorgrids=true,
xmajorgrids=true,
xmin=-12.678,
x
\doifelsemarking
or
\doifelsetext
Thanks, that worked. My final solution (just for the archive, it seems
to be more suitable than the solution in the wiki):
\define\CustomHeader{%
\cap{
\doifelsetext{\getmarking[chapter]}%
{Kapitel \getmarking[chapternumber]: \getmarking
On 1/12/2018 10:47 PM, Rik Kabel wrote:
When \setfirstline is used to set the first line of a paragraph in a
small-cap style, the line is mis-set. This does not occur with every
font and input, but occurs with most fonts and many inputs. The problem
does not seem to be awakened by other styles
When \setfirstline is used to set the first line of a paragraph in a
small-cap style, the line is mis-set. This does not occur with every
font and input, but occurs with most fonts and many inputs. The problem
does not seem to be awakened by other styles (emboldened, italicized
.
Best regards,
Dalyoung
%
\starttext
\startitemize[n]
\item Here is a line of math formulas: $\overline{A} = A$, $A' \subset A$, $A
\cap A' = \emptyset$ and $A^c$ is open.
\item list items one by one in a new line
\startitemize[n, packed, broad][stopper=,left=(, right
to have the
slanted version of the regular small cap glyphs.
My previous sample outputs slanted, but not from the small cap glyphs.
Which is the right way to get them?
Many thanks for your help,
Pablo
--
http://www.
I don’t know if anyone needs \Cap at all, but it’s broken:
\Cap{what}
renders
⋒what
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD
___
If your question is of interest
gt; A \arrow[r, "\phi" near start, "\psi" below, "\eta" near end] \NC B
> \stoptikzcd
>
> \starttikzcd
> T
> \arrow[drr, bend left, "x"]
> \arrow[ddr, bend right, "y"]
> \arrow[dr, dotted, "{(x,y)}" description] \N
Y \arrow[r, "g"] \NC Z
\stoptikzcd
\starttikzcd[column sep=tiny]
\NC \pi_1(U_1) \ar[dr] \ar[drr, "j_1", bend left=20]
\NC
\NC[1.5em] \NR
\pi_1(U_1\cap U_2) \ar[ur, "i_1"] \ar[dr, "i_2" below]
\NC
\NC \pi_
everal
points where stuff is capitalized or turned into caps+smallcaps or
pure smallcaps. My guess is that that should work either with
\WORD{Stuff}, \Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc,
and {\sc\lowercase{Stuff}}. (Not quite, it seems)
I'll use a commercial font called Calluna, bu
+smallcaps or pure
smallcaps. My guess is that that should work either with \WORD{Stuff},
\Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc, and
{\sc\lowercase{Stuff}}. (Not quite, it seems)
I'll use a commercial font called Calluna, but have added Linux Biolinum
O to the example for those who don't
everal
points where stuff is capitalized or turned into caps+smallcaps or
pure smallcaps. My guess is that that should work either with
\WORD{Stuff}, \Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc,
and {\sc\lowercase{Stuff}}. (Not quite, it seems)
I'll use a commercial font called Calluna, bu
everal
points where stuff is capitalized or turned into caps+smallcaps or
pure smallcaps. My guess is that that should work either with
\WORD{Stuff}, \Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc, and
{\sc\lowercase{Stuff}}. (Not quite, it seems)
I'll use a commercial font called C
+smallcaps or pure
smallcaps. My guess is that that should work either with \WORD{Stuff},
\Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc, and
{\sc\lowercase{Stuff}}. (Not quite, it seems)
I'll use a commercial font called Calluna, but have added Linux Biolinum
O to the example for those who don't
\mathcode`\^^M="2208 % \oplus
\mathcode`\^^N="0231 % \infty
\mathcode`\^^O="0140 % \partial
\mathcode`\^^P="321A % \subset
\mathcode`\^^Q="321B % \supset
\mathcode`\^^R="225C % \cap
\mathcode`\^^S="225B % \cup
\mathcode`\^^T="0238 % \forall
\mathcode`\^
ding or following an upright character
o small-cap letter preceding or following a non-whitespace character
There are some obvious patterns here (font style transitions, for
example) but the logic some seems less clear. Can we get a guide?
some day ... but your observations are quite ok ... the co
hree spaced are
used as a break)
* green with
o ς directly preceding another letter (perhaps other terminal
characters, my sample only has this)
o digit preceding *,* in index
o italic letter preceding or following an upright character
o small-cap letter prece
/setupdescriptions
Ah! Perhaps disambiguating would help unsuspecting users. So in
\setupdescriptions we have things like
style = normal bold slanted boldslanted type cap small... command
[i.e. style = name|command]
color = name
before = command
So in the explanation of the foregroundstyle key we could
*,
and aligned, can have multiple alignments, and gives this example:
\begin{align*}
K\approx G * Hi= j+k B\subset C\\
H\approx A_{0}*B_{0} i’= j’+k’ C= D\cap E\\
G\approx \coprod_{\alpha\in A} L_{\alpha} i’’=j’’+k’’ A= D \cup E
\end{align*}
which is typeset so that 'K\approx G * H
.
\starttext
\startformula
\startalign[m=3,distance=3em]
\NC K \NC \approx G * H\NC i \NC = j+k
\NC B \NC \subset C \NR
\NC H \NC \approx A_{0}*B_{0} \NC i' \NC = j'+k'
\NC C \NC = D\cap E \NR
\NC G \NC \approx \coprod_
this example:
\begin{align*}
K \approx G * H i= j+k B \subset C\\
H \approx A_{0}*B_{0} i’= j’+k’ C = D\cap E\\
G \approx \coprod_{\alpha\in A} L_{\alpha} i’’=j’’+k’’ A = D \cup E
\end{align*}
which is typeset so that 'K \approx G * H’ is one equation aligned on the ‘’
with the others below
=a, % a: XX (Xxx Xxx), b: Xxx Xxx (XX), command
%explaincommand=COMMAND#1#2, % to format it yourself
textstyle=normal,
synonymstyle=\cap]
\abbreviation [UN] {UN} {United Nations}
\abbreviation [UK] {UK} {United Kingdom}
\abbreviation [USA] {USA} {United States of America
%explaincommand=COMMAND#1#2, % to format it yourself
textstyle=normal,
synonymstyle=\cap]
\abbreviation [UN] {UN} {United Nations}
\abbreviation [UK] {UK} {United Kingdom}
\abbreviation [USA] {USA} {United States of America}
\abbreviation [UAE] {UAE} {United Arab Emirates
]
\starttext
\starttikzpicture[line width=0.3mm, =stealth, x=1cm, y=1cm,line cap=round,
line join=round]
\tikzstyle{epais}=[line width=0.5mm, line cap=butt]
\tikzstyle{tres epais}=[line width=0.8mm, line cap=butt]
\draw [tres epais] (6.02,3.63)-- (8.88,3.64);
\draw (6.02,3.63)-- (6.03,0.77);
\draw
and the \setff (better use
\feature) has no effect in this case.
For some reason I thought that they did both (supported all the small
cap glyphs as well as released a separate font).
But now I remembered that LM doesn't have bold small caps at all.
But apart from fixing the font: would creating some kind
a separate font for the small capitals and the \setff (better use
\feature) has no effect in this case.
For some reason I thought that they did both (supported all the small
cap glyphs as well as released a separate font).
But now I remembered that LM doesn't have bold small caps at all.
But apart from
\bf PERDU};
\foreach \x in {234,270,306,342}
\node [] at (\x:17.5mm) {\smiley};
\draw[darkgray,-latex,line width=4pt, line cap=round] (90:37mm) --
(90:26mm);
\stoptikzpicture}
\input knuth
\stoptext
___
If your question
Hi,
The \triangle operator is used for instance in the « symmetric difference » of
two subsets: if $E$ is a set and $A \subset E$, and $B \susbet E$, then one
defines
\startformula
A \triangle B := (A \cup B) \setminus (A \cap B).
\stopformula
Then the mapping $(A,B) \mapsto A \triangle B
.
On considère les événements suivants :
\startitemize[2]
\item F : \quotation{la personne choisie est une femme} ;
\item C : \quotation{la personne choisie est un cadre}.
\stopitemize
\startitemize[a][stopper=),style=bold]
\item Définir par une phrase les événements \math{\overline{C}}, \math{F
\cap C
\stoptext
All vowels are fine, but the i is a dotted small cap i. The regular
small cap i is defined as i.sc (and the dotted small cap i is defined
as i.sc too). But FontForge applies both c2sc and smcp substitutions
fine.
Is there any way to solve this?
Many thanks for your help,
Pablo
--
http
{\addfeature[capstosc] AEIOU}
\sc aeiou
\stoptext
All vowels are fine, but the i is a dotted small cap i. The regular
small cap i is defined as i.sc (and the dotted small cap i is defined
as i.sc too). But FontForge applies both c2sc and smcp substitutions
fine.
It seems to be a regression
On 02/17/2014 08:46 PM, Jan Tosovsky wrote:
On 2014-02-17 Pablo Rodriguez wrote:
I have noticed that ConTeXt (beta from 2014.02.14 17:07) has a problem
with Palatino Linotype.
[...]
All vowels are fine, but the i is a dotted small cap i. The regular
small cap i is defined as i.sc
of the italic or slanted glyph makes
the right side-bearing larger at the baseline. The issue with italic
correction is mainly with ascenders or at the cap height, but I think it
isn’t at the base line (or the descenders). Because of that I think it
is important to disable italic correction before
at the base line, since
at the glyph base, the inclination of the italic or slanted glyph makes
the right side-bearing larger at the baseline. The issue with italic
correction is mainly with ascenders or at the cap height, but I think it
isn’t at the base line (or the descenders). Because of that I
-bearing larger at the baseline. The issue with italic
correction is mainly with ascenders or at the cap height, but I think it
isn’t at the base line (or the descenders). Because of that I think it
is important to disable italic correction before points and commas.
The sample shows the issue
On 1/24/2014 5:54 PM, Alexey Kryukov wrote:
Hi,
If I attempt to insert a drop cap after a heading while the paragraph
indentation is enabled, I get the following effect: all lines the drop
cap spans except the first one (e. g. second and third in case of n=3)
get an additional indent, equal
1 - 100 of 348 matches
Mail list logo
