Wolfgang Werners-Lucchini wrote:
> Hallo!
>
> The following simple example doesn't compile
> (ConTeXt ver. 2007.01.02 and Live ConTeXt).
>
> What am I doing wrong?
Diagnostics:
The problem is not caused by the \framed, but by the (lack of)
parsing done by the buffering routines.
Because the \st
Hi all,
I'm afraid there still seems to be a problem with the XeTeX
engine ... try to compile the following (I guess you can choose
whichever OpenType font you have on your machine):
---
\definetypeface[Caslon][rm][Xserif][Adobe Caslon Pro]
\setupbodyfont[Caslon,12pt]
\starttext
\input tuft
Hello,
A document that compiled fine yesterday with 'texmfstart
texexec --environment Labbook.tex Labbook.xml' today gives me this at the
end of the log running by:
xml : loading module ent
(/usr/share/texmf/tex/context/base/xtag-ent.tex))
*
Any pointers as to what I'm screwing up? I
Johannes Graumann wrote:
> Hello,
>
> A document that compiled fine yesterday with 'texmfstart
> texexec --environment Labbook.tex Labbook.xml' today gives me this at the
Have you tried --environment=Labbook.tex ?
Taco
___
ntg-context mailing list
Bang! Dumm... shot himself ... last words: thanks!
Joh
Taco Hoekwater wrote:
>
>
> Johannes Graumann wrote:
>> Hello,
>>
>> A document that compiled fine yesterday with 'texmfstart
>> texexec --environment Labbook.tex Labbook.xml' today gives me this at the
>
> Have you tried --environment=L
� wrote:
> On Wed, 21 Mar 2007, luigi scarso wrote:
>
>
>>> in the following example, there is a page-break after the second section
>>> title. \page[no] does not help.
>>>
>>> Is this normal or a bug?
>>>
>> Normal, I believe
>>
>
> Too bad. I think, there can be still some enhancem
> I'm afraid there still seems to be a problem with the XeTeX
> engine ... try to compile the following (I guess you can choose
> whichever OpenType font you have on your machine):
[snip]
> The same file used to compile with the January release of ConTeXt
> (2007.01.12) ... perhaps something has
Oliver Buerschaper wrote:
> Hi all,
>
> I'm afraid there still seems to be a problem with the XeTeX
> engine ... try to compile the following (I guess you can choose
> whichever OpenType font you have on your machine):
>
> ---
>
> \definetypeface[Caslon][rm][Xserif][Adobe Caslon Pro]
> \setupbo
Peter Rolf wrote:
> hi,
>
> i'm tired of fixing \dogetfigurefilename in every new version. i have
> already shown that there is something wrong with it in my mail from
> 17.01.2007
>
> http://archive.contextgarden.net/message/20070117.153030.344c6989.en.html
>
> i don't say, that i understand the c
> hm, hard to test here, how is Xserif and Adobe Caslon Pro
> Defined ... it looks like no filename comes through
>
> (maybe this weekend i can sit down with someone at the context conf
> to see what happens; i currently have no working mac)
Fine. That'll be me then ;-) I have a Mac and I'm at
Hans Hagen wrote:
> Peter Rolf wrote:
>> hi,
>>
>> i'm tired of fixing \dogetfigurefilename in every new version. i have
>> already shown that there is something wrong with it in my mail from
>> 17.01.2007
>>
>> http://archive.contextgarden.net/message/20070117.153030.344c6989.en.html
>>
>> i don't
On Thu, 22 Mar 2007, Hans Hagen wrote:
> well, it depends, if the next structure does a vskip of some testing
> then there can be a page break
>
> there is no robust way to prevent this in current tex, at least nog when
> some spacing mechansism are used, ok, a penalty 1 may sometimes
> he
� wrote:
> On Thu, 22 Mar 2007, Hans Hagen wrote:
>
>
>> well, it depends, if the next structure does a vskip of some testing
>> then there can be a page break
>>
>> there is no robust way to prevent this in current tex, at least nog when
>> some spacing mechansism are used, ok, a penalty 1000
Hans Hagen wrote:
>>>
>> Thanks for your explanation! Do you know, how the LaTeX people
>> solved this problem? I've never had such surprises with LaTeX.
>>
> ...
> interference with preceding material); i do (did) observe that latex
> has a different spacing model (and interfering penalties may
On 3/22/07, Hans Hagen wrote:
> Oliver Buerschaper wrote:
> > Hi all,
> >
> > I'm afraid there still seems to be a problem with the XeTeX
> > engine ... try to compile the following (I guess you can choose
> > whichever OpenType font you have on your machine):
> >
> > ---
> >
> > \definetypeface[Ca
15 matches
Mail list logo
