the change
but it's possible he forgot to delete a few of them.
When you notice no difference between both versions of a command page
you can delete all of the forgotten pages.
No!
These are the general pages in opposite to instance pages, e.g.
"startsection" and "startchapter" a
hem.
When you notice no difference between both versions of a command page
you can delete all of the forgotten pages.
No!
These are the general pages in opposite to instance pages, e.g.
"startsection" and "startchapter" are instances of "_startsection"?
https://wi
cause this behavior? For what should I look in my setups?
In this instances, location=opposite causes the float to disappear.
Hraban
___
If your question is of interest to others as well, please add an entry to the
On 11/12/21 18:13, Henning Hraban Ramm via ntg-context wrote:
You’re right, tabular numbers are nonproportional. I meant versal (“normal”)
numbers in opposite of oldstyle (mediaeval) numbers.
I think there are two mutually exclusive feature pairs that you're
mixing up:
lnum vs onum
to bear in mind in
> the future. I'd always thought of proportional versus tabular rather than
> proportional + tabular.
You’re right, tabular numbers are nonproportional. I meant versal (“normal”)
numbers in opposite of oldstyle (mediaeval) numbers.
I often use the Alegreya fonts, and the
Thanks to Wolfgang Schuster and Bruce Horrocks I have now a working solution. I
ended up following Bruce’s suggestion of doing a left hand side (LHS) page
opposite the first (RHS) chapter or part page differently than using
after/before modifications of the \chapter and \part setups as I had
s the other boxes by that value!
IMO that makes no sense, CropBox can be completely independent of the other
boxes!
It would be logical to use negative values here, since the size decreases, in
opposite to my suggested handling of the other parameters.
Yes, that would mean a backward incompatibl
ense, CropBox can be completely independent of the other
boxes!
It would be logical to use negative values here, since the size decreases, in
opposite to my suggested handling of the other parameters.
Yes, that would mean a backward incompatible change. But how many of us rely on
the strange current beh
handle these subcitations with the \textcite
command, so that "higher-level" entries are not added to the list when
they are only subcited.
An important guideline that I still have to implement works in the
opposite direction: it says that entries in certain categories should
not be a
subcitations with different alternatives. In general, I handle these
subcitations with the \textcite command, so that "higher-level" entries are not
added to the list when they are only subcited.
An important guideline that I still have to implement works in the opposite
direction: it says th
list when they are only
subcited.
An important guideline that I still have to implement works in the opposite
direction: it says that entries in certain categories should not be added
to the list, but the books or collections containing them should be. I
think I could make this work for the subcita
> }
> >
> > return mydata[stringn]
> >
> > end
> >
> > end
> >
> >
> > interfaces.implement{
> >
> > name = "factorial",
> >
> > public = true,
> >
> > arguments = {"string"},
> >
in each run, both the first and the second
conditions are met, so the compilation is twice as slow, the opposite
result of what I meant to do. How do I fix that?
\definedataset[nicedata]
\starttext
\startluacode
local function dofactorial(n)
local function inner(c,m)
itions
are met, so the compilation is twice as slow, the opposite result of what I
meant to do. How do I fix that?
Jairo
El mié, 24 de mar. de 2021 a la(s) 01:38, Hans Hagen (j.ha...@xs4all.nl)
escribió:
> On 3/24/2021 5:20 AM, Jairo A. del Rio wrote:
> > Thank you very much. It's usefu
Patoline is partly LaTeX based, Speedata Publisher uses LuaTeX, and I know
> of troff and XSL/FO.
The interesting thing here is that Patoline and SILE use some TeX-like syntax,
but the underlying engine is not based on TeX at all. With Speeddata Publi
would like to map lists to ul, list-items to li, headings
> to h1, h2, h3, paragraphs to etc. In the manuals I see that you can do
> the opposite: map xml/html tags to context's elements; I wonder if you can go
> the other way around, and a good place to start reading about it. Apologies
translated to specific html tags? I
mean, the current export output uses divs with custom attributes and
classes, or custom tags; but I would like to map lists to ul, list-items to
li, headings to h1, h2, h3, paragraphs to etc. In the manuals I see
that you can do the opposite: map xml/html tags
]
Another problem is that setting the width and height of a float does not affect
any externafigure side. You need to do a \setupexternalfigure for that.
And there is (afaik) no support for having a “two-page” float. The “opposite”
key is used to put the float (including caption) on the opposite
that using \setupfloat (or other setup), not directly in
\placefloat
4. Place captions in another page (ideally on opposite page)
Problems:
- I can't get # 1 and # 3 at same time
- \setupfloat doesn't have before option, which I could use to change
orientation
- I have no idea how
the English manual and the Dutch manual. Note: I do not intend to create a manual that has the English and Dutch text at opposite sides (as can be done using streams) I’m keen to continue using a single set of source files and thought it would be best to simply type the translated sections and subs
ual and the Dutch manual. Note: I do not intend to create a manual that
> has the English and Dutch text at opposite sides (as can be done using
> streams)
>
>
>
> I’m keen to continue using a single set of source files and thought it would
> be best to simply type the translat
create a manual that
> has the English and Dutch text at opposite sides (as can be done using
> streams)
>
>
>
> I’m keen to continue using a single set of source files and thought it
> would be best to simply type the translated sections and subsections just
> below the
translation has to be created.
It is important that the two manuals are setup similarly so the
section/subsection numbers and question numbers are the same in the
English manual and the Dutch manual. Note: I do not intend to create a
manual that has the English and Dutch text at opposite sides
manuals are setup similarly so the section/subsection numbers and question numbers are the same in the English manual and the Dutch manual. Note: I do not intend to create a manual that has the English and Dutch text at opposite sides (as can be done using streams) I’m keen to continue using a single
mf schrieb am 13.04.2020 um 17:21:
Thanks also for the explanation of backgroundoffset: it's an offset
relative only to the background, and it moves in the opposite direction
of the content offset of \framed.
Looks like \framed[...,offset=VALUE,backgroundoffset=frame,...] is
equivalent
text \eTD
\eTR
\bTR[toffset=1mm]
\bTD left \eTD
\bTD right \eTD
\eTR
\bTR
\bTD another \eTD
\bTD row \eTD
\eTR
\eTABLE
\stoptext
Thanks also for the explanation of backgroundoffset: it's an offset
relative only to the background, and it moves in the opposite direction
Ok, thanks for your advice. It seems that it is better to do framework in
MetaFun and use svg picture as a component instead of opposite.
Best wishes to you all
Janne
> 17 mars 2020 kl. 16:58 skrev Taco Hoekwater :
>
>
>
>> On 17 Mar 2020, at 15:51, Jan-Erik Hägglöf
&
ium=???]
\stoptext
i guess the opposite makes more sense: combine different registers and
then have different entries (kind of categories)
\defineregister[one]
\defineregister[two]
\starttext
one \one{alpha}
two \two{beta}
\subject{ONE} \placeregister[one]
\subject{TWO} \placeregister[t
electro-physics class I am teaching
> using
> circuitikz. Using meters gives some effects I don't quite understand.
>
> The MWE works as shown. The commented lines fail with "Undefined control
> sequence". If I
> put the same 3 lines into Latex (via Texstudio on Linux
Latex (via Texstudio on Linux), just the opposite
happens. The
line with rmeter fails, the other two work.
Why the difference? Some version issue? The "circuitikz manual version
0.9.4.pdf" shows
all 3 types of meters as choice.
Actually I would prefer to use the "ammeter"
Alan Braslau schrieb am 22.07.2019 um 16:37:
I do not know the details, but take a look at the following keywords
(which do the *opposite* of what you are seeking):
\setupnote
[footnote]
[split=verystrict,scope=page]
The scope setting isn't used in the current beta and the code
gt; move lines onto the next page to achieve footnote and reference
> > beging on the same page. If necessary set the footnote on the next
> > page, after the reference.
> >
> > Or would you suggest a better solution? I have a book with
> > grid=yes, so the default
On 11/18/2018 10:22 PM, Pablo Rodriguez wrote:
Hi Hans,
many thanks for having released the new beta.
I experience opposite results with opbd. The first sample is:
\definefontfeature[default][default][protrusion=quality, opbd=yes]
\definefontfamily[mainface][rm][Linux Libertine O
Hi Hans,
many thanks for having released the new beta.
I experience opposite results with opbd. The first sample is:
\definefontfeature[default][default][protrusion=quality, opbd=yes]
\definefontfamily[mainface][rm][Linux Libertine O]
\setupbodyfont[mainface, 300pt
sing his or her own laptop,
> and even then they cannot get it connected to the projector maybe 20%
> of the time...). Things are getting a bit better now on the
> presentation front, however. (PowerPointers still get funny font
> stuff from time to time).
My case is rather the opposite.
ve
>>
>> > but I installed texlive 2018 "scheme-full" with tlmgr -gui in
>> > /home/aragorn /texlive/2018. I then make regular updates in the same
>> > way. No texlive traces in the \usr\share\ directory or elsewhere.
>>
>> I prefer to rely on packag
ou set PATH in emacs as
>
> (setenv "PATH" "/home/aragorn/context/tex/texmf-linux-64/bin/:$PATH" t)
>
> (I have to admit that I didn't know it is possible to use '$PATH' in
> setenv), so it prepends path to context binary to PATH list. The above
>
se '$PATH' in
setenv), so it prepends path to context binary to PATH list. The above
lines do opposite: they append path to context binary to the end of
PATH list.
The first line, 'source ...', helps here because 'setuptex' in turns
prepend path to context binary to PATH.
When you invoke '
it is a bad approach and recursively going into a bin (or whatever) node
to see if there is a nucleus chactacer would be yet another
'configureble option' ... all is possible but the more we get of that
the more one needs to be aware of it and provide control over the
opposite (keep in mind
e subsection" in the
example below.
Tested with ConTeXt ver: 2018.04.04 and LuaTeX, Version 1.07.0.
This seems to be the opposite problem as the one described recently in
the thread "Bug in wrapped placefigure".
Any solution or fix?
Thank you very much for your help.
Char
> if ! command -v ldd >/dev/null || ! ldd --version 2>&1 | grep -E -q
> '^musl'; then
> libc=glic
> else
> libc=musl
> fi
Actually that’s nonsense, the opposite order is better (i. e. the
original one). I’ll explain wh
in description? For example a dash or symbol which
separates the head from the text. In enumerations it seems to be different,
because
there the variable head (title) goes after a static head. I would need the
opposite:
variable head part - static head part. I tried to use headcommand option but it
ect).
>
>If I have this code:
>
>\definefontfamily [documentfont] [mm] [TeX Gyre Pagella Math]
>\definefallbackfamily [documentfont] [mm] [Tex Gyre Adventor]
>[preset=math:lowercaseitalic]
>
>then Tex Gyre Pagella is used for math (\definefallbackfamily has no effect).
>
.
According to your answer the opposite should happen, shouldn't?
I am confused.
The \definefontfamily command creates a typeface which is used to load a
font but after this point
you can’t make changes to it. The \definefallbackfamily command let you
assign additional
characters for a font
lbackfamily has effect).
If I have this code:
\definefontfamily [documentfont] [mm] [TeX Gyre Pagella Math]
\definefallbackfamily [documentfont] [mm] [Tex Gyre Adventor]
[preset=math:lowercaseitalic]
then Tex Gyre Pagella is used for math (\definefallbackfamily has no effect).
According to your answe
D
\eTR
\eTABLE
\stoptext
Can you verify that it's working like expected? Because when I compile
it with latest beta i have the opposite alignment.
The keywords "left" and "right" are meant as raggedleft and raggedright
and the behaviour won’t change for backwards compatibli
On Mon, 18 Jul 2016 18:45:30 +0200
cryo shock <axteff...@gmail.com> wrote:
> Can you verify that it's working like expected? Because when I
> compile it with latest beta i have the opposite alignment.
I assume that you want align=flushleft and align=flushright,
rather than
expected? Because when I compile it
with latest beta i have the opposite alignment.
Greetings, Seba
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl
s not
translate math into italics. But the TeX legacy is the opposite.
\setupbodyfont[xits,10pt]
\startformula
\startalign
I &= ∫_S d(x)\, dx \NR
I &= ∫_S 푑(x)\, dx \NR
I &= ∫_S d(x)\, \mathupright{d} x \NR
e below, where the integral differential “d” is set in
>> upright to disambiguate relative the function named “d”.
>>
>> When Unicode added math styles, it added italics, expecting the ASCII range
>> to be upright, which would be normal if using a text editor that does not
&
talics. But the TeX legacy is the opposite.
\setupbodyfont[xits,10pt]
\startformula
\startalign
I &= ∫_S d(x)\, dx \NR
I &= ∫_S 푑(x)\, dx \NR
I &= ∫_S d(x)\, \mathupright{d} x \NR
I &= ∫_S 푑(x)\, \mathupright{d} x \NR
\stopalign
\stopformula
well, i guess unicode ass
talics. But the TeX legacy is the opposite.
\setupbodyfont[xits,10pt]
\startformula
\startalign
I &= ∫_S d(x)\, dx \NR
I &= ∫_S 푑(x)\, dx \NR
I &= ∫_S d(x)\, \mathupright{d} x \NR
I &= ∫_S 푑(x)\, \mathupright{d} x \NR
\stopalign
\stopformula
\appendtoks \rm
s not
translate math into italics. But the TeX legacy is the opposite.
\setupbodyfont[xits,10pt]
\startformula
\startalign
I &= ∫_S d(x)\, dx \NR
I &= ∫_S 푑(x)\, dx \NR
I &= ∫_S d(x)\, \mathupright{d} x \NR
ma, though. Sometimes left and right retain their
meanings in LTR and RTL and sometimes they mean opposite things. I mean,
alternative=left in RTL acts *similarly* to alternative=right in LTR;
however, headalign=left sort of has the same meaning in LTR and RTL. This
sometimes becomes confusing
issues I noticed:
>
> 1) Why isn't the head text consistently mirrored in the RTL environment?
> It happens only in alt=serried.
>
> 2) Option hang=2 produces a strange result for RTL. The hanging part
> appears on the opposite side of the head text, which somehow pushes the
> hea
result for RTL. The hanging part
appears on the opposite side of the head text, which somehow pushes the
head text outside the text area.
3) Option alt=top for RTL still puts the head text on the left-hand side.
4) I expect the LTR and RTL versions of the same settings to mirror one
another
On 2/5/2016 8:47 AM, Pablo Rodriguez wrote:
On 02/04/2016 10:13 PM, Hans Hagen wrote:
On 2/4/2016 9:27 PM, Pablo Rodriguez wrote:
[...]
The ff-ligature prevents hyphenation with TeX Gyre Pagella, but not with
MinionPro. (This is the opposite of what I reported before.)
it depends
reply, Hans.
I reported the issue in the opposite way it happens:
\definefontfamily[mainface][rm][MinionPro]
\definefontfamily[anotherface][rm][TeX Gyre Pagella]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
\hyphenatedword{LibreOffice libre office
On 02/04/2016 10:13 PM, Hans Hagen wrote:
> On 2/4/2016 9:27 PM, Pablo Rodriguez wrote:
>> [...]
>> The ff-ligature prevents hyphenation with TeX Gyre Pagella, but not with
>> MinionPro. (This is the opposite of what I reported before.)
>
> it depends on the compl
ries to do its best
Many thanks for your reply, Hans.
I reported the issue in the opposite way it happens:
\definefontfamily[mainface][rm][MinionPro]
\definefontfamily[anotherface][rm][TeX Gyre Pagella]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
\hyp
% although the Latin string extends into the margin, TeX still puts
one copy of "hello" there as well.
\dorecurse{10}{سلام }
{\textdir TLT\dorecurse{30}{a}}
\dorecurse{10}{سلام }
% something similar happens here with the opposite par/text dir
\pardir TLT
\dorecurs
e{10}{سلام }
{\textdir TLT\dorecurse{20}{a}}
\dorecurse{10}{سلام }
% although the Latin string extends into the margin, TeX still puts one
copy of "hello" there as well.
\dorecurse{10}{سلام }
{\textdir TLT\dorecurse{30}{a}}
\dorecurse{10}{سلام }
% something similar happens here with the o
; there as well.
> \dorecurse{10}{سلام }
> {\textdir TLT\dorecurse{30}{a}}
> \dorecurse{10}{سلام }
>
> % something similar happens here with the opposite par/text dir
> \pardir TLT
> \dorecurse{10}{bidi }
> {\textdir TRT\dorecurse{20}{آ}}
> \dorecurse{10}{bidi }
>
>
somewhere that the output of mtxrun (which column ?) should be
used and not fc-list output, then I read the opposite, and I read that
the --info option of mtxrun should provide the same family name as
listed with most GUI software, yet I tried and it doesn't…
Thanks.
Regards,
Goulven
the list entry texts (authors)
and partially overlap them.
With autohang=no they don't overlap but are still too close to the list item
text.
It seems it behaves the opposite to what is expected.
What is the correct use of these options? It's not explained in the manual.
3. There are 4 bst files
\stopparagraph
\startparagraph[noindent]
\input ward
\stopparagraph
\startparagraph
\input ward
\stopparagraph
\stoptext
The opposite scenario doesn't work, viz.
==
% setup paragraph indents
\startsetups[paragraph:indent]
\setupindenting[big,yes]
\stopsetups
\defineparagraph[indent][setups
that?
I think ConTeXt behaves the opposite way you expected (or at least, this
is what I get from trial and error).
I'm not sure what you mean but a setting like
\setuphead[summary][style=\bf]
is just that, a setting. If you redefine \bf the style also changes. Or
when you set color=red
the opposite way you expected (or at least, this
is what I get from trial and error).
But maybe for good reasons I don't quite understand, Context implements
this differently.
Hans should know better about that. Coding is actually Greek to me.
At least I think such 'unexpected' behaviour (for me
On 11/19/2014 5:48 PM, Rik Kabel wrote:
(This is a bump, with an improved example, of my earlier note on the
subject.)
In MKIV, \preventmode does not work. It appears to do the opposite of
what is intended, and enable the specified mode. It also does not
prevent the explicit enablement
(This is a bump, with an improved example, of my earlier note on the
subject.)
In MKIV, \preventmode does not work. It appears to do the opposite of
what is intended, and enable the specified mode. It also does not
prevent the explicit enablement of a mode (as can be seen by
uncommenting
not be
inclined to do that, they want to tinker.
Agreed, though for my part with the opposite emphasis. I do not think ConTeXt
is meant to be a “serious product”, as in being developed to be a product in
the “marketplace” of typesetting software — even open/free software. My
impression
) and capabilities. Besides, the tinkering
researchers may not be inclined to do that, they want to tinker.
Agreed, though for my part with the opposite emphasis. I do not think
ConTeXt is meant to be a “serious product”, as in /being developed to be
a product in the “marketplace” of typesetting software
with the opposite emphasis. I do not think
ConTeXt is meant to be a “serious product”, as in /being developed to be
a product in the “marketplace” of typesetting software — even open/free
software. /My impression is exactly yours, it is being developed
primarily for the purposes of Pragma—a small in-crowd
Hi,
Is there a command to produce an averaged integral sign ($\int$ with a
slash drawn across it)?
On a related note: It seems to me that \ointclockwise and
\ointctrclockwise produce results opposite to what their names would
indicate.
Thanks,
Janne Junnila
Janne Junnila janne.junn...@gmail.com writes:
On a related note: It seems to me that \ointclockwise and
\ointctrclockwise produce results opposite to what their names would
indicate.
It seems wrong to me as well. It could be a problem in a mapping
internal to context (or maybe the font
On Mon, 14 Apr 2014, Sanjoy Mahajan wrote:
Janne Junnila janne.junn...@gmail.com writes:
On a related note: It seems to me that \ointclockwise and
\ointctrclockwise produce results opposite to what their names would
indicate.
It seems wrong to me as well. It could be a problem in a mapping
On 4/14/2014 4:22 PM, Aditya Mahajan wrote:
On Mon, 14 Apr 2014, Sanjoy Mahajan wrote:
Janne Junnila janne.junn...@gmail.com writes:
On a related note: It seems to me that \ointclockwise and
\ointctrclockwise produce results opposite to what their names would
indicate.
It seems wrong to me
, is there an opposite command?
Hi David,
as far as I know, location=right is the option you want.
See minimal sample:
\setuppapersize[A6]
\setuppagenumbering[alternative=doublesided, location=right]
\starttext
\input knuth\page
\input zapf\page
\input ward
\stoptext
I hope
Hello all, trying to get page numbers in the outer margin edge of a
double-sided document — marginedge as it is places the numbers to the inside
margin edge, is there an opposite command?
Thanks,
David
___
If your
On 03/03/2014 07:37 PM, David Wooten wrote:
Hello all, trying to get page numbers in the outer margin edge of a
double-sided document — marginedge as it is places the numbers to the
inside margin edge, is there an opposite command?
Hi David,
as far as I know, location=right is the option you
. The opposite page is not completely filled with
text, which makes context crop the height of the page with the float,
too, resulting in a shift of the float into the upper margin. That's
why I want to disable balancing.
Kind regards,
Joshua Krämer
reference.
...
Additionaly, columns are not balanced properly in all cases. When
the first is longer, it is not a big problem. But the opposite
case looks weird.
As the registers are rendered programatically, I cannot intervene
into this process. But can I influence it e.g. using
are not balanced properly in all cases. When the
first is longer, it is not a big problem. But the opposite case
looks weird.
As the registers are rendered programatically, I cannot intervene into this
process. But can I influence it e.g. using 'processors' applied to
problematic index entries
the
first is longer, it is not a big problem. But the opposite case
looks weird.
As the registers are rendered programatically, I cannot intervene into this
process. But can I influence it e.g. using 'processors' applied to
problematic index entries?
Processors can be used for setting the font
the overflowing is triggered?
And always keep all the page references together?
Additionaly, columns are not balanced properly in all cases. When the first
is longer, it is not a big problem. But the opposite case looks weird.
Can I influence this behaviour?
Thanks, Jan
PS: Grid is not activated
with
Unix like operating systems. No bat files or other ancillary code or
invokations are necessary.
Texlive's Context program would probably not run directly on Microsoft
Windows O.S.
hm, my experience is the opposite: texlive context runs on Windows, but I
don't use it because
distribution,
selected with Unix like operating systems. No bat files or other
ancillary code or invokations are necessary.
Texlive's Context program would probably not run directly on
Microsoft Windows O.S.
hm, my experience is the opposite: texlive context runs on Windows,
but I
the table
again.
The product teacher.tex (a teacher manual) can be defined as shown on the
opposite site. What does opposite site mean?
In most cases working with only \starttext and \stoptext in combination
with \input or \enviroment is sufficient. Sufficient for what?
A project structure has
and the rendering is lovely, even on the
extremely complex ligatures. I noticed only two errors, both of which are
simple to describe and consistent:
1) Conjuncts of the form (consonant + virama + र ra) render the opposite
sequence intended. For example:
[U+0915] [U+094D][U+0930] (क्र kra) incorrectly
.
I ran some tests on the output and the rendering is lovely, even on the
extremely complex ligatures. I noticed only two errors, both of which are
simple to describe and consistent:
1) Conjuncts of the form (consonant + virama + र ra) render the opposite
sequence intended. For example:
[U+0915
},alternative=doublesided] ?
Yes :) It helps with page number position, and everything is ok when
using \setuplayout[width=middle]. But when one use narrower width then
the backspace is on the opposite side.
I always thought that backspace is on the left side of single page, or
on the outer sides when
:
\setuppagenumbering[location={footer,right},alternative=doublesided] ?
Yes :) It helps with page number position, and everything is ok when
using \setuplayout[width=middle]. But when one use narrower width then
the backspace is on the opposite side.
I always thought that backspace is on the left side
sence, I understood that these terms are opposite in context?),
the middle one is empty (just to control the space between the to
text-columns), and the right columns, arabic, is right aligned.
I want to control all three by something like .46\textwidth, and no
indentation (like the above result
one ist left-aligned, for the german text (left-algined in the usual sence, I
understood that these terms are opposite in context?), the middle one is
empty (just to control the space between the to text-columns), and the right
columns, arabic, is right aligned.
I want to control all three
side of the glyphs)
there is salt in food unless there's too little or too much of it
present.
the opposite is true for hz and protrusion ... it takes a while to
believe that tex can do a bad job when these are applied extremely and
when applied less extreme one doesn't notice so i find myself
be relied on with OpenType fonts mainly because we don't
control all the fonts and since U+0338 is a combining mark it tends to
have -ve left side bearing (the opposite of CM).
Previously I thought it should be handled as special math accent that
don't get shifted above, but this didn't work because
with different width would not look
good.
ok, so officially it has zero width
This can't be relied on with OpenType fonts mainly because we don't
control all the fonts and since U+0338 is a combining mark it tends to
have -ve left side bearing (the opposite of CM).
ah, ok
Previously I thought
console output, but the pdf
doc created is the same with the same image size issues.
Also of note is that pdflatex output on a pandoc-latex file does almost
exactly the opposite of what context does--all images are scaled to fit
text width by default (like using factor=max in context
for alignments:
\startalignment [right|middle|left]
\input knuth
\stopalignment
however three different command for boxed alignments (furthermore,
\startrightaligned works just the opposite of \startalignment[right]):
\startrightaligned
FooBar
\stoprightaligned
\startmidaligned
created by
system,
i.e. when you put \mainlanguage[en] in your document context enables the mode
“*en”.
The opposite of this are user modes which are enable by the user itself with
\enablemode[…].
Hmmm, alpha.tex defines component a, beta.tex defines b, is that right?
No, that should be a typo
1 - 100 of 410 matches
Mail list logo
