t; is a ligature. So in giving variants for both
words, we cannot just
separate samyag and gomaya, for then the ligature gg is not printed
correctly. We also want to
quote the correct word samyag in the apparatus (which is in roman!).
Now, to make things more
complicated the xml text should
Tex generated by a shell script contains the 300 plus
> > commands with the structure
> >
> > \tfa{ \bold{variable} \par (12 - 0.13) } \blank
> >
> > The problems are that - a) the group, with the two short paras get
> > separated into different columns and someti
;) escribió:
Am typesetting a book that has 'STUDY ONE', 'STUDY TWO' etc. in
place of
CHAPTER ONE, etc. I have no difficulty getting 'STUDY' with
\setuplabeltext[chapter=STUDY~], and I can achieve 'STUDY One'
with the
key conversion=Words in
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.
Am typesetting a book that has 'STUDY ONE', 'STUDY TWO' etc. in place of
CHAPTER ONE, etc. I have no difficulty getting 'STUDY' with
\setuplabeltext[chapter=STUDY~], and I can achieve 'STUDY One' with the
key conversion=Words in \setuphead[chapter].
get
separated into different columns and sometimes pages. How can I prevent
that? In other words, how do I tell Context that this should be treated
as cohesive unit? b) The horizontal space doesn't align across columns.
This probably is because the different conjuncts in each of these lines
rfbuzz (which is what Xe(La)TeX uses
> by default) uses some heuristics to work out these conjuncts (?!).
>
> To answer your specific question regarding the conjuncts in the given
> words you have to use some Unicode hacking to get what you want in
> ConTeXt.
>
> In each of the follow
ssues might be due to
differences in implementation. [Not entirely sure since I am a novice]. My
guess is that Harfbuzz (which is what Xe(La)TeX uses by default) uses some
heuristics to work out these conjuncts (?!).
To answer your specific question regarding the conjuncts in the given words
On Friday, December 31, 2021 6:25:01 PM IST Ajith R via ntg-context wrote:
> The problems are that - a) the group, with the two short paras get
> separated into different columns and sometimes pages. How can I prevent
> that? In other words, how do I tell Context that this should be tre
. How can I prevent
that? In other words, how do I tell Context that this should be treated
as cohesive unit? b) The horizontal space doesn't align across columns.
This probably is because the different conjuncts in each of these lines
have different heights. How can I ask Context to treat ea
ere (unless
it among those things that google grabs - and at some point possible
discards)
The actual problem was with the italic ligatures "a_s", "e_s", "é_s",
"i_s" and "u_s", that should occur only at the end of words and not
everywhere. In
best to help Google improving this font, but I don’t
have time yet.
The actual problem was with the italic ligatures "a_s", "e_s", "é_s", "i_s" and
"u_s", that should occur
only at the end of words and not everywhere. Instead of removing the unwa
lookups = { 1 }
}
}
}
}
A better an dmore reliable approach is this:
\startluacode
local demo = {
name= "demo",
options = {
{
patterns = {
fio = "f|io",
> otherstext={\btxspace{\it\btxlabeltext{others}}},
> etallimit=10,
> etaldisplay=\btxparameter\c!etallimit,
> journalconversion=\v!normal,
> monthconversion=\v!month,
> title=yes,
> separator:names:2={\btxcomma},
> separator:names:3={\btxcomma\btxlabe
{and}\space}]
\setupbtxlist[chicagonum]
\definebtxrendering[chicagonum]
[specification=chicagonum,
sorttype=authoryear,
numbering=no]
\startsetups btx:chicagonum:list:book
\btxdoif{author}{
\btxflush{author}
\btxperiod
}
\btxdoif{title}{
{
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
age[es]
\enableexperiments[fonts.compact]
\setupbodyfont[dejavu] % computer-modern-unicode]
\setuphead[chapter]
[alternative=middle]
\defineregister[Russian]
\setupregister[Russian]
[expansion=yes,
balance=no,
n=2,
command=\Words,
pagenumber=no,
language=ru]
\def\Ruso[#1]%
{\begi
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
ieved:
\unprotect
\mainlanguage[\s!es]
\enableexperiments[fonts.compact]
\setupbodyfont[computer-modern-unicode]
\setuphead[chapter]
[\c!alternative=\v!middle]
\defineregister[Russian]
\setupregister[Russian]
[\c!expansion=\v!yes,
\c!balance=\v!no,
\c!n=2,
\c!command=\Words,
\c!pagen
Last time I was at the ConTeXt conference, a few years back, there was talk
about "monetization" of ConTeXt. In other words, using ConTeXt to generate
revenue. I was wondering if this is still on the agenda. Perhaps we could
have a discussion on how to achieve this. I have one pos
k you, Wolfgang. I'll look into it.
>>>
>>> Regards
>>>
>>> Marcus Vinicius
>>>
>>> On Tue, Oct 26, 2021 at 1:22 AM Wolfgang Schuster <
>>> wolfgang.schuster.li...@gmail.com> wrote:
>>>
>>>
Vinicius
>>
>> On Tue, Oct 26, 2021 at 1:22 AM Wolfgang Schuster <
>> wolfgang.schuster.li...@gmail.com> wrote:
>>
>>> Marcus Vinicius Mesquita via ntg-context schrieb am 26.10.2021 um 00:38:
>>> > Dear list,
>>> >
>>> > Is t
> Is there anything in ConTeXt that could help me with automatic
>> > romanization of ancient greek words?
>>
>> Is the Transliterator module from Philipp Gesang what you're looking for?
>>
>>
>> https://modules.contextgarden.net/cgi-bin/module.cgi/ruid
s there anything in ConTeXt that could help me with automatic
> > romanization of ancient greek words?
>
> Is the Transliterator module from Philipp Gesang what you're looking for?
>
>
> https://modules.contextgarden.net/cgi-bin/module.cgi/ruid=5025059042/action=view/id=50
>
Marcus Vinicius Mesquita via ntg-context schrieb am 26.10.2021 um 00:38:
Dear list,
Is there anything in ConTeXt that could help me with automatic
romanization of ancient greek words?
Is the Transliterator module from Philipp Gesang what you're looking for?
https://modules.contextgarde
Dear list,
Is there anything in ConTeXt that could help me with automatic romanization
of ancient greek words?
TIA
Marcus Vinicius
--
Todas as coisas fatigam o corpo, salvo a música, que não fatiga nem o corpo
nem seus membros, por ser descanso da alma, primavera do coração, distração
do
; \par
> \stopTEXpage
> }
>
> \stoptext
>
> it's an addendum to the widowpenalties and clubpenalties introduced by
> etex but this time it's horizontal; the orphan penalties will be
> inserted before spaces (aka spaceskip, xspaceskip and zerospaceski
paces (aka spaceskip, xspaceskip and zerospaceskip
glue) so in this case 4000 between the last two 'words' and this
trickery can be used to make sure that the last line is not too short
\orphanpenalties 4 4000 3000 -12000 1000\relax
is also intereting
it's work in progress (i
Ok, now that I've had some time to experiment with effects and attributes,
here's what I ended up with. It uses an overlaid double draw to create outlined
text with optional fill (white), border (black). I've only tested it with words
so haven't worked out how it could b
e no effect. What am I doing wrong?
>
> Please advise.
>
> Thanks,
> kauśika
Dear all,
I have also tried this with the available 'words' conversion set. Even in that
case, the conversion is n
\btxparameter{\c!separator:vons}
}
\fi
\ifx\currentbtxsurnames\empty \else
\WORDS{\currentbtxsurnames} % <-- changed line
\ifx\currentbtxjuniors\empty \else
\btxparameter{\c!separator:juniors}
\currentbtxjuniors
\fi
\fi
\
g
\definefont[MyPartFont][EBGaramond at 24pt][line=36pt] %font command to be
used for setting MyPart heading texts
%Macro for adjusting kerning of MyPart heading texts (can any of this can
be handled in the \definefont call?):
\define[1]\MyPartTextCommand{%
\kerncharacters[0.]%increase lett
ok, one can do that
with attributes but that is less efficients options have been introduced
for ligatures, kerns, expansion etc (you can diff the attached lmt file
with the lua file of the same name to see the difference in approach
2. Both mechanisms only work for complete words, is that rig
mechanisms only work for complete words, is that right? So I
can't just provide a pattern such as "uf|forder," I have to provide a
full list with all inflected forms:
auf|fordern
auf|fordert
auf|fordernd
Auf|forderung
Auf|forderungen
and for 1-3 also the forms with a capit
as an interesting result, the first
>>>> character of the words is not in bold. This did not happen with
>>>> lettrine in mkii
>>>
>>> I do not have an answer to your question, but I'd like to point out that
>>> you can keep using le
Gerben Wierda schrieb am 21.07.2021 um 12:00:
On 19 Jul 2021, at 09:56, Nicola <mailto:nvitacolo...@gmail.com>> wrote:
On 2021-07-18, Gerben Wierda <mailto:gerben.wie...@rna.nl>> wrote:
PS. switching \kap and \bf has an interesting result, the first
character of the words is
On 2021-07-21, Gerben Wierda wrote:
>> On 19 Jul 2021, at 09:56, Nicola wrote:
>>
>> On 2021-07-18, Gerben Wierda wrote:
>>> PS. switching \kap and \bf has an interesting result, the first
>>> character of the words is not in bold. This did not happen with
> On 19 Jul 2021, at 09:56, Nicola wrote:
>
> On 2021-07-18, Gerben Wierda wrote:
>> PS. switching \kap and \bf has an interesting result, the first
>> character of the words is not in bold. This did not happen with
>> lettrine in mkii
>
> I do not have an answ
y (\blank[2*big] is the default command after chapter).
> [...]
> PS. switching \kap and \bf has an interesting result, the first
> character of the words is not in bold. This did not happen with lettrine
> in mkii,
Please, avoid adding questions after a multiline signature (because t
On 2021-07-18, Gerben Wierda wrote:
> PS. switching \kap and \bf has an interesting result, the first
> character of the words is not in bold. This did not happen with
> lettrine in mkii
I do not have an answer to your question, but I'd like to point out that
you can keep using
Enterprise Architecture <https://ea.rna.nl/> (main site)
Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>
PS. switching \kap and \bf has an interesting result, the first character of
the wo
at even if
the whole text is wrapped in {\em ...}, the text in the formulae are in
roman font. I've tried the following:
\starttext
{\em
\startformula \startalign[align=left]
\NC {\rm multiple words of text} \NR % Does not provide spacing
\NC \mathrm{multiple words of text} \NR % Does not
help the
words get hyphenated at certain points.
Perhaps a new "optional" hyphenation point macro can be added that
would have super-powers to override the align parameter. There would
be no surprises using such a feature.
We can't use \= unless we drop the \= being macros (an
\explicithyphenationmodecode\explicitdiscretionary
\endgroup}
i will ponder this
I believe that \- defines an *optional* hyphenation point.
Specifying nothyphenated should not hyphenate, even at optional points.
The author can otherwise use hyphenated and arrange to help the
words get hyphenated at certain points
}
i will ponder this
I believe that \- defines an *optional* hyphenation point.
Specifying nothyphenated should not hyphenate, even at optional points.
The author can otherwise use hyphenated and arrange to help the words
get hyphenated at certain points.
Perhaps a new "optional" h
\- defines an *optional* hyphenation point.
Specifying nothyphenated should not hyphenate, even at optional points.
The author can otherwise use hyphenated and arrange to help the words
get hyphenated at certain points.
Perhaps a new "optional" hyphenation point macro can be added
.
Specifying nothyphenated should not hyphenate, even at optional points.
The author can otherwise use hyphenated and arrange to help the words
get hyphenated at certain points.
Perhaps a new "optional" hyphenation point macro can be added that would
have super-powers to override
rtexceptions[it]
appli-ca<200b>ble
obli-gated
\stopexceptions
So it seems that the answer remains the same from when Denis posted a
similar question a few months ago.
indeed, i just wasted an hour figuring out that there is some non letter
in there; so there will never be a matc
lties\widowpenalties{2}{1}
\stopsetups
\starttext
\setuplayout[setups=penalties1]
\samplefile{tufte}\par
Here we are writing some more words to see the effect.
Here we are writing some more words to see the effect.
Here we are writing some more words to see the effect.
\page
\setuplayout[s
rttext
\input zapf
\stoptext
Lines 3, 7, 10, 12 and 13 lack spaces between words:
Coming back to the use of typefaces in
electronic publishing: many of the new
typographersreceivetheirknowledgeand
information about the rules of typogra-
phy from books, from computer maga-
zines
On 5/8/21 3:58 PM, denis.ma...@ub.unibe.ch wrote:
> Looks like I can confirm this... see below. But it seems to depend on your
> PDF viewer. Results in Sumatra and Acrobat differ.
Many thanks for your confirmation, Denis.
With SumatraPDF 3.1.2, I get lines without spaces between word
8. Mai 2021 13:33
> An: mailing list for ConTeXt users
> Betreff: [NTG-context] weird word breaking in Win64
>
> Dear list,
>
> the following sample breaks some words not right in Win64 (I cannot
> reproduce it in Linux):
>
> \enabledirectives[fonts.
Dear list,
the following sample breaks some words not right in Win64 (I cannot
reproduce it in Linux):
\enabledirectives[fonts.injections.method=advance]
\setuppapersize[A6]
\definefontfamily[mainface][rm]
[TeX Gyre Pagella]
\setupbodyfont[mainface]
\starttext
\input zapf
df - but it calls an unrestricted latex.
% rpdfcrop - maybe ok, but let's get experience with repstopdf first.
% texindy,xindy - but is the module feature insecure?
% ulqda - but requires optional SHA1.pm, so why bother.
% tex, latex, etc. - need to forbid --shell-escape, and inherit openou
in luametatex the hyphenation machinery has all kind of extra controls
and the hccode mechanism was introduced as side effect of a feedback
mechanism that also can handle compound words better (althoiugh one can
of course dispute the 'better' part)
From luametatex.pdf in the distribut
a
ligature replacement.
once i know what' sbest i''l make some option someplace
I think it would be better not to change defaults that have been there
for years (to avoid unpleasant surprises).
I was always able to hyphenate words before and after both — and – and
they didn’t include line
il/ntg-context/2021/101871.html as a
ligature replacement.
> once i know what' sbest i''l make some option someplace
I think it would be better not to change defaults that have been there
for years (to avoid unpleasant surprises).
I was always able to hyphenate words before
uments I see
that I have been using "\tfc $+$" in some of my tikz code for about 4 years.
So, it appears to be a old feature. I am thinking of changing the wiki from:
These quick font switches are meant for changing the font style, alternative,
or size of a few words: they do not chan
\tfc $+$" in some of my tikz code for
about 4 years. So, it appears to be a old feature. I am thinking of changing
the wiki from:
These quick font switches are meant for changing the font style, alternative,
or size of a few words: they do not change the bodyfont, so they don't affect
15
> > >> An: 'mailing list for ConTeXt users'
> > >> Betreff: Style options and setupinterlinespace
> > >>
> > >> Hi,
> > >>
> > >> the wiki (https://wiki.contextgarden.net/Font_Switching) currently
> says:
> > &
> >> Betreff: Style options and setupinterlinespace
> >>
> >> Hi,
> >>
> >> the wiki (https://wiki.contextgarden.net/Font_Switching) currently says:
> >>
> >>
> >>> These quick font switches are meant for changing the font style
:
These quick font switches are meant for changing the font style, alternative, or size of a few
words: they do not change the bodyfont, so they don't affect interline spacing or math font
sizes. So, if you want to change the font size of an entire paragraph, use
\switcht
.contextgarden.net/Font_Switching) currently says:
>
>> These quick font switches are meant for changing the font style,
>> alternative, or size of a few words: they do not change the bodyfont, so
>> they don't affect interline spacing or math font sizes. So, if you want
>&
>
> > These quick font switches are meant for changing the font style,
> > alternative, or size of a few words: they do not change the bodyfont, so
> > they don't affect interline spacing or math font sizes. So, if you want to
> > change the font size of an entire
the wiki (https://wiki.contextgarden.net/Font_Switching) currently says:
> These quick font switches are meant for changing the font style, alternative,
> or size of a few words: they do not change the bodyfont, so they don't affect
> interline spacing or math font sizes. So, i
Hi,
the wiki (https://wiki.contextgarden.net/Font_Switching) currently says:
> These quick font switches are meant for changing the font style, alternative,
> or size of a few words: they do not change the bodyfont, so they don't affect
> interline spacing or math font sizes. S
quot;002D secondpart\blank
firstpart\char"2010 secondpart\blank
firstpart\char"2013 secondpart\blank
firstpart\char"2014 secondpart
\type{firstpart---secondpart}
all work as I expect (both words get hyphenated).
The trep feature was already stripped to only ' repla
Hi,
a couple of weeks ago Hans has implemented a tracker that adds a list of
hyphentated words to the log file. I finally managed to play with this. The
result is attached to this mail.
This will permit analyzing hyphenations based on a ConTeXt log file. You need
to enable hyphenation tracking
some more code (doable).
This feature relates to Denis collection of German compound words and
ligature prevention data. Dutch has the same issue. (Denis: we can ditch
the compound word entries now, the ones with -.)
Also, this kind of automatism (keep in mind that normally tex won't
t; > Thank you.
> >
> > MWE where I expect the word "ett" instead of "1":
> > \mainlanguage[sv]
> > \starttext
> > \convertnumber{words}{1}
> > \stoptext
> You have to remake the format:
>
> context --make
>
> (I'll check the co
l if you could
point me in the right direction. There must be some step that I'm
missing.
Thank you.
MWE where I expect the word "ett" instead of "1":
\mainlanguage[sv]
\starttext
\convertnumber{words}{1}
\stoptext
You have to remake the format:
context --make
(I'll
teful if you could
point me in the right direction. There must be some step that I'm
missing.
Thank you.
MWE where I expect the word "ett" instead of "1":
\mainlanguage[sv]
\starttext
\convertnumber{words}{1}
\stoptext
ConTeXt doesn't use the source files itself when y
ere must be some step that I'm
missing.
Thank you.
MWE where I expect the word "ett" instead of "1":
\mainlanguage[sv]
\starttext
\convertnumber{words}{1}
\stoptext
attachment_core-con.lua
Description: Binary data
___
ch would
allows me to get as far as 66 (if I were to need every biblical book)?
Julian
On 16/4/21 5:24 pm, Hans Hagen wrote:
On 4/15/2021 11:28 AM, jbf wrote:
My simple MWE:
\defineregister[bibcit]
\setupregister[bibcit][%
indicator=no,
before=]
text... \bibcit[a]{Gen 3:6 (MAC) }Gen 3:6
On 4/15/2021 11:28 AM, jbf wrote:
My simple MWE:
\defineregister[bibcit]
\setupregister[bibcit][%
indicator=no,
before=]
text... \bibcit[a]{Gen 3:6 (MAC) }Gen 3:6
(and so one for each Genesis reference, then moving on to Leviticus with
[b] etc.)
In other words, I have used the key
My simple MWE:
\defineregister[bibcit]
\setupregister[bibcit][%
indicator=no,
before=]
text... \bibcit[a]{Gen 3:6 (MAC) }Gen 3:6
(and so one for each Genesis reference, then moving on to Leviticus with
[b] etc.)
In other words, I have used the key option [] using the alphabet to
Hi,
a small update on this one :
I’ve built a small python script that uses the patterns from the selnolig
package to extract words with suspicious ligatures from the word list provided
by the Uni Leipzig corpus project. Running the script over a corpus of over 1
million words produces the
; oblig-ated, less
so.
Taco reminded that when producing a set of hyphenation patterns from a
list of hyphenated words, we’re essentially compressing information, and
that some minor deviations are to be expected. However, in my
experience, unexpected breakpoints are almost never due to chance
://www.opentaal.org/projecten/woordafbreking is from
2009. There have apparently been recent updates by a single person (who
incidentally sometimes contributes to the German hyphenation working
group), but they’re rather generic.
fwiw: They are active in collecting words (they also do stuff for open
office
be to use selnoligs patterns in a script
>>>that can be run over a large corpus, such as the DWDS (Digitales
>>>Wörterbuch der deutschen Sprache). That should produce us a more
>>>complete list of words where ligatures must be suppressed.
>>
>> where i
h wrote:
> > Hi everyone
> >
> > Now that Hans has implemented the new ligature suppression mechanism
> > via language goodies - thanks again Hans! - we now need to come up
> > with wordlists.
> >
> > I've started working on a list of German words wit
b.unibe.ch wrote:
> > Hi everyone
> >
> > Now that Hans has implemented the new ligature suppression mechanism
> > via language goodies - thanks again Hans! - we now need to come up
> > with wordlists.
> >
> > I've started working on a list of German words wit
Untested. Lists are not subject to copyright, so public domain should be
legal, even though SE posts are CC-BY-SA. When a word has a single suffix
or prefix (e.g., safflower/s), the two words are listed together, rather
than using an explicit suffix/prefix section.
return {
name
On 4/3/2021 5:06 PM, denis.ma...@ub.unibe.ch wrote:
<https://github.com/denismaier/context-nolig-wordlist>
For those interested, that file only has ligature prevention definitions.
{
actions = {
["|"] = "noligature"
},
words = [[
Auf|lageflä
On 4/3/2021 5:06 PM, denis.ma...@ub.unibe.ch wrote:
1. The new language options features include a tracker that allows for
tracking for which words in a given document ligature prevention
happened, and which words haven’t been touched by the mechanism. It
should be possible to
On 4/3/2021 5:06 PM, denis.ma...@ub.unibe.ch wrote:
Hi everyone
Now that Hans has implemented the new ligature suppression mechanism via
language goodies – thanks again Hans! – we now need to come up with
wordlists.
I’ve started working on a list of German words with ligatures that
should
Hi everyone
Now that Hans has implemented the new ligature suppression mechanism via
language goodies - thanks again Hans! - we now need to come up with wordlists.
I've started working on a list of German words with ligatures that should be
suppressed. The list is derived from the word
nguageoptions
to make it into a compound word (use both to prevent ligatures too).
There's more to come once we get the full picture.
I leave it to Denis to organize the collection of words and definitions
that go into a goodie file.
Hans
ps. Sometimes I wonder if for every new featur
ay to deal with this would be in
the hyphenator. What do you think about this now, a couple of years later?
And, while we're at it: how do you deal with words like "begrifflich" where
you'll want the ff ligature, but not the ffl ligature.
I've tried this
\replaceword[ligs
ay to deal with this would be in
> the hyphenator. What do you think about this now, a couple of years later?
> >
> > And, while we're at it: how do you deal with words like "begrifflich" where
> you'll want the ff ligature, but not the ffl ligature.
&g
ay to deal with this would be in
the hyphenator. What do you think about this now, a couple of years later?
And, while we're at it: how do you deal with words like "begrifflich" where
you'll want the ff ligature, but not the ffl ligature.
I've tried this
\replaceword[ligs
t do you think about this now, a couple of years later?
And, while we're at it: how do you deal with words like "begrifflich" where
you'll want the ff ligature, but not the ffl ligature.
I've tried this
\replaceword[ligs][begrifflich][begri{ffl}ich]
But this break
On 3/24/2021 8:24 PM, denis.ma...@ub.unibe.ch wrote:
Anything, I've missed? Other aspects to think about here? How about
performance issues? (The blockligatures-mechanism resulted in this: with
a word list of about 2200 words it took a bit more than five seconds to
process 23 A5 pages
LMTX.
Can be used for words with multiple wrong ligatures (Auflaufform).
Does not take derived forms into account (e.g., replacements for Auflage and
Auflagen must both be defined).
2. \blockligatures
Works as a font feature to block certain ligatures
Works also for derived forms of a given word
accumulate ? (I'm thinking about preparing a general list of
> > > exceptions, but of course you will also want individual
> > > exceptions.)
> >
> > you can find out by trying ...
>
> Ok, it does...
>
Regarding the plan of preparing a list of suppressed l
;;>
ab
ab
}{}
\stoptext
No output is produced. This has been verified with live.contextgarden.net.
In order for output to be produced, must be changed to and
must be changed to , but these are in the wrong
namespace in this context. In other words, this
text
No output is produced. This has been verified with live.contextgarden.net.
In order for output to be produced, must be changed to and
must be changed to , but these are in the wrong
namespace in this context. In other words, this bug applies to the keyword
element in an apply elem
rse{0}{15}{1}{
{\advance\hsize -#1cm \input tufte \par} }
\stoptext
This will give you in the log file (first and second); the test run has narrow
lines where one word crossed several lines, which actually is the main
complication here:
hyhenated > start hyphenated words
h
ecause no one expects it).
Anyway, a pre-weekend distaction:
\starttext
\enabletrackers[hyphenation.applied]
\enabletrackers[hyphenation.applied.console]
\dontcomplain \dostepwiserecurse{0}{15}{1}{
{\advance\hsize -#1cm \input tufte \par} }
\stoptext
This will give you in the log file (first and second
ce\hsize -#1cm \input tufte \par}
}
\stoptext
This will give you in the log file (first and second); the test run has
narrow lines where one word crossed several lines, which actually is the
main complication here:
hyhenated > start hyphenated words
hyhenated >2 :
201 - 300 of 2388 matches
Mail list logo
