work equally well as in
pdfTeX. XeTeX also has bugs in OpenType Math, but for the reason just
told, this should not affect you.
On the other hand if you need other MKIV features that might indeed be
a problem.
I am wary to use XeTeX because every new small task
with ConTeXt always ends up taking
options end of optionfile
(bibtest.top)
fontslatin modern fonts are not preloaded
languageslanguage en is active
{/home/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin modern fonts (second stage)
(/home/context/tex/texmf
luigi scarso luigi.scarso at gmail.com writes:
can you post the log ?
Can be: if
$context
works than you have a mkiv.
The context command doesn't work at the command line. Here is the log; I'm not
sure how much of it is useful.
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009
ConTeXt User Module / Module Catcodes
)){/home/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin modern fonts (second stage)
(/home/context/tex/texmf-context/tex/context/base/type-siz.mkiv) (/home/context/tex/texmf-context/tex/context/base/type
options end of optionfile
(bibtest.top)
fontslatin modern fonts are not preloaded
languageslanguage en is active
publications wrote a new auxiliary file \jobname.aux
{/home/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin
export to xml
{/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin modern fonts (second stage)
(/usr/share/texmf/tex/context/base/type-siz.mkiv) (/usr/share/texmf/tex/context/base/type-otf.mkiv){/usr/share/texmf/fonts/map/dvips/lm/lm-math.map}{/usr/share/texmf
of optionfile
(bla.top)
fontslatin modern fonts are not preloaded
languageslanguage en is active
{/usr/local/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin modern fonts (second stage)
(/usr/local/context/tex/texmf-context/tex/context
On 15-6-2011 10:59, Ulrike Fischer wrote:
With ConTeXt ver: 2011.06.13 23:08 MKIV fmt: 2011.6.15 (from the
minimals) the following fails:
I have to admit that I never used \letterspacefont (luatex offers it as
a pdftex compatibility feature and as such it's strongly related
Am Wed, 15 Jun 2011 11:48:10 +0200 schrieb Hans Hagen:
On 15-6-2011 10:59, Ulrike Fischer wrote:
With ConTeXt ver: 2011.06.13 23:08 MKIV fmt: 2011.6.15 (from the
minimals) the following fails:
I have to admit that I never used \letterspacefont (luatex offers it as
a pdftex
export enabling export to xml
(/usr/share/texmf/tex/context/base/type-siz.mkiv) (/usr/share/texmf/tex/context/base/type-otf.mkiv){/usr/share/texmf/fonts/map/dvips/lm/lm-math.map}{/usr/share/texmf/fonts/map/dvips/lm/lm-rm.map}{/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map}
fonts
-base] \setupbodyfont[modern]
it will work ok. Cambria Math also results in two different heights of
the operator depending on whether limits are there or not. It might be
a bug somewhere in virtual font setup of LM. In pdfTeX \int and \intop
operators are positioned equally.
Mojca
, only this and the \pdfimagehicolor
primitive can influence this low level stuff.
Btw, just \pdfimageapplygamma 0 (without setting \pdfgamma and
\pdfimagegamma) already changes the PNG image, since the luatex (and pdftex)
internal defaults are not gamma-neutral. No idea if (and then
to which value
answers so far.
Regards, Peter
must be some \pdfimageapplygamma 0, only this and the \pdfimagehicolor
primitive can influence this low level stuff.
Btw, just \pdfimageapplygamma 0 (without setting \pdfgamma and
\pdfimagegamma) already changes the PNG image, since the luatex (and pdftex
primitive can influence this low level stuff.
Btw, just \pdfimageapplygamma 0 (without setting \pdfgamma and
\pdfimagegamma) already changes the PNG image, since the luatex (and pdftex)
internal defaults are not gamma-neutral. No idea if (and then
to which value) this should be fixed
-1.5: If
you have a 16 bit PNG, for PDF-1.4 it will be automatically reduced to 8
bit by luatex and pdftex, so suddenly the PDF file gets smaller, but
actually also the image quality (silently) went down.
These are about the factors affecting the PNG to PDF size. For your big
PNG graphic you
profiles?
removed, I suppose.
Not really a big problem, and doable in mkiv
(see
Hacked image color space.
in
texmf-dist/doc/pdftex/manual/samplepdf
of a recent texlive)
--
luigi
___
If your question is of interest
.
Another factor influencing the size is if it's PDF-1.4 or PDF-1.5: If
you have a 16 bit PNG, for PDF-1.4 it will be automatically reduced to 8
bit by luatex and pdftex, so suddenly the PDF file gets smaller, but
actually also the image quality (silently) went down.
These are about the factors affecting
epäjärjestelmällisyydellistyttymättömyydellänsäkään
järjestelmällisentelentelemättömyydellänsäkään hääyöaie}
\stopcolumns
\stoptext
can be downloaded here: https://pi-xi.net/share/context_hyphen.pdf
I also wrote a close as possible equivalent of the code above in LaTeX and
compiled it with pdfTeX (TL 2011
!
publications wrote a new auxiliary file \jobname.aux
{/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin modern fonts (second stage)
(/usr/share/texmf/tex/context/base/type-siz.mkiv) (/usr/share/texmf/tex/context/base/type-otf.mkiv){/usr/share/texmf/fonts/map/dvips
a couple of days ago ...
Log attached.
Adam
(/home/reviczky/Downloads/thesis/src/prd_finalreport.tex
ConTeXt ver: 2011.05.14 16:34 MKIV fmt: 2011.5.14 int: english/english
(/usr/share/texmf/tex/context/base/cont-new.mkiv) (prd_finalreport.top
){/usr/share/texmf/fonts/map/pdftex/context/mkiv
are not preloaded
languageslanguage en is active
system synctex functionality is enabled!
publications wrote a new auxiliary file \jobname.aux
{/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin modern fonts (second stage)
(/usr/share/texmf/tex
are not preloaded
languageslanguage en is active
backend export enabling export to xml
{/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin modern fonts (second stage)
(/usr/share/texmf/tex/context/base/type-siz.mkiv) (/usr/share/texmf/tex/context/base/type
it is not because of my tex file.
Log attached.
Adam
(/home/reviczky/Downloads/ctx/test/thesis/src/prd_finalreport.tex
ConTeXt ver: 2011.05.08 23:02 MKIV fmt: 2011.5.9 int: english/english
(/usr/share/texmf/tex/context/base/cont-new.mkiv) (prd_finalreport.top
){/usr/share/texmf/fonts/map/pdftex/context
/tex/context/base/type-siz.mkiv) (/usr/share/texmf/tex/context/base/type-otf.mkiv) (/usr/share/texmf/tex/context/base/type-otf.mkiv){/usr/share/texmf/fonts/map/pdftex/context/mkiv-tx.map}{/usr/share/texmf/fonts/map/dvips/lm/lm-math.map}{/usr/share/texmf/fonts/map/dvips/lm/lm-rm.map}{/usr/share/texmf
in MkIV but as you use MkII this setting has no effect. You
can apply the style to the table with the \setups command:
% engine=pdftex
\startsetups table:multiplication
\setupTABLE[each][each][frame=off,align=middle,width=2em,height=2em]
\setupTABLE[row][first][bottomframe=on]
\setupTABLE
engine: pdftex
TeXExec | tex format: cont-en
This is pdfTeX, Version 3.1415926-1.40.10 (MiKTeX 2.8)
initexmf: Unknown format name/engine: cont-en/pdfTeX
I can't find the default format file!
TeXExec | runtime: 0.276
Is there something I'm missing? What exactly is the format file mentioned here
Module / Module Catcodes
)) (/opt/context/tex/texmf-context/tex/context/base/type-siz.mkiv)
(/opt/context/tex/texmf-context/tex/context/base/type-otf.mkiv){/opt/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-tx.map}{/opt/context/tex/texmf/fonts/map/dvips/lm/lm-math.map}{/opt/context/tex
the following:
Your system appears to be confused. You mention texlive 2010,
but this message:
TeXExec | using randomseed 510
TeXExec | tex engine: pdftex
TeXExec | tex format: cont-en
This is pdfTeX, Version 3.1415926-1.40.10 (MiKTeX 2.8)
comes from a miktex-supplied binary, not a texlive one.
Best
/
minimals/current/bin/context/linux/ minimals/current/bin/metapost/linux/
minimals/current/bin/man/ minimals/current/bin/luatex/linux/
minimals/current/bin/xetex/linux/ minimals/current/bin/luatex/linux/
minimals/current/bin/luatex/linux/ minimals/current/bin/pdftex/linux/'
'/opt/context/tex/texmf
one post where it was mentione done should add
//\setupMPpage[offset=1pt]
//(http://www.tug.org/pipermail/pdftex/2001-March/000429.html). I tried,
but did not work however...
Any idea how I should do? Find below minimal example, that does not work
on my computer when compiling with context
, except old stand-alone installation. It's
cause of frustration and after several attempts they give up. Then they
return to LaTeX (like me too).
Well, with TeX Live 2010 it's very simple to use MkII with both pdfTeX and
XeTeX. Hopefully, some future version of TeX Live (2011?) will offer
On Mon, Apr 25, 2011 at 07:59, Anand Raj wrote:
Hi,
The symbols like Pi, Theta are not rendered properly.
What font are you using and just to make sure: do you use pdftex
(texexec) or luatex (context)? Please provide a minimal example. In LM
these symbols are displayed fine in math expressions
{/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin modern fonts (second stage)
(/usr/share/texmf/tex/context/base/type-siz.mkiv) (/usr/share/texmf/tex/context/base/type-otf.mkiv){/usr/share/texmf/fonts/map/dvips/lm/lm-math.map}{/usr/share/texmf/fonts/map/dvips
/fonts/map/dvips/lm/lm-rm.map}{/home/cecil/ConTeXt/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
fontsfallback modern mm 18pt is loaded
fontspreloading latin modern fonts (mono)
fontsfallback modern tt 18pt is loaded
fontsdefining font
) it is. Why this difference?
And you think it’s better to let \blank behave different dependent
on the indenting settings?
% engine=pdftex
\starttext
\setupindenting[yes,medium,first]
\input knuth
\blank
\input knuth
\page
\setupindenting[yes,medium,next]
\input knuth
\blank
\input
this difference?
And you think it’s better to let \blank behave different dependent
on the indenting settings?
% engine=pdftex
\starttext
\setupindenting[yes,medium,first]
\input knuth
\blank
\input knuth
\page
\setupindenting[yes,medium,next]
\input knuth
\blank
\input knuth
\stoptext
system options end of optionfile
(test.top)
fontslatin modern fonts are not preloaded
languageslanguage en is active
publications wrote a new auxiliary file \jobname.aux
{/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin
produce
\fillinfield [dvi]{\DVI} output,
but nowadays, thanks to \fillinfield {Han The Thanh}, we can also
directly produce \fillinfield [pdf] {\PDF}!
Nice eh? Actually, while the first field module was prototyped
in \ACROBAT, the current implementation was debugged in
\fillinfield [pdfTeX
was prototyped
in \ACROBAT, the current implementation was debugged in
\fillinfield [pdfTeX] {\PDFTEX}. Field support in \fillinfield
[ConTeXt] {\CONTEXT} is rather advanced and complete and all
kind of fields are supported. One can hook in appearances, and
validation \fillinfield
directly produce \fillinfield [pdf] {\PDF}!
Nice eh? Actually, while the first field module was prototyped
in \ACROBAT, the current implementation was debugged in
\fillinfield [pdfTeX] {\PDFTEX}. Field support in \fillinfield
[ConTeXt] {\CONTEXT} is rather advanced
can also directly
produce \fillinfield [pdf] {\PDF}!
Nice eh? Actually, while the first field module was prototyped
in \ACROBAT, the current implementation was debugged in
\fillinfield [pdfTeX] {\PDFTEX}. Field support in \fillinfield
[ConTeXt] {\CONTEXT} is rather advanced and complete and all
kind
/local32/texlive/experimental/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin modern fonts (second stage)
(/home/08/reviczky/local32/texlive/experimental/tex/texmf-context/tex/context/base/type-siz.mkiv)
(/home/08/reviczky/local32/texlive/experimental/tex/texmf
$pdfinfo page-test.pdfTitle: page-testSubject:Keywords:Author:Creator: ConTeXt - 2011.02.25 22:03Producer: pdfTeX-1.40.11CreationDate: Sat Mar 19 13:50:49 2011ModDate: ConTeXt - 2011.02.25 22:03Tagged: noPages: 5Encrypted: noPage size: 595.276 x 841.89 pts (A4)File size: 33436 bytesOptimized: noPDF
$pdfinfo page-test.pdf
Title: page-test
Subject:
Keywords:
Author:
Creator:ConTeXt - 2011.02.25 22:03
Producer: pdfTeX-1.40.11
CreationDate: Sat Mar 19 13:50:49 2011
ModDate:ConTeXt - 2011.02.25 22:03
Tagged: no
Pages: 5
Encrypted: no
Page
: pdfTeX-1.40.11
CreationDate: Sat Mar 19 13:50:49 2011
ModDate:ConTeXt - 2011.02.25 22:03
Tagged: no
Pages: 5
Encrypted: no
Page size: 595.276 x 841.89 pts (A4)
File size: 33436 bytes
Optimized: no
PDF version:1.5
With MkIV:
$pdfinfo page
error message:
\count0=0
\loop\ifnum\count05000
\advance\count0 by 1
\shipout\vbox{}
\repeat
\end
\starttext
\dorecurse{1} {test: \recurselevel\page}
\stoptext
pdftex + mkii : 35 sec
xetex + mkii : 35 sec
luatex + mkiv : 40 sec
no crashes.
No sense when you say no crashes without
\ifnum\count05000
\advance\count0 by 1
\shipout\vbox{}
\repeat
\end
\starttext
\dorecurse{1} {test: \recurselevel\page}
\stoptext
pdftex + mkii : 35 sec
xetex + mkii : 35 sec
luatex + mkiv : 40 sec
no crashes.
No sense when you say no crashes without show us the version of your
. It's
cause of frustration and after several attempts they give up. Then they
return to LaTeX (like me too).
Well, with TeX Live 2010 it's very simple to use MkII with both pdfTeX and
XeTeX. Hopefully, some future version of TeX Live (2011?) will offer the
same for MkIV. Script is already
/texmf/fonts/map/dvips/lm/lm-math.map}{C:/context/tex/texmf/fonts/map/dvips/lm/lm-rm.map}{C:/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
system begin file rsfs_test.tex at line 41
backend xmp using file
'C:/context/tex/texmf-context/tex/context/base/lpdf
\end
\starttext
\dorecurse{1} {test: \recurselevel\page}
\stoptext
pdftex + mkii : 35 sec
xetex + mkii : 35 sec
luatex + mkiv : 40 sec
no crashes.
-
Hans Hagen | PRAGMA ADE
On 2011-03-14 Cecil Westerhof cldwester...@gmail.com wrote:
When installing minimals you have MKII, XeTeX and MKIV. I understand that
you should normally use MKIV, but when are the other two used?
MKII can be used either with pdftex or xetex (as you wish, compare
advantages/disadvantages
2011/3/14 Marco net...@lavabit.com
On 2011-03-14 Cecil Westerhof cldwester...@gmail.com wrote:
When installing minimals you have MKII, XeTeX and MKIV. I understand that
you should normally use MKIV, but when are the other two used?
MKII can be used either with pdftex or xetex (as you wish
two used?
MKII can be used either with pdftex or xetex (as you wish, compare
advantages/disadvantages). MKIV can only be used with luatex.
You have to differ between ConTeXt »versions« (mkii, mkiv) and TeX
backends (pdftex, xetex, luatex).
And where do I find the advantages
either with pdftex or xetex (as you wish, compare
advantages/disadvantages). MKIV can only be used with luatex.
You have to differ between ConTeXt »versions« (mkii, mkiv) and TeX backends
(pdftex, xetex, luatex).
And where do I find the advantages/disadvantages? Or can I just always use
MKIV
community. In contrary,
for LaTeX users XeTeX is becoming the mainstream engine to use (best
supported by active developers).
MKII can be used either with pdftex or xetex (as you wish, compare
advantages/disadvantages). MKIV can only be used with luatex.
You have to differ between ConTeXt
-otf.mkiv){/Users/charlesdoherty/context/tex/texmf/fonts/map/dvips/lm/lm-math.map}{/Users/charlesdoherty/context/tex/texmf/fonts/map/dvips/lm/lm-rm.map}{/Users/charlesdoherty/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
system begin file Untitled.tex at line 5
backend
language en is active
fontsbeware: no fonts are loaded yet, using 'lm mono' in box
(/Users/graph/ConTeXt/tex/texmf-context/tex/context/base/page-run.mkiv
loading ConTeXt Page Macros / Runtime Macros
){/Users/graph/ConTeXt/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map
-new.mkiv
)
system test~1.top loaded
(test~1.top)
fontslatin modern fonts are not preloaded
languageslanguage en is active
{/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map}
fontspreloading latin modern fonts (second stage)
(/usr/share/texmf/tex/context
On Sat, 5 Mar 2011, Reviczky, Adam wrote:
only Hans can decide if this can/should be changed
I won't argue for any changes, just thought to ask about it.
I'll think about a workaround outside context.
The error is with the backend.
luatex (and pdftex and even tex) do not like filenames
Am 04.03.2011 um 18:59 schrieb Aditya Mahajan:
How do I disable TeX ligatures in MkII. The following does not work:
\starttext
\tttf\normalnoligatures\font
-- ---
\stoptext
% engine=pdftex
\usetypescript[modern][texnansi]
\setupbodyfont[modern]
\starttext
{\tt -- ---}
\stoptext
On Fri, 4 Mar 2011, Wolfgang Schuster wrote:
Am 04.03.2011 um 18:59 schrieb Aditya Mahajan:
How do I disable TeX ligatures in MkII. The following does not work:
\starttext
\tttf\normalnoligatures\font
-- ---
\stoptext
% engine=pdftex
\usetypescript[modern][texnansi]
\setupbodyfont
from the grey England..
Ian
It's a pdftex feature.
--
luigi
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg
for a given number of line for the next paragraph.
That is exactly what I want: keeping all my paragraphs together. But when I
use it in my file, I get a few lines pro page.
% engine=pdftex
\setupparagraphintro[each][\keeplinestogether{10}]
\starttext
\dorecurse{5}{\input tufte\par}
\stoptext
loading ConTeXt XML Macros / MathML Renderer
- /usr/share/texmf/tex/context/base/x-mathml.lua
resolversmodules loaded: 'calcmath'
(/usr/share/texmf/tex/context/base/x-calcmath.mkiv+ /usr/share/texmf/tex/context/base/x-calcmath.lua)){/usr/share/texmf/fonts/map/pdftex/context/mkiv
latin modern fonts are not preloaded
languageslanguage en is active
resolversmodules loaded: 'lilypond'
(C:/contextminimal/texmf-local/tex/context/third/lilypond/t-lilypond.tex
loading LilyPond module
){C:/contextminimal/texmf-context/fonts/map/pdftex/context/mkiv
version.
The published book is typeset in pdfTeX with ConTeXt MkII, with hz machinery
used, resulting in quite nicely balanced lines.
Those Google Docs are scanned (watch OCR mistakes!) and use horrible font
substitution.
Best example: Preface (=Vorwort), page 6, third paragraph, line 7: den
] node[description] {$*$} (m-2-2);
\stoptikzpicture
\stoptext
(compilation error at the bottom of this email)
I thought at first that this was a luatex problem, but I've ruled that
out with the following plain tex file, which compiles just fine in
plain luatex and in plain pdftex:
\input tikz.tex
engine, but the propagation of
uppercase to subheadings is also encountered.
indeed, inheritance
3) numbercolor=red only works with luatex.
mkii (for pdftex/xetex) will not be patched so mkiv is the (future)
reference in this
I submit the pdf's also.
Hans
the right manual yet or am too stupid to
understand what must be a relatively simple concept.
You can define multiple typefaces.
% engine=pdftex
% fonts
\definetypeface [mainface] [rm] [serif] [palatino][default]
\definetypeface [mainface] [ss] [sans] [iwona-heavy] [default]
\definetypeface
without changing the size of the text
font. I apparently haven't found the right manual yet or am too stupid to
understand what must be a relatively simple concept.
You can define multiple typefaces.
% engine=pdftex
% fonts
\definetypeface [mainface] [rm] [serif] [palatino][default
what must be a relatively simple concept.
You can define multiple typefaces.
% engine=pdftex
% fonts
\definetypeface [mainface] [rm] [serif] [palatino][default]
\definetypeface [mainface] [ss] [sans] [iwona-heavy] [default]
\definetypeface [mainface] [tt] [mono] [modern] [default
in the world. Many of the discussions I see are
started by people trying to use non-western/non-latin scripts.
Sure. Anyhow, I'm not going to spend time following discussions on the
pdftex and xetex list as I don't use these engines and context support
for them is frozen. If context users have
) and this is
why in mkii (pdftex variant) we always generated metrics a directly from
afm files.
The lm and gyre font projects are in fact triggered by people within the
context community as a solution to all these incomplete fonts that have
been used for ages. Fortunately these projects soon became generic
is in the main file with a \stoptext statement.
This works well with pdftex documents and also with
MKII documents. But it fails with MKIV documents. The Context
program will read and use an inserted program but will not return
to the main text stream in the file that did the inputting
In all forms of TeX it is my custom to start with a brief main file and
call the various components of the document into the input stream with
\input statements. The termination of the document is in the main file
with a \stoptext statement.
This works well with pdftex documents and also
well with pdftex documents and also with
MKII documents. But it fails with MKIV documents.
Con you provide a minimal example? This works fine:
\starttext
\input knuth
\stoptext
Aditya
___
If your question
well with pdftex documents and also with
MKII documents. But it fails with MKIV documents. The Context program
will read and use an inserted program but will not return to the main
text stream in the file that did the inputting. It just displays an *
and hangs. Are there new rules in MKIV about
pdftex, just pure mkiv
--
Peter
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage
to time
mkiv: no more mkii files, no more pdftex, just pure mkiv
this can already be done (just install with the --engine=luatex flag)
the main issue is that mtxrun also replaces the ruby texmfstart script
and texexec is launched via mtxrun; so mtxrun needs to be able to deal
with mkii situations
?
mkii: frozen, only some fixes from time to time
mkiv: no more mkii files, no more pdftex, just pure mkiv
this can already be done (just install with the --engine=luatex flag)
the main issue is that mtxrun also replaces the ruby texmfstart script and
texexec is launched via mtxrun; so mtxrun
2 completely different distributions?
mkii: frozen, only some fixes from time to time
mkiv: no more mkii files, no more pdftex, just pure mkiv
this can already be done (just install with the --engine=luatex flag)
the main issue is that mtxrun also replaces the ruby texmfstart script and
texexec
mkiv: no more mkii files, no more pdftex, just pure mkiv
Yes, I like this idea. I don't care about mkii, nor pdftex.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist
: frozen, only some fixes from time to time
mkiv: no more mkii files, no more pdftex, just pure mkiv
Yes, I like this idea. I don't care about mkii, nor pdftex.
In the first place, this idea was meant to make Hans' life easier.
(not the user's life... ;-)
--
Peter
there
Or perhaps 2 completely different distributions?
mkii: frozen, only some fixes from time to time
mkiv: no more mkii files, no more pdftex, just pure mkiv
Yes, I like this idea. I don't care about mkii, nor pdftex.
In the first place, this idea was meant to make Hans' life easier.
(not the user's
:
/Users/hans/TeX/ConTeXt/beta/tex/texmf-cache/luatex-cache/context/c180539b697aa06758debbc1182817e4/formats/cont-en.fmt
/Users/hans/TeX/ConTeXt/beta/tex/texmf-cache/luatex-cache/context/c180539b697aa06758debbc1182817e4/formats/cont-nl.fmt
/Users/hans/TeX/ConTeXt/beta/tex/texmf-osx-64/web2c/pdftex
completely different distributions?
mkii: frozen, only some fixes from time to time
mkiv: no more mkii files, no more pdftex, just pure mkiv
Yes, I like this idea. I don't care about mkii, nor pdftex.
In the first place, this idea was meant to make Hans' life easier.
(not the user's life
/Users/hans/TeX/ConTeXt/beta/tex/texmf-osx-64/web2c/pdftex/cont-en.fmt
/Users/hans/TeX/ConTeXt/beta/tex/texmf-osx-64/web2c/pdftex/cont-nl.fmt
/Users/hans/TeX/ConTeXt/beta/tex/texmf-osx-64/web2c/xetex/cont-en.fmt
/Users/hans/TeX/ConTeXt/beta/tex/texmf-osx-64/web2c/xetex/cont-nl.fmt
looks ok
On Tue, Feb 1, 2011 at 12:35 PM, Hans Hagen pra...@wxs.nl wrote:
On 1-2-2011 11:36, Vedran Miletić wrote:
Same here.
Running mktexlsr manually works, but it doesn't help next ./first-setup
run..
i'll have a look at it (i only tested a luatex only tree sofar)
seem related only to pdftex
On Tue, Feb 1, 2011 at 1:51 PM, luigi scarso luigi.sca...@gmail.com wrote:
i'll have a look at it (i only tested a luatex only tree sofar)
seem related only to pdftex and xetex.
luatex seems ok.
--
luigi
after
$mktexlsr
$texexec --make
builds all the pdftex formats
$texexec --make --engine
for a document, environment prevents also
multiple loading of the file when you use context’s document
structure.
Let me simplify the example:
---
\setupoutput[pdftex]
simplefonts is mkiv only, so remove this or don’t use simplefonts
and macros.tex looks like this:
\setupoutput[pdftex]
\definepapersize[bok][width=7.0in,height=10.0in]
%\setuppapersize[bok][letter]
\setuppapersize[bok][bok]
\setuplayout[location=middle,marking=on]%
\setupwhitespace[line]
\setuptyping[style=small]
Anyone else have this problem?
--
John Culleton
this:
\startenvironment macros
\setupoutput[pdftex]
\definepapersize[bok][width=7.0in,height=10.0in]
%\setuppapersize[bok][letter]
\setuppapersize[bok][bok]
\setuplayout[location=middle,marking=on]%
\setupwhitespace[line]
\setuptyping[style=small]
\stopenvironment
Anyone else have this problem
\input body.tex
\stoptext
and macros.tex looks like this:
\startenvironment macros
\setupoutput[pdftex]
\definepapersize[bok][width=7.0in,height=10.0in]
%\setuppapersize[bok][letter]
\setuppapersize[bok][bok]
\setuplayout[location=middle,marking=on]%
\setupwhitespace[line
of
the file when you use context’s document structure.
Let me simplify the example:
---
\setupoutput[pdftex]
simplefonts is mkiv only, so remove this or don’t use simplefonts
\definepapersize[bok][width=7.0in,height=10.0in]
\setuppapersize[bok
Hello,
This used to work with pdftex:
\starttext
\input \string|echo hello world
\stoptext
What's the recommended way, to do this in mkiv?
I've defined \Pipe{} like this:
\startluacode
userdata = userdata or {}
function userdata.pipe(c)
local h = io.popen(c)
context(h:read
echo.
echo You need to install Ruby first (if you want to use pdfTeX or XeTeX).
echo Fetching files anyway.
echo.
:okay
set OWNPATH=%~dp0
set CONTEXTROOT=%OWNPATH%tex
set PATH=%OWNPATH%bin;%CONTEXTPATH%\texmf-mswin\bin;%PATH%
set CYGWIN=nontsec
rsync -av --exclude 'rsync.exe' --exclude 'cygwin1
the attached first-setup-alt.bat).
Best regards,
Lukas@echo off
setlocal
echo okay ok.log
ruby -e File.delete('ok.log')
if not exist ok.log goto okay
echo.
echo You need to install Ruby first (if you want to use pdfTeX or XeTeX).
echo Fetching files anyway.
echo.
:okay
set OWNPATH=%~dp0
set
/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
systems : begin file prova.tex at line 5
! Math error: parameter \Umathquad\displaystyle is not set.
\mathematics ...rmalstartimath #1\normalstopimath
\fi
\dodosymbol ...bol
/usr/context/tex/texmf-context/tex/context/base/type-otf.mkiv){/home/melmoth/usr/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
systems : begin file prova.tex at line 4
! Math error: parameter \Umathquad\displaystyle is not set.
l.5 $ABC \bullet \star
On Wed, Jan 12, 2011 at 6:12 PM, Mojca Miklavec
mojca.miklavec.li...@gmail.com wrote:
2011/1/12 Michal Kvasnička prgo...@gmail.com:
Hallo.
I tried mtxrun --script mptopdf chart08.1 but I've got the following error.
This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010)
\write18 enabled
601 - 700 of 3678 matches
Mail list logo
