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 Gawa
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 yo
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.
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 \writ
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
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-matc
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 involve
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
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?
>
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?
>
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
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 [ali
12 matches
Mail list logo
