e
context(environment.oldhome or "??")
\stopluacode
\stoptext
ChkEnv.pdf
Description: Adobe PDF document
-- generator : luat-sta.lua
-- state tag : whatever
return {
["context"]={
["version"]="beta",
},
["engines"]={
["luatex&
36 pages/second
Ok, that is not bad (I think on my already old machine one run took some
18 seconds for luatex and of course in mkii with pdftex I could watch a
movie while processing the file.)
The memory footprint also looks ok, especially given all these graphics.
(in most cases lmtx has
ngine=luatex" at the
top line of the source file (but no pdftex and xetex in this installer).
FWIW, the lmtx installation ships with the latest experimental luatex
binary but normally that should not have consequences, but it does
permits testing occasional updates.
Hans
The binary f
e
> the engine in the usual way with "% engine=luatex" at the top line of the
> source file (but no pdftex and xetex in this installer).
I updated LMTX on MacOSX 10.13 today.
The luatex binary in not executable, thus when I run
axel$ context --luatex --version
mtx-context
ource file (but no pdftex and xetex in this installer).
FWIW, the lmtx installation ships with the latest experimental luatex
binary but normally that should not have consequences, but it does
permits testing occasional updat
k and
score calculations) but it's mkii (so you need to run pdftex). Maybe I should
check it with mkiv too.
Could you please tell us where to find that file, even if it is only with mkii?
(I need to prepare some material for my students, for the same reason as
Fabrice…).
Where? On my machine,
t; and score calculations) but it's mkii (so you need to run pdftex). Maybe I
> should check it with mkiv too.
Could you please tell us where to find that file, even if it is only with mkii?
(I need to prepare some material for my students, for the same reason
tions) but it's mkii (so you need to run
pdftex). Maybe I should check it with mkiv too.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
se seem to have met that requirement. I really don't want to
write a huge cascade of if-s to test for different engines.
> afaik there has never been a formal etex version 1 (in use) an
#x27;s
default to etex .. you can try to put this at the top of yuor file
\newcount\eTeXversion \eTeXversion = 2000
\newcount\eTeXrevision \eTeXrevision = 0020
afaik there has never been a formal etex version 1 (in use) and never a
fundamental revision ... in lmtx we no longer have these version
pentype/public/lm/lmroman10-italic.otf
usedmethod=database
system > 12: filename=lmroman10-bolditalic filetype=otf format=otf
foundname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman10-bolditalic.otf
fullname=d:/Ctx-Beta/tex/texmf/fonts/opentype/public/lm/lmroman10-bolditalic
nuth’s TeX than a bloated pdfTeX/LuaTeX.
Indeed, although I admit that I added some primitives that I felt were
missing (which is why we will have foo.lmtx source files).
Hans
-
Hans Hage
f how to apply primitives.
Maybe not PlainTeX, but plain TeX.
E.g. we usually use TeX primitives like \def (even if we have \define), while
with LaTeX you use \newcommand, similar with \vbox and others.
I understood LuaMetaTeX, as a stripped-down typesetting engine, would be closer
to the spir
rse be the yearly tex live snapshots and these will
have the year attached to them.
So, effectively nothing changes, apart from the fact that we no longer
use the labels (and distinction on the website).
I like this change.
A more fundamental distinction is between the versions:
pdftex|xetex
py of some tree is
>> cheap.
>>
>> There will of course be the yearly tex live snapshots and these will
>> have the year attached to them.
>>
>> So, effectively nothing changes, apart from the fact that we no longer
>> use the labels (and distinction on t
them.
So, effectively nothing changes, apart from the fact that we no longer
use the labels (and distinction on the website).
I like this change.
A more fundamental distinction is between the versions:
pdftex|xetex : mkii (probaly not used that much any longer)
luatex|luajittex : mkiv (also th
t from the fact that we no longer
use the labels (and distinction on the website).
A more fundamental distinction is between the versions:
pdftex|xetex : mkii (probaly not used that much any longer)
luatex|luajittex : mkiv (also the test for luatex dev)
luametatex : lmtx (the (upcoming)
On 12/5/2019 1:39 AM, Henri Menke wrote:
It actually seems as if the documentation of LuaTeX is wrong here,
because the behaviour of `\adjustspacing=1' is compatible with
`\pdfadjustspacing=1` in pdfTeX. From the pdfTeX manual:
When \pdfadjustspacing is set to 1, font expansion is ap
It actually seems as if the documentation of LuaTeX is wrong here,
because the behaviour of `\adjustspacing=1' is compatible with
`\pdfadjustspacing=1` in pdfTeX. From the pdfTeX manual:
When \pdfadjustspacing is set to 1, font expansion is applied after
TeX’s normal paragraph bre
nd does it correctly with lualatex.
>> So I would suggest a bug report at https://github.com/pgf-tikz/pgf.
> I just assume that Henri deals with it in due time.
For some reason TikZ tries to load the pdftex driver when used in
ConTe
On Mon, 12 Aug 2019 at 13:42, Jon Wong wrote:
>
> I was able to use `context’ but not `texexec’. The latter (`texexec —pdf
> test.tex’) tells me that some format file (`cont-en.fmt’) can’t be found.
>
> Is `texexec’ obsolete?
texexec is only for Mark II (8-bit pdfTeX, XeTeX)
t because font encodings are
> gone and input is utf8 by default that might need to be changed.
> Structure has more options. I think the biggest conceptual change in the
> setups has been the way footnotes are co
e options. I think the biggest conceptual change in the
setups has been the way footnotes are configured. Of course there are
new commands too.
So, a small example triggering the issue would help,
Hans
ps. Of course the biggest change is that luatex is
ns of this approach, then you can learn metapost/tikz :-)
If you follow this route, then I would add
\usepackage[pdftex,active,tightpage]{preview}
\setlength\PreviewBorder{2mm}
\PreviewEnvironment{tikzpicture}
in the latex preamble. This will create standalone pages that are the same
size the t
On Fri, 12 Apr 2019 23:19:34 +0200
Henning Hraban Ramm wrote:
> minimals installation (2019.04.12 17:43, still not lmtx)
Ah, when I first started using ConTeXt, MkIV was somewhat experimental and it
was still recommended to use MkII (with pdftex) for "production". Now we a
a remnant
from Mark II, as in pdfTeX and XeTeX it would have resulted in an error;
in ConTeXt it just becomes a no-op, which thus shadows LuaTeX’s
behaviour that could actually have been useful.
The situation in Mark IV is documented in languages-mkiv.pdf which is
part of the distribution: Hans re
Hi
We currently have
mkii : which uses pdftex/xetex
mkiv : which uses lua(jit)tex 1.10
and next year we will also have
lmtx : which runs luatex
functionally there is no difference between mkiv and lmtx but there are
some diferences under the hood. It might also turn out to be a bit
still here. — When
> the second author agrees I can deliver them to you. — However there is a
> warning to be made, that the project is 10 years old and was built in
> pdfTeX/ConTeXt MKII.
> >
> > Hi Willi,
> >
> > I sent the files to T
the authors, yes I have these file still here. — When the
>> second author agrees I can deliver them to you. — However there is a warning
>> to be made, that the project is 10 years old and was built in pdfTeX/ConTeXt
>> MKII.
>
> Hi Willi,
>
> I sent the files to T
On Wed, 28 Nov 2018, Willi Egger wrote:
As being one of the authors, yes I have these file still here. — When
the second author agrees I can deliver them to you. — However there is a
warning to be made, that the project is 10 years old and was built in
pdfTeX/ConTeXt MKII.
Hi Willi,
I sent
Hello Tommaso,
As being one of the authors, yes I have these file still here. — When the
second author agrees I can deliver them to you. — However there is a warning to
be made, that the project is 10 years old and was built in pdfTeX/ConTeXt MKII.
Kind regards
Willi
> On 28 Nov 2018, at
.10 for
next texlive 2019, and in our minds "stable" means "in the long term
like pdftex".
In practice this means that luatex comes with lua 5.3.4, that
luajittex uses luajit 2.1 beta3, and that context will assume and support
this setup for a long time. This also means that we
pdf ...
echo.
:ruby
echo okay > ok.log
ruby -e "File.delete('ok.log')"
if not exist "ok.log" goto end
echo.
echo The distribution has been downloaded but if you want to run pdfTeX and/or
XeTeX you
echo need to run this script with the following directive:
echo.
e
ve 2019/dev)
>
> The LuaTeX team is Hans Hagen, Hartmut Henkel, Taco Hoekwater, Luigi
> Scarso.
>
> LuaTeX merges and builds upon (parts of) the code from these projects:
>
> tex : Donald Knuth
> etex : Peter Breitenlohner, Phil Taylor and friends
> omega : John Plaice and
and builds upon (parts of) the code from these projects:
tex : Donald Knuth
etex : Peter Breitenlohner, Phil Taylor and friends
omega : John Plaice and Yannis Haralambous
aleph : Giuseppe Bilotta
pdftex: Han The Thanh and friends
kpathsea : Karl Berry, Olaf Weber and
lor blue;
>>> \stopMPpage
>>>
>>> Is there anything I can do or is it a problem of the source?
>>
>>
>> checking now
>>
>> --
>> luigi
>>
>
>The example is ok on my Raspberry Pi 3 Model B Rev 1.2
>I assume luatex experiment
n my Raspberry Pi 3 Model B Rev 1.2
I assume luatex experimental, because luatex trunk is still with poppler .
# luatex --credits
This is LuaTeX, Version 1.09.0 (TeX Live 2018)
The LuaTeX team is Hans Hagen, Hartmut Henkel, Taco Hoekwater, Luigi Scarso.
LuaTeX merges and builds upon (parts of)
friends
omega : John Plaice and Yannis Haralambous
aleph : Giuseppe Bilotta
pdftex: Han The Thanh and friends
kpathsea : Karl Berry, Olaf Weber and others
lua : Roberto Ierusalimschy, Waldemar Celes and Luiz Henrique de
Figueiredo
metapost : John Hobby, Taco Hoekwater, Luigi
>>>
>>>>> Ideally - to process a single page PDF into another file, with
>>>>> the one page cropped...
>>>>
>>>
>>> The ‘pdfcrop’ command from TeXLive can do that for you on the
>>> command line. It is based around ghostsc
rop a page of a PDF via
> >>> ConTeXt?
> >>>
> >>> Ideally - to process a single page PDF into another file, with
> >>> the one page cropped...
> >>
> >
> > The ‘pdfcrop’ command from TeXLive can do that for you on the
>
from TeXLive can do that for you on the command line.
It is based around ghostscript which can automatically find the crop area,
then uses pdftex,luatex,or xetex to create a new pdf.
It is doable to come up with a solution in ConTeXt if you do not mind
specifying the cropbox manually, but automatic
pdfcrop’ command from TeXLive can do that for you on the command line.
It is based around ghostscript which can automatically find the crop area,
then uses pdftex,luatex,or xetex to create a new pdf.
It is doable to come up with a solution in ConTeXt if you do not mind
specifying the cropbox man
only a
very small percentage of readers will notice (at that time we did
experiments with hz, the expansion in pdftex: in fact nobody noticed
that too, real interesting was that texies commented on all kind of
things related to how tex is supposed to work: a clear demonstration
that the average user
hat only a
>>> very small percentage of readers will notice (at that time we did
>>> experiments with hz, the expansion in pdftex: in fact nobody noticed
>>> that too, real interesting was that texies commented on all kind of
>>> things related to how tex is supp
scale the text area (i
actully implemented that an hour later) ... his opinion was that only a
very small percentage of readers will notice (at that time we did
experiments with hz, the expansion in pdftex: in fact nobody noticed
that too, real interesting was that texies commented on all kind of
ter) ... his opinion was that only a
> very small percentage of readers will notice (at that time we did
> experiments with hz, the expansion in pdftex: in fact nobody noticed
> that too, real interesting was that texies commented on all kind of
> things related to how tex is supposed
at an hour later) ... his opinion was that only a
very small percentage of readers will notice (at that time we did
experiments with hz, the expansion in pdftex: in fact nobody noticed
that too, real interesting was that texies commented on all kind of
things related to how tex is supposed to wo
(or do you want to use) context mkii ?
>
>
> texfont is still shipped
as you can see in
tex/texmf-context/scripts/context/perl
and you can run it with
$ mtxrun --script texfont --help
Do, for r mkii you need to provide in some way pdftex, perl and ruby
(for the scripts under tex/t
GPG Key ID 1C9B22FD
Am 2018-02-23 um 13:50 schrieb Gerard :
> Thanks Thomas,
>
> I use Texworks with Context (pdftex)...
>
> With the code below, I get the text in blue and separator in red. See the
> command \setupcolors[textcolor=red] and \color[blue] before \startco
Thanks Thomas,
I use Texworks with Context (pdftex)...
With the code below, I get the text in blue and separator in red. See
the command \setupcolors[textcolor=red] and \color[blue] before
\startcolumns.
Gérard
--- exemple basique-
\enableregime[utf-8]
\mainlanguage[fr
rts it but i never really used xetex myself and i
haven't used pdftex in a decade)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
$ test\par
% combination of 1 and 3
\stoptext
hm, seems that i messed up a pointer ... i'll fix it ...
(xetex inserts a kern of 2.45pt after the math in latex).
context inserts 2.938pt
(luatex uses the opentype route so it might be different than xetex and
change is that adding a
brace group in the middle of a word (like in of{}fice) does not
prevent ligature creation."
With pdftex it does avoid ligatures, but not reliably. There are
cases where the brace group disappear when pdftex tries out
hyphenation points.
in traditional tex hyphenation is in
dle of a word (like in of{}fice) does not
prevent ligature creation."
With pdftex it does avoid ligatures, but not reliably. There are
cases where the brace group disappear when pdftex tries out
hyphenation points.
--
Ulrike Fischer
http://www.trou
are under TeXworks : you must have
"ConTeXt MKIV" just beside the green arrow. If your compilation doesn't work
maybe it is because you are trying to compile your *.tex file with another
executable (pdftex, pdflatex, or anything else...).
Very good idea to build some Spanis
Am Fri, 16 Jun 2017 11:08:21 +0200 schrieb luigi scarso:
>> I can't reproduce it either in a current minimals, but miktex had
>> for a few days a similar bug which affected pdftex and (according
>> Christian) also luatex: https://sourceforge.net/p/miktex/bugs/2605/
&g
On Fri, Jun 16, 2017 at 11:04 AM, Ulrike Fischer wrote:
> I can't reproduce it either in a current minimals, but miktex had
> for a few days a similar bug which affected pdftex and (according
> Christian) also luatex: https://sourceforge.net/p/miktex/bugs/2605/
The message from him
code'
>
> This happens if the document includes JPEG images, e.g:
>
> \starttext
> \externalfigure[hacker.jpg]
> \stoptext
>
>
>
> not here, with that image.
I can't reproduce it either in a current minimals, but miktex had
for a few days a similar bug which a
-clever will be
limited.
(Ignore the implementation details, which were a series of hacks to make
things work in pdftex, but section 14 explains the different display
math layouts and a strategy to choose between them. It will be really
nice to have something comparable in ConTeXt.
You mean
://ctan.math.washington.edu/tex-archive/macros/latex/contrib/breqn/breqn.pdf
(Ignore the implementation details, which were a series of hacks to make
things work in pdftex, but section 14 explains the different display math
layouts and a strategy to choose between them. It will be really nice to
have something
On Tue, 7 Mar 2017 18:04:34 +0100
Floris van Manen wrote:
> The incorrect nesting seems to be connected to the luatex engine.
> If i have the same source compiled by pdftex, it works as intended.
>
> So is the different rendering an intended feature of luatex, or a
> simple bug
The incorrect nesting seems to be connected to the luatex engine.
If i have the same source compiled by pdftex, it works as intended.
So is the different rendering an intended feature of luatex, or a simple bug?
.F
> On 6 Mar 2017, at 00:34, Floris van Manen wrote:
>
> Is there a
> (except the source) for the newcolumnsets? I want to be able to have
> images span both columns and it would be nice if it played well with
> sections as well.
>
> Best regards, Mikael
Dear list,
(I got some information offlist from Hans regarding NAW, it seems they
used an old pdftex
e space (there are quite a number of
questions on tex.SX where the heuristic fails, e.g. in code
listings), while reflow seems to need glyphs. The speech of Ross
Moore on TUG14 seems to indicate that \pdfinterwordspaceon was
introduced in pdftex to get around this problem.
http://river-valley.zeeba.tv/
ste use an heurisitic more or less
based on the size of the space (there are quite a number of
questions on tex.SX where the heuristic fails, e.g. in code
listings), while reflow seems to need glyphs. The speech of Ross
Moore on TUG14 seems to indicate that \pdfinterwordspaceon was
introduced in pdf
th pdflatex + lualatex), that's imho the reason why microtype
>> copies the fonts.
>
> in fact that is also the case with pdftex: afaik expansion and
> protrusion values are global and once a font is used they get frozen
Yes, exactly.
>
> in luatex (at least the lua fo
t has been expanded with different
stretch limit.
(with pdflatex + lualatex), that's imho the reason why microtype
copies the fonts.
in fact that is also the case with pdftex: afaik expansion and
protrusion values are global and once a font is used they get frozen
in luatex (at least the
py at the tfm level. One can
just use
\let\testb\testa
instead. Information related to fonts at the lua end is not known to
\copyfont.
If the second: Is there in the fontloader a replacement which can be
used to copy fonts?
I think the \copyfont primitive was introduced in pdftex as a ki
m for conversions ... (it's how we deal with
eps and svg input)
Here is the link to the script
http://stdin.fr/Bazar/SpotColorImages
see chapter 3 in the colors-mkiv.pdf manual in the distribution; this
kind of magic is already present for a while (we actually did it in
pdftex / mkii in som
you.
>>> I want to use MkII because, as far as I know, MkII uses pdfTeX; which is
>>> stable. While MkIV uses LuaTeX; which is yet in development. Further,
>>> pdfTeX is better at microtypography.
>>>
>>
> In what respect better? The mechanism in Luatex is
On 10/28/2016 9:06 PM, Pablo Rodriguez wrote:
On 10/28/2016 08:35 PM, Asim ConTeXt wrote:
Thank you.
I want to use MkII because, as far as I know, MkII uses pdfTeX; which is
stable. While MkIV uses LuaTeX; which is yet in development. Further,
pdfTeX is better at microtypography.
In what
On 10/28/2016 08:35 PM, Asim ConTeXt wrote:
> Thank you.
> I want to use MkII because, as far as I know, MkII uses pdfTeX; which is
> stable. While MkIV uses LuaTeX; which is yet in development. Further,
> pdfTeX is better at microtypography.
> Am I correct at these two points?
command :|
mtxrun --script fonts --list --pattern=AnyFont* --all (you can play with *
before and/or after the Font name))
|Hope that helps,|
|JP
|
Le 28/10/2016 à 20:35, Asim ConTeXt a écrit :
Thank you.
I want to use MkII because, as far as I know, MkII uses pdfTeX; which
is stable. While
Thank you.
I want to use MkII because, as far as I know, MkII uses pdfTeX; which is
stable. While MkIV uses LuaTeX; which is yet in development. Further, pdfTeX
is better at microtypography.
Am I correct at these two points? I would like to hear from you.
I found that my system fonts are located
On 8/13/2016 4:12 PM, Vya. Y. wrote:
Hello,
After updating to the latest beta, TeXWorks shows an error message every
time I open and compile a document. ("The procedure entry point could
not be located in the dynamic link library").
I don't undestand how pdftex is involved wh
Hello,
After updating to the latest beta, TeXWorks shows an error message every
time I open and compile a document. ("The procedure entry point could not
be located in the dynamic link library").
I don't undestand how pdftex is involved when I compile to luatex.
Rega
wrong hyphenations.
I have LuaTeX, Version 0.95.0 (TeX Live 2016) on openSUSE 13.2 (Harlequin)
(x86_64) and correct hyphenations. Wolfgangs minimal example
\starttext \hsize=1mm
would synthesize enumerate
\stoptext
produces
would
syn-
the-
size
enu-
mer-
ate
which is what pdfTeX produces as well for
irst-setup.bat weirdness I: cloned system" -- it seems
appropriate to put this one out to the forum as well.
Any explanations and advice would be appreciated. Never had these
problems using when updating manually... Thanks in advance and
if you do a fresh install with
--engine=luatex
then you&#x
up.bat again on the windows7 machine,
got the following errors:
=
mtx-context | running command: pdftex --ini --etex --8bit cont-en.mkii
\dump
warning: c:/ConTeXt/tex/texmf/web2c/texmf.cnf:49: (kpathsea) No cnf value
on lin
e: OSFONTDIR =.
This is pdfTeX, Version 3.141592
ariants. was this dropped in MkIV or was there
> never a persian language environment even in MkII?
MkII (read: ConTeXt with pdfTeX) doesn't support typesetting in Arabic
script at all.
And support for XeTeX has always been limited in ConTeXt. So it's not
really strange if the languag
ex
warning: f:/Sandbox/ConTeXt/tex/texmf/web2c/texmf.cnf:49: (kpathsea) No
cnf value on line: OSFONTDIR =.
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/W32TeX)
(preloaded format=cont-en)
\write18 enabled.
---! f:/Sandbox/ConTeXt/tex/texmf-win64/web2c/pdftex/cont-en.fmt doesn't
m TeXWorks configuration
with ConTeXt Standalone : there is no way to compile directly with pdftex. You
must compile with ConTeXt MK IV luatex. For such a result, you have to set
preferences in your Textadept with the good PATH (where textadept can find the
setuptex of CTX). It's a good thing
n" to my system path
- I downloaded and unzipped Textadept and also added the folder to my
system path.
- I opened a *.tex file with Textadept and pressed "Tools->Compile" but
I only got an error message:
> pdflatex -file-line-error -halt-on-error "untitled-3.tex&q
refers to latex which for
sure will have some way to set up these feaures; i don't know about
plain support
in context protrusion and expansion is supported in mkii (pdftex) and
mkiv (luatex) .. in mkiv there is a bit more control
there is no preprocessing involved (these two features are j
On 2016-04-06 Hans Hagen wrote:
> On 4/5/2016 11:51 PM, Jan Tosovsky wrote:
> > On 2016-04-05 Hans Hagen wrote:
> >> On 4/5/2016 10:55 PM, Jan Tosovsky wrote:
> >>>
> >>> according to http://texdoc.net/texmf-
> >>> dist/doc/latex/microtype/micr
On 4/6/2016 6:48 AM, Henning Hraban Ramm wrote:
Am 2016-04-06 um 03:51 schrieb Jan Tosovsky :
Note that character protrusion requires pdfTeX (version 0.14f or later),
LuaTeX, or
XeTeX (at least version 0.9997). Font expansion works with pdfTeX (version 1.20
for
automatic expansion) or
On 4/5/2016 11:51 PM, Jan Tosovsky wrote:
On 2016-04-05 Hans Hagen wrote:
On 4/5/2016 10:55 PM, Jan Tosovsky wrote:
according to http://texdoc.net/texmf-
dist/doc/latex/microtype/microtype.pdf
pdfTeX offers fine tuning of:
(1) Character protrusion
(2) Font expansion
(3) Tracking
(4
Am 2016-04-06 um 03:51 schrieb Jan Tosovsky :
>
> Note that character protrusion requires pdfTeX (version 0.14f or later),
> LuaTeX, or
> XeTeX (at least version 0.9997). Font expansion works with pdfTeX (version
> 1.20 for
> automatic expansion) or LuaTeX. The package will
On 2016-04-05 Hans Hagen wrote:
> On 4/5/2016 10:55 PM, Jan Tosovsky wrote:
> >
> > according to http://texdoc.net/texmf-
> > dist/doc/latex/microtype/microtype.pdf
> > pdfTeX offers fine tuning of:
> > (1) Character protrusion
> > (2) Font expansion
>
On 4/5/2016 10:55 PM, Jan Tosovsky wrote:
Dear All,
according to http://texdoc.net/texmf-dist/doc/latex/microtype/microtype.pdf
pdfTeX offers fine tuning of:
(1) Character protrusion
(2) Font expansion
(3) Tracking
(4) Additional kerning
(5) Interword spacing
AFAIK ConTeXt covers 1+2+(3?). In
Dear All,
according to http://texdoc.net/texmf-dist/doc/latex/microtype/microtype.pdf
pdfTeX offers fine tuning of:
(1) Character protrusion
(2) Font expansion
(3) Tracking
(4) Additional kerning
(5) Interword spacing
AFAIK ConTeXt covers 1+2+(3?). In recent discussion Hans mentioned
s meant with bad boxes? i read "Underfull \hbox (badness
1) in paragraph..." but don't know how to fix this.
Warnings fron pdftex will dissapear when you switch to MkIV :-).
"Underfull \hbox" may be caused by wrong hyphenation?
Would it be possible that you were compil
es? i read "Underfull \hbox (badness
1) in paragraph..." but don't know how to fix this.
Warnings fron pdftex will dissapear when you switch to MkIV :-).
"Underfull \hbox" may be caused by wrong hyphenation?
Would it be possible that you were compiling a German (or no
e but fix it.
> and what is meant with bad boxes? i read "Underfull \hbox (badness
> 1) in paragraph..." but don't know how to fix this.
Warnings fron pdftex will dissapear when you switch to MkIV :-).
"Underfull \hbox" may be caused by wrong hyphenation?
Would
2} \over 2}
it can lead to exponential number of branches.
With \frac{\text{hello}}{2}, TeX "knows" what style to use for the
arguments. So, extra processing is not needed (at least, this is the
idea in LuaTeX; in PDFTeX, multiple sizes need to be generated). This
can lead to some s
al number of branches.
>
> With \frac{\text{hello}}{2}, TeX "knows" what style to use for the
> arguments. So, extra processing is not needed (at least, this is the
> idea in LuaTeX; in PDFTeX, multiple sizes need to be generated). This
> can lead to some slightl
ntial number of branches.
With \frac{\text{hello}}{2}, TeX "knows" what style to use for the
arguments. So, extra processing is not needed (at least, this is the idea
in LuaTeX; in PDFTeX, multiple sizes need to be generated). This can lead
to some slightly faster processing.
Also see htt
note that de Boer's document, "LaTeX in proper ConTeXt"
>>>> recommends compiling from the command line using texexec rather than
>>>> context. This does not work for me. The command "texexec" exists, and I
>>>> can run it, but it do
exexec" exists, and I
>>> can run it, but it does not produce a .pdf file -- just a .tmp file.
>>
>> That document is a very old one. Nowadays context is preferred to
>> texexec (also known as Mark II
eferred to
> texexec (also known as Mark II or MkII). If you installed context with
> --engines=luatex you explicitly did not installed prerequisites for
> Mark II (pdftex with fonts etc.).
>
> Mojca
> __
101 - 200 of 4105 matches
Mail list logo
