ation journal in Word that I'm hoping to
switch to ConTeXt. Each article is written by a different author and I
currently provide a Word template so they can see how their article will
eventually look and how long it is, etc. I want to do the same for the ConTeXt
version so I have created a te
\convertnumber{word}{#1}}
\dorecurse{5}
{\section{Section \convertnumber{word}{##1}}
\dorecurse{\numexpr#1+##1\relax}{\samplefile{lorem
\stoptext
Wolfgang
___
If your question is of interest to others as
; > \definefontfamily[hebrew] [rm] [SBL Hebrew] [features=f:pointedhebrew]
> > %Set the body font:
> > \setupbodyfont[hebrew]
> > %Set up right-to-left alignment:
> > \setupalign[r2l]
> > \starttext
> > %Characters after normalization, in Unicode canonical
[r2l]
\starttext
%Characters after normalization, in Unicode canonical order (bet +
segol + dagesh + final nun):
בֶּן
%A word with characters in typographically recommended order (bet +
dagesh + segol + final nun):
בֶּן
\stoptext
\startluacode
[rm] [SBL Hebrew] [features=f:pointedhebrew]
%Set the body font:
\setupbodyfont[hebrew]
%Set up right-to-left alignment:
\setupalign[r2l]
\starttext
%Characters after normalization, in Unicode canonical order (bet +
segol + dagesh + final nun):
בֶּן
%A word with characters in typog
three very short
single-word lines with \\ at the end but it may also be a large paragraph.
So, I would like to find a way to let the \framed become a box as narrow as
possible, but not growing wider than a pre-set width.
This is way too difficult for my meagre skills. What I could do (but I
few years ago [1]
>> which can be adapted to your problem.
>>
>> \startluacode
>>
>> local shared = {
>> start = 1,
>> length = 1,
>> before = nil,
>> after = nil,
>> left = fals
ength = 1,
before = nil,
after = nil,
left = false,
right = false,
}
local all = table.setmetatableindex({ }, function(t,k)
return shared
end)
languages.hyphenators.traditional.installmethod("dna",
function(di
hared = {
> start = 1,
> length = 1,
> before = nil,
> after = nil,
> left = false,
> right = false,
> }
>
> local all = table.setmetatableindex({ }, function(t,k)
> return shared
>
= nil,
left = false,
right = false,
}
local all = table.setmetatableindex({ }, function(t,k)
return shared
end)
languages.hyphenators.traditional.installmethod("dna",
function(dictionary,word,n)
return a
ke no difference towards the result.
This is the MWE based on your solution:
\define[2]\mycommandc{
\startxrow
\startxcell o#1 \stopxcell
\startxcell \tt\WORD{5'-#2} \stopxcell
\stopxrow
}
\definebreakpoint[mybreaks][][nright=100,nleft=100,type=1]
\setbreakpoints[mybreaks]
On 4/23/2020 15:01, Benjamin Buchmuller wrote:
Sorry, I have just realized that the problem might not be \WORD{} actually, so
this one hyphenates:
\define[2]\mycommand{
\startxrow
\startxcell o#1 \stopxcell
\startxcell \tt\WORD #2 \stopxcell
\stopxrow
Sorry, I have just realized that the problem might not be \WORD{} actually, so
this one hyphenates:
\define[2]\mycommand{
\startxrow
\startxcell o#1 \stopxcell
\startxcell \tt\WORD #2 \stopxcell
\stopxrow
}
Whereas these ones don’t:
\define[2
Hi again,
I am reading a CSV file into ConTeXt which contains long DNA sequences (>> 40
characters) to place in xtables. So far, this works fine. However, I need to
uppercase the entries and need to \tt them. When I do this inside \WORD
however, they don’t hyphenate any more.
I’m
some older acrobat liked it more when displaying them and
often these older feature are made such that acrobat was served). And
pdf data structures are not something typeset, which for means means:
'word' is just that 'word'.
Hans
---
allowed,
* hyphenation patterns have been applied on the composed word, while before
switching (default) not.
Tested with TL2019 as well as with the newest.
How can these side-effects be suppressed?
Tomáš
%% MWE
\startluacode
fonts.protrusions.classes.tomas_hala = {
vector
I was wrong. The \penalty is not the culprit, but it turns out to be the \Word
macro that introduces the through a parfillskip_code in the internal
list.
dr. Hans van der Meer
> On 5 Mar 2020, at 09:33, Hans van der Meer wrote:
>
> Found the cause in my case: a \penalty0 statement
has a list of predefined styles and describes how to set up
an alternative style:
https://wiki.contextgarden.net/Style_Alternatives#Defining_a_Style_Alternative
From the wiki page:
\definealternativestyle [head:neat] [\WORD] []
While \definealternativestyle[PoemFirstWord][{\bf\upperc
ribes how to set up
an alternative style:
https://wiki.contextgarden.net/Style_Alternatives#Defining_a_Style_Alternative
From the wiki page:
\definealternativestyle [head:neat] [\WORD] []
While \definealternativestyle[PoemFirstWord][{\bf\uppercasing}][] will
work for my needs, I am conc
On 3/4/2020 5:09 PM, Thangalin wrote:
Looking to uppercase the first word of a poem:
\setupindenting[yes, 0.75em]
\setupinitial[
state=start,
n=2,
distance=\zeropoint,
]
% This does not appear to work?
\definealternativestyle[PoemFirstWord][\WORD][]
\definefirstline[PoemFirstLine
Looking to uppercase the first word of a poem:
\setupindenting[yes, 0.75em]
\setupinitial[
state=start,
n=2,
distance=\zeropoint,
]
% This does not appear to work?
\definealternativestyle[PoemFirstWord][\WORD][]
\definefirstline[PoemFirstLine][
alternative=word,
style=PoemFirstWord
ep the space between the heading text and the paragraph from
>> stretching/shrinking in a description?
>>
>> MWE that exhibits variable space between the heading (the defined word) and
>> the paragraph text:
>>
>>
>>\definedescription
>
On Tue, 18 Feb 2020 11:16:58 -0800
Kevin Kenan wrote:
> How can I keep the space between the heading text and the paragraph from
> stretching/shrinking in a description?
>
> MWE that exhibits variable space between the heading (the defined word) and
> the
How can I keep the space between the heading text and the paragraph from
stretching/shrinking in a description?
MWE that exhibits variable space between the heading (the defined word) and the
paragraph text:
\definedescription
[definition]
[headstyle=italic,
indenting
questions, I'm still "in captivity" of swtching
fonts, their styles and font sizes by clicking a combo in Word toolbar
(although I quit using Word about 15 ys ago). And although I'm aware of
different dealing with fonts in TeX (and in professional typesetting in
general), i
I would suggest to advertise with the ending another trademark that is not
a zero-entropy word in the programming world when not randomly capitalized,
and, if possible, that is not an everyday English word either.
Mkiv is a good choice for the moment. If there would be no Mkvi and so on,
it is
t of the
columnset, I guess), and floats, floats, floats.
But here we are:
\setuppapersize[A6]
\showframe[text]
\setupalign[flushleft,broad,nothyphenated]
\define[2]\MySection{\vbox{#2}}
\setuphead[section][
command=\MySection,
%align={flushleft,broad,nothyphenated},
]
\starttext
\section{R
ommand since I also set color and font, but
>> style={\MyDefinedFont\WORD}
>> actually works.
>
> Use \setcharactercasing with style keys when you need multiple settings, it's
> faster than \WORD because no group check is needed.
Ok.
>> My remaining problem in this c
Henning Hraban Ramm schrieb am 11.01.2020 um 19:38:
Thank you very much!
I tried a \framed to no avail.
\framed needs a align setting to allow line breaks.
And I thought I needed my own command since I also set color and font, but
style={\MyDefinedFont\WORD}
actually works.
Use
[big]},
alternative=normal,
after={\blank[halfline]},
numbercolor=,
sectionseparatorset=,
]
\stopsectionblockenvironment
\definefirstline [5W][alternative=word, n=5,s
> Am 2020-01-11 um 19:21 schrieb Wolfgang Schuster
> :
>
> Henning Hraban Ramm schrieb am 11.01.2020 um 18:53:
>> Hi again,
>> I’m trying to get uppercase titles with \WORD, but they aren’t broken into
>> lines; while \WORD works in normal text.
>> Wh
Henning Hraban Ramm schrieb am 11.01.2020 um 18:53:
Hi again,
I’m trying to get uppercase titles with \WORD, but they aren’t broken into
lines; while \WORD works in normal text.
What’s the matter?
ConTeXt uses a horizontal box to place the section title which doesn't
matter when you us
Hi again,
I’m trying to get uppercase titles with \WORD, but they aren’t broken into
lines; while \WORD works in normal text.
What’s the matter?
Best, Hraban
%
\define[2]\MyChapter{
\WORD{#2}
}
\setuphead[chapter][
command=\MyChapter
]
\starttext
\chapter{
\input tufte
}
\WORD{
\input
; \defineenumeration[anmarkning][
> text=Anmärkning,
> title=yes,
> headstyle={\definedfont[Bold*default]\WORD},
> alternative=serried,
> width=fit,
> number=no,
> prefix=no,
> indentnext=no,
> indenting={yes,medium},
> before={\startanmärkningsbakgrunden},% if these t
blunt an instrument in this case -- in
addition to the body font where the problem exists, it works on the
heading and titling font, which does not share the problem.
As Henri's answer hints, I was a bit unclear in my request. It is a
kern
between a word space and the cap J that is the issue.
on to the body font where the problem exists, it works on the
heading and titling font, which does not share the problem.
As Henri's answer hints, I was a bit unclear in my request. It is a
kern
between a word space and the cap J that is the issue. Perhaps a font
feature file is the place to
s, it works on the
heading and titling font, which does not share the problem.
As Henri's answer hints, I was a bit unclear in my request. It is a kern
between a word space and the cap J that is the issue. Perhaps a font
feature file is the place to do such a thing.
\st
which does not share the problem.
As Henri's answer hints, I was a bit unclear in my request. It is a kern
between a word space and the cap J that is the issue. Perhaps a font
feature file is the place to do such a thing.
\startluacode
fonts.handlers.otf.addfeature {
name = "kern&quo
As Henri's answer hints, I was a bit unclear in my request. It is a kern
between a word space and the cap J that is the issue. Perhaps a font
feature file is the place to do such a thing.
--
Rik
___
If your q
dtext[anmärkningsbakgrunden][
width=\textwidth,
background=color,
backgroundcolor=gray,
]
\defineenumeration[anmarkning][
text=Anmärkning,
title=yes,
headstyle={\definedfont[Bold*default]\WORD},
alternative=serried,
width=fit,
number=no,
prefix=no,
indentnext=no,
indenting={yes,medium},
b
s}}
\startitemize
\item margin:
the left margin of the lines made only of page numbers
\item distance:
the distance of the first page number from the last word of the text
\item minwidth:
the shortest acceptable space at the end of the text to try to
start page numbers there
\s
On 12/7/19 4:32 PM, Hans Hagen wrote:
> On 12/7/2019 2:40 PM, Pablo Rodriguez wrote:
>
>> I know, but he was one of my bosses. And I remember I was totally
>> shocked when he explained to me that the standard document format for
>> any word processor was OpenOffice.org.
On 12/7/2019 2:40 PM, Pablo Rodriguez wrote:
I know, but he was one of my bosses. And I remember I was totally
shocked when he explained to me that the standard document format for
any word processor was OpenOffice.org.
Anyone claiming that something is a standard (esp in computer science
a real pain and that trying
>> to write conditionals with document merging was extremely annoying for me.)
>
> You should have.
I know, but he was one of my bosses. And I remember I was totally
shocked when he explained to me that the standard document format for
any word processo
, even if users
paste text from Word documents, is not such a big effort.
I can’t remember which JS editor I used >10 years ago for the
editorial system of a city magazine, but I remember I only allowed a
few tags (authors weren’t allowed to use font and color settings)
an
than containing a gazillion random
>>>>> html style tags which you can never reconstruct back into some
>>>>> structured form.
>>>>
>>>> Don’t exaggerate. Or maybe your company didn’t think about which tags are
>>>> really necessar
er reconstruct back into some
> >>> structured form.
> >>>
> >>> (And yes, my impression is that Massi spent a huge amount of effort in
> >>> configuring the editor and cleaning up the mess. My company didn't and
> >>> ended up with som
nd yes, my impression is that Massi spent a huge amount of effort in
>>> configuring the editor and cleaning up the mess. My company didn't and
>>> ended up with sometimes literally every word in a sentence using a
>>> different font size or style. They gave up on ht
gazillion
random html style tags which you can never reconstruct back into
some structured form.
(And yes, my impression is that Massi spent a huge amount of effort
in configuring the editor and cleaning up the mess. My company
didn't and ended up with sometimes literally every word in a
sentence us
editor and cleaning up the mess. My company didn't and
> > ended up with sometimes literally every word in a sentence using a
> > different font size or style. They gave up on html + cke pretty soon,
> > but couldn't be convinced that this was a bad idea upfront.)
>
>
On Sat, Nov 23, 2019 at 1:02 PM Henning Hraban Ramm wrote:
>
> Don’t exaggerate. Or maybe your company didn’t think about which tags are
> really necessary.
> A proper configuration that doesn’t allow nonsense, even if users paste
> text from Word documents, is not such a big effo
> html style tags which you can never reconstruct back into some
> structured form.
>
> (And yes, my impression is that Massi spent a huge amount of effort in
> configuring the editor and cleaning up the mess. My company didn't and
> ended up with sometimes literally every w
u can use one of the online JS editors like CKeditor.\
Only if you spend an enormous amount of effort making sure that the
code is properly cleaned up rather than containing a gazillion random
html style tags which you can never reconstruct back into some
structured form.
(And yes, my impression
;m currently on the PKP conference, and we are discussing OJS
> plugins for automated PDF production. I was wondering if ConTeXt could be an
> option...
> Best,
> Denis
>
> P.S.: I'll be giving here a brief introduction to XML typesetting with
> C
nTeXt
could be an option...
Best,
Denis
P.S.: I'll be giving here a brief introduction to XML typesetting with
ConTeXt to spread the word... just to let you know.
Running tex on demand is not really a problem but when it has to happen
after clicking a button there is the problem of prevent
I'll be giving here a brief introduction to XML typesetting with
ConTeXt to spread the word... just to let you know.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
mail
that returns the
>>>>>> column number of the target. How can I achieve this?
>>>>>>
>>>>>> Of course, I can get the page number with \pagereference (for the
>>>>>> target) and \at (for the reference), but for calculating the
y add
the word "line" or something else before the number, otherwise I
have to use \inlinerange. It took me some time to find that out.
Wouldn't it be easier to have just one command for the target and
another one for the reference, and everything else, as counters
and headers t
a page, I need
\pagereference (for the target) and \at (for the reference); to
refer to a line, I need \someline (for the target) and \inline (for
the reference), but only if I want it to automatically add the word
"line" or something else before the number, otherwise I have to use
\
On 10/30/2019 8:13 AM, Pablo Rodriguez wrote:
Dear list,
using LuaTeX 2.00 20190729 + ConTeXt MkIV 2019.10.28 18:57 with this sample:
\starttext
\chapter[refer]{amazingchapter}
\hsize\zeropoint
\about[refer]
\stoptext
I’m afraid that LMTX doesn’t hyphenate the word
Dear list,
using LuaTeX 2.00 20190729 + ConTeXt MkIV 2019.10.28 18:57 with this sample:
\starttext
\chapter[refer]{amazingchapter}
\hsize\zeropoint
\about[refer]
\stoptext
I’m afraid that LMTX doesn’t hyphenate the word, while MkIV hyphenates
it fine.
Could anyone confirm
> The java updates keept telling that it runs on 3 billion devices but that
> message doesn't change over years. I always wonder about numbers. One can
> find similar huge numbers for tex usage but what defines usage (forced?
> ontime? for fun? lifelong? advanced or like any w
n't change over years. I always wonder about numbers.
One can find similar huge numbers for tex usage but what defines usage
(forced? ontime? for fun? lifelong? advanced or like any word processor
usage?).
Just 2 cents from a JS programmer who actually thinks that JS is not the
worst L
On 10/7/2019 7:13 PM, Rik Kabel wrote:
On 8/10/2019 10:14, Hans Hagen wrote:
On 8/10/2019 2:25 PM, Jan Ulrich Hasecke wrote:
Hi all,
Visiting a museum in Straßburg I saw an old book from Gutenbergs
times where the
first word of the next page was printed below the last line of the
current
On 10/7/2019 9:20 PM, Henning Hraban Ramm wrote:
Am 2019-10-07 um 19:13 schrieb Rik Kabel :
On 8/10/2019 10:14, Hans Hagen wrote:
On 8/10/2019 2:25 PM, Jan Ulrich Hasecke wrote:
Hi all,
Visiting a museum in Straßburg I saw an old book from Gutenbergs times where the
first word of the next
> Am 2019-10-07 um 19:13 schrieb Rik Kabel :
>
> On 8/10/2019 10:14, Hans Hagen wrote:
>> On 8/10/2019 2:25 PM, Jan Ulrich Hasecke wrote:
>>> Hi all,
>>>
>>> Visiting a museum in Straßburg I saw an old book from Gutenbergs times
>>> where th
On 8/10/2019 10:14, Hans Hagen wrote:
On 8/10/2019 2:25 PM, Jan Ulrich Hasecke wrote:
Hi all,
Visiting a museum in Straßburg I saw an old book from Gutenbergs times
where the
first word of the next page was printed below the last line of the
current page.
The word, sometimes only a
want it to automatically add the word
"line" or something else before the number, otherwise I have to use
\inlinerange. It took me some time to find that out. Wouldn't it be
easier to have just one command for the target and another one for
the reference, and everything else, as c
efer
to a page, I need \pagereference (for the target) and \at (for the reference); to refer
to a line, I need \someline (for the target) and \inline (for the reference), but only if
I want it to automatically add the word "line" or something else before the
number, otherwise I have to
> Besides, I am wondering, regarding the generally very regular and consistent
>> naming of commands in ConTeXt, why this is not so in the case of references.
>> For example, to refer to a page, I need \pagereference (for the target) and
>> \at (for the reference); to refer t
ne, I need \someline (for the target) and \inline (for the
reference), but only if I want it to automatically add the word "line"
or something else before the number, otherwise I have to use
\inlinerange. It took me some time to find that out. Wouldn't it be
easier to have just one co
:
\startMP
draw (0,0) withpen pencircle 1in withcolor red ;
\stopMP
\stoptext
%——
I obtain a color syntax output (« draw » in red, « within » in green for
example). This code does not work anymore in MKIV (every word is the
same color, green). There should be a solution ?
Hard to say without
withcolor red ;
\stopMP
\stoptext
%——
I obtain a color syntax output (« draw » in red, « within » in green for
example). This code does not work anymore in MKIV (every word is the same
color, green). There should be a solution ?
Trying to find some help, in the maling list and the
more information it's
just guess work.
On 22. Aug 2019, at 16:53, Wolfgang Schuster
wrote:
Robert Zydenbos schrieb am 22.08.2019 um 01:42:
I seem to have a problem with Unicode in the indexing function for my book: a
word like āyitu (beginning with an 'a' with a macron over it) is con
Robert Zydenbos schrieb am 22.08.2019 um 01:42:
I seem to have a problem with Unicode in the indexing function for my book: a
word like āyitu (beginning with an 'a' with a macron over it) is considered a
word that starts with a 'y'; the word īga (beginning with an i with
ly-To: mailing list for ConTeXt users
To: mailing list for ConTeXt users
Subject: [NTG-context] formatting index entries: alphabetical order in
Unicode
Date: Thu, 22 Aug 2019 01:42:40 +0200
Mailer:
I seem to have a problem with Unicode in the indexing function for my
book: a word like āyitu (begi
I seem to have a problem with Unicode in the indexing function for my book: a
word like āyitu (beginning with an 'a' with a macron over it) is considered a
word that starts with a 'y'; the word īga (beginning with an i with a macron)
is placed as if it is 'ga'.
ow that there are commands for
>> formatting index entries, like:
>>
>> \index{sl::īga}
>>
>> if I want the word 'īga' to be printed in slanted type. I also know that we
>> can create sub-entries, like
>>
>> \index{īga+emphasized}
>>
&
Robert Zydenbos schrieb am 21.08.2019 um 10:59:
Dear list members,
In my book I am creating an index. I know that there are commands for
formatting index entries, like:
\index{sl::īga}
if I want the word 'īga' to be printed in slanted type. I also know that we can
create sub-ent
Dear list members,
In my book I am creating an index. I know that there are commands for
formatting index entries, like:
\index{sl::īga}
if I want the word 'īga' to be printed in slanted type. I also know that we can
create sub-entries, like
\index{īga+emphasized}
But now I wan
;
>> However, I don't think the issue comes from the file name containing the
>> word « problème »: indeed the attached file gives the same error in lmtx,
>> but not in mkiv:
> well, you can see it when you run the lua file -)
>
>
were used to use MS Word in order for them to use
ConTeXt, and these people have many files with names containing spaces such as
« correction problème 1.tex » (and in fact this is how I noticed this new
behavior of lmtx: when typesetting such a file, lmtx looks for « correction.tex
»).
That is
Hi Hans,
I noticed that the lmtx beta from 2019.08.18 22:27 does not anymore accept
spaces in file names, while the mkiv version does accept it.
I am aware that putting a space in a file name is a very bad habit, but I am
convincing some people who were used to use MS Word in order for them to
lready diverged from Knuth’s TeX in small ways, for
example by allowing the first word of a paragraph to be hyphenated.
Best,
Arthur
___
If your question is of interest to others as well, please
it to automatically add the word "line" or something else before
the number, otherwise I have to use \inlinerange. It took me some time
to find that out. Wouldn't it be easier to have just one command for the
target and another one for the reference, and everything else, as
counte
On 8/10/2019 2:25 PM, Jan Ulrich Hasecke wrote:
Hi all,
Visiting a museum in Straßburg I saw an old book from Gutenbergs times where the
first word of the next page was printed below the last line of the current page.
The word, sometimes only a syllable of the first word from the next page, is
Hi all,
Visiting a museum in Straßburg I saw an old book from Gutenbergs times where the
first word of the next page was printed below the last line of the current page.
The word, sometimes only a syllable of the first word from the next page, is
called catchword or Kustode. They used it to
% fails
\stoptext
Is this a bug or is this a documented limitation of \copy and \frule?
Of course it's a bug ... I'll send you a preliminary one word fix -)
Hans
-
Hans Hage
I don't think the current behavior is a bug, so the following is a
feature request:
With the following fairly minimal example
\setupregister[index][indicator=no, distance=0.5em]
\starttext
ABC\index{x}DEF\index{x+yyz}
\blank
\placeindex
\stoptext
the distance parameter sets (1) th
Zitat von DesdeChaves :
Dear sirs,
Is there a way to make crosswords or word puzzles in context?
In my hippocampus I have a vague idea that this has already been tried, but
I can't find this code anymore.
My crossword puzzle editor https://croisee.fiee.net exports puzzles as
Co
m: Wolfgang Schuster
> To: mailing list for ConTeXt users , DesdeChaves
>
> Subject: Re: [NTG-context] crosswords puzzles
> Message-ID:
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> DesdeChaves schrieb am 22.06.2019 um 11:42:
> &
DesdeChaves schrieb am 22.06.2019 um 11:42:
Dear sirs,
Is there a way to make crosswords or word puzzles in context?
In my hippocampus I have a vague idea that this has already been
tried, but I can't find this code anymore.
AFAIK there are only packages for LaTeX to create crossword bu
Dear sirs,
Is there a way to make crosswords or word puzzles in context?
In my hippocampus I have a vague idea that this has already been tried, but
I can't find this code anymore.
Have a great day
Jorge
_
On 6/2/2019 1:07 PM, Mikael P. Sundqvist wrote:
On Sun, Jun 2, 2019 at 12:47 PM Hans Hagen <mailto:j.ha...@xs4all.nl>> wrote:
On 6/2/2019 8:36 AM, Mikael P. Sundqvist wrote:
> I attach the output (latest lmtx). The word "endast" shows up as
"endas t&
On 6/2/19 12:47 PM, Hans Hagen wrote:
> On 6/2/2019 8:36 AM, Mikael P. Sundqvist wrote:
>
>> I attach the output (latest lmtx). The word "endast" shows up as "endas t".
> that one is too weird indeed, might be a bug
I get weird results using TeX Gyre Pagel
On 6/2/2019 8:36 AM, Mikael P. Sundqvist wrote:
I attach the output (latest lmtx). The word "endast" shows up as "endas t".
that one is too weird indeed, might be a bug
Hans
-
erlinespace=12bp]
\setupbodyfont[lucidaot,9bp]
\starttext
Gränsvärde föreligger i en inre punkt i definitionsmängden om och endast
om höger- och vänstergränsvärde existerar där och är lika.
\stoptext
I attach the output (latest lmtx). The word "endast" shows up as "endas t".
tarttext
Gränsvärde föreligger i en inre punkt i definitionsmängden om och endast
om höger- och vänstergränsvärde existerar där och är lika.
\stoptext
I attach the output (latest lmtx). The word "endast" shows up as "endas t".
So, what does this threshold do? I can play with the 2
> On 12Apr19, at 02:28, Huseyin Özoguz wrote:
>
>> As you can see, we get Ème in the output instead of ème.
>> Is this a bug, or did I miss something?
>>
This is a consequence of command=\Word, set for titles. Try
\setupbtx [apa:list:title] [command=]
Explanation: AP
top
> > \stopbackmatter
> > \startbackmatter
> > \chapter{Rejstřík věcný}
> > \start
> > \switchtobodyfont[8pt]
> > \placeindexsubject
> > \stop
> > \stopbackmatter
> >
> > At the beginning there is a condition for one word (kind of manual c
501 - 600 of 3254 matches
Mail list logo
