[NTG-context] XeTeX in ConTeXt
Dear all,
I have tried to upgrade ConTeXt using
sudo ctxtools --updatecontext
followed by
sudo texmfstart texexec --make en
and
sudo texmfstart texexec --make --xetex en
Following the upgrade a normal ConTeXt document runs perfectly but
when I run XeConTeXt through TeXShop I get the readout below. When I
go back to the TeXLive download of TeX everything works.
Any advice would be welcome.
Thanks,
Charlie
TeXExec | processing document 'SocialSpace.tex'
TeXExec | no ctx file found
TeXExec | tex processing method: context
TeXExec | TeX run 1
TeXExec | writing option file SocialSpace.top
TeXExec | using randomseed 80
TeXExec | tex engine: xetex
TeXExec | tex format: cont-en
This is XeTeXk, Version 3.141592-2.2-0.996 (Web2C 7.5.6)
%-line parsing enabled.
entering extended mode
(./SocialSpace.tex
ConTeXt ver: 2008.05.21 15:21 MKII fmt: 2008.5.23 int: english/
english
language: language en is active
system : cont-new loaded
(/usr/local/texlive/2007/../texmf-local/tex/context/base/cont-new.tex
systems : beware: some patches loaded from cont-new.tex
(/usr/local/texlive/2007/../texmf-local/tex/context/base/cont-new.mkii)
(/usr/local/texlive/2007/../texmf-local/tex/context/base/cont-mtx.tex))
system : cont-old loaded
(/usr/local/texlive/2007/../texmf-local/tex/context/base/cont-old.tex
loading : Context Old Macros
)
system : cont-fil loaded
(/usr/local/texlive/2007/../texmf-local/tex/context/base/cont-fil.tex
loading : Context File Synonyms
)
system : cont-sys.rme loaded
(/usr/local/texlive/2007/../texmf-local/tex/context/user/cont-sys.rme
(/usr/local/texlive/2007/../texmf-local/tex/context/base/type-tmf.tex)
(/usr/local/texlive/2007/../texmf-local/tex/context/base/type-siz.tex)
(/usr/local/texlive/2007/../texmf-local/tex/context/base/type-otf.tex)
(/usr/local/texlive/2007/../texmf-local/tex/context/base/type-
xtx.tex))kpathsea: Running mktextfm lmromanslant10-regular
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1;
nonstopmode; input lmromanslant10-regular
This is METAFONT, Version 2.71828 (Web2C 7.5.6)
kpathsea: Running mktexmf lmromanslant10-regular
! I can't find file `lmromanslant10-regular'.
* ...; nonstopmode; input lmromanslant10-regular
Please type another input file name
! Emergency stop.
* ...; nonstopmode; input lmromanslant10-regular
Transcript written on mfput.log.
grep: lmromanslant10-regular.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode;
input lmromanslant10-regular' failed to make lmromanslant10-regular.tfm.
kpathsea: Appending font creation commands to missfont.log.
bodyfont: 12pt rm is loaded
! Font \*7ptrmslrm*:=lmromanslant10-regular at 7.0pt not loadable:
Metric (TFM)
file or installed font not found.
to be read again
\relax
\xxdododefinefont ...tspec {#4}\newfontidentifier
\let
\localrelativefontsiz...
\dodosettextfamilyA ...amily \fontsize \endcsname
\else \ifcsname
\fontbody ...
\dosettextfamily ...ttextfamily \scriptscriptfont
\let \fontbody
\scriptface...
inserted text ...y \c!bf \dosettextfamily \c!sl
\dosettextfamily \c!
it \do...
\synchronizetext ...athfonts \the \textstrategies
\fi
...
l.1
\definetypeface[Hoefler][rm][Xserif][Hoefler Text]
? x
No pages of output.
Transcript written on SocialSpace.log.
TeXUtil | parsing file SocialSpace.tui
TeXUtil | shortcuts : 169
TeXUtil | expansions: 308
TeXUtil | reductions: 0
TeXUtil | divisions : 0
TeXUtil | loaded files: 1
TeXUtil | temporary files: 0
TeXUtil | commands: 25
TeXUtil | programs: 0
TeXUtil | tuo file saved
TeXExec | runtime: 100.320881
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Odd Behavior in pdftex/xetex
On Fri, 23 May 2008 22:29:06 +0200
Hans Hagen [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
The following specimen was run on live.contextgarden.net with each of
the three typesetters:
\setupcolors[state=start]
\starttext
\input knuth
\bTABLE
\bTR [align=middle]\bTH Range\eTH{}\bTH Value\eTH{}\eTR
\bTR \bTD \type{} 12\eTD{}\bTD 3\eTD{}\eTR
\bTR \bTD 12--16\eTD{}\bTD 2\eTD{}\eTR
\bTR \bTD \type{}16\eTD{}\bTD 1\eTD{}\eTR
\eTABLE
\input knuth
\stoptext
In the case of pdfTeX and XeTeX, the table is given a width equal
to the textwidth; in the caes of LuaTeX, it is typeset correctly
with natural widths.
When \setupcolors is removed, both pdfTeX and XeTeX also produce
the correct result.
This sounds like a bug to me (and took me forever to isolate
\setupcolors - of all things! - as the culprit).
actually it's the \type (combined with colors)
\dontleavehmode \type {xx}
works ok
probably some pdfliteral is playing havoc here so that the width analyer
cannot function well (a limitation of tex is that there's only a small
set subset of \un* and \last* node operations); if you see messages like
this
!!forced exit from shapebox 9!!
that is indeed the case. hoewver, in mkiv i use different trickery so
there we don't have this problem (we also use a different color
mechanism so that helps too)
it's not so much a bug in mkii as well as a side effect/limitation
okay, we could add \dontleavehmode to \type but i'm not sure if that
will not break other things; also, bTABLE is kind of tricky because it
needs to be clever with regards to text and non text and such
If he use \retype the table works.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] XeTeX in ConTeXt
On Fri, May 23, 2008 at 12:55 PM, Charles Doherty wrote: Dear all, I have tried to upgrade ConTeXt using sudo ctxtools --updatecontext followed by sudo texmfstart texexec --make en and sudo texmfstart texexec --make --xetex en Following the upgrade a normal ConTeXt document runs perfectly but when I run XeConTeXt through TeXShop I get the readout below. When I go back to the TeXLive download of TeX everything works. Any advice would be welcome. In order to be able to use the latest ConTeXt, you need to: - install to the latest LM fonts - preferrably install the latest XeTeX For XeTeX, the easiest way is to upgrade it is to download it from here: http://minimals.contextgarden.net/current/bin/xetex/ and replace the old executable (maybe you need to set the executable flag after download) or simply issue something like: rsync -av rsync://contextgarden.net/minimals/current/bin/xetex/osx-yourarchitecture/bin/ /usr/texbin/ For Latin Modern fonts you can try (single line) rsync -av rsync://contextgarden.net/minimals/current/fonts/new/fonts/opentype/public/lm/ /path-to-tex-tree/fonts/opentype/public/lm/ and then run mktexlsr. Mojca ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] luaTeX and on-the-fly MetaPost compilation
Stephan Hennig wrote:
Hi,
I didn't have the opportunity to touch luaTeX yet, but let me ask one
question in advance: Since luaTeX has a built-in MetaPost interpreter,
is it possible to refer to a certain figure in a MetaPost source file
for inclusion, instead of a compiled figure?
As an example, I would like to say in a TeX document (syntax may differ)
\includeMetaPost{foo.2}
In principle something like that is possible, but it needs an extension
to the current system, because you have to filter out the specific
figure you really want, and I don't think Hans has code for that already
(but I could be wrong).
Best wishes,
Taco
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] luaTeX and on-the-fly MetaPost compilation
Stephan Hennig wrote:
Hi,
I didn't have the opportunity to touch luaTeX yet, but let me ask one
question in advance: Since luaTeX has a built-in MetaPost interpreter,
is it possible to refer to a certain figure in a MetaPost source file
for inclusion, instead of a compiled figure?
As an example, I would like to say in a TeX document (syntax may differ)
\includeMetaPost{foo.2}
and this should not refer to the pre-compiled file
foo.2
but to section
figure(2);
...
endfig;
in file
foo.mp
and compile it on-the-fly. Would that be possible?
mplib is still just mp so it ptocessed what is passed to it; no
intelligence is added to the mp kernel
however, when using the lib ons is in control over what is passed to it
in the past i did what you describe in metafun by using just a macro
(loadfigure) which filters the image from a file;
in luatex we can be more clever (i admit that i hadn;t yet thought of
replacing the macro -)
using lua we get something ...
function filterfromMPblob(data,number)
return
(data:match(string.format(beginfig%%(%s%%).-endfig,number)) or ) .. ;
end
test this with:
str = [[
beginfig(1)
draw fullcircle ;
endfig ;
beginfig(2)
draw fullcircle ;
endfig ;
]]
print(filterfromMPblob(str,2))
glue to tex:
\def\includeMetaPost#1#2% io.loaddata is part of l-io.lua
{\directlua0{tex.print(filterfromMPblob(io.loaddata(#1,#2)))}}
of course this need to be embeded in some general mp support
(i'll add it to my todolist; actually a bit more is involved since one
probably wants to include the data between the figures too since it may
be called upon)
-
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
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] \Asterisk
Jesse Alama wrote: I was working on a document in which I wanted use a symbol that, acording to the Comprehensive LaTeX Symbol List, goes by the name of \Asterisk or \bigast (see p. 22). I saw, though, that this seems to be missing in ConTeXt. Might it be tucked away in some module, or is it just absent? If it's really not there, what would it take to add it? you can peek in the symb-* files; if it's math then maybe in the math-ams file - 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] luaTeX and on-the-fly MetaPost compilation
Hans Hagen schrieb:
glue to tex:
\def\includeMetaPost#1#2% io.loaddata is part of l-io.lua
{\directlua0{tex.print(filterfromMPblob(io.loaddata(#1,#2)))}}
of course this need to be embeded in some general mp support
(i'll add it to my todolist; actually a bit more is involved since one
probably wants to include the data between the figures too since it may
be called upon)
Thank you for the outline. For the exact mechanism of how to process an
.mp file I think there are three possible cases:
1. Strictly process what's between figure(n)..endfig only.
For this example
pair pnt;
pnt:=origin;
beginfig(1);
pnt:=(100,100);
drawdot pnt;
endfig;
beginfig(2);
drawdot pnt;
endfig;
end
compilation of figure 2 should fail, since variable pnt is undeclared.
2. Process everything up-to the specified figure, omitting stuff inside
non-matching figure numbers. In the example above, the output of figure
2 should be a dot at point (0,0). This case is convenient if multiple
figures share common variables or macros that are defined outside the
scope of beginfig..endfig. This should be the default case for .mp file
interpretation.
3. Process everything up-to the specified figure, including all
non-matching figures, but discard their output. That is, in the
example, the output of figure 2 should be a dot at point (100,100),
since pnt was modified in figure 1.
Note, this is not a pressing feature for me. The advantage is that
MetaPost and TeX code can be held in separate files (which has several
advantages) and users can easily compile the code in a single TeX run,
without knowing about Makefiles. Well, there is the \write18 feature.
But that is as difficult to use as a Makefile or even more difficult for
the inexperienced user.
Best regards,
Stephan Hennig
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] luaTeX and on-the-fly MetaPost compilation
Stephan Hennig wrote: Thank you for the outline. For the exact mechanism of how to process an .mp file I think there are three possible cases: 1. Strictly process what's between figure(n)..endfig only. 2. Process everything up-to the specified figure, omitting stuff inside non-matching figure numbers. 3. Process everything up-to the specified figure, including all non-matching figures, but discard their output. 4. Start a new MP instance, process the whole file, save and remember the outputs (store fig.1, fig.2, fig.3 etc), then immediately close the MP instance again. The advantage is that this makes the metapost input behave exactly the same as a true external figure, something that is not possible when an already running MP instance is re-used. This is important, because the state of an already running instance can be altered in such a way that a perfectly valid metapost source suddenly fails to run. That may happen with embedded metapost code as well of course, but in that case it is much easier to correct and diagnose the problem. Best wishes, Taco ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] luaTeX and on-the-fly MetaPost compilation
Taco Hoekwater wrote: it is much easier to correct and diagnose the problem. Although these actions are usually done in reverse order ;-) ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] luaTeX and on-the-fly MetaPost compilation
Stephan Hennig wrote: Note, this is not a pressing feature for me. The advantage is that MetaPost and TeX code can be held in separate files (which has several advantages) and users can easily compile the code in a single TeX run, without knowing about Makefiles. Well, there is the \write18 feature. But that is as difficult to use as a Makefile or even more difficult for the inexperienced user. i'll put it on my todo list (let me know if it gets pressing -) - 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Thanks for the boxes with schems
Thanks, Hans, for the suggestion. It works quite well, except the \ae{}
macro starts producing a lowercase j. My guess is this refers to an
encoding issue, since I found that using \sc tends to not do small caps
except for using Computer Modern.
I did RTFM, but I'm just not making the connection. If someone can point
me to a document on fonts that I can work through ... the section in the
manual left me a little confused. After using Pagemaker, Quark, and
InDesign, I kinda get the approach but it seems to be a culture shock
like Metafont was and remains. I copied the examples from the manual
when I did a book mock-up for work and that worked real well. Everyone
was impressed by what ConTeXt could do, although the official workflow
will remain Incopy and InDesign. Still, I uotdid an experienced graphic
designer using Adobe CS3 with my little bit of code for schemas. ConTeXt
and friends have some unique benefits.
So if I could solve the font mystery, I would be grateful. I have some
books, for example, that I would like to reproduce with ConTeXt by
scanning the Fraktur and OCR'ing with tesseract, then doing the layout
with ConTeXt. I have an Ernestine Bible (Das Weimarische Bibelwerk) for
which the binding is shot but the pages are good. This way will take
much less than scanned images, although some images will remain.
Ultimately I would like to make something like yfonts, but with unicode
or some standard encoding to allow either umlauts or superscript e. In
my own library I have books from the early eighteenth century on, and
Google books has more, so there's no lack of subjects to scan into
Fontforge.
Charles
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Thanks for the boxes with schems
Charles P. Schaum wrote:
Thanks, Hans, for the suggestion. It works quite well, except the \ae{}
macro starts producing a lowercase j. My guess is this refers to an
encoding issue, since I found that using \sc tends to not do small caps
except for using Computer Modern.
what encoding do you use? ec or texnansi .. and what font do you want to
use?
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
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] interim fix for aesc-like macro
I found an interim fix for the \ae macro in the schemata: put the word with the macro in an hbox, and the problem goes away. I wonder what the mechanics behind that are. I tend to have weird documents with dead languages. Who knows, maybe I want to cite Aelfric using Old English letters or Sir Gawain or whatever Middle High German with a yogh or similar glyph. Come to think of it, Gothic would be cool, too. So, figuring out the mechanics would be helpful. Thanks, Charles ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
