lt I am getting is:
->Observer, The 223
But what I want is /Observer, The/ (in other words, in italics).
Clearly I am doing something wrong, or not enough, or... maybe
there is another way to achieve waht I
lt I am getting is:
->Observer, The 223
But what I want is /Observer, The/ (in other words, in italics).
Clearly I am doing something wrong, or not enough, or... maybe
there is another way to achieve waht I
2018
>
> \stoptext
>
> The only result I am getting is:
>
> ->Observer, The 223
>
> But what I want is *Observer, The* (in other words, in italics).
>
> Clearly I am doing something wrong,
. The Observer
MWE
\defineregister[myindex]
\defineprocessor[style][style=italic]
\starttext
In \myindex{style->Observer, The} {\em The Observer} of 31 July 2018
\stoptext
The only result I am getting is:
->Observer, The 223
But what I want is /Observer, The/ (in other words, in i
]
\setuplabeltext
[chapter=Chapter\nobreakspace]
\setuphead
[chapter]
[conversion=Words]
\setuphead
[chapter]
[sectionsegments=chapter]
\setuphead
[section]
[sectionsegments=chapter:section]
\starttext
\startpart [title=Mypart]
\startchapter [title=Some Chapter
y '1. My title'.
Here's what an MWE with the code I posted looks like:
\setuphead
[part]
[placehead=yes,
bodypartlabel=part]
\setuplabeltext
[part=Section\nobreakspace]
\setuplabeltext
[chapter=Chapter\nobreakspace]
\setuphead
[chapter]
[conversion=Words]
\setup
ions' are numbered in arabic numbers, Chapters
> are meant to be in words.
\setuplabeltext
[chapter=Chapter\nobreakspace]
\setuphead
[chapter]
[conversion=Words]
> Issue 3 might already be solved once I resolve Issue 2!
>
> But given that I have parts, the chapters at the mom
', and the Chapter numbers need to be words and
sequential throughout the book, not restarting at each part/section.
Issue 1:
Parts need to be called 'Section' (Section 1, section 2 etc.). I thought
I could achieve this with:
\setuphead
[part]
[
placehead=yes,
bodypartlabel=section
em now.
I assume this was removed with LMTX... is it possible to introduce it again?
My problem is not to make the arrow bigger, I actually want to make it smaller.
I have 2 long words above it, and so it's really long. I could use \clap{}, but
then the spacing is gone and my 2 words clash wit
ion/translation of the general words for titles, glossaries,...
>
> Now regarding the labels, how could I provide the translations? Should I add
> a line with translation for each term (or the most important, I have seen
> that the French labels are not all translated)?
Ideally take the latest v
Hi Hans and Mojca,
I join a file containing the list of
patterns for Esperanto and the definition/translation of the
general words for titles, glossaries,...
In fact there is a file for Esperanto
in:
C:\Users\Alain\context-lmlx\tex\texmf
r all [I’m afraid I
don’t know]) Indic scripts.
Why are second versions? Using their own words:
“The OpenType script tags can also correlate with a particular OpenType
Layout implementation, with the result that more than one script tag may
be registered for a given Unicode script (e.g
[I’m afraid I
don’t know]) Indic scripts.
Why are second versions? Using their own words:
“The OpenType script tags can also correlate with a particular OpenType
Layout implementation, with the result that more than one script tag may
be registered for a given Unicode script (e.g. 'deva' and '
v/syst-ini.mkiv) :
Your luatex binary is too old, you need at least version 1.10!))
> 121 words of node memory still in use:
> 11 glue_spec nodes
> avail lists: 2:2,5:1
> No pages of output.
In Dockerfile for alpine linux https://github.com/minidocks/context
<https://github.c
tex/texmf-context/tex/context/base/mkiv/cont-en.mkiv
(/usr/share/tex/texmf-context/tex/context/base/mkiv/context.mkiv
(/usr/share/tex/texmf-context/tex/context/base/mkiv/syst-ini.mkiv) :
Your luatex binary is too old, you need at least version 1.10!))
> 121 words of node memory still in
nes is a dynamic
process. The
239 space between words is flexible and we don't know in advance when a
\hpos {A-1}
240 >> {word} or piece of a word |<|maybe it's best to talk of typographic
\hpos {A-2}
241 {globs} instead|>| will end up on the page. It might even cros
Hi list,
I have successfully managed to get a vertically-oriented page number in
words in the margins, but NOT with the number prefixed by the word
'page'. I thought I would be able to do this by adding viewerprefix=Page
(mentioned on the wiki for \setupuserpagenumber) but it gives me
r
>
> so, this new keyword scanner is more picky in the sense that when it
> notices a potential keywors start it will complain earlier which might
> actually catch potential errors ealier (in this case all follow up words
> that start with a 'p' or 'm'
>
> another change in scanning is tha
so, you'rve just been lucky so far
so, this new keyword scanner is more picky in the sense that when it
notices a potential keywors start it will complain earlier which might
actually catch potential errors ealier (in this case all follow up words
that start with a 'p' or 'm'
another change
Hello Julian!
On Thu, 15 Oct 2020 at 00:08, jbf wrote:
> I wonder if someone could explain to me what controls (or how to
> control) the space between Chapter and chapter number in my TOC given
> the setup I have.
>
> At the moment I get ChapterOne instead of Chapter One, and I do not know
>
one has except for the first 5 words. And yes, there's also
similar trickery for protrusion, \noprotrusion, but i didn't test it.
This is in addition the the already mentioned \nokerning and
\noligaturing features that also obey grouping.
All this in the perspective of (luameta)tex giving
I wonder if someone could explain to me what controls (or how to
control) the space between Chapter and chapter number in my TOC given
the setup I have.
At the moment I get ChapterOne instead of Chapter One, and I do not know
what is causing that.
Here is my set up (at least all the parts
Hi,
has \zwnj (or the equivalent unicode character) bad consequences for
hyphenation? Like, when you'd preprocess your files and add \zwnj in
appropriate places, will that break hyphenation for these words?
Best,
Denis
On 10/14/2020 2:09 PM, Denis Maier wrote:
Hi,
has \zwnj (or the equivalent unicode character) bad consequences for
hyphenation? Like, when you'd preprocess your files and add \zwnj in
appropriate places, will that break hyphenation for these words?
So, this:
\mainlanguage[nl
On 10/14/2020 2:09 PM, Denis Maier wrote:
Hi,
has \zwnj (or the equivalent unicode character) bad consequences for
hyphenation? Like, when you'd preprocess your files and add \zwnj in
appropriate places, will that break hyphenation for these words?
yes, which is why we don't want
On 10/8/2020 7:05 PM, Henning Hraban Ramm wrote:
Am 08.10.2020 um 17:41 schrieb Denis Maier :
where can I find the hyphenation patterns used by ConTeXt? I have two wrongly
hyphenated words, and I want to check whether this is due to incorrect
patterns. (I tried the source browser
Hi,
where can I find the hyphenation patterns used by ConTeXt? I have two
wrongly hyphenated words, and I want to check whether this is due to
incorrect patterns. (I tried the source browser... not much luck so
far.) The words are:
1. applicable => hyphenated as applic-able
2. obliga
> Am 08.10.2020 um 17:41 schrieb Denis Maier :
>
> where can I find the hyphenation patterns used by ConTeXt? I have two wrongly
> hyphenated words, and I want to check whether this is due to incorrect
> patterns. (I tried the source browser... not much luck so far.) The
Hi,
you can find patterns on this directory:
texlive/2020/texmf-dist/tex/context/patterns/mkiv/
Best wishes,
Tomáš
Thu, Oct 08, 2020 ve 05:41:09PM +0200 Denis Maier napsal(a):
# Hi,
#
# where can I find the hyphenation patterns used by ConTeXt? I have
# two wrongly hyphenated words, and I
/
In the words of the specification: "The Citation Style Language (CSL) is
an XML-based format to describe the formatting of citations, notes and
bibliographies". I.e., it's quite similar to what bibtex (the language,
not the format) is, or what context's own bibliographic language does.
Th
by default, right? In other words,
\forgetparagraphfreezing, recovers the default behaviour of MkIV.
So, I suspect that this will not change; if we want to apply
Lettrine to a paragraph, from now on we must wrap it up with
\forgetparagraphfreezing and \setparagraphfreezing.
Please correct me
El 17/9/20 a las 12:35, Wolfgang Schuster escribió:
Eduardo Bohoyo schrieb am 17.09.2020 um 10:14:
Thank you for this illustrative example, Wolfgang.
So, what \forgetparagraphfreezing does is to reverse the order that
lmtx currently imposes by default, right? In other words
Eduardo Bohoyo schrieb am 17.09.2020 um 10:14:
Thank you for this illustrative example, Wolfgang.
So, what \forgetparagraphfreezing does is to reverse the order that
lmtx currently imposes by default, right? In other words,
\forgetparagraphfreezing, recovers the default behaviour of MkIV
So, what \forgetparagraphfreezing does is to reverse the order that lmtx
currently imposes by default, right? In other words,
\forgetparagraphfreezing, recovers the default behaviour of MkIV.
So, I suspect that this will not change; if we want to apply Lettrine to
a paragraph, from now on we must
as the label, I have:
\setuplabeltext
[en]
[chapter={\bf Chapter }, appendix=APPENDIX ]
But elsewhere I have:
\setupheads[chapter][indentnext=no,conversion=Words,distance=.25em]
So is that what is affecting my appendices, and if so how do I do it so
that Chapters get words (One, Two, etc
]
[chapter={\bf Chapter }, appendix=APPENDIX ]
But elsewhere I have:
\setupheads[chapter][indentnext=no,conversion=Words,distance=.25em]
So is that what is affecting my appendices, and if so how do I do it so
that Chapters get words (One, Two, etc) and Appendices get letters (A,B,
etc
will be simply 'Foreword' and 'Preface', obviously.
*Foreword Author name*
*Preface Author name*
I am using \hskip 1cm to separate the authors' names from either of
those two words. But this does not give me the kind of exact
positioning I need to get the two author names directly
a Foreword and a Preface, I am using \title for
these. And both have separate authors. The titles will be simply
'Foreword' and 'Preface', obviously.
*Foreword Author name*
*Preface Author name*
I am using \hskip 1cm to separate the authors' names from either of
those two words. But this does
for
these. And both have separate authors. The titles will be simply
'Foreword' and 'Preface', obviously.
*Foreword Author name*
*Preface Author name*
I am using \hskip 1cm to separate the authors' names from either of
those two words. But this does not give me the kind of exact
ble:
>
> \define[1]\ChapterTocEntry{%
> \structurelistuservariable{author}\crlf%
> #1\crlf% title
> %\structurelistuservariable{subtitle}}%
> }
>
> \setuplist[chapter][
> textcommand=\ChapterTocEntry,
> ]
>
> So, in other words I swapped the word 'section' in your
) and an author, and added, below what I
already have in the preamble:
\define[1]\ChapterTocEntry{%
\structurelistuservariable{author}\crlf%
#1\crlf% title
%\structurelistuservariable{subtitle}}%
}
\setuplist[chapter][
textcommand=\ChapterTocEntry,
]
So, in other words I swapped the word
On 9/2/2020 7:56 AM, jbf wrote:
Am working on a book where most chapters are simply labeled Chapter One,
Chapter Two etc., and this has been achieved easily enough with
\setuplabeltext[chapter=Chapter ] (also including
\setupheads[conversion=Words] to get One, Two instead of 1 2
Am working on a book where most chapters are simply labeled Chapter One,
Chapter Two etc., and this has been achieved easily enough with
\setuplabeltext[chapter=Chapter ] (also including
\setupheads[conversion=Words] to get One, Two instead of 1 2).
But several chapter labels need to have
-sided setup (in other words a standard 8.5"x5.5" book):
\setuplayout
[backspace=16mm,
topspace=12mm,
header=6mm,
headerdistance=10mm,
footerdistance=9mm,
footer=8mm,
width=fit,
horoffset=12.7mm,
location=middle,
height=198mm,
at what InDesign calls margins might be termed a
> little differently in ConTeXt and I have no experience with InDesign.
>
> My initial setup was as follows for a paper size defined as
> [width=140mm,height=216mm] double-sided setup (in other words a standard
> 8.5&
no experience with
InDesign.
My initial setup was as follows for a paper size defined as
[width=140mm,height=216mm] double-sided setup (in other words a standard
8.5"x5.5" book):
\setuplayout
[backspace=16mm,
topspace=12mm,
header=6mm,
headerdistance=10mm,
footerdi
loaded fonts: 2 files: librisadfstd-regular.otf,
texgyrepagella-math.otf
In other words, only two, not three definitions are working at any one
time. Or is it not accepting [ss] for some reason regardless? I have
tried any number of existing sans serif fonts and none of them will
load. I know the family
---
>
> ConTeXt loads the [rm] and the [mm] but not the [ss]. Be assured that
> the ss typeface is available. So if, for example, I comment out the
> first line ([rm]) and change the Libris to rm instead, I am told:
>
> mkiv lua stats > loaded fonts: 2 files: librisadfs
So if, for example, I comment out the
first line ([rm]) and change the Libris to rm instead, I am told:
mkiv lua stats > loaded fonts: 2 files: librisadfstd-regular.otf,
texgyrepagella-math.otf
In other words, only two, not three definitions are working at any one
time. Or is it not accepti
ct from
> what is required on screen (ii) I am using Mk IV (iii) I need spot colors set
> up for cmyk, and for now I need shades between black and white (e.g. light
> gray) for a simple design feature.
>
> My question is this: is the use of color keywords sufficient? Or in other
> words,
colors set up for cmyk, and for now I need shades
between black and white (e.g. light gray) for a simple design feature.
My question is this: is the use of color keywords sufficient? Or in
other words, have predefined color names like lighgray already been
defined in, say cmyk terms behind
On 8/20/20 1:10 PM, Hans Hagen wrote:
> On 8/20/2020 12:38 PM, Pablo Rodriguez wrote:
>> [...]
>> This time, I have to remove two words, such as in:
>>
>>string.gsub([[\xmlraw{#1}{.}]]," del ", " "):gsub(" de la ", " &qu
thanks for your reply, Hans.
I now see that \xmlraw is the way to go.
I have two questions in word replacement and Lua (maybe there is some
lpeg magic that could be used).
This time, I have to remove two words, such as in:
string.gsub([[\xmlraw{#1}{.}]]," del ", " "):gsub(&quo
))})
> \stopxmlsetups
Many thanks for your reply, Hans.
I now see that \xmlraw is the way to go.
I have two questions in word replacement and Lua (maybe there is some
lpeg magic that could be used).
This time, I have to remove two words, such as in:
string.gsub([[\xmlraw{#1}{.}]],"
tstringwordspaced\somemacro{\input knuth}
> >>
> >> It only works with explicit TeX "words". How to circumvent this
> >> inconvenience? Thanks in advance.
> >
> > You can't feed knuth.tex to the command because it contains multiple
> > p
:
\applytosplitstringwordspaced\somemacro{\input knuth}
It only works with explicit TeX "words". How to circumvent this
inconvenience? Thanks in advance.
You can't feed knuth.tex to the command because it contains multiple
paragraphs but even when your file contains only a single paragraph it
isn
}
It only works with explicit TeX "words". How to circumvent this
inconvenience? Thanks in advance.
You can't feed knuth.tex to the command because it contains multiple
paragraphs but even when your file contains only a single paragraph it
isn't perfect because the linebreak after the
Hi, list! :D
I've found \applytosplitstringwordspaced and many other commands reading on
the mailing list and TeX StackExchange. An issue with those is: the
following does not work:
\applytosplitstringwordspaced\somemacro{\input knuth}
It only works with explicit TeX "words". How to
Near them, on the sand,
Half sunk a shattered visage lies, whose frown,
And wrinkled lip, and sneer of cold command,
Tell that its sculptor well those passions read
Which yet survive, stamped on these lifeless things,
The hand that mocked them, and the heart that fed;
And on the pedestal, these words appea
w it crashes:
> >
> >
> \setuphead[chapter][alternative=middle,textstyle=\cap,numbercommand=\WORDS]
> >
> \setuphead[section][sectionsegments=section,align=middle,textstyle={\bf},conversion=R,numbercommand={\bf}]
> >
> \setuphead[subsection][numbercommand=,textstyle={\it},sectionseg
Jairo A. del Rio schrieb am 04.08.2020 um 06:07:
The following worked some days ago. Now it crashes:
\setuphead[chapter][alternative=middle,textstyle=\cap,numbercommand=\WORDS]
\setuphead[section][sectionsegments=section,align=middle,textstyle={\bf},conversion=R,numbercommand={\bf}]
\setuphead
,numbercommand=\WORDS]
\setuphead[section][sectionsegments=section,align=middle,textstyle={\bf},conversion=R,numbercommand={\bf}]
\setuphead[subsection][numbercommand=,textstyle={\it},sectionsegments=subsection,conversion=n]
\starttext
\startchapter[title=Dummy chapter]
\startsection[title=Dummy
. Beginning
with PDF 1.6, the size of the unit may be set on a page-by-page basis; the
default remains at 1/ 72 inch.
In other words: you need to change the unit per page so the page is at least
3x3 and maximally 14400x14400.
> On 9 Jul 2020, at 12:10, Hans Hagen wrote:
>
> On 7/9/202
ration[proposition][alternative=top,text=Proposición,headalign=middle,numberconversion=R,headstyle=\WORDS,style=\emph,referenceprefix=prop]
> > \starttext
> > \startproposition[1]
> > \dorecurse{10}{\input ward}
> > \stopproposition
> > \in[prop:1]
> > \
ration[proposition][alternative=top,text=Proposición,headalign=middle,numberconversion=R,headstyle=\WORDS,style=\emph,referenceprefix=prop]
> \starttext
> \startproposition[1]
> \dorecurse{10}{\input ward}
> \stopproposition
> \in[prop:1]
> \stoptext
>
> works almost perfectly.
The following:
\setupinteraction[state=start,focus=standard,color=black,contrastcolor=black]
\defineenumeration[proposition][alternative=top,text=Proposición,headalign=middle,numberconversion=R,headstyle=\WORDS,style=\emph,referenceprefix=prop]
\starttext
\startproposition[1]
\dorecurse{10
rt on, but it seems clear that he values "usability, good
function, and getting the job done well" much higher than he
values "backward compatibility forever". In other words, if
something is broken or not good enough, he doesn't hesitate to fix
it or improve i
blank line after the last item.
Spacing was not affected at all, only mysterious words in square brackets
showed up in the output.
??
-Original Message-
From: ntg-context [mailto:ntg-context-boun...@ntg.nl] On Behalf Of Henning
Hraban Ramm
Sent: Wednesday, June 17, 2020 2:27 PM
To: mailing
kground=color,
>> backgroundcolor=yellow]
>>
>> \starttext
>>
>> \m{1 + 2 = \unit{3 kilo newton}}
>>
>> \m{1 + 2 = \Highlight{\unit{3 kilo newton}}}
>>
>> \stoptext
>>
>> Wolfgang
>>
>
> Is there a way
noyed that I couldn’t really search for commands that are also
regular words.
Thank you so much!
And thanks again to Garulfo for the whole effort of restructuring the wiki!
Hraban
___
If your question is of inter
+ 2 = \unit{3 kilo newton}}
>
> \m{1 + 2 = \Highlight{\unit{3 kilo newton}}}
>
> \stoptext
>
> Wolfgang
>
Is there a way to highlight just the words and leave the space white?
Something like \overstrikes?
Greetings
Axel
word search as of yet).
>
> See https://www.lua.org/manual/5.3/manual.html#6.4.1 for the syntax of lua
> string patterns.
>
> * The search index only contains 7-bit ASCII ‘words’ that contain at least
> one of 'a-zA-Z’ (writing an LPEG for unicode matching is a tricky and
&g
is some relevant information:
* The search field uses a Lua string pattern to match a single word (no
multi-word search as of yet).
See https://www.lua.org/manual/5.3/manual.html#6.4.1 for the syntax of lua
string patterns.
* The search index only contains 7-bit ASCII ‘words’ that contain
above be the right way to
achieve my purpose? In other words, I want the text that follows the
chapter title to follow immediately for specific chapters, rather
than the considerable vertical space that follows the default setup
for chapter titles.
Julian
Change
\def\MyChapterCommand#1#2
is that when I try to process the original example, I get a
fatal error at the line which reads \chapter{test} \input tufte.
I'm not sure why that error, but that aside, would the
\def\MyChapterCommand approach suggested above be the right way to
achieve my purpose? In other words, I want the text
example, I get a
fatal error at the line which reads \chapter{test} \input tufte.
I'm not sure why that error, but that aside, would the
\def\MyChapterCommand approach suggested above be the right way to
achieve my purpose? In other words, I want the text that follows the
chapter title to follow
:05:
Hi list,
I want my table of contents to look like:
Chapter 1
section 5
section 10
section 15
In other words with section items indented.
I presumed I would need to do something with \setuplist[section]. I
know how to control interline
jbf schrieb am 02.06.2020 um 03:05:
Hi list,
I want my table of contents to look like:
Chapter 1
section 5
section 10
section 15
In other words with section items indented.
I presumed I would need to do something with \setuplist[section]. I
Hi, everybody. I expect you to be safe.
I found the following issues.
*First. *The following gives wrong results for Spanish numbers
\mainlanguage[es]
\starttext
\convertnumber{words}{100}
%Prints "ciento" instead of "cien"
\convertnumber{words}{200}
%Prints "do
Hi list,
I want my table of contents to look like:
Chapter 1
section 5
section 10
section 15
In other words with section items indented.
I presumed I would need to do something with \setuplist[section]. I know
how to control interline
%%
\stopmodule
What have I to do if, instead of "color" or "style", I want to use
another keyword, as "dummy" and get its value? Something like
\definelook[lol][dummy = blabla]
\lol{words}
%e.g. words \emph{blabla} or something simila
to do if, instead of "color" or "style", I want to use another
keyword, as "dummy" and get its value? Something like
\definelook[lol][dummy = blabla]
\lol{words}
%e.g. words \emph{blabla} or something similar
so "lol" is a word, a number or whatever. I'
On 5/17/2020 5:00 PM, Wolfgang Schuster wrote:
Bruce Horrocks schrieb am 17.05.2020 um 13:47:
If I want the words Top and Bottom at the top and bottom of a page
then "Top \vfill Bottom" works as expected. If I use the same in an
extreme table I get an error and I don't know why
Bruce Horrocks schrieb am 17.05.2020 um 13:47:
If I want the words Top and Bottom at the top and bottom of a page then "Top \vfill
Bottom" works as expected. If I use the same in an extreme table I get an error and
I don't know why.
What's the 'official' way to align top and bottom
If I want the words Top and Bottom at the top and bottom of a page then "Top
\vfill Bottom" works as expected. If I use the same in an extreme table I get
an error and I don't know why.
What's the 'official' way to align top and bottom in an xrow?
MWE
\setuppapersize [A4] [A4]
oth resolve to
`Function`.
The actual behaviour is that comments are highlighted correctly, but
I do not get any syntax highlighting for functions.
Thanks for t-vim, btw: I can't express in words how nice an idea it is!
Nicola
, very,\\ very etc. etc. long title}, what happens is that part of
the caption still appears on the right-hand page of the spread.
Is there a way that I can limit the appearance of the caption to just one (the
left-hand) page? In other words, so the figure is spread but not the caption
ll appears on the right-hand page of
> the spread.
>
> Is there a way that I can limit the appearance of the caption to just one
> (the left-hand) page? In other words, so the figure is spread but not the
> caption? Or alternatively, have the caption neatly split across the two pa
of the caption to just
one (the left-hand) page? In other words, so the figure is spread but
not the caption? Or alternatively, have the caption neatly split across
the two pages with appropriate space inbetween? I tried various
combinations, including an \hfill halfway through the title
ating. Why isn’t this
> straightforward? I am sorry, everybody is very helpful, but the frustration
> mounts again.
I couldn't help here because I understand better the LaTeX font mechanism than
ConTeXt one but I don't use ConTeXt as often as LaTeX. If I understand
correctly, fallba
On 4/30/2020 2:05 AM, jbf wrote:
Hi list,
With 99% of work complete on a book, including single page images, I now
find myself confronted with a final problem: how to run one image across
facing pages or in other words, one image (plus its caption) across a
two-page spread
> Am 30.04.2020 um 02:05 schrieb jbf :
>
> Hi list,
>
> With 99% of work complete on a book, including single page images, I now find
> myself confronted with a final problem: how to run one image across facing
> pages or in other words, one image (plus its capti
a final problem: how to run one image across facing
> pages or in other words, one image (plus its caption) across a two-page
> spread, such that there is no gap.
>
> I have tried a number of fairly crass attempts (obviously too simple) to see
> if I could get somewhere near what I
Hi list,
With 99% of work complete on a book, including single page images, I now
find myself confronted with a final problem: how to run one image across
facing pages or in other words, one image (plus its caption) across a
two-page spread, such that there is no gap.
I have tried a number
ctory
3. reload the font cache
4. enrich your vocabulary by learning the words “thank you”
5. never have to deal with stupid people who didn’t read all 10,000 lines of
the log file you posted
6. profit!
Thomas
___
I
s; string s;
s := "\framed{" & name & "}”;
% s := "\type-" & name & "-";
p := textext( s);
p
enddef;
But, this is what is in string s before it is sent to textext():
\framed {{Hello}, "(a)" [World]!}
In other words, the escapes on th
will be pretty complex. If I drop the use of \type{} inside
the btex-etex I have to ‘escape' everything that TeX doesn’t see as normal text
catcode. That, again might play havoc with breaking words across lines later.
G
> On 29 Mar 2020, at 15:09, Wolfgang Schuster
> wrote:
>
> Ger
these in a box of the
> aspect ratio of the box it needs to fit in. So, for instance, I have a box
> that is 50 (high) by 130 (wide) and
> - if the text fits in the box, just typeset it. Break the words (yes or no)
> - if the size set does not fit in the box, make it smaller so it f
s was written. (My acroread is just broken and in xpdf and mupdf
I guess there is no service to display it.)
What is the reason that keyword attribute does not accept commas whereas
others (title, author...) do?
# keyword={{a, b, c}},
As far as I know, key words (in papers, books etc.) are used
s just broken and in xpdf and mupdf
I guess there is no service to display it.)
What is the reason that keyword attribute does not accept commas whereas
others (title, author...) do?
# keyword={{a, b, c}},
As far as I know, key words (in papers, books etc.) are used only as a comma
301 - 400 of 2268 matches
Mail list logo
