ifferent page breaks. I
>>> experienced
>>> around 2-5 pages difference in a 100 page document.
>>
>> The interlinespace in MkII and MkIV is the same and both use a distance
>> of 2.8ex between the lines.
>
> Yes, but ex means different dimensions in pdf
fails?
Thanks a lot,
Xan.
PS: I attach too running.txt that outputs the texexec.
% interface=en output=pdftex
% Regime
\enableregime[utf]
% Choose a font
%\usetypescript [palatino][\defaultencoding]
\setupbodyfont [palatino,12pt]
% Be tolerant with paragraph building
\setuptolerance [horizontal,
MkII and MkIV is the same and both use a distance
> of 2.8ex between the lines.
Yes, but ex means different dimensions in pdftex and luatex. For example
\starttext
1ex = \the\dimexpr1ex\relax \crlf
2.8ex = \the\dimexpr2.8ex\relax
\stoptext
gives in MKII
1ex = 5.16667pt
2.8ex = 14.46669pt
and
arted their talk about TeX Gyre by screaming "Full
> >> compatibility means no progress!" at the audience :-)
> >
> > I know that, I read some of the GUST people papers;). I thought,
> > however, that it wouldn't influence my documents *so much*;).
&g
w that, I read some of the GUST people papers;). I thought,
> however, that it wouldn't influence my documents *so much*;).
LuaTeX did not always behave like pdfTeX and if you want the same result
in your document as in the past, don't switch. The
e document.
>
> The interlinespace in MkII and MkIV is the same and both use a distance
> of 2.8ex between the lines. One difference between the two engines are
> the used fonts, pdfTeX use type 1 fonts and luaTeX MkIV opentype fonts.
Thank you for your prompt answers. I am a bit surpr
> interline
> space from the font. So, you will get different page breaks. I
> experienced
> around 2-5 pages difference in a 100 page document.
The interlinespace in MkII and MkIV is the same and both use a distance
of 2.8ex between the lines. One difference between the two engines
/tex/texmf-context/fonts/map/
pdftex/context/original-public-lm.map}
! Missing } inserted.
}
\unvbox
\doplacenoteinserts ...ing \unvcopy \else \unvbox
\fi
\currentnoteins \fi \s...
\next3 ...oprocessnotes
support the pdftex-style map format
* mkiv now has support for 'special' features like knockout vs
overprint and spot colors via attributes
For pdftex users, there are not that many changes, but users of
xetex of luatex are advised to update a.s.a.p.
The wiki page is here
On Wed, Oct 29 2008, Tobias Burnus wrote:
> I have a scenario which fails with the current mechanism - even if
> following the sym links worked. Assume that a user only puts a texmf.cnf
> under "$HOME/texmf/web2c/texmf.cnf". That file will be used by "luatex",
> &
f/web2c/texmf.cnf". That file will be used by "luatex",
> "pdftex" etc. but "luatools" will still resolve
> /usr/share/texmf/.../luatools.lua if it follows $SELF.
well, users can always force a file
if there is logic we can try to follow it, if there is hard c
er checks
> "$HOME/texmf/web2c" where a user could have put his file. For pdftex
> $HOME/texmf/web2c has a higher precedence than /usr/share/texmf/web2c. I
> assume that the same thing is true for "luatex". In any case the luatex
> binary contains the following string:
"luatools") there is no problem as
>> luatex uses the compile-time path and finds the texmfcnf file.
>>
> hm, but since luatools is ran using texlus (which is luatex) the same
> should apply
>
I think the algorithm used to find the texmf.cnf file is diffe
Tobias Burnus wrote:
> c) Werner asks: Why is the KPSE library not used?
>
I have a scenario which fails with the current mechanism - even if
following the sym links worked. Assume that a user only puts a texmf.cnf
under "$HOME/texmf/web2c/texmf.cnf". That file will be used by &
fonts : resetting map file list
{/Volumes/Data/Users/mjg14747/Applications/context/tex/texmf-context/
fonts/map/pdftex/context/original-empty.map}
fonts : using map file: original-base
{/Volumes/Data/Users/mjg14747/Applications/context/tex/texmf-context/
fonts/map/pdftex/context/ori
8, at 1:28 PM, Wolfgang Schuster wrote:
[…]
Why don't you use TeXworks, it already comes with the right
settings for pdfTeX, XeTeX and LuaTeX.
Wolfgang
___
If your question is of interest to others as well
an error message:
>>
>> MtxRun | unknown script 'context.lua' or 'mtx-context.lua'
>>
>> My interpretation is, that underway the path to the lua scripts is
>> 'forgotten'
>>
>> Kind regards
>>
lua scripts is
>> 'forgotten'
>>
>> Kind regards
>>
>> Willi
>
> Why don't you use TeXworks, it already comes with the right
> settings for pdfTeX, XeTeX and LuaTeX.
>
> Wolfgang
>
;
> MtxRun | unknown script 'context.lua' or 'mtx-context.lua'
>
> My interpretation is, that underway the path to the lua scripts is
> 'forgotten'
>
> Kind regards
>
> Willi
Why don't you use TeXw
>> Original Tex is not an option, since PDF, today's font formats
>> (and Unicode) and many algorithms didn't exist when Knuth decided
>> no features would be added anymore. Maybe I should hack the source
>> code of pdftex or luatex? I can try that, but that'
>>>> Original Tex is not an option, since PDF, today's font
>>>> formats (and Unicode) and many algorithms didn't exist when
>>>> Knuth decided no features would be added anymore. Maybe I
>>>> should hack the source code of pdftex o
Mauricio wrote:
>> Mauricio wrote:
>>
>>> Original Tex is not an option, since PDF, today's font formats
>>> (and Unicode) and many algorithms didn't exist when Knuth decided
>>> no features would be added anymore. Maybe I should hack the source
&
Hi,
On Tue, 21 Oct 2008 07:14:50 -0600, Mauricio <[EMAIL PROTECTED]>
wrote:
> Original Tex is not an option, since PDF, today's font formats
> (and Unicode) and many algorithms didn't exist when Knuth decided
> no features would be added anymore. Maybe I should hack th
> Mauricio wrote:
>
>> Original Tex is not an option, since PDF, today's font formats
>> (and Unicode) and many algorithms didn't exist when Knuth decided
>> no features would be added anymore. Maybe I should hack the source
>> code of pdftex or luatex?
Mauricio wrote:
> Original Tex is not an option, since PDF, today's font formats
> (and Unicode) and many algorithms didn't exist when Knuth decided
> no features would be added anymore. Maybe I should hack the source
> code of pdftex or luatex? I can try that, but that
d my habilities.
Original Tex is not an option, since PDF, today's font formats
(and Unicode) and many algorithms didn't exist when Knuth decided
no features would be added anymore. Maybe I should hack the source
code of pdftex or luatex? I can try that, but that's going to be
hard wor
the same
> size. There is no size variation with \tfa, \tfb, etc. If I remove
> all the \ss commands then the sizing works again.
As an extra data point, I see this in the texexec log:
pdftex (file ec-urw-palatino.map): cannot open font map file
>
>
> I'm using MacTeX 2008.
arttext
>
> \startMPcode
> path p ; p := unitsquare xyscaled (5cm,5cm) ;
>
> linear_shade(p,1,red, blue) ;
> \stopMPcode
>
> \stoptext
>
> This runs fine with pdftex and luatex, but with xetex I get
>
> ! Undefined control sequen
: 12pt rm is loaded
specials : pdftex loaded
system : test.top loaded
(test.top) (test.tuo) (test.tuo)
systems: begin file test at line 1
(foo.tex
! LuaTeX error r:/tex/texmf-context/tex/context/base/core-buf.lua:63:
attempt to call method 'sub' (a nil value
ll be gone
>
> Hans
>
hmmm
Beginning to dump on file cont-nl.fmt
(format=cont-nl 2008.10.17)
41100 strings of total length 689878
500860 memory locations dumped; current usage is 188&493721
39395 multiletter control sequences
\font\nullfont=nullfont
0 preloaded fonts
0 words of pdfTeX
f any other components
are critical as well (I did not hear about any "too new version"
problem until now), maybe one needs to ask Akira about splitting those
libraries as well.
Metapost is part of the "big package" with all the possible binaries
(includ
On Mon, Oct 13, 2008 at 3:43 PM, Tobias Burnus <[EMAIL PROTECTED]> wrote:
> Hello,
>
> using
>
> \enableregime[utf]
> \starttext
> Σ, σ or ς?
> \stoptext
>
> with pdftex prints "Σ, σ or σ?" (but the latter should be a \varsigma
> and not a \
Hi,
linear shading in MP does not work with xetex. Consider
\setupcolors[state=start]
\starttext
\startMPcode
path p ; p := unitsquare xyscaled (5cm,5cm) ;
linear_shade(p,1,red, blue) ;
\stopMPcode
\stoptext
This runs fine with pdftex and luatex, but with xetex I get
! Undefined
On Mon, 13 Oct 2008, Tobias Burnus wrote:
Hello,
using
\enableregime[utf]
\starttext
Σ, σ or ς?
\stoptext
with pdftex prints "Σ, σ or σ?" (but the latter should be a \varsigma
and not a \sigma). And with LuaTeX the result is even "Σ, or ?", i.e.
the small sigmas disapp
Hello,
using
\enableregime[utf]
\starttext
Σ, σ or ς?
\stoptext
with pdftex prints "Σ, σ or σ?" (but the latter should be a \varsigma
and not a \sigma). And with LuaTeX the result is even "Σ, or ?", i.e.
the small sigmas disappear completely.
Can this be fixed, even though
2008/10/12 Hans Hagen <[EMAIL PROTECTED]>:
> Olivier Guéry wrote:
>> Hello,
>>
>> I tried to put logo on my pages.
>> I got an undefine control sequence with luatex.
>> This small exemple look to run fine with pdftex but not luatex in context
>>
Olivier Guéry wrote:
> Hello,
>
> I tried to put logo on my pages.
> I got an undefine control sequence with luatex.
> This small exemple look to run fine with pdftex but not luatex in context
> live.
>
> \definelogo[mypic][bottom][left]
> [state=start,c
Hello,
I tried to put logo on my pages.
I got an undefine control sequence with luatex.
This small exemple look to run fine with pdftex but not luatex in context live.
\definelogo[mypic][bottom][left]
[state=start,command={\externalfigure[pic]}]
\placelogos[mypic]
\starttext
Hello world
omparable to texmf.cnf. This
are stored in \miktex\config.
If you move .ini-files of the second sort to a place where e.g. pdftex
looks for .ini-file of the first sort you can get very bewildering error
messages. And as it is easy to confuse the files one should always check
the
>> will still not build in Miktext2.7->Settings->Format cont-en.pdftex.
>>
>> Creating the cont-en.pdftex format file...
>> Running pdftex...
>> This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (INITEX)
>>
>> entering extended mode
>>
>>
> Creating the cont-en.pdftex format file...
> Running pdftex...
> This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (INITEX)
>
> entering extended mode
>
> ("C:\Program Files\MiKTeX 2.7\tex\context\config\cont-en.ini")
>
> ! Emergency stop.
>
> &l
Am Thu, 2 Oct 2008 23:57:40 +0200 schrieb Mojca Miklavec:
>> makefmt: pdftex failed on cont-en.ini.
>> initexmf.EXE: The operation failed for some reason.
>
> I got that one lots of time as well, but no idea why.
It simply means that a format generation didn't work. If
t; something or other.
(I guess that I'm reading mail in the wrong order.)
Interesting ... On my installation (well, some random computer in a
lab) the context format was not there at all.
> I tried adding a new format, calling it cont-en, compiler pdftex, and input
> filename cont-
ed the filename database, but the formats will still not
> build in Miktext2.7->Settings->Format cont-en.pdftex.
>
> Creating the cont-en.pdftex format file...
> Running pdftex...
> This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (INITEX)
>
> entering extended mo
rmat cont-en.pdftex.
Creating the cont-en.pdftex format file...
Running pdftex...
This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (INITEX)
entering extended mode
("C:\Program Files\MiKTeX 2.7\tex\context\config\cont-en.ini")
! Emergency stop.
<*> cont-en.ini
Mojca,
I tried running Miktex2.7->Settings->Formats, selecting cont-en.pdftex, then
tried changing input filename from cont-en.ini to cont-en.tex, but I was "not
allowed to change built-in" something or other.
I tried adding a new format, calling it cont-en, compiler p
-pdftrim trim pages from file(s)
>> TeXExec | --process process file
>> TeXExec |
>> TeXExec | --help --all shows all switches
>>
>> However, I cannot make the formats. Going to Miktex 2.7->Settings-
>>> Formats, attempting to build cont-en resul
>> $ C:\temp>texmfstart texexec --help
>> TeXExec | version 6.2.0 - 1997-2006 - PRAGMA ADE/POD
>>
>> However, I cannot make the formats. Going to Miktex 2.7->Settings-
>> >Formats, attempting to build cont-en results in, even though I've
>> copi
Mojca,
When I try to build cont-en, using the settings you proposed from Context
Garden, I get:
Creating the cont-en.pdftex format file...
Running pdftex...
This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (INITEX)
entering extended mode
("C:\Program Files\MiKTeX 2.7\tex\context\c
t
> it's about spaces in filenames, but need to try it out.
Since mptopdf works for me, it isn't about spaces. It looks like the
mptopdf program could be better replaced by another simple script:
Try:
C:\Testing>pdftex "&mptopdf" \processMPfile{example.1}
This is pd
xmfstart texexec --help
> TeXExec | version 6.2.0 - 1997-2006 - PRAGMA ADE/POD
>
> However, I cannot make the formats. Going to Miktex 2.7->Settings->Formats,
> attempting to build cont-en results in, even though I've copied cont-en.ini
> into the directory expected by
le(s)
> TeXExec | --process process file
> TeXExec |
> TeXExec | --help --all shows all switches
>
> However, I cannot make the formats. Going to Miktex 2.7->Settings-
> >Formats, attempting to build cont-en results in, even though I've
> copied cont-en.ini
cont-en results in, even though I've copied cont-en.ini
into the directory expected by Miktex 2.7.
Creating the cont-en.pdftex format file...
Running pdftex...
This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (INITEX)
entering extended mode
("C:\Program Files\MiKTeX 2.7\t
Miklavec wrote:
> I got ConTeXt working on this machine, but mptopdf indeed seems to
> be broken.
>
> c:\Documents and Settings\Uporabnik\My Documents\test>mp example
> (example.mpCreating example.mpx...
> This is pdfTeX, Version 3.1415926-1.40.9 (MiKTeX 2.7)
> ent
I got ConTeXt working on this machine, but mptopdf indeed seems to be broken.
c:\Documents and Settings\Uporabnik\My Documents\test>mp example
(example.mpCreating example.mpx...
This is pdfTeX, Version 3.1415926-1.40.9 (MiKTeX 2.7)
entering extended mode
(C:/DOCUME~1/UPORAB~1/LOCALS~1/T
d.
I wanted to recompile the binaries right away, but svn up on the
server just returned me
svn: In directory 'bin/tex/linux-64/current/pdftex/bin'
svn: Can't copy
'bin/tex/linux-64/current/pdftex/bin/.svn/tmp/text-base/pdftex.svn-base'
to 'bin/tex/linux-64/curre
setgvalue {\??id #1\??id #2}
>> {\dodostopregister
>> [#1][#3...
>> l.5 ...rtregister[index][umlautä]{Umlaute&– ä}
>>
>> ?
>>
>>
>>
>> UTF in maintext but not in index-marks ...
>>
>
;
>
>
> UTF in maintext but not in index-marks ...
>
> What can be done now (besides re-writting the document)?
\startregister[index][umlautae]{...}
...
\stopregister[index][umlautae]
You could use umlauts in macro names only with XeTeX and LuaTeX
but not with pdfTeX.
Wolfgang
ile found
>> TeXExec | tex processing method: context
>> TeXExec | TeX run 1
>> TeXExec | writing option file firstfile.top
>> TeXExec | using randomseed 1382
>> TeXExec | tex engine: pdftex
>> TeXExec | tex format: cont-en
>> This is pdfTeXk, Version 3.1
/razzle/
> firstfile.tex'
> TeXExec | no ctx file found
> TeXExec | tex processing method: context
> TeXExec | TeX run 1
> TeXExec | writing option file firstfile.top
> TeXExec | using randomseed 1382
> TeXExec | tex engine: pdftex
> TeXExec | tex format: cont-en
> T
op
TeXExec | using randomseed 1382
TeXExec | tex engine: pdftex
TeXExec | tex format: cont-en
This is pdfTeXk, Version 3.1415926-1.40.9 (Web2C 7.5.7)
%&-line parsing enabled.
(/usr/local/texlive/2008/texmf/web2c/natural.tcx)
entering extended mode
(/Users/tom/Desktop/stuff/razzle/firstfile.tex
John Culleton wrote:
>>>
>>> \pdfobjcompresslevel=0
>>> or
>>> \pdfminorversion=4
>
> It turns out that the OP was using Acrobat 5, so it all fits together.
>
> Does the same command work with plain pdftex?
It should, both co
hostscript nor in my code.
> >
> > I am fairly certain the bug will also go away if you start your
> > new context documents with
> >
> > \pdfobjcompresslevel=0
> > or
> > \pdfminorversion=4
It turns out that the OP was using Acrobat 5, s
tex. It is due to using
> {style=\switchtobodyfont[tt]} in the table setup. Using [modern,tt]
> works fine, but this is not necessary with MkII.
Use style=mono.
> 4. This is a MkII issue (or maybe it is a pdftex problem?) MkII on
> 2007, texexec --dvi on 2008, and MkIV all w
in my code.
Unfortunatly, I'm not sure about this.
During these years I have discover bugs in pdftex/luatex but also in
ghostoscript too;
really, it seems that I have found another one this week in gs 8.63, but
not in gs8.62
pdf spec. gs, luatex/context mkiv are moving target;
three year ago t
r.tex). A working alternative is
commented in that file.
3. MkIV will not typeset the file test.tex. It is due to using
{style=\switchtobodyfont[tt]} in the table setup. Using [modern,tt]
works fine, but this is not necessary with MkII.
4. This is a MkII issue (or maybe it is a pdft
evious version of Context I have also fails this test:
ConTeXt ver: 2007.01.12 15:56 MKII fmt: 2007.9.26 int:
english/english
My test file at the moment is:
\setupoutput[pdftex]
\starttext
foo
\stoptext
I am testing on LInux Slackware 12.
Perhaps Hans or Thanh would care to comment.
--
version of the file, dating back to February, also
blows up.
The preamble to the file plus dummy text looks like this:
\setupoutput[pdftex]
\setupindenting[none]
\setupwhitespace[medium]
\frenchspacing
\setupcolors[state=start]
\setuphead[chapter][head=nomarking
nd\em\/}
>>>> Try this:
>>>>
>>>> \define\Colorit%
>>>> {\groupedcommand{\color[blue]\em}\/}
>>>
>>> tried it ... but still no hyphenation!
>> You are running pdftex, 'cause it worked fine in mkiv :-)
>>
>> \def\Co
gt;>> \define\Colorit%
>>> {\groupedcommand{\color[blue]\em}\/}
>>
>>
>> tried it ... but still no hyphenation!
>
> You are running pdftex, 'cause it worked fine in mkiv :-)
>
> \def\Colorit%
> {\groupedcommand{\color[red]\em\penalty1\hskip0
Steffen Wolfrum wrote:
> Am 24.09.2008 um 10:39 schrieb Taco Hoekwater:
>
>>
>> Steffen Wolfrum wrote:
>>> \def\Textit%
>>> {\groupedcommand\em\/}
>> Try this:
>>
>> \define\Colorit%
>> {\groupedcommand{\color[blue]\em}\/}
>
>
Hi!
Nobody an idea?
Cheers,
Eyke
2008/9/22 holzminister <[EMAIL PROTECTED]>:
> Hi,
>
> it's me again. :)
>
> Why can I only click the green dots left of the words but not the
> words themself? (Tested with luatex an pdftex.)
>
>>>>
> \setupcolo
Hi,
it's me again. :)
Why can I only click the green dots left of the words but not the
words themself? (Tested with luatex an pdftex.)
>>>
\setupcolors
[state=start]
\setupinteraction
[state=start]
\setuplist
[subsection]
[interaction=all,
while "\Nano" and "\Milli" works fine.
"$\mu$" works, so it doesn't look like a font problem.
The following code works with pdftex/MarkII, but fails under Luatex
0.29beta/MarkIV.
\usemodule[units]
\starttext Hello world! $1\Micro\Meter$ $1\Micro\Second$
\stoptext
quot;\Milli" works fine.
> "$\mu$" works, so it doesn't look like a font problem.
> The following code works with pdftex/MarkII, but fails under Luatex
> 0.29beta/MarkIV.
>
> \usemodule[units]
> \starttext Hello world! $1\Micro\Met
t;>
>>>> \stoptext
>>> run ok here, but the question is .. what exactly do you expect to see
>>>
>> to be exact: some orange text :)
>
> can you check if the current beta is more in sync with pdftex?
>
orange text *AND* 'OVP 1' mode :)
t
> 2. I don't get an error when I compile with mkii. Here's the log of the
> > succesfull compile; http://pastebin.com/m2c98019d.
>
> Works here (ConTeXt - 2008.09.10 14:01, pdfTeX-1.40.9, luaTeX-0.28.0)
> both with mkii and mkiv.
>
> Jano
>
Still doesn&#
estion is .. what exactly do you expect to see
>>
>
> to be exact: some orange text :)
can you check if the current beta is more in sync with pdftex?
-
Hans Hagen | PRAGMA
og of the
> succesfull compile; http://pastebin.com/m2c98019d.
Works here (ConTeXt - 2008.09.10 14:01, pdfTeX-1.40.9, luaTeX-0.28.0)
both with mkii and mkiv.
Jano
___
If your question is of interest to others as
ist
{C:/context/tex/texmf-context/fonts/map/pdftex/context/original-empty.map}
fonts : using map file: original-base
{C:/context/tex/texmf-context/fonts/map/pdftex/context/original-base.map}
fonts : using map file: lm-math
{C:/context/tex/texmf/fonts/map/dvips/lm/lm-math.map}
fonts
xact: some orange text :)
Acrobat8 menu 'Advanced'-->'Print Production'-->'Output Preview...'
[Output Preview Window]
- select 'Color Warnings' entry in the 'Preview' listbox
- check the now visible 'Show Overprinting' checkbox
No
I usually compose short documents (paper, homework, report etc.) which
usually runs 8-10 pages.
There will be considerable difference between traditional TeX (CJK for
LaTeX, or pdftex MKII using subfonts) and MKIV.
That means, every MKIV Chinese document I compile will spend 10
seconds loading the
On Sat, Sep 13 2008, Alan Stone wrote:
> All give a black&white output, except the rgb (somecolor): and
> (somecolor)*: ones
No problem here. Versions:
[EMAIL PROTECTED]:~> context --version
MtxRun | current version: 2008.09.10 14:01
[EMAIL PROTECTED]:~> pdftex --version
Am 13.09.2008 um 18:53 schrieb Willi Egger:
> Hi Guru's
>
> In the pdftex environment the enclosed file will result in an
> address-label on position 8 from the top on a sheet with 14 labels.
>
> When compiling this file with LuaTeX, then the label is placed
> s
Hi Guru's
In the pdftex environment the enclosed file will result in an address-
label on position 8 from the top on a sheet with 14 labels.
When compiling this file with LuaTeX, then the label is placed
somewhere down left and the dimensions are messed up.
I am stummied...
Curren
o many things in lua ...
it's the price of flexibility and opening up
(3) although we do our best to speed up luatex and mkiv as much as
possible it's not our intention to compete in speed with pdftex (only
type 1, frozen funtionality, etc) and xetex (depencency of libraries,
closed
I'm not sure whether this might be a problem with
> my editor WinEdt, but I'm sure you can show me the
> right direction.
>
> Regards,
>
> Jürgen
>
>
> % language=de tex=pdfetex output=pdftex
> \usetypescript[modern]
> \mainlanguage[de]
> \enableregime[
the
right direction.
Regards,
Jürgen
% language=de tex=pdfetex output=pdftex
\usetypescript[modern]
\mainlanguage[de]
\enableregime[utf]
\setupencoding[texnansi]
\starttext
äöüß ÄÖÜ
\stoptext
___
If your question is
> Wolfgang Schuster wrote:
> How old is your TeX installation, the name of the binary is now pdftex
> and no longer pdfetex
Seems to be somewhat older since pdftex is not known as executable.
He says pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2c 7.5.2)
(I'm hopefully waiting f
Am 2008-09-08 um 15:32 schrieb Wolfgang Schuster:
> How old is your TeX installation, the name of the binary is now pdftex
> and no longer pdfetex
>
>> \language[de]
>
> Use \mainlanguage[de], \language is just for local switches.
And please read http://wiki.contextgarden.ne
gt; version (as can be seen in the 'Contents'-title of the
> TOC).
>
> % language=de tex=pdfetex output=pdftex
How old is your TeX installation, the name of the binary is now pdftex
and no longer pdfetex
> \language[de]
Use \mainlanguage[de], \language is just for local s
Hi,
Doing my first steps with ConTeXt (after about ten years
experience with LaTeX) I was running into the following
problem.
Running the enclosed example I got still the english
version (as can be seen in the 'Contents'-title of the
TOC).
% language=de tex=pdfetex output=pdftex
\l
linux/ minimals/current/bin/context/linux/
minimals/current/bin/metapost/linux/
minimals/current/bin/pdftex/linux/ minimals/current/bin/man/'
'/home/yue/context/tex/texmf-linux'
run | rsync -rpztlv --stats
contextgarden.net::'minimals/current/bin/common/linux/
minimals/current/bi
On Sun, Sep 7, 2008 at 6:33 AM, Yue Wang wrote:
> btw, I think Windows users are not command line experts. I think the
> minimal installer can add more options.
> for example, which distribution to choose (MKIV or XeTeX or pdfTeX),
Isn't that available already? (No windows to t
btw, I think Windows users are not command line experts. I think the
minimal installer can add more options.
for example, which distribution to choose (MKIV or XeTeX or pdfTeX),
which fonts to be download (TeXGyre, Kurier, Iwona...) according to
the distribution (in MKIV and XeTeX, download otf
n the edit query.
> The previous method was assuming that TeX boxes do not overlap,
> which is reasonable for LaTeX but not for ConTeXt.
> This assumption is no longer considered.
>
> Once Martin and Jonathan fix pdfTeX & XeTeX sources, you'll have a
> chance to ex
I am trying to process a file using the ConTeXt minimals and MK II
that now complains:
.
.
.
{/Users/alancbowen/Library/texmf/fonts/map/pdftex/context/tasgreek.map}
! Argument of \next has an extra }.
\par
}
...{,\CCC:4:124 \CCC:4:126 \CCC:4:124
in the latest TeXShop there is
>> Added support for SyncTeX. SyncTeX is new synchronization technology by
>> Jerome Laurens which is included in TeX Live 2008 (but not earlier TeX
>> distributions). The technology is built directly into pdfTeX and XeTeX. In
>> modern TeX distr
Hi all,
"\Micro" in the "units" module failed, while "\Nano" and "\Milli" works fine.
"$\mu$" works, so it doesn't look like a font problem.
The following code works with pdftex/MarkII, but fails under Luatex
0.29beta/MarkIV.
\usemodule[
his in one of the last line when you generate
>>> the format).
>>
>> The generation saves the files to
>> C:/texlive/2008/texmf-var/web2c/pdftex/*.fmt
>> and kpsewhich cont-de.fmt gives no out
1501 - 1600 of 4105 matches
Mail list logo
