] [alegreya]
\definefontsynonym[AlegreyaSans-Regular][name:AlegreyaSans-Regular]
\definefontsynonym[AlegreyaSans-Italic][name:AlegreyaSans-Italic]
\definefontsynonym[AlegreyaSans-Caps][name:AlegreyaSansSC-Regular]
\definefontsynonym[AlegreyaSans-ItalicCaps][name:AlegreyaSansSC-Italic
[sans] [alegreya]
\definefontsynonym[AlegreyaSans-Regular][name:AlegreyaSans-Regular]
\definefontsynonym[AlegreyaSans-Italic][name:AlegreyaSans-Italic]
\definefontsynonym[AlegreyaSans-Caps][name:AlegreyaSansSC-Regular]
\definefontsynonym[AlegreyaSans-ItalicCaps][name:AlegreyaSansSC-Italic
exgyretermes-regular*forceno]
% \addfeature{forceyes}
With
\definedfont[texgyretermes-regular*forceyes]
active we get the expected result: small caps plus some negative squeeze (=
spread in this case).
With
\definedfont[texgyretermes-regular*forceno]
\addfeature{forceyes}
active we get an *unexpected
-it]
\stoptypescript
As is well known, \sc selects the small caps only from the Serif font, not from
SerifBold etc. But MyFont has smallcaps for every style. So in the typescript
we make that explicit and apply the smcp=yes fontfeature to SerifCapsBold etc.
But this does not work: \sc still only applies
-BoldIt] %
[features=myfont-it]
\stoptypescript
As is well known, \sc selects the small caps only from the Serif font,
not from SerifBold etc. But MyFont has smallcaps for every style. So
in the typescript we make that explicit and apply the
smcp=yes fontfeature to SerifCapsBold etc
-it]
\stoptypescript
As is well known, \sc selects the small caps only from the Serif font, not from
SerifBold etc. But MyFont has smallcaps for every style. So in the typescript
we make that explicit and apply the smcp=yes fontfeature to SerifCapsBold etc.
But this does not work: \sc still only
][
mode=node,
ccmp=yes, % character composition
liga=yes, tlig=yes, % ligatures
pnum=yes,
cpsp=yes, % capital spacing
kern=yes,
language=dflt,
protrusion=quality,
expansion=quality,
]
\definefontfeature[smallcaps][ % use with \addff
smcp=yes, % smallcaps
% c2sc=yes, % caps
On 4/3/23 09:07, Peter Münster via ntg-context wrote:
> Hi,
>
> I'm quite sure, that this worked some time ago with the standard font (LM):
I had the same impression, Peter.
But LM fonts don‘t have the OT feature smcp:
\setuppapersize[A8]
\starttext
\doloopoverlist{lm, pagella, termes,
On 4/3/2023 9:07 AM, Peter Münster via ntg-context wrote:
Hi,
I'm quite sure, that this worked some time ago with the standard font (LM):
\setff{smallcaps} Normal and \bf bold Small Caps.
(See also https://wiki.contextgarden.net/Bold_small_caps).
But it does not work with the latest ConTeXt
Hi,
I'm quite sure, that this worked some time ago with the standard font (LM):
\setff{smallcaps} Normal and \bf bold Small Caps.
(See also https://wiki.contextgarden.net/Bold_small_caps).
But it does not work with the latest ConTeXt version.
How could I get bold small caps with the latest
typescript for Roboto:
\definefontfeature[robotofeatures][
mode=node,
ccmp=yes, % character composition
liga=yes, tlig=yes, % ligatures
pnum=yes,
cpsp=yes, % capital spacing
kern=yes,
language=dflt,
protrusion=quality,
expansion=quality,
]
\definefontfeature[smallcaps][ % us
hat happen to be used for caps) .. at t he
> cost of runtime i'll add a check against overwriting these
Many thanks for the fix, Hans.
Pablo
___
If your question is of interest to others as well, please add an entry
]}]
\starttext
\section{Just text}
{\feature[+][section]Just text}
\stoptext
LMTX outputs no small caps and it fallbacks to Noto Emoji. LuaTeX gives
the right output.
Am I missing something or have I hit a bug in LMTX?
more a bug in your approach: you specify a range where you also
overwrite
LMTX outputs no small caps and it fallbacks to Noto Emoji. LuaTeX gives
the right output.
Am I missing something or have I hit a bug in LMTX?
Many thanks for your help,
Pablo
___
If your question is of interest
variable fonts,
axes are only accesible using their name (not their tag) in the axis
section (not in the design axis section), aren't they?
And each font feature requires a new font instance (unlike other font
features such as small caps or many other OpenType features), doesn't it?
> btw, we don't chec
dtldocumentasanst dtldocumenta dtldocumentasanst
DTL Documenta Sans T Regular.otf
dtldocumentasanstcaps dtldocumenta dtldocumentasanstcaps
DTL Documenta Sans T Caps Regular.otf
dtldocumentasanstcapsregular dtldocumenta dtldocumentasanstcaps
DTL Documenta Sans T Caps
Am 25.05.22 um 22:23 schrieb Stefan Nedeljkovic via ntg-context:
Dear list,
A quick question about a font that has a separate file for small caps. I
have the following:
\starttypescript [sans] [dtl-documenta-sans-t]
\definefontsynonym[Sans] [name:dtldocumentasanst][features=default
Dear list,
A quick question about a font that has a separate file for small caps. I
have the following:
\starttypescript [sans] [dtl-documenta-sans-t]
\definefontsynonym[Sans] [name:dtldocumentasanst][features=default]
\definefontsynonym[SansItalic]
[name:dtldocumentasanstitalic][features
typeface [custodia] [rm] [serif] [custodia]
[default]
> >
> >
> >
> >
> >
> > \usetypescript[custodia][uc]
> >
> > \setupbodyfont[custo
; >
>> > > tf=Serif sa 1,
>> > >
>> > > it=SerifItalic sa 1,
>> > >
>> > > md=SerifMedium sa 1,
>> > >
>> > > mi=SerifMediumItalic sa 1,
>> > >
>> > > bf=SerifBold sa 1,
ic sa 1,
> > >
> > > md=SerifMedium sa 1,
> > >
> > > mi=SerifMediumItalic sa 1,
> > >
> > > bf=SerifBold sa 1,
> > >
> > > bi=SerifBoldItalic sa 1]
> > >
> >
>
> Regular Hamburgerfons,
>
> {\it Italic Hamburgerfons},
>
> {\md Medium Hamburgerfons},
>
> {\mi Medium Italic Hamburgerfons},
>
> {\bf Bold Hamburgerfons},
>
> {\bi Bold Italic Hamburgerfons},\\
>
>
>
,
> >
> > mi=SerifMediumItalic sa 1,
> >
> > bf=SerifBold sa 1,
> >
> > bi=SerifBoldItalic sa 1]
> >
> > \stoptypescript
> >
> >
> >
> > \definetypeface [custodia] [rm] [serif] [custodia] [default]
> >
> >
> >
[custodia,rm,10pt]
\starttext
Regular Hamburgerfons,
{\it Italic Hamburgerfons},
{\md Medium Hamburgerfons},
{\mi Medium Italic Hamburgerfons},
{\bf Bold Hamburgerfons},
{\bi Bold Italic Hamburgerfons},\\
\setff{smallcaps}{Small Caps Hamburgerfons},
\setff{smallcaps}{\it Small Caps Italic
,10pt]
\starttext
Regular Hamburgerfons,
{\it Italic Hamburgerfons},
{\md Medium Hamburgerfons},
{\mi Medium Italic Hamburgerfons},
{\bf Bold Hamburgerfons},
{\bi Bold Italic Hamburgerfons},\\
\setff{smallcaps}{Small Caps Hamburgerfons},
\setff{smallcaps}{\it Small Caps Italic
understand that lwc can have
problems with a text whose chapters have capital letters and small caps
on the first page with less text than on the following pages; with long
quotations that involve paragraphs of different layout and separated
from the main text; with more than one footnot
t;foo"] = "oof"
and such and there is in the next version also an exception mechanism
that permits clone a transliteration and add exceptions
There is another issue if one wants to use a dropcap and the rest of
that first word, and several following words are to be ty
for Serbian cyrillic and latin.
There is another issue if one wants to use a dropcap and the rest of
that first word, and several following words are to be typeset in small
caps.
If that first letter is Љ (or other two letters that transliterate as
digraphs), then the second letter of the digraph
Use alt + hjkl to resize windows
nnoremap :resize -2
nnoremap :resize +2
nnoremap :vertical resize -2
nnoremap :vertical resize +2
" I hate escape more than anything else
inoremap jk
inoremap kj
" Easy CAPS
inoremap viwUi
nnoremap viwU
" TAB in general mode wi
contain small
caps (in place of lowercase characters) and old style
figures (in place of digits), and other variant glyphs and
additional ligatures (usually the font name contains OsF,
SC, Alt, or Exp). Sometimes these are not allocated to a
Unicode point, but only identified by name (e.g
Often there are additional font files which contain small
caps (in place of lowercase characters) and old style
figures (in place of digits), and other variant glyphs and
additional ligatures (usually the font name contains OsF,
SC, Alt, or Exp). Sometimes these are not allocated to a
Unicode point
On 10/3/2021 1:41 AM, Bruce Horrocks via ntg-context wrote:
In the test suite, the file fonts/features-005.tex is failing for me on latest
lmtx. All three items appear the same each time i.e. no small caps and no
old-style digits on the second and third.
<http://www.pragma-ade.com/cont
In the test suite, the file fonts/features-005.tex is failing for me on latest
lmtx. All three items appear the same each time i.e. no small caps and no
old-style digits on the second and third.
<http://www.pragma-ade.com/context/latest/cont-tst.zip>
Can anyone else reproduce this,
e any generic way
of detecting a leading quotation mark while keeping initial caps on the
first character?
i'll send you something off-list to test
-
Hans Hagen | PRAGM
nts; small minds
> discuss people.
> \stoptext
>
> However, the leading quotation mark is gobbled. Is there any generic way of
> detecting a leading quotation mark while keeping initial caps on the first
> character?
>
Not really generic, and maybe not what you want, but there i
while keeping initial caps on the first
character?
Thank you!
___
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/ntg-co
% surname to small caps in list
\startsetups \s!btx:\s!list:\s!author:inverted
\fastsetup{\s!btx:\s!list:\s!author:concat}
\ifx\currentbtxvons\empty \else
\texdefinition{\s!btx:\s!cite:\s!author:\s!de}
\doifnotmode {\s!btx:\s!de} {
\currentbtxvons
caps (e.g. KNUTH, Donald). If I wanted to
change the whole name to small caps I’d do something like this:
\btxdoif {author} {
{\sc \btxflush{author}}
\btxperiod
}
How do I change the “font” of the surname only? Can this be done by
redefining a TeX macro (like in BibLaTeX’s
res:
> >
> > * Its title should appear in the ToC, but its number should never be
> > printed in the ToC or in the text.
> > * It should always start on an odd page.
> > * Its text should be in a larger size than the text of the body, set
> >
ToC, but its number should never be
printed in the ToC or in the text.
* It should always start on an odd page.
* Its text should be in a larger size than the text of the body, set
in all caps, and set with extra letterspacing.
* Most importantly, the title of the heading should appear
ts number should never be
> > printed in the ToC or in the text.
>
> number=no.
>
> > * It should always start on an odd page.
>
> This is the default for \setuphead[part] (only noticeable in doublesided
> documents).
>
> > * Its text should be in a larger
doublesided
documents).
> * Its text should be in a larger size than the text of the body, set
> in all caps, and set with extra letterspacing.
style is the right option there.
> * Most importantly, the title of the heading should appear on its own
> page wi
e ToC or in the text.
- It should always start on an odd page.
- Its text should be in a larger size than the text of the body, set in
all caps, and set with extra letterspacing.
- Most importantly, the title of the heading should appear on its own
page without a header or footer. The text of t
TeXt Development Team",
license = "see context related readme files"
}
-- A BachoTeX 2013 experiment, probably not that useful. Eventually I used a
simpler
-- more generic example. I'm sure no one ever notices of even needs this code.
--
-- As a follow up on a question by Alan about s
body text starts with a drop cap:
> \defineinitial[normal][
> n=3,
> m=1,
> distance=18pt, % <== Add this
> state=start
> ]
>
> % Special case: drop cap starting with a quote
> \defineinitial[quote][
> n=3,
> m=2,
> distance=13pt,
&
initials may need special adjustments, depending on the font
\defineinitial[Q][
voffset=2\lineheight,
n=3,
m=1,
distance=18pt,
state=start
]
% Full first line in small caps
\definefirstline[smallcapsfirstline][
alternative=line,
style=smallcaps,
]
% First n words in small caps
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]
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!
net/Simple_Typescript_Example>
Not meant as a criticism - just a naive question from someone who is puzzled.
Yes, you could also abuse \sc for another style.
Small caps are a bit special though, nowadays they’re often contained in fonts
and you address them via OpenType features.
aive question from someone who is puzzled.
Yes, you could also abuse \sc for another style.
Small caps are a bit special though, nowadays they’re often contained in fonts
and you address them via OpenType features.
Hraban
__
m srb trk
> smcp cyrl dflt
> dflt dflt
> grek dflt
> latn dflt
>
> so just don't specify a script
I’m afraid that this doesn’t get the Greek small caps (either with
2020.12.30 16:45 o
On 1/5/2021 6:53 PM, Pablo Rodriguez wrote:
On 1/5/21 5:11 PM, Hans Hagen wrote:
On 1/5/2021 4:46 PM, Pablo Rodriguez wrote:
[...]
If script=auto, current latest (2021.01.05 10:45) works fine. If it is
set to Latin (as above), I don’t get small caps.
Besides the potential issue in ConTeXt, I
On 1/5/21 5:11 PM, Hans Hagen wrote:
> On 1/5/2021 4:46 PM, Pablo Rodriguez wrote:
>> [...]
>> If script=auto, current latest (2021.01.05 10:45) works fine. If it is
>> set to Latin (as above), I don’t get small caps.
>>
>> Besides the potential issue in ConTeX
]
\starttext
\feature[+][onumsmcp]\tfb abc123ABC
\stoptext
If script=auto, current latest (2021.01.05 10:45) works fine. If it is
set to Latin (as above), I don’t get small caps.
Besides the potential issue in ConTeXt, I think that "script=auto" may
be safer than "script=latn"
If script=auto, current latest (2021.01.05 10:45) works fine. If it is
set to Latin (as above), I don’t get small caps.
Besides the potential issue in ConTeXt, I think that "script=auto" may
be safer than "script=latn". Or am I taking too much for granted?
Many thanks for your
rom 64s to 58s in one of the
documents I have.
Unrelated to this, I’m afraid that the current latest doesn’t like my
definition of small caps and I don’t get them (either with or without
experiments) in many documents.
But I know I have to provide a sample that displays the issue.
Many thanks for t
Hi Joaquín,
Actually it depends on the font you are using, but on th eother hand it seems
that \Caps is broken in LMTX.
The following gives a correct result in mkiv but results in an error in LMTX:
\setupbodyfont[lucidaot]
\starttext
Test {\sc Test} {\Caps Test}
{\smallcaps Test}
\meaning
a file that I used to compile well, an error
is generated because the \Caps macro is not recognized.
I can't get the desired effect with \sc, it has to be with \Caps.
I have tried to compile it with LMTX but there too is considered that
\Caps is an undefined control sequence.
--
Joaquín Ataz
conflict: regular
texgyrepagella ... texgyrepagellaregular
texgyrepagella-regular.otf conflict: regular
So three questions:
1. Does Tex Gyre Pagella Math contain everything I need for my body font
(ignore Arial - I use that for drop caps and a few other things and it
works as it should
... texgyrepagellaregular
texgyrepagella-regular.otf conflict: regular
So three questions:
1. Does Tex Gyre Pagella Math contain everything I need for my body font
(ignore Arial - I use that for drop caps and a few other things and it
works as it should)?
2. If so, do I still need
I have come up with part answers to my two questions. The remaining
unanswered question is in the final line.
The question I can now answer, after some experimenting, is how to
ensure that I can use small caps as part of the Alegreya family when I
need to do so. This is how my definitions now
.*
This time, realizing I needed to also use small caps, and because
AlegreyaSC of various weights is available in my system, you can see how
I thought I would need to add it into the definitions below - in the
second line.
Then in the body of the document where I needed small caps, I did as
follows
\setfirstline is
not applied at all, i.e., there are no small caps. If I comment out the
first \setfirstline, then the second one does produce small caps, but
again, a whole paragraph is set in small caps, not just the first line.
$ context --version
mtx-context | ConTeXt Process Management 1.03
mtx
s), but after first tests I found flaws:
>> – Numbers are a bit too dark; table numbers look a bit too big, oldstyle
>> numbers a bit too small.
>> – Small caps are lacking accented vowels including umlauts.
>> – Cyrillic is missing Kyrgyz/Kazakh letters (i.e. Cyrillic e
, oldstyle
> numbers a bit too small.
> – Small caps are lacking accented vowels including umlauts.
> – Cyrillic is missing Kyrgyz/Kazakh letters (i.e. Cyrillic extended).
> – Kerning is not yet perfect.
> – Accents sit a bit too close on the letters.
> – Swash capitals don’t
h repertoire
(Latin, poly Greek, Cyrillic, Byzantine/Greek music symbols, math and other
symbols), but after first tests I found flaws:
– Numbers are a bit too dark; table numbers look a bit too big, oldstyle
numbers a bit too small.
– Small caps are lacking accented vowels including umlauts.
– Cyrilli
> style={\sca},
>
> What is the correct substitute for that?
Do your titles wear garb?
(SCA = Society for Creative Anachronism)
;D
HR
___
If your question is of interest to others as well, please add an entry to
On 2/17/2020 4:48 PM, Mikael P. Sundqvist wrote:
style={\sca},
\tf\smallcaps
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038
> Hi,
> > >
> > > One can easily enable small caps when using lucida, see the old
> mail
> > > https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
> > >
> > > Could this be added to the type script
On 2/15/2020 10:02 PM, Mikael P. Sundqvist wrote:
On Sat, Feb 15, 2020 at 9:50 PM Hans Hagen <mailto:j.ha...@xs4all.nl>> wrote:
On 2/15/2020 4:34 PM, Mikael P. Sundqvist wrote:
> Hi,
>
> One can easily enable small caps when using lucida, see the old
On 2/15/2020 4:34 PM, Mikael P. Sundqvist wrote:
Hi,
One can easily enable small caps when using lucida, see the old mail
https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
Could this be added to the type script file?
best use \smallcaps or somethign equivalent
Hi,
One can easily enable small caps when using lucida, see the old mail
https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
Could this be added to the type script file?
/Mikael
___
If your question
\definefontsynonym [Charis-Bold][file:CharisSIL-B.ttf]
\definefontsynonym [Charis-BoldItalic] [file:CharisSIL-BI.ttf]
\definefontsynonym [Charis-Roman-Caps] [Charis-Roman]
\stoptypescript
\starttypescript [serif] [charis] [name]
\setups[font:fallback:serif
iling list for ConTeXt users
Subject: [NTG-context] Coding for new Unicode characters
Date: Sun, 29 Dec 2019 12:52:18 +1300
Mailer: Evolution 3.32.4
Organization: Indica et Buddhica
I am using Latin Modern Roman to typeset some proceedings and need the
following characters in regular, italic, and
I am using Latin Modern Roman to typeset some proceedings and need the
following characters in regular, italic, and small caps:
Character: ṉ U+1E49
Name: LATIN SMALL LETTER N WITH LINE BELOW
Character: Ṉ U+1E48
Name: LATIN CAPITAL LETTER N WITH LINE BELOW
Character: ḻ U+1E3B
Name: LATIN SMALL
the exact command line parameters for pandoc that set
>> the toc flag to true.
>>
>> An equivalent method will be to control this using a ConTeXt mode.
>> Redefining \completecontent to \empty seems too drastic.
>>
>> Aditya
>>
>>
>>
>> -
e-ID: <857b6e26-0b65-c2a4-6569-e664f0111...@gmx.es>
> Content-Type: text/plain; charset=utf-8
>
> Hi Wolfgang,
>
> I have two requests to be implemented in \definefontfamily.
>
> The first one is that is able to load fonts not defined as entries in
> the font databa
this works
\stoptext
The second one would be to allow method=uppercase to
\definefallbackfamily, so it could be used to fake small caps (such as
in https://mailman.ntg.nl/pipermail/ntg-context/2018/092878.html.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
Hi Wolfgang,
as I reported the issue with the fonts and LMTX, I remembered two
suggestions I wanted to post here.
The first one is enabling the use of "method=uppercase" in
\definefallbackfamily (to get fake caps, such as in
https://mailman.ntg.nl/pipermail/ntg-context/2018/0
uippercase unicode properties so it's safe
In that case i'm afraid we'd have a scaled down, embolded, uppercase
version of the font, not a small-caps variant with a consistent thickess
of the glyphs.
no, it more 'clever'
I think i should specify only the lower case letters' ranges.
n
uppercase
version of the font, not a small-caps variant with a consistent thickess
of the glyphs.
I think i should specify only the lower case letters' ranges.
Massimiliano
___
If your question is of interest to othe
elax regular,
italic,slanted,bold,bolditalic,boldslanted,caps,
italiccaps,slan
\syst_helpers_do_process_comma_list ...m_gobble #1
,]\relax \global
\advance ...
\simplefonts@definetextfont ...rocesscommacommand
\syst_helpers_do_process_comma...
\relax regular,
italic,slanted,bold,bolditalic,boldslanted,caps, italiccaps,slan
\syst_helpers_do_process_comma_list ...m_gobble #1
,]\relax \global \advance ...
\simplefonts@
relax regular,
italic,slanted,bold,bolditalic,boldslanted,caps, italiccaps,slan
\syst_helpers_do_process_comma_list ...m_gobble #1
,]\relax \global \advance ...
\simplefonts@definetextfont ...rocesscommacommand
embold feature (similar to the slanted
font feature) that fakes the bold font with
\starteffect[both]...\stopeffect and it doesn’t strecht the font?
much is possible if i can motivate myself
Good to know in order to propose new features :-).
Hm.
Fake bold / slanted / small caps / of a bas
be possible to add a embold feature (similar to the slanted
>>>> font feature) that fakes the bold font with
>>>> \starteffect[both]...\stopeffect and it doesn’t strecht the font?
>>>
>>> much is possible if i can motivate myself
>
> Good to kn
,10pt]
\starttext
Blabla
$p'(1)$
{\sc Blabla}
\stoptext
On Sat, 2018-03-03 at 15:13 +0100, Eric Detrez wrote:
> I don't find any hint to my problem.
> I bought Lucida fonts from Tugboat.
> I want to get small caps AND primes (P'(x))
> It seem I can't have both
> When I use
&
\setupbodyfont[lucidaot]
\starttext
Blabla
{\feature[+][f:smallcaps]Blabla}
{\setsmallcaps Blabla}
\stoptext
Wolfgang
Eric Detrez <mailto:i...@eric-detrez.fr>
3. März 2018 um 15:13
I don't find any hint to my problem.
I bought Lucida fonts from Tugboat.
I want to get smal
I don't find any hint to my problem.
I bought Lucida fonts from Tugboat.
I want to get small caps AND primes (P'(x))
It seem I can't have both
When I use
\usetypescript[lucida]
\setupbodyfont[lucidaot,10pt,rm]
I don't have smallcaps
When I use
\usetypescript[lucida]
\setupbodyfont
txrenderingdefinitions
>
> You define two different sets of definitions: one for the citations in the
> text (in the form \startsetups btx:cite:XXX), one for the list of references
> (in the form \startsetups btx:list:XXX). Here you can make all the formatting
> you want: a
can make all the formatting you want:
article name in red, author name for articles in small caps, journal name in
3D, whatever. Again, just look at publ-imp-apa.mkvi and try to understand how
it works; it’s not that difficult.
> The second question is: how can one write a file
(emboldened, italicized).
\definefirstline[SC][alternative=line,style=\setfontfeature{smallcaps}]%
or =\sc
\definefirstline[BD][alternative=line,style=bold]
\definefirstline[IT][alternative=line,style=italic]
\setupbodyfont[termes,11pt]% requires font with small caps
).
\definefirstline[SC][alternative=line,style=\setfontfeature{smallcaps}]%
or =\sc
\definefirstline[BD][alternative=line,style=bold]
\definefirstline[IT][alternative=line,style=italic]
\setupbodyfont[termes,11pt]% requires font with small caps
\starttext
\setfirstline[SC
tended to:
\starttext
\setff{smallcaps} Normal and \bf bold Small Caps.
{\sc Normal and \bf bold Small Caps.}
\stoptext
doesn't produce bold small caps - see the attached files.
So - how to get bold small caps?
at least you need a bold font that has smallcaps ...
how do I get list of fonts
Hello,
I'm trying to typeset some text in bold + smallcaps.
But even the sample on wiki:
http://wiki.contextgarden.net/Bold_small_caps
extended to:
\starttext
\setff{smallcaps} Normal and \bf bold Small Caps.
{\sc Normal and \bf bold Small Caps.}
\stoptext
doesn't
Henning Hraban Ramm <mailto:te...@fiee.net>
8. November 2017 um 10:57
Ahoi,
I’m working on ePubs again and need a bit more information in the
exported xml.
E.g. I defined my own small caps macro:
\def\SC#1{{\sc\lowercase{#1}}}
to be able to say \SC{ISO} instead of changing ever
tyle option:
\setupbackend[export=yes]
\definehighlight[read][style=\word\sc]
\starttext
\starthighlight[read] ROT ROT ROT\stophighlight
\stoptext
Other approach would be to use your own CSS file:
.read { text-transform: lowercase; font-variant: small-caps; }
In any case, you ne
Ahoi,
I’m working on ePubs again and need a bit more information in the exported xml.
E.g. I defined my own small caps macro:
\def\SC#1{{\sc\lowercase{#1}}}
to be able to say \SC{ISO} instead of changing everything into lowercase like
{\sc iso}.
(I also tried OpenType features, but those were
Am 2017-09-23 um 21:28 schrieb Thomas A. Schmitz <thomas.schm...@uni-bonn.de>:
>> The result of \infull is always in small caps, and I don’t like that. I
>> couldn’t find its definition in the source* nor a setup command.
>
> It's defined in strc-syn.mkiv,
Am 2017-09-23 um 21:28 schrieb Thomas A. Schmitz <thomas.schm...@uni-bonn.de>:
>> The result of \infull is always in small caps, and I don’t like that. I
>> couldn’t find its definition in the source* nor a setup command.
>
> It's defined in strc-syn.mkiv,
1 - 100 of 725 matches
Mail list logo
