Re: [NTG-context] xetext-pdftex differences
Steffen Wolfrum wrote:
> On Wed, 11 Apr 2007 17:44:18 +0200, Mojca Miklavec wrote:
>
>> You should try to get "uc" working if possible, but you need to add
>> some definitions from my previous mail. If you want to stick with
>> texnansi, you should better use pdfTeX.
>>
>
> I have a document with German as the main language, defined ...
>
> \usetypescriptfile[type-gyr]
> \usetypescript[times][texnansi]
> \mainlanguage[de]
> \setupbodyfont[times,10pt]
>
> and inserted Arabic quotes in Arabic AlBayan.ttf, defined ...
>
> \font\geeza="AlBayan" at 10pt
>
>
> That's why it's typeset with XeTeX. But nevertheless texnansi for
> TeXGyreTermes seems to be fine (at least for now).
>
technically one can define a virtual font which uses TeXGyreTermes as base, but
has additional glyphs taken from AlBayan; I do have experimental code for that
but have to cook up an interface (not that hard, i only need time and
motivation); that way you dont't need to switch to geeza in between
\ctxlua {
fonts.define.methods.install("weird", {
{ "include-method", "base" } ,
{ "copy-char" , "lmroman10-regular" , 65, 66 } , {
"copy-range", "lmsans10-regular" , 0x0100, 0x01FF } ,
{ "copy-range", "lmtypewriter10-regular", 0x0200, 0xFF00 } ,
{ "fallback-range", "lmtypewriter10-regular", 0x, 0x0200 }
})
}
\starttext
\startTEXpage
[EMAIL PROTECTED]
\test \eacute \rcaron \adoublegrave \char"0200
AB\char65\char65
\stopTEXpage
Along these lines ... but then properly interfaced -)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] xetext-pdftex differences
Steffen Wolfrum wrote: > On Wed, 11 Apr 2007 19:22:39 +0200, Hans Hagen wrote: > > >> luatex itself has still the pdftex machinery around, so you can use map >> files to handle things when you use for instance type one fonts. >> > > > Does this mean for document with different fonts > I will be able to use my good old mapfiles like > > pads8r AGaramond-Semibold "TeXBase1Encoding ReEncodeFont" <8r.enc > > > and also an opentype fonts like > > DecoTypeNaskh.ttf > > together in one ConTeXt document, typeset with luatex? > indeed - pads8r is a rather dump tfm file, so that goes through the normal tex machinery - DecoTypeNaskh.ttf is an open type font and can be used directly \definefont[whatever][DecoTypeNaskh] should be enough Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] xetext-pdftex differences
On Wed, 11 Apr 2007 17:44:18 +0200, Mojca Miklavec wrote: > You should try to get "uc" working if possible, but you need to add > some definitions from my previous mail. If you want to stick with > texnansi, you should better use pdfTeX. I have a document with German as the main language, defined ... \usetypescriptfile[type-gyr] \usetypescript[times][texnansi] \mainlanguage[de] \setupbodyfont[times,10pt] ... and inserted Arabic quotes in Arabic AlBayan.ttf, defined ... \font\geeza="AlBayan" at 10pt That's why it's typeset with XeTeX. But nevertheless texnansi for TeXGyreTermes seems to be fine (at least for now). Thank you, Steffen ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] xetext-pdftex differences
On Wed, 11 Apr 2007 19:22:39 +0200, Hans Hagen wrote: > luatex itself has still the pdftex machinery around, so you can use map > files to handle things when you use for instance type one fonts. Does this mean for document with different fonts I will be able to use my good old mapfiles like pads8r AGaramond-Semibold "TeXBase1Encoding ReEncodeFont" <8r.enc http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] xetext-pdftex differences
Mojca Miklavec wrote: > LuaTeX will probably support those old encodings, but you would want > to use "uc" (unicode) encoding for both engines, otherwise it makes no > sense to use XeTeX instead of pdfTeX at all. > luatex itself has still the pdftex machinery around, so you can use map files to handle things when you use for instance type one fonts. ttf and otf are supported as wide fonts, but of course one needs to make sure that the unicode to glyph mapping is ok in context mkiv i will intercept the encoding-prefixed fonts (texnansi-mojca-regular) so this is transparent for users by using some lua glue code but mainly because i read afm files instead of tfm files (so, texnansi-mojca will in fact use mojca.afm); non prefixed names will use the tfm file (this is pretty safe because the texnansi-* names were only there when proper afm files are also there; i mainly provide this features for existing typescripts) in general, encodings are not something to worry about not even uc as encoding is needed in mkiv > All of your questions mentioned here belong to the ConTeXt mailing > list (XeTeX mailing list is mostly for XeLaTeX and low-level XeTeX > discussions) since it's really about the ConTeXt user-interface. The > only thing you could ask for on the XeTeX list is the question of > supporting ec/texnansi-encoded fonts (I prefer to wait for luaTeX than > to bother about those "soon-to-become-obsolete" additions). > indeed, there is no need to mess up xetex with obsolete encoding stuff; luatex will still have much pdftex code around so there the penalty is less, but eventually users have to move on Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] xetext-pdftex differences
On 4/11/07, Steffen Wolfrum <[EMAIL PROTECTED]> wrote:
> Moica, thanks for your detailed support!
>
> On Tue, 10 Apr 2007 21:27:47 +0200, Mojca Miklavec wrote:
> >> Where do I go when I experience differences between context/pdftext
> >> and context/xetex?
> >
> > What do you mean?
>
> these:
>
> >> For example with context/xetex I get ...
> >>
> >> ! Undefined control sequence.
> >> \stopframedtext ->\dostopframedtext
> >
> ...
> >> ... and I do get "SS" instead of eszett ("ß") with the following:
> >
> > Interesting effect ... (as if the encoding was unknown)
>
>
> I have to admit that it I never understood which encoding to use when
Me neither. Until I figured out that some of my letters were missing
in texnansi. texnansi & ec are 8-bit encodings used by "old" TeX
(pdfTeX) and only support 256 different characters. (you need to use a
different encodings for greek, cyrillic, vietnamese, ...)
The main problem is that XeTeX is not really backward compatible in
that respect: old fonts don't work since XeTeX thinks that the glyphs
are unicode-encoded, but they're in ec/texnansi/whatever other
encoding. If it nevertheless works, that is by a pure coincidence
(when you only need English letters ...).
In case that you would want to get the old fonts working with XeTeX,
you need to ask Jonathan. He said that it might be implemented, but
it's not really high on the priority list (it's just a problem during
transition state when 8'bit fonts still dominate in the TeX world).
LuaTeX will probably support those old encodings, but you would want
to use "uc" (unicode) encoding for both engines, otherwise it makes no
sense to use XeTeX instead of pdfTeX at all.
> if, for example, I just write english/german/french then I could also use
> texnansi, this works perfect :
>
> \usetypescriptfile[type-gyr]
> \usetypescript[times][texnansi]
> \mainlanguage[de]
> \enableregime[utf]
>
> \setupbodyfont[times,9pt]
That's because texnansi is based on "ansi" in the upper half of the
table and unicode is "by accident" the same in that area. So it's
really "coincedence" that it works. You should not use it that way
unless you have no better choice.
> > Which version of ConTeXt? It works OK here with 2007.03.22, but I need
> > to try the new beta. In principle this should not happen, it's
> > probably a bug or some other local problem.
>
> it is version 2007.01.12 (didn't you recommend to stay with the january
> version?)
It depends on what you want to do. The current version is indeed not
stable in that respect.
>
> >> Whom to tell this?
> >
> > Mailing list is the perfect place.
>
>
> I was wondering whether the xetex or the context list is better as it is a
> mixed xetex/context-topic
> and for Adam is in "paternity leave" I had no idea on which list someone
> continues.
All of your questions mentioned here belong to the ConTeXt mailing
list (XeTeX mailing list is mostly for XeLaTeX and low-level XeTeX
discussions) since it's really about the ConTeXt user-interface. The
only thing you could ask for on the XeTeX list is the question of
supporting ec/texnansi-encoded fonts (I prefer to wait for luaTeX than
to bother about those "soon-to-become-obsolete" additions).
>
> > At the beginning I had problems with XeTeX as well since Times
> > resolved to 'Times Roman:mapping=tex-text', which resolved to the name
> > 'mapping=tex-text' (a side effect of recent that should probably be
> > fixed somehow in the near future), but that problem disappeared later.
> > I had to temporary fix this (leftovers before TeXGyre family managed
> > to overload everything perhaps?):
>
>
> right, "Times Roman:mapping=tex-text": This also happened to me when using ...
>
> \usetypescriptfile[type-gyr]
> \usetypescript[times][uc]
>
> ... that's why I used ...
>
> \usetypescriptfile[type-gyr]
> \usetypescript[times][ec]
>
>
> ... but probably I should have used "texnansi" (see above).
You should try to get "uc" working if possible, but you need to add
some definitions from my previous mail. If you want to stick with
texnansi, you should better use pdfTeX.
Mojca
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] xetext-pdftex differences
Moica, thanks for your detailed support!
On Tue, 10 Apr 2007 21:27:47 +0200, Mojca Miklavec wrote:
>> Where do I go when I experience differences between context/pdftext
>> and context/xetex?
>
> What do you mean?
these:
>> For example with context/xetex I get ...
>>
>> ! Undefined control sequence.
>> \stopframedtext ->\dostopframedtext
>
...
>> ... and I do get "SS" instead of eszett ("ß") with the following:
>
> Interesting effect ... (as if the encoding was unknown)
I have to admit that it I never understood which encoding to use when
if, for example, I just write english/german/french then I could also use
texnansi, this works perfect :
\usetypescriptfile[type-gyr]
\usetypescript[times][texnansi]
\mainlanguage[de]
\enableregime[utf]
\setupbodyfont[times,9pt]
> Which version of ConTeXt? It works OK here with 2007.03.22, but I need
> to try the new beta. In principle this should not happen, it's
> probably a bug or some other local problem.
it is version 2007.01.12 (didn't you recommend to stay with the january
version?)
>> Whom to tell this?
>
> Mailing list is the perfect place.
I was wondering whether the xetex or the context list is better as it is a
mixed xetex/context-topic
and for Adam is in "paternity leave" I had no idea on which list someone
continues.
> At the beginning I had problems with XeTeX as well since Times
> resolved to 'Times Roman:mapping=tex-text', which resolved to the name
> 'mapping=tex-text' (a side effect of recent that should probably be
> fixed somehow in the near future), but that problem disappeared later.
> I had to temporary fix this (leftovers before TeXGyre family managed
> to overload everything perhaps?):
right, "Times Roman:mapping=tex-text": This also happened to me when using ...
\usetypescriptfile[type-gyr]
\usetypescript[times][uc]
... that's why I used ...
\usetypescriptfile[type-gyr]
\usetypescript[times][ec]
... but probably I should have used "texnansi" (see above).
Steffen
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] xetext-pdftex differences
On 4/8/07, Steffen Wolfrum wrote:
> Hi,
>
> as there are some on this list working/playing with xetex/context:
> Where do I go when I experience differences between context/pdftext and
> context/xetex?
What do you mean?
> For example with context/xetex I get ...
>
> ! Undefined control sequence.
> \stopframedtext ->\dostopframedtext
Which version of ConTeXt? It works OK here with 2007.03.22, but I need
to try the new beta. In principle this should not happen, it's
probably a bug or some other local problem.
> ... and I do get "SS" instead of eszett ("ß") with the following:
Interesting effect ... (as if the encoding was unknown)
> \usetypescriptfile[type-gyr]
> \usetypescript[times][ec]
This should be
\usetypescript[times][uc]
but in principle it shouldn't work without additional definitions in
typescript files. See below.
> \mainlanguage[de]
> \enableregime[utf]
> \setupbodyfont[times,9pt]
Or, to prevent from an additional source of problems (overloading
times properly):
\definetypeface[times][rm][serif][termes][default][encoding=uc]
\setupbodyfont[times,9pt]
> Hello Thermes! 1234567890 üööäß
>
>
> Whom to tell this?
Mailing list is the perfect place.
OK, so here are some additional definitions (which should probably go
to type-gyre.tex one day):
A complete list of synonyms:
\definetypescriptprefix [n:adventor] [TeXGyreAdventor] % gothic URW Gothic L
\definetypescriptprefix [n:bonum][TeXGyreBonum]% bookman
URW Bookman L
\definetypescriptprefix [n:chorus] [TeXGyreChorus] % chancery
URW Chancery L
\definetypescriptprefix [n:cursor] [TeXGyreCursor] % curier
Nimbus Mono L
\definetypescriptprefix [n:heros][TeXGyreHeros]% helvetica
Nimbus Sans L
\definetypescriptprefix [n:pagella] [TeXGyrePagella] % palatino
URW Palladio L
\definetypescriptprefix [n:schola] [TeXGyreSchola] % schoolbook
Century Schoolbook L
\definetypescriptprefix [n:termes] [TeXGyreTermes] % times
Nimbus Roman No9 L
\definetypescriptprefix [f:adventor] [ag]
\definetypescriptprefix [f:bonum][bk]
\definetypescriptprefix [f:chorus] [zc]
\definetypescriptprefix [f:cursor] [cr]
\definetypescriptprefix [f:heros][hv]
\definetypescriptprefix [f:pagella] [pl]
\definetypescriptprefix [f:schola] [cs]
\definetypescriptprefix [f:termes] [tm]
Then you need definitions for uc encoding:
\starttypescript [serif] [adventor,bonum,heros,pagella,schola,termes] [uc]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Regular]
[file:texgyre\typescripttwo-regular][encoding=\typescriptthree]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Italic]
[file:texgyre\typescripttwo-italic] [encoding=\typescriptthree]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Bold]
[file:texgyre\typescripttwo-bold] [encoding=\typescriptthree]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-BoldItalic]
[file:texgyre\typescripttwo-bolditalic] [encoding=\typescriptthree]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Caps]
[\typescriptprefix{n:\typescripttwo}-Regular]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-ItalicCaps]
[\typescriptprefix{n:\typescripttwo}-Italic]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-BoldCaps]
[\typescriptprefix{n:\typescripttwo}-Bold]
\definefontsynonym
[\typescriptprefix{n:\typescripttwo}-BoldItalicCaps]
[\typescriptprefix{n:\typescripttwo}-BoldItalic]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Slanted]
[\typescriptprefix{n:\typescripttwo}-Italic]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-BoldSlanted]
[\typescriptprefix{n:\typescripttwo}-BoldItalic]
\stoptypescript
% definitions for SmallCaps are wrong, since they're a feature in OT
fonts and that is a bit broken (or at least not stable enough) at the
moment.
And you also need the following:
% ec,texnansi,cs,el,qx,rm,t5,t2a,t2b,t2c,l7x
\starttypescript [serif] [times] [uc]
\definefontsynonym [Times-Roman] [TeXGyreTermes-Regular]
[encoding=\typescriptthree]
\definefontsynonym [Times-Italic] [TeXGyreTermes-Italic]
[encoding=\typescriptthree]
\definefontsynonym [Times-Bold][TeXGyreTermes-Bold]
[encoding=\typescriptthree]
\definefontsynonym [Times-BoldItalic] [TeXGyreTermes-BoldItalic]
[encoding=\typescriptthree]
\definefontsynonym [Times-Caps][TeXGyreTermes-Caps]
[encoding=\typescriptthree]
\definefontsynonym [Times-Slanted] [Times-Italic]
\definefontsynonym [Times-BoldSlanted] [Times-BoldItalic]
\stoptypescript
Something strange is happening though. If you load these definitions
with XeTeX, it works OK. If one loads them with pdfTeX, it doesn't
work, since TeXGyreTermes-Regular isn't defined. When I think a bit, I
understand why it's not defined (because it's part of "termes" family,
not part of "t
[NTG-context] xetext-pdftex differences
Hi,
as there are some on this list working/playing with xetex/context:
Where do I go when I experience differences between context/pdftext and
context/xetex?
For example with context/xetex I get ...
! Undefined control sequence.
\stopframedtext ->\dostopframedtext
... and I do get "SS" instead of eszett ("ß") with the following:
\usetypescriptfile[type-gyr]
\usetypescript[times][ec]
\mainlanguage[de]
\enableregime[utf]
\setupbodyfont[times,9pt]
Hello Thermes! 1234567890 üööäß
Whom to tell this?
Steffen
P.S. Besides these details it is amazing how smooth ConTeXt files run with
XeTeX!!
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texmfstart/pdftex parameters
> texmfstart texexec --pass=\'-file-line-error -halt-on-error\' hello Very sly. And the short form also worked: texexec --pass=\'-file-line-error -halt-on-error\' hello -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texmfstart/pdftex parameters
Hi all, > is there a way to pass parameters from texmfstart texexec to pdftex? > I'd like to call pdftex with -file-line-error and -halt-on-error. Just for the record: I've found a simple solution, which works OK here on MacOS X (should be the same on any unix): texmfstart texexec --pass=\'-file-line-error -halt-on-error\' hello this way (internally) the command looks like --pass='.' which will be the way it gets passed to texmfstart. Patrick -- ConTeXt wiki and more: http://contextgarden.net ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texmfstart/pdftex parameters
> Thanks. From reading the mails I can't see a solution. Perhaps > Sanjoy knows one. I don't know, unfortunately. Hans sent me a proposed fix, but it didn't work. One problem is that passing multiple options is working on Hans's setup, so the problem is elusive. I need to learn a bit of ruby. -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texmfstart/pdftex parameters
Hi Aditya >> is there a way to pass parameters from texmfstart texexec to pdftex? >> I'd like to call pdftex with -file-line-error and -halt-on-error. > > --passon=-file-line-error > > There was a recent thread where Sanjoy had trouble passing two > parameters to --passon. I do not remember if that was resolved or not. Thanks. From reading the mails I can't see a solution. Perhaps Sanjoy knows one. Patrick -- ConTeXt wiki and more: http://contextgarden.net ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texmfstart/pdftex parameters
On Fri, 9 Mar 2007, Patrick Gundlach wrote: > Hi all, > > is there a way to pass parameters from texmfstart texexec to pdftex? > I'd like to call pdftex with -file-line-error and -halt-on-error. --passon=-file-line-error There was a recent thread where Sanjoy had trouble passing two parameters to --passon. I do not remember if that was resolved or not. Aditya ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] texmfstart/pdftex parameters
Hi all, is there a way to pass parameters from texmfstart texexec to pdftex? I'd like to call pdftex with -file-line-error and -halt-on-error. Patrick -- ConTeXt wiki and more: http://contextgarden.net ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
2007/2/5, luigi scarso <[EMAIL PROTECTED]>: > This seem to be fixed with 1.40.3 release of pdftex . This _is_ fixed and the only reason for 1.40.3. :-} Best Martin ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
On 1/31/07, Johan Sandblom <[EMAIL PROTECTED]> wrote: > When I moved from pdftex-1.30.5-2.2 (from texlive-base-bin > 2005.dfsg.2-10 on debian) to pdftex-1.40.1 suddenly ligatures in This seem to be fixed with 1.40.3 release of pdftex . luigi ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures (pdftex bug)
See minimal example here: http://sarovar.org/tracker/index.php?func=detail&aid=729&group_id=106&atid=493 Best, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
> The -recorder switch of pdftex/web2c (don't know how to use that > with texexec) Like so: texexec --passon=-recorder file.tex The --passon feature had lapsed in the transition from perl to ruby texexec, but Hans and Taco fixed it in one of the recent ConTeXt releases. I now use it all the time to get compiler-like error msgs: texexec --passon=-file-line-error ... filtering the output through egrep -i -A 4 '^([^ :]+:[0-9]+: |output written.*pages)' to select the error lines and a bit of context, so to speak. -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
2007/2/2, Johan Sandblom <[EMAIL PROTECTED]>: > Sorry, neglected to mention (it was long ago and I had forgotten), I > installed it with texfont Btw: The -recorder switch of pdftex/web2c (don't know how to use that with texexec) will write a list of all files used by pdftex (including fonts) to a file. And if you put all these files in the same directory as your input file, pdftex will use those, so you don't have to fiddle with texmf-*. Best Martin ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
2007/2/2, Taco Hoekwater <[EMAIL PROTECTED]>: I am trying to work this out, but I obviously miss the gentium font files (metric and map files, as wel as the actual fonts). I can get the ttfs from the sil site, but where did the tfms and map files come from? Take mine: http://www.fiee.net/texnique/?menu=0-1-4 Greetlings, Hraban ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
Sorry, neglected to mention (it was long ago and I had forgotten), I installed it with texfont texfont --ma --in --ve=sil --co=gentium --fontroot=/usr/share/texmf --afmpl [--en=ec] hmm, can't remember if it was /usr/share on the end Thank you for your efforts Johan 2007/2/2, Taco Hoekwater <[EMAIL PROTECTED]>: > Hi Johan, > > Johan Sandblom wrote: > > For the time being I simplified my design and removed the use of Zapf > > Chancery, and there is no problem. > > I am trying to work this out, but I obviously miss the gentium > font files (metric and map files, as wel as the actual fonts). > I can get the ttfs from the sil site, but where did the tfms > and map files come from? > > Best, > Taco > ___ > ntg-context mailing list > ntg-context@ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-context > -- Johan Sandblom N8, MRC, Karolinska sjh t +46851776108 17176 Stockholm m +46735521477 Sweden "What is wanted is not the will to believe, but the will to find out, which is the exact opposite" - Bertrand Russell ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
Hi Johan, Johan Sandblom wrote: > For the time being I simplified my design and removed the use of Zapf > Chancery, and there is no problem. I am trying to work this out, but I obviously miss the gentium font files (metric and map files, as wel as the actual fonts). I can get the ttfs from the sil site, but where did the tfms and map files come from? Best, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
For the time being I simplified my design and removed the use of Zapf
Chancery, and there is no problem.
Johan
2007/2/1, Hans Hagen <[EMAIL PROTECTED]>:
> Johan Sandblom wrote:
> > It took a lot of searching for a minimal case, apparently there are
> > many levels of interaction here. The file below has blanks for fi fl
> > ff when compiled with pdftex-1.40.1 but not with pdftex-1.30.5. Do you
> > need some parts of my tex/font setup as well?
> >
> > Johan
> >
> > \usetypescriptfile[type-sil-gentium]
> > \usetypescript[my][sil-gentium]
> > \setupbodyfont[sil-gentium, 10pt]
> >
> > \definetypeface
> > [chance]
> > [cg]
> > [calligraphy]
> > [chancery]
> > [default]
> > [encoding=texnansi]
> >
> > \def\ChCmd#1#2{%
> > \switchtobodyfont[14pt]
> > \setupinterlinespace[small]
> > \framed[width=15cm, align=normal, frame=off]
> > {\framed[frame=off, align=middle, offset=2mm,
> > width=.8\textwidth]{#2}
> > \hfilll\switchtobodyfont[chance,30pt]
> > \framed[background=color, backgroundcolor=black, width=3cm,
> > align=right]{\white\bf#1}}}
> >
> > \setuphead
> > [chapter]
> > [command=\ChCmd,
> > header=empty,
> > page=right]
> >
> > \starttext
> >
> > \chapter[meth]{Methods for studying human brain function}
> >
> > fill significantly flog flash floozy flagellation
> >
> > \stoptext
> >
> > 2007/2/1, Taco Hoekwater <[EMAIL PROTECTED]>:
> >
> >> Hi Johan,
> >>
> >> If the only change is the pdftex version, than it sounds like this
> >> is a pdftex bug. Any chance you can create a small standalone testfile?
> >>
> >> Best, Taco
> >>
> >> Johan Sandblom wrote:
> >>
> >>> When I moved from pdftex-1.30.5-2.2 (from texlive-base-bin
> >>> 2005.dfsg.2-10 on debian) to pdftex-1.40.1 suddenly ligatures in
> >>> gentium exhibited erratic behavior: they appeared correctly (or, more
> >>> accurately, the letters appeared, they did not look like a proper
> >>> ligature) on screen in xpdf and acroread but did not print (there were
> >>> just empty spaces). On windows, the fi, fl, and ff combinations made
> >>> blanks, just as on the printer. Reverting to pdftex-1.30.5-2.2
> >>> corrected the problem. Gentium is from ttf-gentium 1.02-2 on debian
> >>> and the typescript I use is below. Perhaps my poor typesetting
> >>> knowledge has lead me wrong and the lack of true ligatures is the
> >>> actual problem?
> >>>
>
> no, but it may be related to a bug in vf handling that has been resolved
> by now (new version of pdftex coming)
>
> Hans
>
> --
>
> -
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -
>
> ___
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
--
Johan Sandblom N8, MRC, Karolinska sjh
t +46851776108 17176 Stockholm
m +46735521477 Sweden
"What is wanted is not the will to believe, but the
will to find out, which is the exact opposite"
- Bertrand Russell
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
Johan Sandblom wrote:
> It took a lot of searching for a minimal case, apparently there are
> many levels of interaction here. The file below has blanks for fi fl
> ff when compiled with pdftex-1.40.1 but not with pdftex-1.30.5. Do you
> need some parts of my tex/font setup as well?
>
> Johan
>
> \usetypescriptfile[type-sil-gentium]
> \usetypescript[my][sil-gentium]
> \setupbodyfont[sil-gentium, 10pt]
>
> \definetypeface
> [chance]
> [cg]
> [calligraphy]
> [chancery]
> [default]
> [encoding=texnansi]
>
> \def\ChCmd#1#2{%
> \switchtobodyfont[14pt]
> \setupinterlinespace[small]
> \framed[width=15cm, align=normal, frame=off]
> {\framed[frame=off, align=middle, offset=2mm, width=.8\textwidth]{#2}
> \hfilll\switchtobodyfont[chance,30pt]
> \framed[background=color, backgroundcolor=black, width=3cm,
> align=right]{\white\bf#1}}}
>
> \setuphead
> [chapter]
> [command=\ChCmd,
> header=empty,
> page=right]
>
> \starttext
>
> \chapter[meth]{Methods for studying human brain function}
>
> fill significantly flog flash floozy flagellation
>
> \stoptext
>
> 2007/2/1, Taco Hoekwater <[EMAIL PROTECTED]>:
>
>> Hi Johan,
>>
>> If the only change is the pdftex version, than it sounds like this
>> is a pdftex bug. Any chance you can create a small standalone testfile?
>>
>> Best, Taco
>>
>> Johan Sandblom wrote:
>>
>>> When I moved from pdftex-1.30.5-2.2 (from texlive-base-bin
>>> 2005.dfsg.2-10 on debian) to pdftex-1.40.1 suddenly ligatures in
>>> gentium exhibited erratic behavior: they appeared correctly (or, more
>>> accurately, the letters appeared, they did not look like a proper
>>> ligature) on screen in xpdf and acroread but did not print (there were
>>> just empty spaces). On windows, the fi, fl, and ff combinations made
>>> blanks, just as on the printer. Reverting to pdftex-1.30.5-2.2
>>> corrected the problem. Gentium is from ttf-gentium 1.02-2 on debian
>>> and the typescript I use is below. Perhaps my poor typesetting
>>> knowledge has lead me wrong and the lack of true ligatures is the
>>> actual problem?
>>>
no, but it may be related to a bug in vf handling that has been resolved
by now (new version of pdftex coming)
Hans
--
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
It took a lot of searching for a minimal case, apparently there are
many levels of interaction here. The file below has blanks for fi fl
ff when compiled with pdftex-1.40.1 but not with pdftex-1.30.5. Do you
need some parts of my tex/font setup as well?
Johan
\usetypescriptfile[type-sil-gentium]
\usetypescript[my][sil-gentium]
\setupbodyfont[sil-gentium, 10pt]
\definetypeface
[chance]
[cg]
[calligraphy]
[chancery]
[default]
[encoding=texnansi]
\def\ChCmd#1#2{%
\switchtobodyfont[14pt]
\setupinterlinespace[small]
\framed[width=15cm, align=normal, frame=off]
{\framed[frame=off, align=middle, offset=2mm, width=.8\textwidth]{#2}
\hfilll\switchtobodyfont[chance,30pt]
\framed[background=color, backgroundcolor=black, width=3cm,
align=right]{\white\bf#1}}}
\setuphead
[chapter]
[command=\ChCmd,
header=empty,
page=right]
\starttext
\chapter[meth]{Methods for studying human brain function}
fill significantly flog flash floozy flagellation
\stoptext
2007/2/1, Taco Hoekwater <[EMAIL PROTECTED]>:
> Hi Johan,
>
> If the only change is the pdftex version, than it sounds like this
> is a pdftex bug. Any chance you can create a small standalone testfile?
>
> Best, Taco
>
> Johan Sandblom wrote:
> > When I moved from pdftex-1.30.5-2.2 (from texlive-base-bin
> > 2005.dfsg.2-10 on debian) to pdftex-1.40.1 suddenly ligatures in
> > gentium exhibited erratic behavior: they appeared correctly (or, more
> > accurately, the letters appeared, they did not look like a proper
> > ligature) on screen in xpdf and acroread but did not print (there were
> > just empty spaces). On windows, the fi, fl, and ff combinations made
> > blanks, just as on the printer. Reverting to pdftex-1.30.5-2.2
> > corrected the problem. Gentium is from ttf-gentium 1.02-2 on debian
> > and the typescript I use is below. Perhaps my poor typesetting
> > knowledge has lead me wrong and the lack of true ligatures is the
> > actual problem?
> >
> > Regards, Johan
> >
> >
> >
> >
> >
> > ___
> > ntg-context mailing list
> > ntg-context@ntg.nl
> > http://www.ntg.nl/mailman/listinfo/ntg-context
>
--
Johan Sandblom N8, MRC, Karolinska sjh
t +46851776108 17176 Stockholm
m +46735521477 Sweden
"What is wanted is not the will to believe, but the
will to find out, which is the exact opposite"
- Bertrand Russell
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
Hi Johan, If the only change is the pdftex version, than it sounds like this is a pdftex bug. Any chance you can create a small standalone testfile? Best, Taco Johan Sandblom wrote: > When I moved from pdftex-1.30.5-2.2 (from texlive-base-bin > 2005.dfsg.2-10 on debian) to pdftex-1.40.1 suddenly ligatures in > gentium exhibited erratic behavior: they appeared correctly (or, more > accurately, the letters appeared, they did not look like a proper > ligature) on screen in xpdf and acroread but did not print (there were > just empty spaces). On windows, the fi, fl, and ff combinations made > blanks, just as on the printer. Reverting to pdftex-1.30.5-2.2 > corrected the problem. Gentium is from ttf-gentium 1.02-2 on debian > and the typescript I use is below. Perhaps my poor typesetting > knowledge has lead me wrong and the lack of true ligatures is the > actual problem? > > Regards, Johan > > > > > > ___ > ntg-context mailing list > ntg-context@ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-context ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] problem with pdftex-1.40.1 and Gentium ligatures
When I moved from pdftex-1.30.5-2.2 (from texlive-base-bin 2005.dfsg.2-10 on debian) to pdftex-1.40.1 suddenly ligatures in gentium exhibited erratic behavior: they appeared correctly (or, more accurately, the letters appeared, they did not look like a proper ligature) on screen in xpdf and acroread but did not print (there were just empty spaces). On windows, the fi, fl, and ff combinations made blanks, just as on the printer. Reverting to pdftex-1.30.5-2.2 corrected the problem. Gentium is from ttf-gentium 1.02-2 on debian and the typescript I use is below. Perhaps my poor typesetting knowledge has lead me wrong and the lack of true ligatures is the actual problem? Regards, Johan -- Johan Sandblom N8, MRC, Karolinska sjh t +46851776108 17176 Stockholm m +46735521477 Sweden "What is wanted is not the will to believe, but the will to find out, which is the exact opposite" - Bertrand Russell type-sil-gentium.tex Description: TeX document ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] crash with pdftex-1.40
Sanjoy Mahajan wrote: >>But this should be enough to reproduce it: >>\starttext >>\input "\string|echo -n bla" >>\stoptext > > > Breaks here too, using pdftex 1.40.0, context 2006.12.27, Ubuntu i386: This bug is found and fixed and will be corrected in the next pdftex release. Best, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] crash with pdftex-1.40
It breaks here on Ubuntu 6.06 LTS, latest pdftex, latest context distro
t is
\starttext
\def\myCMD#1{%..
\stoptext
t1 is
\starttext
\input "\string|echo -n bla"
\stoptext
luigi
[EMAIL PROTECTED]:/tmp# texmfstart texexec --pdf t
TeXExec | processing document 't'
TeXExec | no ctx file found
TeXExec | tex processing method: context
TeXExec | TeX run 1
TeXExec | writing option file t.top
TeXExec | using randomseed 1369
TeXExec | tex engine: pdfetex
TeXExec | tex format: cont-en
This is pdfTeXk, Version 3.141592-1.40.0 (Web2C 7.5.6)
\write18 enabled.
%&-line parsing enabled.
(/opt/texlive/2005-test/texmf/web2c/natural.tcx)
entering extended mode
(./t.tex
ConTeXt ver: 2007.01.02 13:44 MK II fmt: 2007.1.3 int: english/english
language: language en is active
system : cont-new loaded
(/opt/texlive/2005-test/texmf-dist/tex/context/base/cont-new.tex
systems : beware: some patches loaded from cont-new.tex
(/opt/texlive/2005-test/texmf-dist/tex/context/base/cont-new.mkii))
system : cont-old loaded
(/opt/texlive/2005-test/texmf-dist/tex/context/base/cont-old.tex
loading : Context Old Macros
)
system : cont-fil loaded
(/opt/texlive/2005-test/texmf-dist/tex/context/base/cont-fil.tex
loading : Context File Synonyms
)
system : cont-sys loaded
(/opt/texlive/2005-test/texmf-dist/tex/context/base/cont-sys.tex
(/opt/texlive/2005-test/texmf-dist/tex/context/base/type-exa.tex)
(/opt/texlive/2005-test/texmf-dist/tex/context/base/type-syn.tex)
(/opt/texlive/2005-test/texmf-dist/tex/context/base/type-enc.tex)
(/opt/texlive/2005-test/texmf-dist/tex/context/base/type-siz.tex)
(/opt/texlive/2005-test/texmf-dist/tex/context/base/type-map.tex)
(/opt/texlive/2005-test/texmf-dist/tex/context/base/type-spe.tex)
(/opt/texlive/2005-test/texmf-dist/tex/context/base/type-akb.tex))
bodyfont: 12pt rm is loaded
language: patterns en->ec:ec->1->2:3 uk->ec:ec->2->2:3 de->texnansi:tex
nansi->3->2:3 de->ec:ec->4->2:3 fr->texnansi:texnansi->5->2:3 fr->ec:ec->6->2:3
es->ec:ec->7->2:3 pt->texnansi:texnansi->8->2:3 pt->ec:ec->9->2:3 it->texnansi
:texnansi->10->2:3 it->ec:ec->11->2:3 nl->texnansi:texnansi->12->2:3 nl->ec:ec-
>13->2:3 cz->il2:il2->14->2:3 cz->ec:ec->15->2:3 sk->il2:il2->16->2:3 sk->ec:ec
->17->2:3 pl->pl0:pl0->18->2:3 pl->ec:ec->19->2:3 pl->qx:qx->20->2:3 loaded
specials: tex,postscript,rokicki loaded
system : t.top loaded
(./t.top
specials: loading definition file tpd
(/opt/texlive/2005-test/texmf-dist/tex/context/base/spec-tpd.tex
specials: loading definition file fdf
(/opt/texlive/2005-test/texmf-dist/tex/context/base/spec-fdf.tex
(/opt/texlive/2005-test/texmf-dist/tex/context/base/spec-fdf.mkii))
specials: fdf loaded
)
specials: fdf,tpd loaded
)
systems : system commands are enabled
(/opt/texlive/2005-test/texmf-dist/tex/context/base/sort-def.tex)
(/opt/texlive/2005-test/texmf-dist/tex/context/base/sort-lan.tex)
(/opt/texlive/2005-test/texmf-dist/tex/context/base/pdfr-def.tex)
systems : begin file t at line 1
(./texcmd.tmp) (./texcmd.tmp) (./texcmd.tmp)*** glibc detected ***
pdfetex: free(): invalid next size (fast): 0x0852eba8 ***
=== Backtrace: =
/lib/tls/i686/cmov/libc.so.6[0xb7eae8bd]
/lib/tls/i686/cmov/libc.so.6(__libc_free+0x84)[0xb7eaea44]
pdfetex[0x80a776b]
pdfetex[0x8078858]
pdfetex[0x806c3a9]
pdfetex[0x8078666]
pdfetex[0x80a55fd]
pdfetex[0x8059b11]
pdfetex[0x80a90a7]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc)[0xb7e5d8cc]
pdfetex[0x804a471]
=== Memory map:
08048000-08169000 r-xp 08:03 607410
/opt/texlive/2005-test/bin/i386-linux/pdfetex
08169000-0818 rw-p 0012 08:03 607410
/opt/texlive/2005-test/bin/i386-linux/pdfetex
0818-08545000 rw-p 0818 00:00 0 [heap]
b3c0-b3c21000 rw-p b3c0 00:00 0
b3c21000-b3d0 ---p b3c21000 00:00 0
b3dfd000-b7e48000 rw-p b3dfd000 00:00 0
b7e48000-b7f75000 r-xp 08:03 2638865/lib/tls/i686/cmov/libc-2.4.so
b7f75000-b7f77000 r--p 0012c000 08:03 2638865/lib/tls/i686/cmov/libc-2.4.so
b7f77000-b7f79000 rw-p 0012e000 08:03 2638865/lib/tls/i686/cmov/libc-2.4.so
b7f79000-b7f7c000 rw-p b7f79000 00:00 0
b7f7c000-b7fa r-xp 08:03 2638873/lib/tls/i686/cmov/libm-2.4.so
b7fa-b7fa2000 rw-p 00023000 08:03 2638873/lib/tls/i686/cmov/libm-2.4.so
b7faa000-b7fb4000 r-xp 08:03 2605080/lib/libgcc_s.so.1
b7fb4000-b7fb5000 rw-p 9000 08:03 2605080/lib/libgcc_s.so.1
b7fb5000-b7fbb000 rw-p b7fb5000 00:00 0
b7fbb000-b7fd4000 r-xp 08:03 2605078/lib/ld-2.4.so
b7fd4000-b7fd6000 rw-p 00018000 08:03 2605078/lib/ld-2.4.so
bfbbf000-bfbd4000 rw-p bfbbf000 00:00 0 [stack]
e000-f000 ---p 0
Re: [NTG-context] crash with pdftex-1.40
> But this should be enough to reproduce it: > \starttext > \input "\string|echo -n bla" > \stoptext Breaks here too, using pdftex 1.40.0, context 2006.12.27, Ubuntu i386: *** glibc detected *** pdfetex: free(): invalid next size (fast): 0x082d42f0 *** Running texexec with --verbose says what the pdftex command that texexec runs is, and this is the minimal version of it: pdfetex -fmt=cont-en b.tex where b.tex is Peter's minimal (3-line) file above. Strangely, "pdftex -etex -ini c.tex", where c.tex is b.tex with "\input cont-en" as the first line, did not crash. I rebuilt pdf(e)tex make sure not to strip the binaries, and ran it with debugging libraries and valgrind, like so: LD_LIBRARY_PATH=/usr/lib/debug: valgrind pdfetex -fmt=cont-en b.tex and the output is included below. Here is the chunk from it, where the problem is first detected by valgrind: ==27710== Invalid write of size 1 ==27710==at 0x4022756: strcpy (mc_replace_strmem.c:271) ==27710==by 0x80A774D: open_in_or_pipe (pdftexextra.c:1354) ==27710==by 0x8078857: startinput (pdftex1.c:4870) ==27710==by 0x806C3A8: expand (pdftex0.c:11501) ==27710==by 0x80786CB: getxtoken (pdftex1.c:24) ==27710==by 0x80A4B88: maincontrol (pdftex3.c:5246) ==27710==by 0x8059B10: mainbody (pdftexini.c:5664) ==27710==by 0x80A90A6: main (pdftexextra.c:349) -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien) == valgrind run == ==27710== Memcheck, a memory error detector. ==27710== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al. ==27710== Using LibVEX rev 1606, a library for dynamic binary translation. ==27710== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP. ==27710== Using valgrind-3.2.0-Debian, a dynamic binary instrumentation framework. ==27710== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al. ==27710== For more details, rerun with: -v ==27710== This is pdfTeX, Version 3.141592-1.40.0 (Web2C 7.5.6) \write18 enabled. entering extended mode (./b.tex ConTeXt ver: 2006.12.27 11:34 MK II fmt: 2007.1.4 int: english/english language: language en is active system : cont-new loaded (/usr/share/texmf/tex/context/base/cont-new.tex systems : beware: some patches loaded from cont-new.tex (/usr/share/texmf/tex/context/base/cont-new.mkii)) system : cont-old loaded (/usr/share/texmf/tex/context/base/cont-old.tex loading : Context Old Macros ) system : cont-fil loaded (/usr/share/texmf/tex/context/base/cont-fil.tex loading : Context File Synonyms ) system : cont-sys.rme loaded (/usr/share/texmf/tex/context/user/cont-sys.rme (/usr/share/texmf/tex/context/base/type-exa.tex) (/usr/share/texmf/tex/context/base/type-syn.tex) (/usr/share/texmf/tex/context/base/type-enc.tex) (/usr/share/texmf/tex/context/base/type-siz.tex) (/usr/share/texmf/tex/context/base/type-map.tex) (/usr/share/texmf/tex/context/base/type-spe.tex) (/usr/share/texmf/tex/context/base/type-akb.tex)) bodyfont: 12pt rm is loaded language: patterns en->ec:ec->1->2:3 uk->ec:ec->2->2:3 de->texnansi:tex nansi->3->2:3 de->ec:ec->4->2:3 fr->texnansi:texnansi->5->2:3 fr->ec:ec->6->2:3 es->ec:ec->7->2:3 pt->texnansi:texnansi->8->2:3 pt->ec:ec->9->2:3 it->texnansi :texnansi->10->2:3 it->ec:ec->11->2:3 nl->texnansi:texnansi->12->2:3 nl->ec:ec- >13->2:3 cz->il2:il2->14->2:3 cz->ec:ec->15->2:3 sk->il2:il2->16->2:3 sk->ec:ec ->17->2:3 pl->pl0:pl0->18->2:3 pl->ec:ec->19->2:3 pl->qx:qx->20->2:3 loaded specials: tex,postscript,rokicki loaded systems : no b.top systems : system commands are enabled (/usr/share/texmf/tex/context/base/sort-def.tex) (/usr/share/texmf/tex/context/base/sort-lan.tex)==27710== Invalid write of size 1 ==27710==at 0x4022756: strcpy (mc_replace_strmem.c:271) ==27710==by 0x80A774D: open_in_or_pipe (pdftexextra.c:1354) ==27710==by 0x8078857: startinput (pdftex1.c:4870) ==27710==by 0x806C3A8: expand (pdftex0.c:11501) ==27710==by 0x80786CB: getxtoken (pdftex1.c:24) ==27710==by 0x80A4B88: maincontrol (pdftex3.c:5246) ==27710==by 0x8059B10: mainbody (pdftexini.c:5664) ==27710==by 0x80A90A6: main (pdftexextra.c:349) ==27710== Address 0x567459C is 0 bytes after a block of size 12 alloc'd ==27710==at 0x4021396: malloc (vg_replace_malloc.c:149) ==27710==by 0x813748C: xmalloc (xmalloc.c:28) ==27710==by 0x80A7737: open_in_or_pipe (pdftexextra.c:1353) ==27710==by 0x8078857: startinput (pdftex1.c:4870) ==27710==by 0x806C3A8: expand (pdftex0.c:11501) ==27710==by 0x80786CB: getxtoken (pdftex1.c:24) ==27710==by 0x80A4B88: maincontrol (pdftex3.c:5246) =
Re: [NTG-context] crash with pdftex-1.40
2007/1/4, Peter Münster <[EMAIL PROTECTED]>: > this is probably only related to pdfTeX and not to ConTeXt, but I'm too > lazy to subscribe yet to another list... ;) I can't reproduce this with my old ConTeXt 2005.01.31 on SUSE 10.1. Best Martin ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] engine should be pdftex
� wrote: > On Wed, 3 Jan 2007, Hans Hagen wrote: > > >> You need to delete all traces of pdfetex, pdfetex.pool, pdfetex, >> pdfetex.exe, pdfetex.dll, trhe pdfetex engine path, etc >> > > Thanks, this helps. > > Another question concerning formats: in TeX-live 2007, what should be the > right place to put the formats? > "texexec --make --all" puts them into texmf-config/web2c but all other > programs put them into texmf-var/web2c > > hm, dunno, in tetex there was a rather long and weird list of paths, dunno how it is today here i keep binaries and formats in paths like texmf-mswin/bin|web2c texmf-linux/bin|web2c esp since we can never be sure if binaries match and pool files and such may differ Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] crash with pdftex-1.40
Martin Schröder wrote: > 2007/1/4, Peter Münster <[EMAIL PROTECTED]>: > >>this is probably only related to pdfTeX and not to ConTeXt, but I'm too >>lazy to subscribe yet to another list... ;) > > I can't reproduce this with my old ConTeXt 2005.01.31 on SUSE 10.1. I have only the pdftex-1.40-rc4 here (no problem). I'll try the texlive and final standalone binaries tomorrow. Best, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] crash with pdftex-1.40
Hello, this is probably only related to pdfTeX and not to ConTeXt, but I'm too lazy to subscribe yet to another list... ;) While playing around with the new shell escaping in pdftex-1.40, I got the following crash: TeXExec | processing document 'test' TeXExec | no ctx file found TeXExec | tex processing method: context TeXExec | TeX run 1 TeXExec | writing option file test.top TeXExec | using randomseed 121 TeXExec | tex engine: pdftex TeXExec | tex format: cont-en This is pdfTeX, Version 3.141592-1.40.0 (Web2C 7.5.6) \write18 enabled. (/opt/TeX-live/texmf/web2c/natural.tcx) entering extended mode (./test.tex ConTeXt ver: 2007.01.02 13:44 MK II fmt: 2007.1.4 int: english/english language: language en is active system : cont-new loaded (/opt/TeX-live/texmf-context/tex/context/base/cont-new.tex systems : beware: some patches loaded from cont-new.tex (/opt/TeX-live/texmf-context/tex/context/base/cont-new.mkii)) system : cont-old loaded (/opt/TeX-live/texmf-context/tex/context/base/cont-old.tex loading : Context Old Macros ) system : cont-fil loaded (/opt/TeX-live/texmf-context/tex/context/base/cont-fil.tex loading : Context File Synonyms ) system : cont-sys loaded (/home/peter/.TeX/cont-sys.tex (/opt/TeX-live/texmf-context/tex/context/user/cont-sys.rme (/opt/TeX-live/texmf-context/tex/context/base/type-exa.tex) (/opt/TeX-live/texmf-context/tex/context/base/type-syn.tex) (/opt/TeX-live/texmf-context/tex/context/base/type-enc.tex) (/opt/TeX-live/texmf-context/tex/context/base/type-siz.tex) (/opt/TeX-live/texmf-context/tex/context/base/type-map.tex) (/opt/TeX-live/texmf-context/tex/context/base/type-spe.tex) (/opt/TeX-live/texmf-context/tex/context/base/type-akb.tex)) (/home/peter/.TeX/dd-macros.tex loading : Macros for Delta Dore )) bodyfont: 12pt rm is loaded language: patterns nl->texnansi:texnansi->1->2:3 nl->ec:ec->2->2:3 fr-> texnansi:texnansi->3->2:3 fr->ec:ec->4->2:3 de->texnansi:texnansi->5->2:3 de->e c:ec->6->2:3 it->texnansi:texnansi->7->2:3 it->ec:ec->8->2:3 pt->texnansi:texna nsi->9->2:3 pt->ec:ec->10->2:3 hr->ec:ec->11->2:3 pl->pl0:pl0->12->2:3 pl->ec:e c->13->2:3 pl->qx:qx->14->2:3 cz->il2:il2->15->2:3 cz->ec:ec->16->2:3 sk->il2:i l2->17->2:3 sk->ec:ec->18->2:3 sl->ec:ec->19->2:3 ru->t2a:t2a->21->2:3 en->ec:e c->22->2:3 uk->ec:ec->23->2:3 us->ec:ec->24->2:3 agr->agr:agr->25->2:3 da->ec:e c->26->2:3 sv->ec:ec->27->2:3 af->ec:ec->28->2:3 no->ec:ec->29->2:3 deo->ec:ec- >30->2:3 es->ec:ec->31->2:3 ca->ec:ec->32->2:3 la->ec:ec->33->2:3 ro->ec:ec->34 ->2:3 tr->ec:ec->35->2:3 fi->ec:ec->37->2:3 hu->ec:ec->38->2:3 loaded specials: tex,postscript,rokicki loaded system : test.top loaded (./test.top specials: loading definition file tpd (/opt/TeX-live/texmf-context/tex/context/base/spec-tpd.tex specials: loading definition file fdf (/opt/TeX-live/texmf-context/tex/context/base/spec-fdf.tex (/opt/TeX-live/texmf-context/tex/context/base/spec-fdf.mkii)) specials: fdf loaded ) specials: fdf,tpd loaded ) systems : system commands are enabled (./test.tuo) (./test.tuo) (./test.tuo) (./test.tuo) (./test.tuo) (./test.tuo) (./test.tuo) (./test.tuo) (./test.tuo) (./test.tuo) (/opt/TeX-live/texmf-context/tex/context/base/sort-def.tex) (/opt/TeX-live/texmf-context/tex/context/base/sort-lan.tex) (./test.tuo) (./test.tuo) (/opt/TeX-live/texmf-context/tex/context/base/pdfr-def.tex) systems : begin file test at line 1 (./texcmd.tmp) (./texcmd.tmp) (./texcmd.tmp)TeXExec | runtime: 0.318195 *** glibc detected *** pdftex: free(): invalid next size (fast): 0x0850f718 *** === Backtrace: = /lib/libc.so.6[0xb7dbe911] /lib/libc.so.6(__libc_free+0x84)[0xb7dbff84] pdftex[0x80a54b9] pdftex[0x80774fe] pdftex[0x806b764] pdftex[0x807732e] pdftex[0x80a2d2d] pdftex[0x8059f1c] pdftex[0x80a6e3b] /lib/libc.so.6(__libc_start_main+0xdc)[0xb7d7087c] pdftex[0x804a9e1] === Memory map: 08048000-08145000 r-xp fe:01 262328 /opt/TeX-live/bin/pdftex 08145000-0815c000 rw-p 000fc000 fe:01 262328 /opt/TeX-live/bin/pdftex 0815c000-08539000 rw-p 0815c000 00:00 0 [heap] b3a0-b3a21000 rw-p b3a0 00:00 0 b3a21000-b3b0 ---p b3a21000 00:00 0 b3b13000-b3b1d000 r-xp 03:02 114396 /lib/libgcc_s.so.1 b3b1d000-b3b1e000 rw-p 9000 03:02 114396 /lib/libgcc_s.so.1 b3b3b000-b7d5b000 rw-p b3b3b000 00:00 0 b7d5b000-b7e74000 r-xp 03:02 114286 /lib/libc-2.4.so b7e74000-b7e76000 r--p 00118000 03:02 114286 /lib/libc-2.4.so b7e76000-b7e78000 rw-p 0011a000 03:02 114286 /lib/libc
Re: [NTG-context] engine should be pdftex
On Wed, 3 Jan 2007, Hans Hagen wrote: > You need to delete all traces of pdfetex, pdfetex.pool, pdfetex, > pdfetex.exe, pdfetex.dll, trhe pdfetex engine path, etc Thanks, this helps. Another question concerning formats: in TeX-live 2007, what should be the right place to put the formats? "texexec --make --all" puts them into texmf-config/web2c but all other programs put them into texmf-var/web2c Cheers, Peter -- http://pmrb.free.fr/contact/ ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
> the pdftex list nowadays is mostly a latex bug/support report list ; > pdftex and luatex development have their own lists > hmm I think this is the complete list. http://www.ntg.nl/mailman/listinfo/dev-context http://www.ntg.nl/mailman/listinfo/ntg-context http://www.ntg.nl/mailman/listinfo/ntg-pdftex http://tug.org/mailman/listinfo/pdftex http://www.ntg.nl/mailman/listinfo/dev-luatex ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
On Thu, 4 Jan 2007, Martin Schröder wrote: > 2007/1/4, Aditya Mahajan <[EMAIL PROTECTED]>: > > Is there someplace where I can download pdftex binaries for windows? > > The sarovar site only has source code. > > Akira's W32TeX: > http://www.fsci.fuk.kindai.ac.jp/~kakuto/win32-ptex/web2c75-e.html Thanks Aditya ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
2007/1/4, Aditya Mahajan <[EMAIL PROTECTED]>: > Is there someplace where I can download pdftex binaries for windows? > The sarovar site only has source code. Akira's W32TeX: http://www.fsci.fuk.kindai.ac.jp/~kakuto/win32-ptex/web2c75-e.html Or get the latest TexLive test image. Best Martin ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
On Thu, 4 Jan 2007, Hans Hagen wrote: > Sanjoy Mahajan wrote: > >>> which makes be believe that it will not work for normal cases. > >>> However, how about adding a switch to texexec, say --draft, which > >>> will run the document in draftmode until no more runs are needed, and > >>> will then run a final typesetting run without the draftmode. This may > >>> speed up the execution time for long documents significantly. > >>> > >>> > >> indeed > >> > >> remind me to play with this feature > >> > > > > When you do: --final could do what Aditya suggests by default (if > > making pdf). Then no need to add another switch to texexec. > > > maybe later, when i feel comfortable enough with it; for the moment i added > --draft Great. Is there someplace where I can download pdftex binaries for windows? The sarovar site only has source code. Aditya ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
Sanjoy Mahajan wrote: >>> which makes be believe that it will not work for normal cases. >>> However, how about adding a switch to texexec, say --draft, which >>> will run the document in draftmode until no more runs are needed, and >>> will then run a final typesetting run without the draftmode. This may >>> speed up the execution time for long documents significantly. >>> >>> >> indeed >> >> remind me to play with this feature >> > > When you do: --final could do what Aditya suggests by default (if > making pdf). Then no need to add another switch to texexec. > maybe later, when i feel comfortable enough with it; for the moment i added --draft Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
> > which makes be believe that it will not work for normal cases. > > However, how about adding a switch to texexec, say --draft, which > > will run the document in draftmode until no more runs are needed, and > > will then run a final typesetting run without the draftmode. This may > > speed up the execution time for long documents significantly. > > > indeed > > remind me to play with this feature When you do: --final could do what Aditya suggests by default (if making pdf). Then no need to add another switch to texexec. -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
Martin wrote: > 2007/1/3, Aditya Mahajan <[EMAIL PROTECTED]>: > >> which makes be believe that it will not work for normal cases. >> However, how about adding a switch to texexec, say --draft, which >> will run the document in draftmode until no more runs are needed, and >> will then run a final typesetting run without the draftmode. This may >> speed up the execution time for long documents significantly. >> > > It helps especially if your document produces a large pdf and/or > includes many and/or large images. > and it probably also makes a difference when one uses many fonts (hz or so - less file access, no vector calculations, etc) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
Aditya Mahajan wrote: > > which makes be believe that it will not work for normal cases. > However, how about adding a switch to texexec, say --draft, which > will run the document in draftmode until no more runs are needed, and > will then run a final typesetting run without the draftmode. This may > speed up the execution time for long documents significantly. > indeed remind me to play with this feature Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] engine should be pdftex
Sanjoy Mahajan wrote: >> "texexec --make --all" puts the formats in the subdirectory >> "pdfetex" but I think it should be "pdftex" now. >> > > If 'now' means with pdftex 1.40.0, I think you're right. But that > would break context with earlier pdftex's. I've made a symlink from > /var/lib/texmf/web2c/pdftex to pdfetex and all is okay now. > TexLive2006 works without that hack, because it doesn't put the > context formats in an $engine subdirectory, which may cause other > problems. > > See the thread "debian context updates" (Tue, 02 Jan 2007 20:39:40 GMT). > You need to delete all traces of pdfetex, pdfetex.pool, pdfetex, pdfetex.exe, pdfetex.dll, trhe pdfetex engine path, etc If texexec finds something pdfetex, it assumes pdfetex is there (unfortunately downward compatiility is not one of the strong points of tex distributions; they often assume wipe-out-install-new. texexec tries to cope with this as good as possible but we need to take older binary installations into account (else we could drop any reference to pdfetex) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] engine should be pdftex
> "texexec --make --all" puts the formats in the subdirectory > "pdfetex" but I think it should be "pdftex" now. If 'now' means with pdftex 1.40.0, I think you're right. But that would break context with earlier pdftex's. I've made a symlink from /var/lib/texmf/web2c/pdftex to pdfetex and all is okay now. TexLive2006 works without that hack, because it doesn't put the context formats in an $engine subdirectory, which may cause other problems. See the thread "debian context updates" (Tue, 02 Jan 2007 20:39:40 GMT). -Sanjoy `Not all those who wander are lost.' (J.R.R. Tolkien) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] engine should be pdftex
Hello, "texexec --make --all" puts the formats in the subdirectory "pdfetex" but I think it should be "pdftex" now. Cheers, Peter -- http://pmrb.free.fr/contact/ ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
luigi scarso wrote: > On 1/2/07, Taco Hoekwater <[EMAIL PROTECTED]> wrote: > >> Hi, >> >> The next message probably also is interestering to a few of you that >> are not subscribed to the pdftex list. >> > Oh, i'm one of the few... > the pdftex list nowadays is mostly a latex bug/support report list ; pdftex and luatex development have their own lists Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
Sanjoy Mahajan wrote:
> >From the texexec man page:
>
> --fast
> Typeset the document(s) as fast as possible without causing
> problems.
>
> --final
> Perform a final run without skipping anything. This option is
> typically used with --fast.
>
> So --fast --final could be the pair of switches to add. But I tried
> an experiment with mediocre results, using this test file:
>
> == q.tex =
> \doifnotmode{*last}{\pdfdraftmode=1}
> \starttext
> \completecontent
>
> \chapter{A}
> \dorecurse{500}{\input tufte\par}
>
> \chapter{B}
> \dorecurse{400}{\input tufte\par}
>
> \chapter{C}
> \dorecurse{100}{\input tufte\par}
>
> \stoptext
>
>
> I ran it with the attached Makefile, which produced this output:
>
> ctxtools --purge --all > /dev/null
> rm -f q.pdf
> texexec --verbose --fast --final q.tex > run.log
> Total runs: 4 (counted by grepping run.log for running: pdfetex)
> Draftmode runs: 3 (counted by grepping run.log for pdfdraftmode)
> TeXExec | runtime: 7.987485
>
> Then I commented out the first line and reran it:
>
> ctxtools --purge --all > /dev/null
> rm -f q.pdf
> texexec --verbose --fast --final q.tex > run.log
> Total runs: 4
> Draftmode runs: 0 (just to check)
> TeXExec | runtime: 8.307869
>
> So the draftmode saves 4% in the runtime. But the fastest is to not
> use the draftmode and not use --final (which causes an extra run).
> Maybe I missing a trick, but the draftmode didn't save much time. I
> guess I should make the test file read in a few huge images?
>
try bigger stuff, say a file with some 100 meg pictures and 25 fonts ; that's
what draftmode is for (one of those ideas that popped up during eurotex 2006 at
our usual pdftex dev chat).
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
On 1/2/07, Taco Hoekwater <[EMAIL PROTECTED]> wrote: > Hi, > > The next message probably also is interestering to a few of you that > are not subscribed to the pdftex list. Oh, i'm one of the few... by the way http://www.logosrl.it/context/pdftex/1.40.0-2.2 Also, greping pdftex list I found http://pdfedit.petricek.net/pdfedit.index_e luigi. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
2007/1/3, Sanjoy Mahajan <[EMAIL PROTECTED]>: > Maybe I missing a trick, but the draftmode didn't save much time. I > guess I should make the test file read in a few huge images? Yes. And if you then generate PDF 1.5 with object stream and compression, you can gain much. I have a test case which goes from 17.8s to 1.2s. On an [EMAIL PROTECTED] Best Martin ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
>From the texexec man page:
--fast
Typeset the document(s) as fast as possible without causing
problems.
--final
Perform a final run without skipping anything. This option is
typically used with --fast.
So --fast --final could be the pair of switches to add. But I tried
an experiment with mediocre results, using this test file:
== q.tex =
\doifnotmode{*last}{\pdfdraftmode=1}
\starttext
\completecontent
\chapter{A}
\dorecurse{500}{\input tufte\par}
\chapter{B}
\dorecurse{400}{\input tufte\par}
\chapter{C}
\dorecurse{100}{\input tufte\par}
\stoptext
I ran it with the attached Makefile, which produced this output:
ctxtools --purge --all > /dev/null
rm -f q.pdf
texexec --verbose --fast --final q.tex > run.log
Total runs: 4 (counted by grepping run.log for running: pdfetex)
Draftmode runs: 3 (counted by grepping run.log for pdfdraftmode)
TeXExec | runtime: 7.987485
Then I commented out the first line and reran it:
ctxtools --purge --all > /dev/null
rm -f q.pdf
texexec --verbose --fast --final q.tex > run.log
Total runs: 4
Draftmode runs: 0 (just to check)
TeXExec | runtime: 8.307869
So the draftmode saves 4% in the runtime. But the fastest is to not
use the draftmode and not use --final (which causes an extra run).
Maybe I missing a trick, but the draftmode didn't save much time. I
guess I should make the test file read in a few huge images?
-Sanjoy
.PHONY: runit clean
runit: clean
texexec --verbose --fast --final q.tex > run.log
@echo -n "Total runs: " ; grep "running: pdfetex" run.log | wc -l
@echo -n "Draftmode runs: " ; grep "pdfdraftmode enabled" run.log | wc
-l
@grep runtime: run.log
clean:
ctxtools --purge --all > /dev/null
rm -f q.pdf
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
2007/1/3, Aditya Mahajan <[EMAIL PROTECTED]>: > which makes be believe that it will not work for normal cases. > However, how about adding a switch to texexec, say --draft, which > will run the document in draftmode until no more runs are needed, and > will then run a final typesetting run without the draftmode. This may > speed up the execution time for long documents significantly. It helps especially if your document produces a large pdf and/or includes many and/or large images. Best Martin ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
On Tue, 2 Jan 2007, Peter Münster wrote:
> On Tue, 2 Jan 2007, Taco Hoekwater wrote:
>
> >- draftmode: With \pdfdraftmode=1 or the commandline switch -draftmode
> > pdfTeX doesn't write the output pdf and doesn't actually read any
> > images, thus speeding up compilations when you know you need an extra
> > run but don't care about the output, e.g. just to get the BibTeX
> > references right
>
> Hello,
> I'm thinking of "\doifnotmode{*last}{\pdfdraftmode=1}", but how do I ask
> for an additional imposition pass?
Interesting idea. I do not (yet) have pdf-1.40 so I can not test this.
Does it work for "normal" cases? The modes manual says
*last* This mode is set if the last run in a session is taking place.
Normally this is not known in advance, unless one has asked for an
additional imposition pass.
which makes be believe that it will not work for normal cases.
However, how about adding a switch to texexec, say --draft, which
will run the document in draftmode until no more runs are needed, and
will then run a final typesetting run without the draftmode. This may
speed up the execution time for long documents significantly.
Aditya
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
On Tue, 2 Jan 2007, Taco Hoekwater wrote:
>- draftmode: With \pdfdraftmode=1 or the commandline switch -draftmode
> pdfTeX doesn't write the output pdf and doesn't actually read any
> images, thus speeding up compilations when you know you need an extra
> run but don't care about the output, e.g. just to get the BibTeX
> references right
Hello,
I'm thinking of "\doifnotmode{*last}{\pdfdraftmode=1}", but how do I ask
for an additional imposition pass?
Cheers and happy new year!
Peter
--
http://pmrb.free.fr/contact/
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [Fwd: [pdftex] pdftex 1.40]
On Jan 2, 2007, at 3:21 PM, Taco Hoekwater wrote: > Hi, > > The next message probably also is interestering to a few of you that > are not subscribed to the pdftex list. > > Best, Taco Taco and all other pdftex-developers, congratulations on getting version 1.40 ready for the new year! I had been using it since the first betas and never had any problems; it's great that you're going stable. Just one short remark for all those who may want to upgrade to this version: if you use opentype fonts, the .otf files have now to reside under TEXMF/fonts/opentype; right until the last beta, they were (only?) found under TEXMF/fonts/type1, but this is no longer the case. Apart from this, everything seems to be wonderfully stable. And now we all wait for luatex (or for luatools.lua so we can play around with it)... Best wishes Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] [Fwd: [pdftex] pdftex 1.40]
Hi,
The next message probably also is interestering to a few of you that
are not subscribed to the pdftex list.
Best, Taco
Original Message
Subject: [pdftex] pdftex 1.40
Date: Mon, 1 Jan 2007 17:56:59 +0100
From: Martin Schröder <[EMAIL PROTECTED]>
To: PDF-TeX mailing list <[EMAIL PROTECTED]>
http://sarovar.org/download.php/1139/pdftex-1.40.0.tar.bz2
http://sarovar.org/download.php/1140/pdftex-1.40.0.tgz
http://sarovar.org/download.php/1141/pdftex-1.40.0.zip
http://sarovar.org/download.php/1142/pdftex-1.30.6-1.40.0.diff.gz
The pdfTeX team is happy to announce the release of a new stable version:
===
pdfTeX 1.40.0
===
This is the announcement of pdfTeX 1.40.0, an extended version of TeX that
can create PDF directly from TeX source files and enhance the result of TeX
typesetting with the help of PDF.
===
Main changes of pdfTeX 1.40.0
===
- pdfetex (as a separate binary/program) is gone; all extensions are now in
pdftex. The make files still know about the target pdfetex, but it's just
a copy of pdftex
- The sources of TeX, eTeX and pdfTeX have been merged into one file
pdftex.web and one change file pdftex.ch. The sources of TeX and eTeX
distributed are just there for reference
- New features:
- pdfTeX can now generate PDF 1.5 object streams, which leads to smaller
PDFs. This is controlled by setting \pdfobjcompresslevel to a value >0
(3 compress everything, 2 don't compress /Info, 1 also don't compress
embedded PDFs) and works only with PDF >=1.5
- pdfTeX now supports another image file format: JBIG2 files (.jbig2)
- the memory allocated for objects and destination names now grows
dynamically
- pdfTeX now generates smaller PDFs since for char positioning the width
of chars (/Widths) is stored with more precision and so the chars must
rarely be positioned separately
- the PK resolution is now taken from the "pk_dpi" parameter in texmf.cnf
if it has not been set in the format file or by the user
- pdfTeX now removes the generated pdf in case of a fatal error
- pdfTeX now sets /ModDate and /Trapped in the InfoDict by default (the
values can be overridden with \pdfinfo)
- the format of warnings and errors issued by pdfTeX has been changed and
unified
- the output of -version has been extended and now includes information
about the libraries actually used, which can be handy when using shared
libraries
- rules and their positioning on the page are now inside a qQ group
- New primitives:
- pdfTeX can now handle colourstacks.
- \pdfcolorstackinit
A stack is initialized by \pdfcolorstackinit. It expands to the
number of the new stack. The common case, the traditinal color stack
is already initialized as first stack: \pdfcolorstackinit page direct
{0 g 0 G} The keyword "page" means that this stack is page based. At
the start of the new page, the current stack value is automatically
set.
- \pdfcolorstack
\pdfcolorstack push {}
pushes the current value on the stack and sets the .
\pdfcolorstack pop
pops and sets the current stack value.
\pdfcolorstack current
sets the current stack value without changing the stack. This is
useful for stacks that are initialized without keyword "page". Thus
the page start setting can be set manually.
\pdfcolorstack set {}
The current value is set to .
- Transformation matrices can now be manipulated more cleanly:
Currently matrix changes are done and hidden inside \pdfliteral nodes;
pdfTeX doesn't parse its contents and does not know the new settings of
the transform matrix. Thus the new primitives to save pdfTeX from
parsing \pdfliteral contents and to notify pdfTeX about matrix changes
to use them in calculating link and anchor positions.
- \pdfsetmatrix{ }
is the equivalent to \pdfliteral{0 0 cm}
- \pdfsave is the equivalent to \pdfliteral{q}
- \pdfrestore is the equivalent to \pdfliteral{Q}
- \pdfprimitive\TeX-primitive executes the original \TeX-primitive even
if the command has been redefined since. E.g.
\let\relax\undefined\pdfprimitive\relax
expands to \relax.
\ifpdfprimitive\TeX-primitive is true if \TeX-primitive has its
original meaning
- \ifpdfabsnum and \ifpdfabsdim are like \ifnum and \ifdim, but don't
care about negative numbers
- shell escape: if the first character of a filename for \openin,
\openout \input is a pipe symbol (|),
[NTG-context] French spacing and pdfTeX-1.40
Hello,
(it's a repost, in case my previous email got lost...)
my attempt to get correct French spacing before punctuation does no more
work with the latest ConTeXt-beta.
Is there now a new method with pdfTeX-1.40 to get automatically the good
spacing (as announced some months ago)?
Today I try it like this (without success):
%%% module t-french.tex %%%
\def\activateSomeCharacters{%
\defineactivecharacter « {\leftguillemot\,}%% does not work
\defineactivecharacter » {\,\rightguillemot}% % with utf-encoding
%
% \defineactivecharacter ; {\,\lettersemicolon}% % does not work
%
\defineactivecharacter ? {\,\letterquestionmark}% % does not work with
\defineactivecharacter : {\,\lettercolon}% % project/product
\defineactivecharacter ! {\,\letterexclamationmark}}% structure
\startlanguagespecifics[fr]
\activateSomeCharacters
\setupitemize[symbol=2]
\lccode`\'=`\'
\stoplanguagespecifics
\mainlanguage[fr]
\appendtoks\activateSomeCharacters\to\everystarttext
Greetings, Peter
--
http://pmrb.free.fr/contact/
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] French spacing with pdfTeX-1.40 and ConTeXt-beta
Hello,
my attempt to get correct French spacing before punctuation does no more
work with the latest ConTeXt-beta.
Is there now a new method with pdfTeX-1.40 to get automatically the good
spacing?
Today I try it like this (without success):
%%% module t-french.tex %%%
\def\activateSomeCharacters{%
\defineactivecharacter « {\leftguillemot\,}% does not work
\defineactivecharacter » {\,\rightguillemot}% with utf-encoding
%
% \defineactivecharacter ; {\,\lettersemicolon}% does not work
%
\defineactivecharacter ? {\,\letterquestionmark}%does not work with
\defineactivecharacter : {\,\lettercolon}% project/product
\defineactivecharacter ! {\,\letterexclamationmark}}%structure
\startlanguagespecifics[fr]
\activateSomeCharacters
\setupitemize[symbol=2]
\lccode`\'=`\'
\stoplanguagespecifics
\mainlanguage[fr]
\appendtoks\activateSomeCharacters\to\everystarttext
Greetings, Peter
--
http://pmrb.free.fr/contact/
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] pdfTeX-1.40 does not find format
� wrote: > > Does "not downward compatible" mean, that there are other more serious > issues? > each year downward compatibily has someho wbeen broken (changes in binaries, tds, font names; but by now texmfstart/texexec should catch such problems) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] pdfTeX-1.40 does not find format
On Wed, 1 Nov 2006, Hans Hagen wrote: > pdfetex is no longer valid, it's pdftex now (includes etex); so. remove > any trace of pdfetex, take the latest texexec, adn regenerate the formats Hello Hans, this is exactly what I did: I removed bin/pdfetex and web2c/pdfetex.pool and then "texexec --make --all" puts its format to web2c/pdfetex/cont-en.fmt It's texexec from ConTeXt-2006.10.27 > (in this respect 1.40 is not downward compatible with tex live) Do you mean TeX live 2005 or the development version (svn-head)? Does "not downward compatible" mean, that there are other more serious issues? Cheers, Peter -- http://pmrb.free.fr/contact/ ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] pdfTeX-1.40 does not find format
� wrote:
> Hello,
>
> I try to use the beta versions of ConTeXt and pdfTeX now and I find the
> following issue (on latest TeX-live):
> with "TEXFORMATS = .;$TEXMF/web2c/{$engine,}" in texmf.cnf and
> pdfTeX-1.40.XXX, texexec --make writes the formats to
> texmf-config/web2c/pdfetex but pdftex looks only into texmf-config/web2c
> A symbolic link from texmf-config/web2c/cont-en.fmt to pdfetex/cont-en.fmt
> solves the problem.
>
> Is this issue already known and is there perhaps a better solution?
>
pdfetex is no longer valid, it's pdftex now (includes etex); so. remove any
trace of pdfetex, take the latest texexec, adn regenerate the formats
(in this respect 1.40 is not downward compatible with tex live)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] pdfTeX-1.40 does not find format
Hello,
I try to use the beta versions of ConTeXt and pdfTeX now and I find the
following issue (on latest TeX-live):
with "TEXFORMATS = .;$TEXMF/web2c/{$engine,}" in texmf.cnf and
pdfTeX-1.40.XXX, texexec --make writes the formats to
texmf-config/web2c/pdfetex but pdftex looks only into texmf-config/web2c
A symbolic link from texmf-config/web2c/cont-en.fmt to pdfetex/cont-en.fmt
solves the problem.
Is this issue already known and is there perhaps a better solution?
Cheers, Peter
--
http://pmrb.free.fr/contact/
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Newbie question: Different PDF-output with pdftex versus tex - ghostscript
2006/10/1, Robert Kroon <[EMAIL PROTECTED]>: > v2.09 as text editor. When I generate output with the pdftex default > script I get a pdf-file with poor letter quality (thick p's and t's > and j's). Also the combination of the characters ij are shown as .. > in the pdf-file. When I switch to the default Texshopscript "tex + > ghostscipt" I'll get a dvi-file. Double-clicking on this file > generates a PDF-file with high quality characters and the ij characters. > Apparently there is something wrong in my setup. Does this help? http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3 http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1 Best Martin ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Newbie question: Different PDF-output with pdftex versus tex - ghostscript
Hi, I've installed Tex and Context on my Mac through II-installer and started to experiment with simple Context files. I'm using Texshop v2.09 as text editor. When I generate output with the pdftex default script I get a pdf-file with poor letter quality (thick p's and t's and j's). Also the combination of the characters ij are shown as .. in the pdf-file. When I switch to the default Texshopscript "tex + ghostscipt" I'll get a dvi-file. Double-clicking on this file generates a PDF-file with high quality characters and the ij characters. Apparently there is something wrong in my setup. Any ideas? Many thanks in advance, Robert Kroon ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Hi! On Fri, 11 Aug 2006, Taco Hoekwater wrote: > Andreas Schneider wrote: >> Thanks a lot, with that it works now (with the texnansi encoding)! These >> facts should be mentioned in the docs. > > The next version of texfont will create a dvips and dvipdfmx map file > as well as a pdftex one, making life a bit easier. Good! >> But gv gives an error when I try to view the ps file: >> >> Error: /undefined in ECEncoding > > This is error is because lm-ec.enc does not name its encoding > "ECEncoding " but "enclmec", so you have to change the ReEncode > strings in the map file. Ah, thanks again, with that it now works perfectly. Andreas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Andreas Schneider wrote: > Thanks a lot, with that it works now (with the texnansi encoding)! These > facts should be mentioned in the docs. The next version of texfont will create a dvips and dvipdfmx map file as well as a pdftex one, making life a bit easier. > But gv gives an error when I try to view the ps file: > > Error: /undefined in ECEncoding This is error is because lm-ec.enc does not name its encoding "ECEncoding " but "enclmec ", so you have to change the ReEncode strings in the map file. Best, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Tue, 8 Aug 2006, Taco Hoekwater wrote: > This process works in a similar fashion for all programs like > pdftex, dvipdfmx, dvips, and xdvi, but texfont only creates a > map file for pdftex. Unf, the pdftex map file cannot be used by > dvips, so for dvips you have to create your own (like you did). > > When you create a map file for dvips for a texfont-installed > font family, it needs to have those *-raw-* entries that will > map the fonts to the real postscript font files on your harddisk, > and those were missing from your bgj.map. > > Using the attached map file fragment, I can create a postscript file > that has fi ligatures of your example in texnansi encoding using > dvips. I have no xdvi here to try it, but that should work as well. Thanks a lot, with that it works now (with the texnansi encoding)! These facts should be mentioned in the docs. I also have created another map file ec-bgj.map with the entries ec-raw-bgjb ElegantGaramondBT-Bold "ECEncoding ReEncodeFont" schrift.ps . [1] But gv gives an error when I try to view the ps file: Error: /undefined in ECEncoding Operand stack: Fa 139 --nostringval-- 29 13 --nostringval-- 28 38 101 --nostringval-- 3 91.3242 --nostringval-- 91.3242 0 Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:1051/1123(ro)(G)-- --dict:0/20(G)-- --dict:73/200(L)-- --dict:80/300(L)-- --dict:10/12(L)-- Current allocation mode is local Last OS error: 2 GPL Ghostscript 8.01: Unrecoverable error, exit code 1 My printer does not print it either. Maybe the reason is that I use lm-ec.enc, but ECEncoding is defined in EC.enc which is slightly different. > The second problem: > > texfont simply does not 'do' EC correctly (at least not on my machine). > There are simply no fi ligatures, not in pdftex either. I will > investigate this further. On my machine the font works without problems with pdftex (texexec --pdf) and the ec encoding, ligatures and umlauts are okay. Andreas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Aug 9, 2006, at 4:52 PM, Hans Hagen wrote: > i see, interesting; before we do that, can you check if we can/need to > do the same with texnansi, qx, etc ? > > Hans texnansi is OK, in my experience, and qx as well. t5 also has some LIGKERN instructions at the beginning, but doesn't have f-ligatures in its character set, AFAICS, so this should work as well. I can run some texts this weekend (if you want) and see what comes up. Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Thomas A. Schmitz wrote: > And for the LIGKERN: yes, I asked about them on the tex-fonts list a > while ago, and nobody considered them a problem. IMHO, they're > totally useless or even worse, but I received the same ol' answers: > can't change that, it's legacy etc. I think Mojca knows something > indeed, not even broken things are fixed; i wonner what those ol' users are doing with their patterns since i expect an update in patterns to have more consequences than a fix in fonts > about this as well. So my suggestion would be: make ec a synonym for > lm-ec in texfont (but then, because of one or to glyphnames, lm- > ec.enc has to be in the mapfile as well). > i see, interesting; before we do that, can you check if we can/need to do the same with texnansi, qx, etc ? Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Aug 9, 2006, at 3:58 PM, Taco Hoekwater wrote: >> I've experimented with afm2pl, and as I wrote in an earlier mail: the >> beginning of EC.enc with its additional LIGKERN instructions confuses >> it so it will not include default ligatures. > > As it turns out, this is the same for afm2tfm. And to make matters > even more confusing, I had the following problem: At one point, > I had copied EC.enc to the current directory and fixed it. However, > it still didn't work, because: > >[EMAIL PROTECTED] new]$ ls *.enc >EC.enc > >[EMAIL PROTECTED] new]$ kpsewhich --progname=dvips ec.enc >/opt/tex/teTeX/texmf/fonts/enc/dvips/base/EC.enc > > because of a line in /opt/tex/teTeX/texmf/aliases :-/ > > > > Either way, it seems that this LIGKERN interpretation that > overrules the afm file is actually considered a feature. The > sane way out seems to be to ship our own encoding files in > >fonts/enc/texfont > > or so. > > Taco Yes, I have a dim recollection that afm2tfm has the same problem. Isn't lm-ec.enc the better choice anyway? Couldn't we make texfont default to lm-ec.enc when it is called with --en=EC? And for the LIGKERN: yes, I asked about them on the tex-fonts list a while ago, and nobody considered them a problem. IMHO, they're totally useless or even worse, but I received the same ol' answers: can't change that, it's legacy etc. I think Mojca knows something about this as well. So my suggestion would be: make ec a synonym for lm-ec in texfont (but then, because of one or to glyphnames, lm- ec.enc has to be in the mapfile as well). Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Taco Hoekwater wrote: > because of a line in /opt/tex/teTeX/texmf/aliases :-/ > > ah, the dreadful aliases file ... in tex live they're gone ; let's hope that this aliases fiel does not contain anything related to context tex files (patterns for instance) > > Either way, it seems that this LIGKERN interpretation that > overrules the afm file is actually considered a feature. The > sane way out seems to be to ship our own encoding files in > >fonts/enc/texfont > > or so. > hm, we can let texfont search for a texfont-ec file first (the map file can still refer to the normal one i suppose) (an alternative is to let texfont copy the ec.enc file to the local path, remove the messy lines, and remove that one afterwards) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Thomas A. Schmitz wrote: > On Aug 8, 2006, at 11:57 PM, Taco Hoekwater wrote: > > >>>how does -afmpl perform? i always suspected afm2tfm not to take non >>>existing ligs into account >> >>Just as bad (here, at least). I'll get back to you about this >>tomorrow, >>it is too late for me to do serious work. >> > > > I've experimented with afm2pl, and as I wrote in an earlier mail: the > beginning of EC.enc with its additional LIGKERN instructions confuses > it so it will not include default ligatures. As it turns out, this is the same for afm2tfm. And to make matters even more confusing, I had the following problem: At one point, I had copied EC.enc to the current directory and fixed it. However, it still didn't work, because: [EMAIL PROTECTED] new]$ ls *.enc EC.enc [EMAIL PROTECTED] new]$ kpsewhich --progname=dvips ec.enc /opt/tex/teTeX/texmf/fonts/enc/dvips/base/EC.enc because of a line in /opt/tex/teTeX/texmf/aliases :-/ Either way, it seems that this LIGKERN interpretation that overrules the afm file is actually considered a feature. The sane way out seems to be to ship our own encoding files in fonts/enc/texfont or so. Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Hans Hagen wrote: >> > > well, we can consider to let texfont use a ec-fixed encoding for > afm2tfm and the regular ec encoding for the rest > > --afmencoding=ec-fixed > > or so or fix afm2pl. > > for a while afm2pl was the default, but then it suddenly defaulted to > latex default (em) spacing which ruined a project here because that > went unnoticed and resulted in incompatible output, so it made me > more careful; i'm not sure to what extend afm2pl uses the same > default for the fontdimen related things as afm2tfm from the afm2pl documentation: -f font_dimensions afm2tfm compatible settings would be something like -f 300,100,0,1000, But as of 0.702 -f afm2tfm is also accepted Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Thomas A. Schmitz wrote: > On Aug 8, 2006, at 11:57 PM, Taco Hoekwater wrote: > > >>> how does -afmpl perform? i always suspected afm2tfm not to take non >>> existing ligs into account >>> >> Just as bad (here, at least). I'll get back to you about this >> tomorrow, >> it is too late for me to do serious work. >> >> > > I've experimented with afm2pl, and as I wrote in an earlier mail: the > beginning of EC.enc with its additional LIGKERN instructions confuses > well, we can consider to let texfont use a ec-fixed encoding for afm2tfm and the regular ec encoding for the rest --afmencoding=ec-fixed or so > it so it will not include default ligatures. If you delete this, it > will work. If you use lm-ec.enc (which has a number of mistakes fixed > anyway), it works. BUT afm2pl needs a file default.lig which is not > present in all TeX distributions. I asked Siep a couple of months > ago, and he replied there was a switch to ignore default.lig, but in > she > that case, the default ligs would have to be supplied by texfont > itself (which should be doable). IMHO, texfont should switch to > afm2pl by default; it's much better at preserving kerning information > (Adam, any thoughts on this?), and it makes virtual fonts > unnecessary. I now use it regularly for all my font needs and am very > satisfied with it. > for a while afm2pl was the default, but then it suddenly defaulted to latex default (em) spacing which ruined a project here because that went unnoticed and resulted in incompatible output, so it made me more careful; i'm not sure to what extend afm2pl uses the same default for the fontdimen related things as afm2tfm Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Aug 8, 2006, at 11:57 PM, Taco Hoekwater wrote: >> how does -afmpl perform? i always suspected afm2tfm not to take non >> existing ligs into account > > Just as bad (here, at least). I'll get back to you about this > tomorrow, > it is too late for me to do serious work. > I've experimented with afm2pl, and as I wrote in an earlier mail: the beginning of EC.enc with its additional LIGKERN instructions confuses it so it will not include default ligatures. If you delete this, it will work. If you use lm-ec.enc (which has a number of mistakes fixed anyway), it works. BUT afm2pl needs a file default.lig which is not present in all TeX distributions. I asked Siep a couple of months ago, and he replied there was a switch to ignore default.lig, but in that case, the default ligs would have to be supplied by texfont itself (which should be doable). IMHO, texfont should switch to afm2pl by default; it's much better at preserving kerning information (Adam, any thoughts on this?), and it makes virtual fonts unnecessary. I now use it regularly for all my font needs and am very satisfied with it. Best Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Hans Hagen wrote: > Taco Hoekwater wrote: > >>The second problem: >> >>texfont simply does not 'do' EC correctly (at least not on my machine). >>There are simply no fi ligatures, not in pdftex either. I will >>investigate this further. > > how does -afmpl perform? i always suspected afm2tfm not to take non > existing ligs into account Just as bad (here, at least). I'll get back to you about this tomorrow, it is too late for me to do serious work. Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Taco Hoekwater wrote: > > > When you create a map file for dvips for a texfont-installed > font family, it needs to have those *-raw-* entries that will > map the fonts to the real postscript font files on your harddisk, > and those were missing from your bgj.map. the reason why i create the map files the way we do is that i want to prevent pdftex to be too clever in sharing font resources (thre are versions out there that assume sequivalent "Names" to always equivalent which is not always true (think of slanted or extended fonts) (i've been bitten too often by that so i play safe) it is no problem to add that entry optionally (grep for cleanfont in texexec.pl; to tired to see the light now) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Taco Hoekwater wrote: > > The second problem: > > texfont simply does not 'do' EC correctly (at least not on my machine). > There are simply no fi ligatures, not in pdftex either. I will > investigate this further. how does -afmpl perform? i always suspected afm2tfm not to take non existing ligs into account Hans -- - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Hi Andreas, Andreas Schneider wrote: On Tue, 8 Aug 2006, Taco Hoekwater wrote: Somehow you yourself (and not texfont!) have created a font map file called bgj.map for dvips, and that file is wrong. Hmm, I have created it just for LaTeX. Since it contains only entries for ec-bgj* (without 'raw') it should not interfere with the other mapfiles (created by texfont) which are for ec-raw-bgj* and texnansi-raw-bgj* (with 'raw'), or am I mistaken? Anyway xdvi complains about texnansi-raw-bgj* (see example below which I had already included in one of my previous mails). There are two problems that I can see. There is only one that you can fix, and there is another problem that is a base texfont issue. The fixable problem first: If there is a virtual font, then dvi processors will recursively break it down into its constituents (those are the *-raw-* font metrics). Eventually, when there are no longer virtual fonts to resolve, it looks for the 'base' fonts in its map file. This process works in a similar fashion for all programs like pdftex, dvipdfmx, dvips, and xdvi, but texfont only creates a map file for pdftex. Unf, the pdftex map file cannot be used by dvips, so for dvips you have to create your own (like you did). When you create a map file for dvips for a texfont-installed font family, it needs to have those *-raw-* entries that will map the fonts to the real postscript font files on your harddisk, and those were missing from your bgj.map. Using the attached map file fragment, I can create a postscript file that has fi ligatures of your example in texnansi encoding using dvips. I have no xdvi here to try it, but that should work as well. The second problem: texfont simply does not 'do' EC correctly (at least not on my machine). There are simply no fi ligatures, not in pdftex either. I will investigate this further. Taco texnansi-raw-bgjb ElegantGaramondBT-Bold"TeXnANSIEncoding ReEncodeFont" ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Tue, 8 Aug 2006, Taco Hoekwater wrote: Somehow you yourself (and not texfont!) have created a font map file called bgj.map for dvips, and that file is wrong. Hmm, I have created it just for LaTeX. Since it contains only entries for ec-bgj* (without 'raw') it should not interfere with the other mapfiles (created by texfont) which are for ec-raw-bgj* and texnansi-raw-bgj* (with 'raw'), or am I mistaken? Anyway xdvi complains about texnansi-raw-bgj* (see example below which I had already included in one of my previous mails). Andreas - \setuppapersize[A4][A4] \mainlanguage[de] \language[de] \enableregime[windows] \setupencoding[default=texnansi] \usetypescriptfile[type-eleggar] \usetypescript[eleggar] \setupbodyfont[eleggar,11pt] \setupbodyfontenvironment[default][em=italic] \starttext Einige Zeichen: "`, "', --, "<, "> Ligaturen: fi, fl, ff, ffi, ffl Aufgelöste Ligaturen: f"|i, f"|l Umlaute: ä, ö, ü, ß, Ä, Ö, Ü; "a, "o, "u, "s \stoptext - xdvi.bin: Warning: Character 228 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 132 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 147 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 150 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 12 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 8 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 246 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 252 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 223 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 214 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 220 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace.___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Andreas Schneider wrote: > On Tue, 8 Aug 2006, Hans Hagen wrote: > >>if the problem is in a font not having glyphs, you can consider making a >>special encoding vector + enco-* file; not that complex since one can >>start with an existing one > > > The problem is that it does work with pdftex (tex -> pdf via > texexec --pdf), but it does NOT work with tex -> dvi -> ps via > texexec, dvips (some glyphs, such as ligatures and umlauts, don't > work in the latter case). It should be possible to get it working, > as fontinst is able to do it, so I don't know why I should need an > extra encoding. Somehow you yourself (and not texfont!) have created a font map file called bgj.map for dvips, and that file is wrong. Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Tue, 8 Aug 2006, Hans Hagen wrote: > if the problem is in a font not having glyphs, you can consider making a > special encoding vector + enco-* file; not that complex since one can > start with an existing one The problem is that it does work with pdftex (tex -> pdf via texexec --pdf), but it does NOT work with tex -> dvi -> ps via texexec, dvips (some glyphs, such as ligatures and umlauts, don't work in the latter case). It should be possible to get it working, as fontinst is able to do it, so I don't know why I should need an extra encoding. Andreas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: font only works with pdftex
Andreas Schneider wrote: > On Mon, 7 Aug 2006, Hans Hagen wrote: > >> since you're typesetting german ... why not using the texnansi encoding >> instead of the flawed ec encoding? >> > > The problem is that it doesn't work with the texnansi encoding either. > See my last mails. > if the problem is in a font not having glyphs, you can consider making a special encoding vector + enco-* file; not that complex since one can start with an existing one Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: font only works with pdftex
On Mon, 7 Aug 2006, Hans Hagen wrote: > since you're typesetting german ... why not using the texnansi encoding > instead of the flawed ec encoding? The problem is that it doesn't work with the texnansi encoding either. See my last mails. Andreas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Mon, 7 Aug 2006, Taco Hoekwater wrote: Andreas Schneider wrote: but xdvi gives error messages like [...] My guess is that you have to copy the final file you used to the folder where dvips (and xdvi, which looks in the same place normally) looks for encoding files. I created a symlink in my private texmf tree (ec.enc -> lm-ec.enc) and ran texhash, and after that it was all the same. Anyway, this would not explain why I have the same symptom with the texnansi encoding, too. Maybe it helps debugging that dvips gives different error messages: This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2006.08.07:1402' -> schrift.ps <8r.enc>. Warning: module writet1 of dvips (file bgjr.pfb): glyph `pi' undefined Warning: module writet1 of dvips (file bgjr.pfb): glyph `product' undefined Warning: module writet1 of dvips (file bgjr.pfb): glyph `ffl' undefined Warning: module writet1 of dvips (file bgjr.pfb): glyph `ffi' undefined Warning: module writet1 of dvips (file bgjr.pfb): glyph `ff' undefined Warning: module writet1 of dvips (file bgjr.pfb): glyph `dotlessj' undefined [1] Also I get a slightly different result: With gv I can see some umlauts in the postscript file (ä, ö, ü work, but ß does not). Instead of the ligatures there are only spaces. Andreas___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] What about Lua in pdftex ?
luigi scarso wrote: > What about Lua in pdftex ? > you may expect around the end of the year; i'm currently playing with some alphaware in order to explore possibilities and interfacing needs -) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] What about Lua in pdftex ?
What about Lua in pdftex ? ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] TeX i-Package updated, Easy Mac font support for PDFTeX
The TeX i-Package has been updated. It now contains support for
several Mac fonts using the gtamacfonts package. Both LaTeX and
ConTeXt are supported. Note: only PDFTeX (not TeX+dvips) is
supported. PS trickery like font expansion and pstricks is not
supported. This is all because of the formats of the fonts (truetype).
Apple ships the fonts packed in socalled "font suit cases". PDFTeX
can only use the fonts unpacked. To unpack them a tool called fondu
can be used. There is an i-Package for fondu. If fondu is installed
*before* TeX is installed, the TeX i-Package will automatically
unpack the Mac fonts in the right TeX directory. Note that
distributing the Apple fonts (packed or unpacked) is a breach of
copyright, hence I do not distribute the fonts and nor should you.
After installing fondu and TeX, you can us it like this:
To use these fonts with LaTeX, put e.g. the following in your file:
\usepackage[T1]{fontenc}
\usepackage{gtamachoefler}
Such a style file will make Hoefler Text the serif (roman) text font
and Gill Sans the sans serif font. The following basic styles are
available:
gtamacbaskerville.sty
gtamacdidot.sty
gtamacgeorgia.sty
gtamachoefler.sty
There are more. See the manual for details. For the same effect using
ConTeXt, enter e.g.:
\usetypescriptfile[type-gtamacfonts]
\usetypescript[Hoefler][ec]
\setupbodyfont[Hoefler,12pt]
Support for ConTeXt is better than support for LaTeX for the simple
reason that ConTeXt is more powerful.
Example documents and a manual can be found in the texmf.gwtex/doc/
fonts/gtamacfonts subdirectory. To get the manual you can type
"texdoc gtamacfonts" in a Terminal window. Also check out "texdoc
GTAHoeflerSymbols" in a Terminal window.
G
PS. I expect to do one more update with this with some changes to the
manual and such, but nothing fundamental.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
Hi Hans and Hans, Hans Hagen wrote: Hans van der Meer wrote: I use (as root: sudo) the following shell script to install the latest pdfetex. For me it works. It might be of use to you. #!/bin/sh echo "Installing Pdftex..." umask 022 unzip pdftex-1.30.4.zip cd pdftex-1.30.4 sh ./Build cp -f build/texk/web2c/pdftex `which pdftex` cp -f build/texk/web2c/pdftex.pool `kpsewhich pdftex.pool` no need for pdftex, is kind of obsolete, and afaik pdfetex is always the default Yes. I will remove these two lines from the wiki page as well. cp -f build/texk/web2c/pdfetex `which pdfetex` which -> kpsewhich No, "which" is correct. You want to replace the executable pdfetex that is in the path. On all distributions (except the minimal zips), the bin tree is outside of kpsewhich scope. cp -f build/texk/web2c/pdfetex.pool `kpsewhich pdfetex.pool` chown -R root:wheel /usr/local/teTeX what is this wheel thing? The "wheel" user group is a unix security measure (of sorts). chmod -R u+w /usr/local/teTeX chmod -R a+r /usr/local/teTeX why not make that place independent as well? Hans is chmodding the directory, not the executable. I'm doubt these chown/chmod lines are really needed after each update of pdfetex (the will only do something the first time the script is run). It looks to me like you had a rather peculiar umask in effect when you installed teTeX 3.0. Cheers, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
Hans van der Meer wrote: I use (as root: sudo) the following shell script to install the latest pdfetex. For me it works. It might be of use to you. #!/bin/sh echo "Installing Pdftex..." umask 022 unzip pdftex-1.30.4.zip cd pdftex-1.30.4 sh ./Build cp -f build/texk/web2c/pdftex `which pdftex` cp -f build/texk/web2c/pdftex.pool `kpsewhich pdftex.pool` no need for pdftex, is kind of obsolete, and afaik pdfetex is always the default cp -f build/texk/web2c/pdfetex `which pdfetex` which -> kpsewhich cp -f build/texk/web2c/pdfetex.pool `kpsewhich pdfetex.pool` chown -R root:wheel /usr/local/teTeX what is this wheel thing? chmod -R u+w /usr/local/teTeX chmod -R a+r /usr/local/teTeX why not make that place independent as well? chmod -R u+w `which pdfetex` `which pdfetex.pool` umask 027 cd .. echo "Installing Pdftex done." exit wikiable Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
On 11/29/05, Hans van der Meer <[EMAIL PROTECTED]> wrote: > I use (as root: sudo) the following shell script to install the > latest pdfetex. For me it works. It might be of use to you. > > #!/bin/sh > echo "Installing Pdftex..." > umask 022 > unzip pdftex-1.30.4.zip > cd pdftex-1.30.4 > sh ./Build > cp -f build/texk/web2c/pdftex `which pdftex` > cp -f build/texk/web2c/pdftex.pool `kpsewhich pdftex.pool` > cp -f build/texk/web2c/pdfetex `which pdfetex` > cp -f build/texk/web2c/pdfetex.pool `kpsewhich pdfetex.pool` ok > chown -R root:wheel /usr/local/teTeX > chmod -R u+w /usr/local/teTeX > chmod -R a+r /usr/local/teTeX > umask 027 I can not understand these commands. Why need that ? > cd .. > echo "Installing Pdftex done." > exit Why not add command "fmtutil-sys --refresh" at end of your script ? -- http://vnoss.org Vietnamese Open Source Software Community ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
I use (as root: sudo) the following shell script to install the
latest pdfetex. For me it works. It might be of use to you.
#!/bin/sh
echo "Installing Pdftex..."
umask 022
unzip pdftex-1.30.4.zip
cd pdftex-1.30.4
sh ./Build
cp -f build/texk/web2c/pdftex `which pdftex`
cp -f build/texk/web2c/pdftex.pool `kpsewhich pdftex.pool`
cp -f build/texk/web2c/pdfetex `which pdfetex`
cp -f build/texk/web2c/pdfetex.pool `kpsewhich pdfetex.pool`
chown -R root:wheel /usr/local/teTeX
chmod -R u+w /usr/local/teTeX
chmod -R a+r /usr/local/teTeX
umask 027
cd ..
echo "Installing Pdftex done."
exit
yours sincerely,
dr. H. van der Meer
On Nov 28, 2005, at 21:51, Thomas A. Schmitz wrote:
I have once tried to set up TeX on gentoo, and found this to be the
most complicated and least user-friendly distribution I have ever
seen. There's a bunch of texmf-trees in all kinds of bizarre
locations, and a symlink farm in /etc like you wouldn't believe,
and there's not a shred of documentation to be seen anywhere. So
they make everything as complex as possible, but the TeX binaries
are simply dumped into /usr/bin, so the only way to update is via
the emerge system. But enough of this rant: be careful to figure
out what cnf file is a symlink and which one is "real." They have
an entire web2c tree in /etc/conf.d/texmf, if memory serves right,
and the cnf files are regenerated from texmf.d/00texmf.cnf or
somesuch, so this is the file you need to modify. But in the end,
you may find it's not worth the trouble: just unmerge tetex and
install a vanilla teTeX system.
Best
Thomas
On Nov 28, 2005, at 9:05 PM, Nikolai Weibull wrote:
Taco Hoekwater wrote:
Nikolai Weibull wrote:
I've followed the instructions listed at
http://wiki.contextgarden.net/TeTeX_3.0_installation, but it won't
quite give. The problem is that I use the Gentoo installation
setup
as a base and have the latest ConTeXt installed in /usr/local/
share.
Does anyone know what options to pass to pdftex's configure-script
to match the setup on a Gentoo system (where stuff is stored in
/etc/texmf and /var/lib/texmf)?
It would be simplest (and definately justified) to ask this to the
Gentoo maintainer, because (s)he has apparently succeeded in setting
that up (Gentoo's trees seem to bear only a passing resemblance to
teTeX and would be more accurately called Gentoo-TeX).
Sadly, there's no separate pdfetex ebuild for Gentoo. If there
was, I
wouldn't have to mess with this :-).
My best guess: find the non-etc version of texmf.cnf (I'm fairly
certain there is one), and attempt to pass the root of texmf tree
that contains it as --datadir to the configure script.
Yes, there's one in /var/lib/texmf/web2c. The reason for this
layout is
to separate architecture-dependent files and non-architecture-
dependent
files. I can't say that the added complexity justify this
separation.
nikolai
--
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
Hi, Nikolai Weibull wrote: The only texmf.cnf lives in /etc/texmf.cnf; other are symlinks to it. Do you have a symlink in /etc/share/texmf/web2c as well? Well, I have with a standard-SUSE-10.0 teTeX only /etc/texmf/web2c/texmf.cnf and neither of those others. To find the texmf.cnf, which TeX uses, enter: kpsewhich texmf.cnf (gives here: /usr/share/texmf/web2c/texmf.cnf) to find the real file (you can also edit the symlink, actually), use readlink: readlink -f `kpsewhich texmf.cnf` (gives here: "/etc/texmf/web2c/texmf.cnf", the symlink above is actually "../../../../etc/texmf/web2c/texmf.cnf") Tobias ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
A las 19:43 del mar 29 nov, Nikolai Weibull tuvo a bien escribir:
> Jose Antonio Rodriguez wrote:
>
> > After some try and swear...
>
> I know how that goes :-(
>
> > $ diff Build Build~
> > 69c69
> > < (cd texk/web2c; $MAKE texmf=${TEXMF_PATH:-/usr/share/texmf} pdftex
> > pdfetex) || exit 1
> > ---
> > > (cd texk/web2c; $MAKE pdftex pdfetex || exit 1) || exit 1
> >
> > When it compiles, just copy pdfetex to /usr/bin, and the *.fmt and
> > *.pool to /var/lib/texmf/web2c - this is where formats live.
>
> OK, thanks, I'll try that.
>
> > The only texmf.cnf lives in /etc/texmf.cnf; other are symlinks to it.
>
> Do you have a symlink in /etc/share/texmf/web2c as well?
>
> nikolai
>
Sorry, I made a typo:
$ locate texmf.cnf
/etc/texmf/web2c/texmf.cnf # real; make a backup!
/etc/texmf/texmf.d/00texmf.cnf
-- forget it - just a template, it'll overwrite your when
updating
/usr/share/texmf/web2c/texmf.cnf-- link
/var/lib/texmf/web2c/texmf.cnf -- link
I just compiled and installed pdftex 1.30.4 without problems.
But to be safe, in the Build script include "--prefix=/usr" in the
config options if you have the main tree in /usr/share/texmf.
You'll also have a ~/.texmf-var - this is where I put the ConTeXt files.
As in the wiki, you have to run fmtutil-sys --refresh afterwards
Luck
--
José Antonio Rodríguez
[EMAIL PROTECTED]
'El Fuego vive en los corazones de quienes aman el futuro' (Agni Yoga)
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
Jose Antonio Rodriguez wrote:
> After some try and swear...
I know how that goes :-(
> $ diff Build Build~
> 69c69
> < (cd texk/web2c; $MAKE texmf=${TEXMF_PATH:-/usr/share/texmf} pdftex pdfetex)
> || exit 1
> ---
> > (cd texk/web2c; $MAKE pdftex pdfetex || exit 1) || exit 1
>
> When it compiles, just copy pdfetex to /usr/bin, and the *.fmt and
> *.pool to /var/lib/texmf/web2c - this is where formats live.
OK, thanks, I'll try that.
> The only texmf.cnf lives in /etc/texmf.cnf; other are symlinks to it.
Do you have a symlink in /etc/share/texmf/web2c as well?
nikolai
--
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
A las 19:03 del lun 28 nov, Nikolai Weibull tuvo a bien escribir:
> I've followed the instructions listed at
> http://wiki.contextgarden.net/TeTeX_3.0_installation, but it won't quite
> give. The problem is that I use the Gentoo installation setup as a base
> and have the latest ConTeXt installed in /usr/local/share. Does anyone
> know what options to pass to pdftex's configure-script to match the
> setup on a Gentoo system (where stuff is stored in /etc/texmf and
> /var/lib/texmf)?
>
> Thanks.
>
> nikolai
>
I have built pdftex-1.30.3 following the wiki on a Gentoo box - which is
what I use. After some try and swear, changing this line in the Build
script of the pdftex dist, made it work:
$ diff Build Build~
69c69
< (cd texk/web2c; $MAKE texmf=${TEXMF_PATH:-/usr/share/texmf} pdftex pdfetex)
|| exit 1
---
> (cd texk/web2c; $MAKE pdftex pdfetex || exit 1) || exit 1
When it compiles, just copy pdfetex to /usr/bin, and the *.fmt and
*.pool to /var/lib/texmf/web2c - this is where formats live.
The only texmf.cnf lives in /etc/texmf.cnf; other are symlinks to it.
--
José Antonio Rodríguez
[EMAIL PROTECTED]
'El Fuego vive en los corazones de quienes aman el futuro' (Agni Yoga)
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
I have once tried to set up TeX on gentoo, and found this to be the
most complicated and least user-friendly distribution I have ever
seen. There's a bunch of texmf-trees in all kinds of bizarre
locations, and a symlink farm in /etc like you wouldn't believe, and
there's not a shred of documentation to be seen anywhere. So they
make everything as complex as possible, but the TeX binaries are
simply dumped into /usr/bin, so the only way to update is via the
emerge system. But enough of this rant: be careful to figure out what
cnf file is a symlink and which one is "real." They have an entire
web2c tree in /etc/conf.d/texmf, if memory serves right, and the cnf
files are regenerated from texmf.d/00texmf.cnf or somesuch, so this
is the file you need to modify. But in the end, you may find it's not
worth the trouble: just unmerge tetex and install a vanilla teTeX
system.
Best
Thomas
On Nov 28, 2005, at 9:05 PM, Nikolai Weibull wrote:
Taco Hoekwater wrote:
Nikolai Weibull wrote:
I've followed the instructions listed at
http://wiki.contextgarden.net/TeTeX_3.0_installation, but it won't
quite give. The problem is that I use the Gentoo installation setup
as a base and have the latest ConTeXt installed in /usr/local/share.
Does anyone know what options to pass to pdftex's configure-script
to match the setup on a Gentoo system (where stuff is stored in
/etc/texmf and /var/lib/texmf)?
It would be simplest (and definately justified) to ask this to the
Gentoo maintainer, because (s)he has apparently succeeded in setting
that up (Gentoo's trees seem to bear only a passing resemblance to
teTeX and would be more accurately called Gentoo-TeX).
Sadly, there's no separate pdfetex ebuild for Gentoo. If there was, I
wouldn't have to mess with this :-).
My best guess: find the non-etc version of texmf.cnf (I'm fairly
certain there is one), and attempt to pass the root of texmf tree
that contains it as --datadir to the configure script.
Yes, there's one in /var/lib/texmf/web2c. The reason for this
layout is
to separate architecture-dependent files and non-architecture-
dependent
files. I can't say that the added complexity justify this separation.
nikolai
--
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
Taco Hoekwater wrote:
> Nikolai Weibull wrote:
> > I've followed the instructions listed at
> > http://wiki.contextgarden.net/TeTeX_3.0_installation, but it won't
> > quite give. The problem is that I use the Gentoo installation setup
> > as a base and have the latest ConTeXt installed in /usr/local/share.
> > Does anyone know what options to pass to pdftex's configure-script
> > to match the setup on a Gentoo system (where stuff is stored in
> > /etc/texmf and /var/lib/texmf)?
> It would be simplest (and definately justified) to ask this to the
> Gentoo maintainer, because (s)he has apparently succeeded in setting
> that up (Gentoo's trees seem to bear only a passing resemblance to
> teTeX and would be more accurately called Gentoo-TeX).
Sadly, there's no separate pdfetex ebuild for Gentoo. If there was, I
wouldn't have to mess with this :-).
> My best guess: find the non-etc version of texmf.cnf (I'm fairly
> certain there is one), and attempt to pass the root of texmf tree
> that contains it as --datadir to the configure script.
Yes, there's one in /var/lib/texmf/web2c. The reason for this layout is
to separate architecture-dependent files and non-architecture-dependent
files. I can't say that the added complexity justify this separation.
nikolai
--
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Building and installing pdftex 1.30 on teTeX 3.0
On 11/28/05, Nikolai Weibull <[EMAIL PROTECTED]> wrote: > I've followed the instructions listed at > http://wiki.contextgarden.net/TeTeX_3.0_installation, but it won't quite > give. The problem is that I use the Gentoo installation setup as a base > and have the latest ConTeXt installed in /usr/local/share. Does anyone > know what options to pass to pdftex's configure-script to match the > setup on a Gentoo system (where stuff is stored in /etc/texmf and > /var/lib/texmf)? The simple way, IMHO, is to build teTeX into /usr/local/teTeX. After finished all, you need put "/usr/local/teTeX/bin" at top of your $PATH and that should ok. PATH=/usr/local/teTeX/bin:/usr/bin:. By this way I have always teTeX/pdfetex/ConTeXt up-to-date on my FC4 box. Cheers, -- http://vnoss.org Vietnamese Open Source Software Community ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
