” as a funny way to say “not famous, but somewhat
known” (and yes, I know Latin and what the words really mean).
That was my understanding. Infamous=Not famous; that is, not as well
known as others. A slight play on words
I used “infamous” as a funny way to say “not famous, but somewhat
known” (and yes, I know Latin and what the words really mean).
That was my understanding. Infamous=Not famous; that is, not as well
known as others. A slight play on words.
--
Joaquín Ataz López
Departamento de Derecho civil
plies to JUH’s quote, though.
I used “infamous” as a funny way to say “not famous, but somewhat known”
(and yes, I know Latin and what the words really mean).
Hraban
___
If your question is of interest to others
ion, design process etc.
>
> I just browsed the dissertation about the (Vietnamese) "Dilinh" font and
>
> found the considerations interesting.
>
> "Gul" has matching Devanagari & Latin, "Tarisel" has variations from
>
> readable text
and
found the considerations interesting.
"Gul" has matching Devanagari & Latin, "Tarisel" has variations from
readable text to abstracted lombardic unciale, and "Wierd" has matching
deconstruc
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
> pages
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> level 1, o
ches loaded from cont-new.mkiv
close source> level 1, order 1, name
'C:/Users/adeim/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './ctx-test-MetaPost-pdf', input
'./ctx-test-MetaPost-pdf.tex', result './ctx-test-MetaPost-pdf'
fo
, of course.
%We are giving below an example of a text written in a Latin language,
in which we want to print here and there some text in ancient Greek,
Arabic and Chinese.
\setuplanguage[fr][patterns={fr,agr}]
\mainlanguage[fr]
\setuplayout [backspace=40mm]
\setuppagenumbering[alternative
ks fine putting content on realpage numbers that can
be divided by 4 (with modulo 0).
As far as I get, Michael was looking to place content on realpage
numbers get modulo 3 when divided by 4.
At least, this is what would fit my needs to place the imprint on the
(excuse the Latin adjective [before
>>>> document (possibly with furagana) ? I am using MacOS and I have several
>>>> Japanese fonts on the system.
>>>> I have some old examples which do not typeset correctly now, maybe because
>>>> they use the old module simplefonts an
t correctly now, maybe because
>>> they use the old module simplefonts and commands such as \setcjkmainfont
>>> and friends.
>>
>> Try to replace the simplefonts calls with something like
>>
>> \definefontfamily[myfonts][rm][Som
[SomeFont]
> \definefontfamily[myfonts][ss][SomeOtherFont]
>
> \setupbodyfont[myfonts,rm,12pt]
>
> With Latin fonts, it usually works.
>
> Hraban
> ___
> If your question is of interest to ot
they
use the old module simplefonts and commands such as \setcjkmainfont and
friends.
Try to replace the simplefonts calls with something like
\definefontfamily[myfonts][rm][SomeFont]
\definefontfamily[myfonts][ss][SomeOtherFont]
\setupbodyfont[myfonts,rm,12pt]
With Latin fonts, it usually works
the nineties I used numeric sort keys for a Sanskrit index
where the letters were Latin (with lots of diacritics) but the sort order
was Indic (a, ā, i, ī, ... k, kh, g, gh, ...). I assigned a two-digit
"number" (01, 02, 03, ...) to each grapheme and the sort key consisted o
. Is this an oversight or did they get axed?
I assumed that most moved on to utf so ... when i looked at these
definitions there were plenty greek, cyrillic, etc that were just there
because in mkii we had to follow the 'name' route and it's a waste of
memory and hash entries. For now I kept the latin
ources/general/manuals/math
system > files > jobname
'./math-mkiv-t-b-ce3b35636ef01ee62897a2beb76049e0', input
'./math-mkiv-t-b-ce3b35636ef01ee62897a2beb76049e0.tmp', result
'./math-mkiv-t-b-ce3b35636ef01ee62897a2beb76049e0'
fonts > latin modern fonts
yfontenvironment[16pt]
> \setupbodyfont[mainface, 16pt]
> \starttext
> \startmakeup[standard][style=\bf]
> \switchtobodyfont[coverface]
> This is a cover.
> \stopmakeup
>
> This is text.
> \stoptext
>
> Compiling the sample with current latest (2024.01.08 11:23),
This is text.
\stoptext
Compiling the sample with current latest (2024.01.08 11:23), LMTX puts
Latin Modern Roman (no bold) and MkIV puts Termes (no bold).
The results with previous latest (2023.09.26 18:19), cover is in Termes
bold with LMTX and in Termes regular with MkIV.
I guess there might
On Fri, 1 Dec 2023 15:09:32 +0100
Wolfgang Schuster wrote:
> You get the same error with Latin Modern as soon as you use a non
> predefined font size in combination with bold math.
True, thanks for pointing that out. I wasn't aware and frankly,
that's rather unexpected behaviour.
So
[mainface, 8.5pt]
\starttext
\bold{\math{x_y}}
\stoptext
You get the same error with Latin Modern as soon as you use a non
predefined font size in combination with bold math.
begin example
% \starttypescript [math] [default] [size]
% \definebodyfont [8.5pt] [mm] [default
ce > level 1, order 1, name
'/usr/share/texmf/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source> level 1, order 1, name
'/usr/share/texmf/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname
m > files > jobname './mathtry', input './mathtry.tex', result
'./mathtry'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
system > synctex functionality is enabled, expect 5-10 pct runtime
overhead!
open source > level 1,
he time comes for
testing -)
Anyway, we're entering the bug cq. side effect becomes feature area
here; just like yesterdays perfect bidi algorithm is todays less pefect
one replaced by ...
But therein lies the problem: ConTeXt shows the rendering by default, and we
need to turn it off. Since mos
ure if it still works.
Anyway, we're entering the bug cq. side effect becomes feature area
here; just like yesterdays perfect bidi algorithm is todays less pefect
one replaced by ...
But therein lies the problem: ConTeXt shows the rendering by default, and we
need to turn it off. Since most
never considered making it an opentype feature in the font itself,
but since his focus is/was XeTeX/HB (HB is rather rigid and dictatorial) I
guess that's not surprising.)
But therein lies the problem: ConTeXt shows the rendering by default, and we
need to turn it off. Since most non-Latin typo
as some fonts
visualized them by default
But therein lies the problem: ConTeXt shows the rendering by default, and we
need to turn it off. Since most non-Latin typography targets Uniscribe
applications which allows for toggling, the font developers (commercial or
free) don't have to concern
ling in a WYSIWYG
context -- can't speak for HarfBuzz -- so there is no harm in having explicit
symbols in the font.
sure, as long as there is no rendering ... they show the input
But therein lies the problem: ConTeXt shows the rendering by default, and we
need to turn it off. Since most non-
ike Notepad/Word allow for toggling in a WYSIWYG
context -- can't speak for HarfBuzz -- so there is no harm in having explicit
symbols in the font.
sure, as long as there is no rendering ... they show the input
The upshot is that, for non-Latin scripts, some toggling capability in ConTeXt
is
ri, Uthmanic, and Noto Naskh Arabic --
all free fonts.
Industry workhorses like Linotype Lotus (Arabic) also have them.
Uniscribe applications like Notepad/Word allow for toggling in a WYSIWYG
context -- can't speak for HarfBuzz -- so there is no harm in having explicit
symbols in the font.
t/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './pablo', input './pablo.tex', result
'./pablo'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
system > synctex functionality is enabled, expect 5-10 pct r
/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source> level 1, order 1, name
'C:/Users/Hermann/Downloads/context-mswin/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './blackrule1', input './blackru
om cont-new.mkiv
close source> level 1, order 1, name
'C:/Users/Hermann/Downloads/context-mswin/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './blackrule1', input './blackrule1.tex',
result './blackrule1'
fonts > latin modern
> level 1, order 1, name
'C:/Users/Hermann/Downloads/context-mswin/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './blackrule1', input './blackrule1.tex',
result './blackrule1'
fonts > latin modern fonts are not preloaded
languages
need it in a project i can waste the time on it, otherwise i
rather spend the time on things we (and users) can actually use and have
fun with.
At some point in the future, will aim to put together some typescripts using
Latin Modern as base, and probably New Computer Modern (Greek, Hebrew, Coptic
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
] [\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
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.
ConTeXt has a command which can be used to check whether the current
active font
ty betty. I know it's hard to teach an ol' dog new tricks,
> but… it's worth to try! right?
>
> Also, Did you see the attachment I sent prior to your message?
Maybe your system is broken?
>
> > 2. The example below results in a correct output for \TEX.
> >
>
> Not in my end wi
I sent prior to your message?
> 2. The example below results in a correct output for \TEX.
>
Not in my end with any font other than latin modern
> \setuplayout[width=16cm]
> \showmakeup
>
> \starttext
>
> Thus, I came to the conclusion that the designer of a new
>
enced
> by a single person. Once the initial design is
>
>
>>
>>>
>>> and opted to load another font, other than cmr that is, a \frenchspacing
>>> approach wouldn't be further required
>>
>> cmr? Not used in ConTeXt for a long time. (And wha
e further required
>
> cmr? Not used in ConTeXt for a long time. (And what does the changing
> of font have to do with this?)
latin modern.
>
> >
> > Bear with me here, in the current state, for example, and as long as say
> >
> > «…person.␣{\obeylines Once the ini
On Tue, 2023-08-15 at 18:22 +0200, Hans Hagen wrote:
> On 8/15/2023 5:33 PM, Hamid,Idris wrote:
>
>
> > so [\s!designsize=\s!auto] means there is no explicit call to
lmroman8-regular etc.? Interesting..
>
>
> check the lfg file ...
On that note, there seems to be an inconsistency in the
Ah, the goodies files.. Got it and thanks for the clarifications.
Best wishes
Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
On Aug 15, 2023, 10:22 AM -0600, Hans Hagen , wrote:
** Caution: EXTERNAL Sender **
On 8/15/2023 5:33 PM,
texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source> level 1, order 1, name
'/home/xan/bin/context-current/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './dev', in
On 8/15/2023 5:33 PM, Hamid,Idris wrote:
so [\s!designsize=\s!auto] means there is no explicit call to lmroman8-regular
etc.? Interesting..
check the lfg file ...
Hans
-
Hans Hagen |
e 12pt roman
%D bodyfont.
-)
> well, in type-imp-latinmodern.mkiv i can find 'designsize' ... you're
> not relying on some gpt driven search machine are you?
No just the search files feature in Notepad++ -)
Ok, looking at type-imp-latinmodern.mkiv, under latin-modern-designsize, I see
On 8/15/2023 4:35 PM, Hamid,Idris wrote:
But for sure ConTeXt used to load lmroman12-regular (or the computer-modern 12
pt) by default. So things have changed..
afaik mkiv always had modern as default an dnot the designsize
typescript (after all, we only have math 10pt)
well you can load
remember a very long time ago some
experiments with typescripts for computer-modern opticals, before latin modern
became default (it's all foggy now..)
But for sure ConTeXt used to load lmroman12-regular (or the computer-modern 12
pt) by default. So things have changed..
> well you can load the
On 8/15/2023 3:56 PM, Hamid,Idris wrote:
Dear gang,
It seems that ConTeXt does not currently implement optical scaling for Latin
Modern -- at least not by default. For example:
===
\startTEXpage[offset=1em]
Test {\tfa Test} {\tfb Test} {\tfc Test} {\tfd Test} {\tfx Test} {\tfxx Test
Dear gang,
It seems that ConTeXt does not currently implement optical scaling for Latin
Modern -- at least not by default. For example:
===
\startTEXpage[offset=1em]
Test {\tfa Test} {\tfb Test} {\tfc Test} {\tfd Test} {\tfx Test} {\tfxx Test}
\stopTEXpage
===
In the log we have
new.mkiv
close source> level 1, order 1, name
'/home/xan/bin/context-current/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './dev', input './dev.tex', result './dev'
fonts > latin modern fonts are not preloaded
lang
t entirely and we're back to Latin Modern for all sizes.
Assuming that this is expected behavior, it appears to follow that fontfeatures
cannot be invoked for \switchtobodyfont and the like, only from within the
typescript read by \switchtobodyfont etc.
===
REQUEST:
Since ALMFixed
system > files > jobname 'dev', input './dev', result 'dev'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 2, order 3, name
'/home/xan/zync/docencia/candoc8/apunts-espa/dev.tex'
modules > 'p
On 8/5/23 21:16, Marcus Vinicius Mesquita wrote:
> Dear List,
>
> I have a lot of latin words in a document with the length of the
> vowels indicated by diacritics, for example: fīlĭa.
>
> Is it possible somehow to make these words searchable without the diacritics?
> That i
023, at 20:16, Marcus Vinicius Mesquita
> wrote:
>
> Dear List,
>
> I have a lot of latin words in a document with the length of the
> vowels indicated by diacritics, for example: fīlĭa.
>
> Is it possible somehow to make these words searchable without the diacritics?
&g
Dear List,
I have a lot of latin words in a document with the length of the
vowels indicated by diacritics, for example: fīlĭa.
Is it possible somehow to make these words searchable without the diacritics?
That is, if I make a search for filia in the final pdf file, fīlĭa
would also be found
rendering of Latin Modern, Pagella,
Brill - a nice gratis font for download but with a strange license, so
dangerous to use for real work -, and Minion. It also includes a table of
composition analysis for each of the transliteration characters.
https://www.dropbox.com/scl/fi
> On 18 Jul 2023, at 21:49, Hans Hagen wrote:
>
> On 7/18/2023 9:37 PM, Gerben Wierda wrote:
>> I have a document that includes text and PDFs (which themselves have been
>> created with LMTX)
>> When it is compiled I see:
>> fonts > latin modern
On 7/18/2023 9:37 PM, Gerben Wierda wrote:
I have a document that includes text and PDFs (which themselves have been
created with LMTX)
When it is compiled I see:
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level
I have a document that includes text and PDFs (which themselves have been
created with LMTX)
When it is compiled I see:
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 2, name './ArchiMate-sheets.t
/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source> level 1, order 1, name
'/context-lmtx-2/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './atestinlucida-OTF-9
And the reason probably is that the font is defined as sans serif [ss]?Sent from my iPhoneOn 5 Jul 2023, at 00:12, Gerben Wierda wrote:Found it (I think)\definefontfamily defines tf= but the text says \rmIf I use \tf in the text it works.If I use \rm in the text it works for default Latin Modern
Found it (I think)
\definefontfamily defines tf= but the text says \rm
If I use \tf in the text it works.
If I use \rm in the text it works for default Latin Modern but not for any font
defined. This is true regardless of using rm= or tf= in the definition.
So, it seems to be the combination
lowercase names (without spaces), e.g. "bi=boldoblique" (or
>> "bi=bolditalic").
>
> No and no. With th elatter it doesn't load Helvetica at all, Error shown:
> selectfont > the requested font 'Helvetica' has no files for the 'tf'
> alternative, Latin M
n
> you use lowercase names (without spaces), e.g. "bi=boldoblique" (or
> "bi=bolditalic").
No and no. With th elatter it doesn't load Helvetica at all, Error shown:
selectfont > the requested font 'Helvetica' has no files for the 'tf'
alternative, Latin Modern is used instead
ptext
>
> Wolfgang
>
> Gerben Wierda via ntg-context schrieb am 16.06.2023 um 15:19:
>> I was wrong, not just the bold doesn't work, everything is replaced with
>> Latin Modern. Cabin isn't used at all.
>>
>>> On 16 Jun 2023, at 15:05, Gerben Wierda via
jumped over the lazy dog}
\input knuth
\stoptext
Wolfgang
Gerben Wierda via ntg-context schrieb am 16.06.2023 um 15:19:
I was wrong, not just the bold doesn't work, /everything/ is replaced
with Latin Modern. Cabin isn't used at all.
On 16 Jun 2023, at 15:05, Gerben Wierda via ntg-context
I was wrong, not just the bold doesn't work, everything is replaced with Latin
Modern. Cabin isn't used at all.
> On 16 Jun 2023, at 15:05, Gerben Wierda via ntg-context
> wrote:
>
> I've been trying to use the open source Cabin font
> (https://fonts.google.com/specimen/
/**'
> mtx-install-modules |
> mtx-install-modules | renewing file database
>
> mtx-install-modules |
> mtx-install-modules | installed: tikz
> mtx-install-modules |
>
>
> system > beware: some patches loaded from cont-new.mkiv
> close source> le
xmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './tikz-sample-2', input
'./tikz-sample-2.mkiv', result './tikz-sample-2'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level
m/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './tk-tst', input './tk-tst.tex',
result './tk-tst'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 2, name './t
made their money by shoving down acroread all over. It's no secret
> Normally context will fall bakc on latin modern but when you explicitly load
> a font setup and that one doesn't have math fonts it will not be set up
I checked the type-imp-* file. Unicode-math from latex had no issues on
> > without an error
> > >
> > > I still stand for what I said earlier. That lot and their heirs already
> > > made their money by shoving down acroread all over. It's no secret
> > Normally context will fall bakc on latin modern but when you explicitly load
made their money by shoving down acroread all over. It's no secret
> Normally context will fall bakc on latin modern but when you explicitly load
> a font setup and that one doesn't have math fonts it will not be set up
> right and then you get these parameter relates messages. The minion
, while loading myriad and minion et co
without an error
I still stand for what I said earlier. That lot and their heirs already
made their money by shoving down acroread all over. It's no secret
Normally context will fall bakc on latin modern but when you explicitly
load a font setup and that one
ex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source> level 1, order 1, name
'/home/vm/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './context 24',
which can be downloaded from
> https://fonts.google.com/noto/specimen/Noto+Sans+Math
>
> But I use it like the following
>
> \definefontfamily[myfonts][rm][latin modern roman]
> \definefontfamily[myfonts][mm][noto sans math]
> \setupbodyfont[myfonts,rm,12pt]
> \starttext
> Test
Hi,
I try to use the Noto Sans Math fnt which can be downloaded from
https://fonts.google.com/noto/specimen/Noto+Sans+Math
But I use it like the following
\definefontfamily[myfonts][rm][latin modern roman]
\definefontfamily[myfonts][mm][noto sans math]
\setupbodyfont[myfonts,rm,12pt]
\starttext
; >
> > > > > sure, why should it, you want lucida so better quit with an error than
> > > > > kicking in some font; actually cmr math fonts have been obsoleted for
> > > > > way
> > > > > over a decade by latin modern math fonts in 32 b
but it looks very
similar at first sight
(of course... ). I was deceived because I remember its shapes quite well (C
,g a ).
>
> If you talk about the text font, Hans changed the concrete typescript
> so that it uses the variable "mono" Latin modern instead of the
> concrete t
k well.
If you talk about the text font, Hans changed the concrete typescript
so that it uses the variable "mono" Latin modern instead of the
concrete text font that comes from Computer modern unicode. But the
font is also boldened slightly, and perhaps that is what causes your
problem (It d
fonts have been obsoleted for way
over a decade by latin modern math fonts in 32 bit font engines
Font loading and processing time can be mosty neglected so these 16 seconds
come from something else, maybe there are ways to trace file access. Another
possibility is that your fonts are not cached
e been obsoleted for way
> > > over a decade by latin modern math fonts in 32 bit font engines
>
> Font loading and processing time can be mosty neglected so these 16 seconds
> come from something else, maybe there are ways to trace file access. Another
> possibility is that your
On 3/31/2023 10:08 PM, Carlos via ntg-context wrote:
sure, why should it, you want lucida so better quit with an error than
kicking in some font; actually cmr math fonts have been obsoleted for way
over a decade by latin modern math fonts in 32 bit font engines
Font loading and processing
om an
> > undefined font family. For example, plain TeX doesn't allow \it or \sl in
> > subscripts. Proceed, and I'll try to forget that I needed that character.»
> >
> > There's not even a fallback to cmr or any other font.
>
> sure, why should it, you want lu
h fonts have been obsoleted for
way over a decade by latin modern math fonts in 32 bit font engines
There was not even a personalized touch in the output. That message sounds like
one of these new GPT-chat features. Dry. When I read that «Proceed, and I'll
try to forget it…» part the first thin
hes loaded from cont-new.mkiv
close source> level 1, order 1, name
'/home/xan/bin/context-minimal/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './a', input './a.tex', result './a'
fonts > latin modern fonts are not preloaded
languages
text/base/mkxl/cont-new.mkxl'
system > files > jobname './atestinlucida-context-55', input
'./atestinlucida-context-55.mkiv', result './atestinlucida-context-55'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source
gt; files > jobname './test', input './test.tex', result './test'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 2, name './test.tex'
fonts > preloading latin modern fonts (second stage)
fo
Thanks, Pablo and Bruce. Both solutions work well.
> I had similar issues with \section and only the Latin script was involved.
Btw, just in case if anyone shares this idea: is it possible to have a
zulip channel for ConTeXt? It's free for open source projects, has a
interface for exist
t clear for me whether the CJK fonts are
only for fragments in these languages or the main text is written in any
of these languages.
I had similar issues with \section and only the Latin script was involved.
Again
s a source of confusion both in fonts and in programming,
> because some programs normalize these letters, so for string
> operations and searches, you may obtain surprising results.
“Charachter normalization” is tricky (for me, mainly with the Latin
alphabet).
https://wiki.contextgar
iv
close source> level 1, order 1, name
'/opt/luametatex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './test', input './test.tex', result './test'
fonts > latin modern fonts are not preloaded
languages > language 'en' is a
close source> level 1, order 1, name
'/opt/luametatex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname './test', input './test.tex', result './test'
fonts > latin modern fonts are not preloaded
languages > language 'en' is activ
xl/cont-new.mkxl'
> system > beware: some patches loaded from cont-new.mkiv
> close source> level 1, order 1, name
> '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
> system > files > jobname './complexes_2', input
> './comple
e './complexes_2', input
'./complexes_2.tex', result './complexes_2'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 2, name './complexes_2.tex'
open source > level 2, order 3, name 'exercises.mki
\getbuffer}\par
{\tt \getbuffer}\par
{\bf \getbuffer}\par
{\it \getbuffer}\par
{\sl \getbuffer}\par
{\bi \getbuffer}\par
{\bs \getbuffer}\par
{\sc \getbuffer}
Should be Palatino: $x + y$ $f({\bi x})$
Should be Latin Modern: ${\cal I}$ $\mathcal{I}$ $\mathscr{I}$
\stoptext
signature.asc
Description
ward }
Should be Palatino: $x + y$
Should be Latin Modern: ${\cal I}$ $\mathcal{I}$ $\mathscr{I}$
\stoptext
signature.asc
Description: Message signed with OpenPGP
___
If your question is of interest to others as well
1 - 100 of 2570 matches
Mail list logo
