d I have many instances,
> 40 or more in some cases). However, I did not ask for a 'simple' solution,
> just a solution! Thank you.
>
> Julian
>
> On 1/2/22 11:09, Adam Reviczky wrote:
>> Hi Julian,
>>
>> How about using the keys in every i
1:09, Adam Reviczky wrote:
Hi Julian,
How about using the keys in every instance?
\setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
\defineprocessor[special][style=italic]
\starttext
P\index[Plenary+periti]{Plenary Council+{\it periti} (experts)}
B\index[Plenary+beriti]{Plenary Council+{
Hi Julian,
How about using the keys in every instance?
\setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
\defineprocessor[special][style=italic]
\starttext
P\index[Plenary+periti]{Plenary Council+{\it periti} (experts)}
B\index[Plenary+beriti]{Plenary Council+{\it beriti} (experts
processor is not
for the 'periti' case above but I use it for book titles.
\setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]
\defineprocessor[special][style=italic]
In the periti case it is the \it command that clearly interferes with
correct alphabetic positioning in the
s with the subentry
surrounded by single quotes. It too comes first in the list if I use a
double key. So clearly it is the fact that there is formatting ({\it
something}) or quotes ({‘word’}) in a subentry that causes the problem,
and I am wondering how to overcome this.
Julian
On 30/1/22 2
in three columns. The problem is, if there
> is an item with a somewhat long description, it can be split across columns.
> See the example below:
>
> \starttext
> \startcolumns[n=3]%
> \startitemize[1]%
> \item pizza cutter
>
be split across columns. See the
example below:
\starttext \startcolumns[n=3]% \startitemize[1]% \item
pizza cutter \item a word processor (or notebook paper)
\stopitemize% \stopcolumns%\stoptext
In the example, it split the second item across the
Hi Julian,
Have you tried \index[Innovative]{‘Innovative’}?
See wiki entry: https://wiki.contextgarden.net/Registers
- To sort a word (such as "ConTeXt" under "C"), use: \index
<https://wiki.contextgarden.net/Command/index>[CONTEXT]{\ConTeXt}
You would have to cha
Afghanistan (in Iran a
> parasang is 6 kilometers now).
(Personnaly I think the Roman mile has its origin in the Persian « mil »: I
> think the etymology of the word mile based on the word « mille », a
> thousand, cannot be correct since it does not correspond to one thousand of
> any
On 1/26/2022 10:07 PM, jbf via ntg-context wrote:
Just be careful, though (writing as a native English speaker), because
the word 'polymath' for English speaker is not a reference to
mathematicians at all. (Greek/mathē/ means 'learning' not mathematics).
Translators a
Just be careful, though (writing as a native English speaker), because
the word 'polymath' for English speaker is not a reference to
mathematicians at all. (Greek/mathē/ means 'learning' not mathematics).
Translators are well aware of the danger of homonyms, and if you
think the
etymology of the word mile based on the word « mille », a thousand, cannot be
correct since it does not correspond to one thousand of any other unit of
length used in the Roman empire).
Best regards: Otared
the Persian empire, and are still used, in particular the parasang, in
Iran and Afghanistan (in Iran a parasang is 6 kilometers now). (Personnaly I
think the Roman mile has its origin in the Persian « mil »: I think the
etymology of the word mile based on the word « mille », a thousand, cannot be
c
topitemize\stopcolumns
%word search clues (should be simple, but strangely this keeps getting the ☞
logo added instead of showing numbers)
\startitemize[n]
\item a type of hat worn
\item a cold season
\stopitemize
_
pile this code which Joey sent me and it won't populate
`\placenotes[footnote]` with any content:
\startbuffer [bib]
@Book{clark1989,
author = {Clark, William},
title = {Railroads \word{and} railroad towns \word{in} New Mexico},
publisher = {New Mexico Magazine},
year = {1989},
address =
> On 23 Jan 2022, at 21:40, Joel via ntg-context wrote:
>
> I am adding items to an index simply using `\index{word}`.
>
> There are a few cases where instead of printing just the page number where
> `\index{word}` is placed, I need the entire page range for that chapter
Am 23.01.22 um 22:40 schrieb Joel via ntg-context:
I am adding items to an index simply using `\index{word}`.
There are a few cases where instead of printing just the page number
where `\index{word}` is placed, I need the entire page range for that
chapter to be displayed. For instance, if
I am adding items to an index simply using `\index{word}`.
There are a few cases where instead of printing just the page number where
`\index{word}` is placed, I need the entire page range for that chapter to be
displayed. For instance, if Chapter 3 spans page 22-50, and I place
`\index{word
I've avoided forcing capitalization in too many places in the SBL rendering
because there are often language-specific (or, within English, even
dialect-specific) differences regarding what should be capitalized. I think
I already enforce capitalization of the first word, t
ll of the words that should not be capitalized
in my BiBTeX file as with \word{of} so they will ignore any instructions to
become capitalized.
--Joel
___
If your question is of interest to others as well, please a
as are conversions; kauśika is working on
> >
> > Perhaps the following notes are useful.
> >
> > 1. The simplest way, and what I was talking about, is to write and print
> > Sanskrit in
> > transliteration.
> >
> > ānandaḥ -> ānandaḥ
write and print
Sanskrit in
transliteration.
ānandaḥ -> ānandaḥ
2. Then we can of course write and print the same word in the usual
Indian Script (Devanāgarī)
आनन्दः -> आनन्दः
3. But for academic use, one wants an input in roman (e-text are usually
in roman), and the option
-> ānandaḥ
2. Then we can of course write and print the same word in the usual
Indian Script (Devanāgarī)
आनन्दः -> आनन्दः
3. But for academic use, one wants an input in roman (e-text are
usually in roman), and the option
to have an output in Devanāgarī)
ānandaḥ -> आनन्दः
On 1/9/2022 11:23 AM, hanneder--- via ntg-context wrote:
1. In Sanskrit prose it is possible to produce compounds that span a few
lines. The concept of
"word" or "word division" fails here, as are the TeX mechanisms.
What we need in practice would be a "hyph
few
lines. The concept of
"word" or "word division" fails here, as are the TeX mechanisms.
What we need in practice would be a "hyphenation" for the language
Sanskrit that hyphenates
after all Sanskrit vowels (in transcription this would be a, ā, i,
ī,
re about that or is that
> user-unfriendly (my technical knowledge is rather limited).
>
>
> Dear Hans,
>
> two recurring problems are rather specifically Indological and they concern
> hyphenation and
> font.
>
> 1. In Sanskrit prose it is possible to produce compounds that s
> ntg-context@ntg.nl> het volgende geschreven:
> >
> > I was just writing a mail (below) and saw:
> >
> >> They do indic scripts and Kai made the first version of the devanagari
> code for the context fontloader code that I then optimized.
> >
> > Fasc
On Sun, Jan 09, 2022 at 11:46:44PM +0100, Hans Hagen via ntg-context wrote:
> On 1/9/2022 11:23 AM, hanneder--- via ntg-context wrote:
>> 1. In Sanskrit prose it is possible to produce compounds that span a few
>> lines. The concept of
>> "word" or "word
ere can I learn more about that or is that
> user-unfriendly (my technical knowledge is rather limited).
>
>
> Dear Hans,
>
> two recurring problems are rather specifically Indological and they concern
> hyphenation and
> font.
>
> 1. In Sanskrit prose it is possible
On 1/9/2022 11:23 AM, hanneder--- via ntg-context wrote:
1. In Sanskrit prose it is possible to produce compounds that span a few
lines. The concept of
"word" or "word division" fails here, as are the TeX mechanisms.
What we need in practice would be a "hyph
d [chapter] [page=no]
\startdocument [title={Dummy title}]
\dorecurse{5}
{\startchapter[title={Chapter \convertnumber{word}{#1}}]
\samplefile{lorem}
\stopchapter}
\stopdocument
Wolfgang
___
If your ques
e context fontloader code that I then optimized.
> >
> > Fascinating. Where can I learn more about that or is that
> > user-unfriendly (my technical knowledge is rather limited).
> >
> >
> > Dear Hans,
> >
> > two recurring problems are rather spec
ion and
> font.
>
> 1. In Sanskrit prose it is possible to produce compounds that span a few
> lines. The concept of
> "word" or "word division" fails here, as are the TeX mechanisms.
>
> What we need in practice would be a "hyphenation" for the
).
Dear Hans,
two recurring problems are rather specifically Indological and they
concern hyphenation and
font.
1. In Sanskrit prose it is possible to produce compounds that span a
few lines. The concept of
"word" or "word division" fails here, as are the TeX mechanis
gt;
>
>
> On Fri, Jan 7, 2022 at 6:25 PM hanneder--- via ntg-context <
> ntg-context@ntg.nl> wrote:
>
>>
>> Probably the situation in South Asian Studies (Indology) is peculiar.
>> As I indicated, there are mostly no budgets for book typesetting in
>&
peculiar.
As I indicated, there are mostly no budgets for book typesetting in
Indology and
I know of no real expert for typesetting in this field. In other
words, the authors
have do it themselves, usually in Word etc., but some do use TeX etc.
Our publications
series (Indologi
have do it themselves, usually in Word etc., but some do use TeX etc.
Our publications
series (Indologica Marpurgensia) is, for instance, all done with LaTeX,
as are my publications
with Harrassowitz, which is the largest publisher in our field in
Germany. There is no institution
offering
rt for typesetting in this field. In other
> words, the authors
> have do it themselves, usually in Word etc., but some do use TeX etc.
> Our publications
> series (Indologica Marpurgensia) is, for instance, all done with
> LaTeX, as are my publications
> with Harrassowitz, which i
Probably the situation in South Asian Studies (Indology) is peculiar.
As I indicated, there are mostly no budgets for book typesetting in
Indology and
I know of no real expert for typesetting in this field. In other
words, the authors
have do it themselves, usually in Word etc., but some do
workflow,
otherwise Word-based (->XML->LaTeX or ->InDesign). Of course they accept
all kind of data; it looks like they’re really good in automated workflows.
But I guess there are strong competitors in the far east..
ertainment. Almost all publishers still expect a Word
file, so the tool of choice is pandoc to downgrade from TeX to docx.
Sorry to end on this depressing note.
Word documents for critical editions? In that case, publishers will have
to typeset the book themselves, won’t they?
As far as I
ersion, if necessary.
A light–weight markup language for critical editions would be something
to consider, in that case. (But it is something to be developed, if it
makes sense at all.)
> But in publication practice in my field, most of this is just for
> private entertainment. Almost all publis
sion,
if necessary. But in publication practice in my field, most of this
is just for private
entertainment. Almost all publishers still expect a Word file, so
the tool of choice
is pandoc to downgrade from TeX to docx. Sorry to end on this
depressing note.
Best
Jürgen
---
Prof. Dr.
separate. Code in TEI
xml (or a subset of it) and develop a ConTeXt stylesheet to process it.
I am used to TeX-code, and so I'd rather stick to that and let ekdosis
do the conversion,
if necessary. But in publication practice in my field, most of this is
just for private
entertainment. Almo
nTeXt stylesheet to
process it.
I am used to TeX-code, and so I'd rather stick to that and let ekdosis
do the conversion,
if necessary. But in publication practice in my field, most of this is
just for private
entertainment. Almost all publishers still expect a Word file, so the
tool of
Hello dear list,
I work with grids and in many cases a footnote on one of the last lines
forces and too early page break.
See this min-example:
\setuplayout[grid=yes]
\showgrid
\starttext
\dorecurse{40}{Word.\\}
Word.\footnote{Footnote}
\stoptext % Lines 41 on page 1 is empty
It preserves
xts topics, I
ignored your precious piece of work. I was interested by the
questions of Pr. Jürgen Hanneder, because even if I don't know a
word of Sanskrit, it is allways a true pain to begin with
technical requisits when your real job is to think about the
problematic m
sted by the questions of Pr. Jürgen Hanneder, because even if I don't
> know a word of Sanskrit, it is allways a true pain to begin with technical
> requisits when your real job is to think about the problematic meaning of
> ancients or less ancients texts. You precise clearly what
I-XML with ConTeXt : even if I am interested by clever printing and
issues with multi-languages texts topics, I ignored your precious piece
of work. I was interested by the questions of Pr. Jürgen Hanneder,
because even if I don't know a word of Sanskrit, it is allways a true
pain to
m a simple TeX user)
I’m only a ConTeXt newbie (who has been using it for about a decade 😅).
There might be other solutions, but I’m afraid I don’t know which is
exactly the problem you are facing.
Sorry, but the text structure isn’t clear to me (this is independent
from the fact that I don’t unders
2}]{koraṇṭīkaḥ }
\rdg[wit={N3}]{goraṃṭaka}
\rdg[wit={M1}]{ghoraṃṭakaḥ }
\rdg[wit={V8}]{\unm kāhapauraṇṭaka}
\rdg[wit={Vu}]{koraṃḍīka}
\rdg[wit={V2}]{kauraṃḍīkaḥ }
\rdg[wit={N20}]{paura...kaḥ } %illeg
\rdg[wit={C1,J3,L1,N11,V5,V19}]{{\supplied{\gap{reason=lost,unit=wor
ṇṭakaḥ }
> \rdg[wit={N12}]{kauraṃṭaka}
> \rdg[wit={J14,V26}]{kauraṇḍakaḥ }
> \rdg[wit={J2}]{koraṃṭaka}
> \rdg[wit={J4,N21,N23}]{koraṃtakaḥ }
> \rdg[type=stemmapoint,wit={C6,N13,Tü,V22,Vu}]{koraṃṭakaḥ }% stemma point?
> \rdg[wit={N2}]{koraṇṭīkaḥ }
> \rdg
\rdg[wit={C1,J3,L1,N11,V5,V19}]{{\supplied{\gap{reason=lost,unit=word,
quantity=1
}\app{\lem[wit={ceteri}]{surānandaḥ }
\rdg[wit={B2,N12}]{sarānanda}
\rdg[wit={C2,J2,N2,N3,V3,N22,V2}]{surānanda}
\rdg[wit={N24}]{śurānaṃdaḥ }
\rdg[wit={J4}]{sarānandaḥ }
\rdg[wit={C1
\setuphead[chapter].
My question: how do I get ONE instead of One.
I tried conversion=WORDS (or WORD), but that is not recognised and
the
output then becomes STUDY 1, which I don't want.
I also tried playing with
\definestructureconversionset[myconversion][
and I can achieve 'STUDY One' with the
> key conversion=Words in \setuphead[chapter].
>
> My question: how do I get ONE instead of One.
>
> I tried conversion=WORDS (or WORD), but that is not recognised and the
> output then becomes STUDY 1, which I don't want.
My question: how do I get ONE instead of One.
I tried conversion=WORDS (or WORD), but that is not recognised and the
output then becomes STUDY 1, which I don't want.
I also tried playing with \definestructureconversionset[myconversion][
,A,] then adding the numberconversionset=myconversion t
On Friday, December 31, 2021 6:26:36 PM IST Ajith R via ntg-context wrote:
> In most paragraphs, the sentences go beyond the right margin. How can I ask
> Context to break the word at the margin, without hyphenating every word
> manually?
Malayalam hyphenation may be invoked by se
break the word at the margin, without hyphenating every word
manually?
Thanks,
ajith
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http
fault btx rendering, I get the same error:
```
\startbuffer [bib]
@Book{clark1989,
author = {Clark, William},
title = {Railroads \word{and} railroad towns \word{in} New Mexico},
publisher = {New Mexico Magazine},
year = {1989},
address = {Albuquerque, New Mexico},
isbn = {9780937206126}
}
\stopb
eter{punct}}
\begingroup
\letbtxparameter{punct}\empty % don't pass the trailing punctuation down
to the inline setup
\startfootnote
\Word{\fastsetup{btx:sbl:cite:inline}}% capitalize the first word in
the footnote (needed to render "Ibid." and "Idem" correctly)
%
s not
recognized within the footnote environment...
\startfootnote
\Word{\fastsetup{btx:sbl:cite:inline}}% capitalize the first word in
the footnote (needed to render "Ibid." and "Idem" correctly)
% Add a closing period, unless the righttext ends with punctuation
\doifendswi
n the header and \placenotes[footnote]
where I want the endnotes to appear. It complains this error:
"Undefined control sequence \doifendswithpunctelse"
What did I do wrong?
--Joel
Code follows:
\usemodule[publ-imp-sbl]
\startbuffer [bib]
@Article{na2006,
title={Volcanoes \word{of} Ne
}
>
> The problem with this last example, is if my citations appear within the
> paragraph, then I end up with a paragraph break in the wrong place!
>
> Here is my minimum working example, which won't compile unless I add a
> blank line between the two citations.
>
> \usemodu
ich won't compile unless I add a blank line between the two citations.
\usemodule[publ-imp-sbl]
\startbuffer [bib]
@Article{na2006,
title={Volcanoes \word{of} New Mexico},
year={2006},
journal
}][]{clark1989}
>>
>> After much trial and error, I found this will compile:
>>
>> \autocite[{\loc[2]}][]{na2006}
>>
>> \autocite[{\loc[2]}][]{clark1989}
>>
>> The problem with this last example, is if my citations appear within the
>> pa
Here is my minimum working example, which won't compile unless I add a
> blank line between the two citations.
>
> \usemodule[publ-imp-sbl]
> \startbuffer [bib]
>
> @Article{na2006,
> title={Volcanoes \word{of} New Mexico},
> year={2006},
> journal={New Mexico Earth Ma
s my minimum working example, which won't compile unless I add a blank
line between the two citations.
\usemodule[publ-imp-sbl]
\startbuffer [bib]
@Article{na2006,
title={Volcanoes \word{of} New Mexico},
year={2006},
journal={New Mexico Earth Matters},
publisher={New Mexico Bureau \word{of} G
(4) Finally, the actual bibliographic entry in \placelistofpublications
> uses a strange format, with the first author listed as Last + First order,
> all subsequent authors in First + Last order, such as "Burns, Anna, Robert
> Smith, and Judith Green.", meanwhile "et al.&qu
ted!
--Joel
Minimal working example follows:
\startbuffer [bib]
@Book{ball1996,
author = {Ball, Larry},
title = {Desert lawmen: The high sheriffs \word{of} New Mexico \word{and}
Arizona, 1846-1912},
publisher = {University \word{of} New Mexico Press},
year = {1996},
address = {Albuquerque, NM},
Am 10.12.21 um 12:53 schrieb Wolfgang Schuster:
Henning Hraban Ramm via ntg-context schrieb am 10.12.2021 um 08:20:
Am 09.12.21 um 19:00 schrieb Henning Hraban Ramm via ntg-context:
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS&
Henning Hraban Ramm via ntg-context schrieb am 10.12.2021 um 08:20:
Am 09.12.21 um 19:00 schrieb Henning Hraban Ramm via ntg-context:
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS"; now it
makes "sS".
(I
On 12/10/2021 8:20 AM, Henning Hraban Ramm via ntg-context wrote:
Am 09.12.21 um 19:00 schrieb Henning Hraban Ramm via ntg-context:
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS"; now it
makes "sS".
(If the curr
Am 09.12.21 um 19:00 schrieb Henning Hraban Ramm via ntg-context:
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS"; now it
makes "sS".
(If the current font contains an uppercase ß that would be even better,
but t
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS"; now it
makes "sS".
(If the current font contains an uppercase ß that would be even better,
but those are rare).
I can’t tell when it changed (some LMTX versi
ge[es]
\setupbodyfont[dejavu]
\defineregister
[Russian]
[n=1,
command=\Words,
pagenumber=no,
language=ru,
textalternative=horizontal,
distance=0pt]
\setupregister [Russian] [2] [textstyle=bold,left={, }]
\setupregister [Russian] [3] [textstyle=italic,left={, }]
% word category me
ngroup
\getdummyparameters
[word=,
category=,
meaning=,
#1]%
\setregisterentry
[Russian]
[keys={\dummyparameter{word}},
entries:1={\dummyparameter{word}},
entries:2={\dummyparameter{category}},
entries:3={\dummyparameter{meaning}}]%
\en
v!yes,
\c!balance=\v!no,
\c!n=2,
\c!command=\Words,
\c!pagenumber=\v!no,
\c!language=\s!ru]
\def\Ruso[#1]%
{\begingroup
\getdummyparameters[word=,category=,meaning=,#1]%
\Russian[\dummyparameter{word}]%
{\bold{\dummyparameter{word}}
\italic{\dummyparameter{cat
umber=\v!no,
\c!language=\s!ru]
\def\Ruso[#1]%
{\begingroup
\getdummyparameters[word=,category=,meaning=,#1]%
\Russian[\dummyparameter{word}]%
{\bold{\dummyparameter{word}}
\italic{\dummyparameter{category}}
\dummyparameter{meaning}}%
\endgroup}
\protect
\Ruso
[word=исчис
\expanded{\writetolist[chapter]{}{#1}}
\startBilingualTitle
\noindentation\setlatin{}\tfd\setupinterlinespace\feature[+][smallcaps]\word{#1}\feature[<]
\nextBilingualTitle
\hfill\nextBilingualTitle
\noindentation\setarabic{}\tfd\setupinterlinespace{#2}
\stopBilingual
(as expected) when closesymbol is
> not set (or, is empty). Therefore, here I have set closesymbol={U+200B},
> which is the zero width space.
>
> Thanks,
> kauśika
Dear list,
As it turns out, my workaround here is subpar since it inserts an undesired
line after the descr
nored.
With \NS the alignment is also wrong in the same way.
\starttext
\starttabulate[|lp(.2\textwidth)|lp(.2\textwidth)|lp(.2\textwidth)|lp(.2\textwidth)|]
Default \NC Linux \NC MacOS \NC Windows \NC\NR
\HL
Text Proc \NC LibreOffice \NC Apple Pages \NC MS Office (Word) \NC\NR
PDF Viewer\NC Evi
pagenumbering
> [alternative=doublesided]
>
> \showframe
>
> \starttext
> \dorecurse{10}{\expanded{\chapter{Chapter
> \convertnumber{word}{\recurselevel
> \stoptext
this looks interesting, but it's not quite what I want.
I think I would like to have a different so
?
\setuphead
[chapter]
[page=yes,
alternative=inmargin,
location=outer,
align=outer]
\setuppagenumbering
[alternative=doublesided]
\showframe
\starttext
\dorecurse{10}{\expanded{\chapter{Chapter
\convertnumber{word}{\recurselevel
\stoptext
Wolfgang
; > \startluacode
>> >
>> > local upperlimit = 9
>> >
>> > context.starttabulate({ "|l|l|l|" })
>> > for i=1,upperlimit do
>> > context.NC()
>> > context("word 1")
>> > context.NC()
>&g
;
> > context.starttabulate({ "|l|l|l|" })
> > for i=1,upperlimit do
> > context.NC()
> > context("word 1")
> > context.NC()
> > context("word 2")
> > context.NC()
> > context("word 3")
> > context.NC()
()
context("word 1")
context.NC()
context("word 2")
context.NC()
context("word 3")
context.NC()
context.AR()
end
context.stoptabulate()
\stopluacode
\stoptext
But it compiles with no problems with MKIV.
context version: 2021.09.06 11:47
How to avoid this wit
Dear list,
In the MWE below, ConTeXt lmtx throws an error with the message in the
title:
\starttext
\startluacode
local upperlimit = 9
context.starttabulate({ "|l|l|l|" })
for i=1,upperlimit do
context.NC()
context("word 1")
context.NC()
context("word 2"
\startchoice
\choice not so short choice
\choice must wrap here
\choice another choice
\choice yet another choice
\stopchoice
results in
A. not so short choiceB. must wrap here
C. another choice___D. yet another choice
In another word, it should have the sa
= through the start of the word "this". See pdf here:
weird indeed (has to do with 'ligaturing') ... i'll look into it
-
Hans Hagen | PRAGMA ADE
Ridderst
My Minimal:
\starttext
$==$ this
$f(x)= x^2$
\switchtobodyfont[times]
$==$ this
$f(x)= x^2$
\switchtobodyfont[modern]
$==$ this
$f(x)= x^2$
\stoptext
This is producing an =, a large space (about two characters wide), then an
= through the start of the word "this". See pdf he
s too long. Source (pretty
> official):
> https://www.academie-francaise.fr/abreviations-des-adjectifs-numeraux
>
> So for numbers starting from 3 the proper abbreviation is ‘e’.
>
> For 1 and 2 it’s more complicated, however, as it depends on the
> gender. For 1:
> * mascul
ause it’s too long. Source (pretty
official):
https://www.academie-francaise.fr/abreviations-des-adjectifs-numeraux
So for numbers starting from 3 the proper abbreviation is ‘e’.
For 1 and 2 it’s more complicated, however, as it depends on the
gender. For 1:
* masculine: 1er
* feminine: 1re
In add
f
>> fonts > beware: no fonts are loaded yet, using 'lm mono' in box
>> fonts > checking > char i (U+00069) in font '' with id 0: missing
>> fonts > checking > char n (U+0006E) in font '' with id 0: miss
(U+0006E) in font '' with id 0: missing
warnings. Maybe some things need to be adjusted?
THis normally means that you have someting before the \starttext that
gets typeset (here the word "in")
Hans
-
header,footer,right]
>
> \definehead
>[MyPart]
>[part]
>
> \definecharacterkerning
>[mypartkerning]
>[factor=0.,
> features=letterspacing]
>
> \setuphead
>[MyPart]
>[placehead=yes,
> number=no,
> page=blan
Thank you, Hans. Very nice indeed your solutions.
Marcus Vinicius
On Sat, Aug 7, 2021 at 5:37 AM Hans Hagen wrote:
> On 8/6/2021 10:58 PM, Marcus Vinicius Mesquita via ntg-context wrote:
> > Dear list,
> > in the mwe below, the expected result is ok for most entries but fails
&g
haracterkerning
[mypartkerning]
[factor=0.,
features=letterspacing]
\setuphead
[MyPart]
[placehead=yes,
number=no,
page=blankpagebreak,
header=empty,
footer=empty,
align={flushleft,nothyphenated},
style=MyPartFont,
textstyle={\setcharacterkerning[mypartk
On 8/6/2021 10:58 PM, Marcus Vinicius Mesquita via ntg-context wrote:
Dear list,
in the mwe below, the expected result is ok for most entries but fails
when the word contains the letters ó or ô.
We get zoolco instead of zoológico, and termtro instead of termômetro.
What am I doing wrong?
mwe
Dear list,
in the mwe below, the expected result is ok for most entries but fails when
the word contains the letters ó or ô.
We get zoolco instead of zoológico, and termtro instead of termômetro. What
am I doing wrong?
mwe:
\def\stripnumber#1%
{\cldcontext{lpeg.match(lpeg.stripper
ning over the node list, the second
mechanism is using a callback at the hyphenation level (so per language)
where each word is anyway checked against an exception list, so in
addition that word can now be fed into a function and depending on
outcome be fed back into the machinery
(there are tracke
201 - 300 of 3248 matches
Mail list logo
