Am 27.03.2025 um 23:11 schrieb Rik Kabel:
On 2025-03-27 13:03, Alan Caruanambo wrote:
\sc gets different results when changing the default font. See
attached PDF.
\starttext
\startbuffer
{\sc Use CaPs and SmAll caps (preserve casing)}
\stopbuffer
\getbuffer
\setupbodyfont[dejavu
On 2025-03-27 13:03, Alan Caruanambo wrote:
\sc gets different results when changing the default font. See
attached PDF.
\starttext
\startbuffer
{\sc Use CaPs and SmAll caps (preserve casing)}
\stopbuffer
\getbuffer
\setupbodyfont[dejavu] \getbuffer \crlf
\setupbodyfont[ibmplex,rm
\sc gets different results when changing the default font. See attached PDF.
\starttext
\startbuffer
{\sc Use CaPs and SmAll caps (preserve casing)}
\stopbuffer
\getbuffer
\setupbodyfont[dejavu] \getbuffer \crlf
\setupbodyfont[ibmplex,rm] \getbuffer
\stoptext
sc-test.pdf
Description
On 4/3/24 07:16, Peter Münster wrote:
> On Tue, Apr 02 2024, Andres Conrado Montoya wrote:
>
>> You shouldn't run context as root in any case.
>
> I don’t run context as root. But I need to erase the cache in
> /opt/context/tex/texmf-cache as root, because the user doesn’t have the
> permission to
On Tue, Apr 02 2024, Andres Conrado Montoya wrote:
> You shouldn't run context as root in any case.
I don’t run context as root. But I need to erase the cache in
/opt/context/tex/texmf-cache as root, because the user doesn’t have the
permission to do that.
--
Peter
__
You shouldn't run context as root in any case. But glad it worked.
El mar, 2 abr 2024 a las 15:34, Peter Münster () escribió:
> On Tue, Apr 02 2024, Pablo Rodriguez via ntg-context wrote:
>
> > mtxrun --script cache --erase && mtxrun --generate
>
> Thanks. It did not work after doing it as root
On Tue, Apr 02 2024, Pablo Rodriguez via ntg-context wrote:
> mtxrun --script cache --erase && mtxrun --generate
Thanks. It did not work after doing it as root, but then I saw, that
there is also a cache in the user home-directory, so I’ve done it as the
user too, and now it works.
--
On 4/2/24 21:23, Mikael Sundqvist wrote:
> On Tue, Apr 2, 2024 at 9:16 PM Peter Münster wrote:
>> [...]
>> TIA for any hints,
>
> Hans wrote in his email:
> -- If you have troubles (crash) you need to wipe the cache due to a
> change in lua bytecode storage (no easy way to catch it).
>
> Did you d
Hi,
On Tue, Apr 2, 2024 at 9:16 PM Peter Münster wrote:
>
> Hi,
>
> With ConTeXt version 2024.04.01, the \sc command produces an error:
>
> fonts > preloading latin modern fonts (second stage)
> fonts > 'fallback modern rm 12pt' is loaded
Hi,
With ConTeXt version 2024.04.01, the \sc command produces an error:
fonts > preloading latin modern fonts (second stage)
fonts > 'fallback modern rm 12pt' is loaded
pages > flushing realpage 1, userpage 1, subpage 1
close source>
] [\setsmallcaps] [\setsmallcaps]
:
\unexpanded\def\setsmallcaps{\doaddfeature{f:smallcaps}}
So on the wiki we should say that \sc is a deprecated/legacy command
that no longer makes sense in an opentype-features world. New users
should no longer use it.
It depends on the font, e.g. Latin Modern still
}}
So on the wiki we should say that \sc is a deprecated/legacy command
that no longer makes sense in an opentype-features world. New users
should no longer use it.
It depends on the font, e.g. Latin Modern still requires \sc because it
provides a separate file for smallcaps but no smcp feature
Hamid,Idris schrieb am 19.08.2023 um 20:36:
Many thanks. From font-pre.mkiv:
\definealternativestyle [\v!smallcaps] [\setsmallcaps] [\setsmallcaps]
:
\unexpanded\def\setsmallcaps{\doaddfeature{f:smallcaps}}
So on the wiki we should say that \sc is a deprecated/legacy command
that no longer
Many thanks, Pablo. Yes, you are right. As mentioned in the reply to Wolfgang,
will edit the wiki to reflect the legacy\deprecated status of \sc.
As for grep: Normally I use the nice "find in files" feature of Notepad++ -)
Am editing the wiki and have moved the original link to the mo
Many thanks. From font-pre.mkiv:
\definealternativestyle [\v!smallcaps] [\setsmallcaps] [\setsmallcaps]
:
\unexpanded\def\setsmallcaps{\doaddfeature{f:smallcaps}}
So on the wiki we should say that \sc is a deprecated/legacy command that no
longer makes sense in an opentype-features world. New
On 8/19/23 16:03, Hamid,Idris wrote:
> [...]
> Yes, there is an easy workaround:
>
> \definefontfeature[smallcaps][smcp=yes]
Hi Idris,
just a minor comment.
This is already defined in lines 96-99 of font-pre.mkxl:
\definefontfeature
[smallcaps]
[always]
[smcp=yes]
And also in lines 7
Hamid,Idris schrieb am 19.08.2023 um 16:03:
Dear gang,
Consider the following typescript template:
\definefontfeature
[myfont-tf-sc]
[mode=node,script=latn,language=dflt,trep=no,
protrusion=quality,expansion=quality,
compose=yes,combine=yes,tlig=yes,
kern=yes,liga=yes,onum=yes
Dear gang,
Consider the following typescript template:
\definefontfeature
[myfont-tf-sc]
[mode=node,script=latn,language=dflt,trep=no,
protrusion=quality,expansion=quality,
compose=yes,combine=yes,tlig=yes,
kern=yes,liga=yes,onum=yes,cpsp=yes,smcp=yes, % smcp activie
trnsl=force
Hi font wizards,
I’m trying to get rid of \sc and \os, but font features are unreliable...
With default LM, only the classical variants work.
With termes, heros, iwona, antykwa OTF sc and os work, while classical \sc and
\os don’t.
With gentium both sc work, while the font doesn’t have onum
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
gt; \setupbodyfont[mainface]
> \starttext
> {\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
Dear list,
I have noticed that ConTeXt (beta from 2014.02.14 17:07) has a problem
with Palatino Linotype.
Here the sample:
\definefontfeature[capstosc][c2sc=yes]
\definefontfamily[mainface][serif][Palatino Linotype]
\setupbodyfont[mainface]
\starttext
{\addfeature[capstosc] AEIOU}
\sc aeiou
upbodyfont[antykwa]
\starttext
abc \sc def
\stoptext
The bug is also present in TL 2010. It works fine with MKII.
Add \definefontfeature[smallcaps][smallcaps][script=latn] to your document.
Thank you Wolfgang, this helps, but:
- Why do the smallcaps works in LM, Antykwa Poltawskiego
ykwa-torunska]
>> \setupbodyfont[antykwa]
>> \starttext
>> abc \sc def
>> \stoptext
>>
>> The bug is also present in TL 2010. It works fine with MKII.
>>
>
> Add \definefontfeature[smallcaps][smallcaps][script=latn] to your document.
Thank you Wol
Am 17.07.10 23:41, schrieb Mojca Miklavec:
Dear list,
I didn't yet figure out why, but small caps font for Antykwa Torunska
doesn't work in MKIV:
\usetypescript[antykwa-torunska]
\setupbodyfont[antykwa]
\starttext
abc \sc def
\stoptext
The bug is also present in TL 2010. It works
Dear list,
I didn't yet figure out why, but small caps font for Antykwa Torunska
doesn't work in MKIV:
\usetypescript[antykwa-torunska]
\setupbodyfont[antykwa]
\starttext
abc \sc def
\stoptext
The bug is also present in TL 2010. It works fine with MK
Under the latest beta (2009.10.02 13:14), it doesn't seem possible
to access \SerifCapsSlanted by combining the \em and \sc font
switches. The following test case demonstrates this:
http://www.ntg.nl/pipermail/ntg-context/2003/002453.html
Thanks Wolfgang. I will investigate further.
Am 15.10.2009 um 12:03 schrieb Tim Wraight:
Hi,
Under the latest beta (2009.10.02 13:14), it doesn't seem possible
to access \SerifCapsSlanted by combining the \em and \sc font
switches. The following test case demonstrates this:
http://www.ntg.nl/pipermail/ntg-context/2003/002453
Hi,
Under the latest beta (2009.10.02 13:14), it doesn't seem possible to
access \SerifCapsSlanted by combining the \em and \sc font switches.
The following test case demonstrates this:
---
\definefont [SlantyCaps][SerifCapsSlanted]
\starttext
{\em Italics works.} \par
{\sc Small
chola,schoolbook,termes,times]
[ec,texnansi,cs,qx,rm,t5,t2a,t2b,t2c,l7x]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Caps]
[\typescriptthree-q\typescriptprefix{f:\typescripttwo}r-sc]
[encoding=\typescriptthree]
There are no t2a fonts with small caps defined, so simple usage
]
[ec,texnansi,cs,qx,rm,t5,t2a,t2b,t2c,l7x]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Caps]
[\typescriptthree-q\typescriptprefix{f:\typescripttwo}r-sc]
[encoding=\typescriptthree]
There are no t2a fonts with small caps defined, so simple usage like
\usetypescript[times
Hi,
The following minimal examples work fine with pdftex, but give unexpected
results with newer betas and luatex (tested under ConTeXt - 2008.11.10 21:40 --
luaTeX-0.30.2):
% engine=luatex
\setupcapitals [sc=yes]
\abbreviation [OTAN] {otan} {Organisation du Traité de l'Atlantique
> > But there are at least two other problems with the file (so there must be a
> > cleaner way):
> > - I would like to use LM wherever possible, but now even for normal \sc
> > the CM fonts are used.
>
> I get lmr for normal caps in your example.
>
> You can us
there are at least two other problems with the file (so there must be a
> cleaner way):
> - I would like to use LM wherever possible, but now even for normal \sc
> the CM fonts are used.
I get lmr for normal caps in your example.
You can use the (lmcsc10 instead of cmcsc10) directly or create
On Thu, 29 Dec 2005, Taco Hoekwater wrote:
> This file boils down to a single equivalent command:
>
> \definebodyfont
> [15pt,14pt,13pt,12pt,11pt,10pt,9pt,8pt,7pt,6pt,5pt]
> [sc]
> [bf=cmbcsc10 sa 1,
>tf=cmcsc10 sa 1]
Thanks Taco, indeed much cle
way, feel free to update the wiki.
Hi Peter,
This file boils down to a single equivalent command:
\definebodyfont
[15pt,14pt,13pt,12pt,11pt,10pt,9pt,8pt,7pt,6pt,5pt]
[sc]
[bf=cmbcsc10 sa 1,
tf=cmcsc10 sa 1]
Please don't set \pdfpkresolution in the module, the user
may
re at least two other problems with the file (so there must be a
cleaner way):
- I would like to use LM wherever possible, but now even for normal \sc
the CM fonts are used.
- It would be better, to have just one command for all possible sizes. If
you want 17.8pt, it wouldn't work unti
inebodyfont [12pt] [rm]
[tf=cmr12,
bf=cmbx12,
it=cmti12,
sl=cmsl12,
bi=cmbxti10 at 12pt,
bs=cmbxsl10 at 12pt,
sc=cmcsc10 at 12pt]
OK, I know that they map further to lmr, but not all of them do (bold
typewriter font doesn't for example). Why not using lmr nam
Hello,
finally I got bold small caps with the attached module.
It's certainly a bad hack, but unfortunately I don't know nothing about
typescripts, variants and other details about fonts in ConTeXt (it looks
too complicated to me...).
If somebody knows a cleaner way, feel free to update the wiki.
On Fri, 2 Dec 2005, Taco Hoekwater wrote:
> > In updmap.cfg I had to replace "Map lm.map" by "Map lm-ec.map", now it
> > works.
>
> Then you have to include the other encoding map files as well
> (like e.g. lm-texnansi.map and lm-qx.map) The beauty of lm.map
> was that there was only one file.
>
� wrote:
On Wed, 30 Nov 2005, Hans Hagen wrote:
with the recent version (2005.11.30), I get a strange font in dvips output,
when using \sc.
dvips messages don't show any error:
This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com)
' TeX output 2005.
Taco Hoekwater wrote:
Peter M�nster wrote:
But I've found the solution:
In updmap.cfg I had to replace "Map lm.map" by "Map lm-ec.map", now it
works.
Then you have to include the other encoding map files as well
(like e.g. lm-texnansi.map and lm-qx.map) The beauty of lm.map
was that the
Peter Münster wrote:
But I've found the solution:
In updmap.cfg I had to replace "Map lm.map" by "Map lm-ec.map", now it
works.
Then you have to include the other encoding map files as well
(like e.g. lm-texnansi.map and lm-qx.map) The beauty of lm.map
was that there was only one file.
I g
On Wed, 30 Nov 2005, Hans Hagen wrote:
> >with the recent version (2005.11.30), I get a strange font in dvips output,
> >when using \sc.
> >dvips messages don't show any error:
> >This is dvips(k) 5.95a Copyright 2005 Radical Eye Software
> >(www.radicaleye.c
� wrote:
Hello,
with the recent version (2005.11.30), I get a strange font in dvips output,
when using \sc.
dvips messages don't show any error:
This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com)
' TeX output 2005.11.30:2115' -> test.ps
. [1]
Hello,
with the recent version (2005.11.30), I get a strange font in dvips output,
when using \sc.
dvips messages don't show any error:
This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com)
' TeX output 2005.11.30:2115' -> test.ps
. [1]
Here my tes
] [\typescriptthree-lmcsc10]
[encoding=\typescriptthree]
should be
\definefontsynonym [cmtcsc10] [\typescriptthree-lmtcsc10]
[encoding=\typescriptthree]
(see two times 't' ^ ^)
If this font exist I suggest to extend type-siz.tex:
(see line
On 18 Mar 2005, at 16:30, Ulrich Dirr wrote:
Adam Lindsay wrote:
Faking, whether within ConTeXt or within your driver, seems to be the
only option: Small Caps were never designed for Optima, afaik.
But it's in Optima Nova
http://www.linotype.com/58171/optimanovacdformacandpc-
compilation.html?PHPS
Ulrich Dirr wrote:
Adam Lindsay wrote:
Faking, whether within ConTeXt or within your driver, seems to be the
only option: Small Caps were never designed for Optima, afaik.
But it's in Optima Nova
http://www.linotype.com/58171/optimanovacdformacandpc-compilation.html?PHPS
ESSID=b120c89ddacf24bf95bb
On 18 Mar 2005, at 15:30, Ulrich Dirr wrote:
Adam Lindsay wrote:
Faking, whether within ConTeXt or within your driver, seems to be the
only option: Small Caps were never designed for Optima, afaik.
But it's in Optima Nova
http://www.linotype.com/58171/optimanovacdformacandpc-
compilation.html?PHPS
Adam Lindsay wrote:
> Faking, whether within ConTeXt or within your driver, seems to be the
> only option: Small Caps were never designed for Optima, afaik.
But it's in Optima Nova
http://www.linotype.com/58171/optimanovacdformacandpc-compilation.html?PHPS
ESSID=b120c89ddacf24bf95bb7499629b6e70
Hi Gerben,
On 18 Mar 2005, at 14:24, Gerben Wierda wrote:
When I use the Optima font I do not have real small capitals. It seems
\sc does not try to emulate them and also the new \lettrine ignores
it.
You could emulate them with the \kap command. (and its relatives)
I'm not sure what a blo
When I use the Optima font I do not have real small capitals. It seems
\sc does not try to emulate them and also the new \lettrine ignores it.
Is there a way I can still have my SC? Maybe faked by using a smaller
size capitals?
Thanks,
G
___
ntg
53 matches
Mail list logo
