Re: [NTG-context] Bug in context

[Hans Hagen via ntg-context]

On 5/13/2023 2:04 PM, Lutz Haseloff via ntg-context wrote:

Hi Hans, hi all,

I mainly use ConTeXt in a server environment. So I am a friend of the 
console.

I found a small problem there.
When I invoke context with parameter --ansi,
the logfile remains empty.
I tried Linux aarch64 and Windows64.
sure, as it makes no sense to write ansi sequences to the log so then 
that channel is turned off


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

Re: [NTG-context] Bug in context

[Marco Patzer via ntg-context]

On Sat, 13 May 2023 14:04:49 +0200
Lutz Haseloff via ntg-context  wrote:

> When I invoke context with parameter --ansi, the logfile remains
> empty.

I can confirm:

  https://www.mail-archive.com/ntg-context@ntg.nl/msg90303.html

Marco
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Bug in context

[Lutz Haseloff via ntg-context]

Hi Hans, hi all,

I mainly use ConTeXt in a server environment. So I am a friend of the console.
I found a small problem there.
When I invoke context with parameter --ansi,
the logfile remains empty.
I tried Linux aarch64 and Windows64.

Greetings Lutz___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Bug in Context LMTX and font EBGaramond

[Jannik Voges]

Hello,


I found a bug using EBGaramond (I use the font data from TeXLive 2019)
with Context LMTX. I attached the TeX-File and the PDF I get when
typesetting with Context LMTX.


Thanks

Jannik Voges



Bug.pdf
Description: Adobe PDF document


Bug.tex
Description: TeX document
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bug in CONTEXT/LuaTeX or just buggy font

[Hans Hagen]

On 8/10/2016 5:19 PM, Mohammad Hossein Bateni wrote:



On Wed, Aug 10, 2016 at 11:03 AM, Hans Hagen > wrote:

On 8/9/2016 10:41 PM, Mohammad Hossein Bateni wrote:

Hello,

I have a bunch of simple fonts for Arabic/Persian.  These fonts lack
Latin characters, etc., so I use fallbacks to work with them.

I just noticed that \high does not work with them, and have not been
able to pinpoint the issue.  See the MWE below.


\starttypescript [serif][samim][name]
  \definefontsynonym[Serif][Samim]
\stoptypescript

\definetypeface [myfont][rm] [serif][samim][default]
\setupbodyfont [myfont]

\starttext
%\definedfont[Samim*arabic]
۱۲۳\high{۴}۵۶.
\stoptext


I am using Persian digits because the font lacks Latin digits as I
mentioned.  If I use the \definedfont approach, I don't see the
character ۴ (argument of \high) at all.  With the typescript
approach,
the same character /is/ typeset but is /not/ raised; it appears
on the
baseline but with smaller size.

Any ideas why this is happening?  Could it be that some
parameters, for
instance, \exheight are not properly set/read for this font?
Actually,
I looked at the non-math fontdimens in syst-fnt.mkiv, and everything
except \slantperpoint (expected) and \exheight (awkward) is
non-zero.  I
don't know where \exheight comes from—perhaps from the height of
glyph
for 'x', which the font lacks—however, \emheight is 12pt,
although the
font also lacks a glyph for 'm'.

I am also attaching the font in case that helps.


Normally one sets up a proper bodyfont (and environment if needed)
while you use just a simple font switch and that one is unrelated to
any other font setting.


Thanks!  But what does a `proper' bodyfont contain beside defining rm,
ss, tt and mm for 'myfont' above (with regular, bold, italic, and
bolditalic)?  The above was a MWE but in my real example I am setting up
these things that I mentioned in a larger typescript.  How can I modify
the font or the typescript definitions (or the environment) to get
\exheight right?


at least rm (or ss), mm and tt

x heights and emwidths come from the font (parameters) and as last 
resort are derived from other properties



I'll add two new commands: \sx and \sxx so that you can say:

\setuplow [style=\sx]
\setuphigh[style=\sx]


 If I do this, this will not get attached to the font; right?  For
instance, if I define two bodyfonts 'myfonta' and 'myfontb', and switch
between them in the document, then I have to stick to these two setups
if one font, say 'myfonta', is problematic.  Is that correct?


it's dynamicly calculated (for performance reasons once per font instance)

you can play with these:

\setuplow [down=.48\exheight]
\setuphigh[up=.86\exheight]

e.g. use other values, but if your ex and em are bad you can expect many 
other issues (so best use decent fonts)



for such cases. However, as these are derived relative scales they
are normally not compatible with \tx and txx sizes.

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl
 | 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  : http://foundry.supelec.fr/projects/contextrev/

wiki : http://contextgarden.net

___




___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___




--

-
  Hans Hagen | PRAGMA ADE

Re: [NTG-context] Bug in CONTEXT/LuaTeX or just buggy font

[Mohammad Hossein Bateni]

On Wed, Aug 10, 2016 at 11:03 AM, Hans Hagen  wrote:

> On 8/9/2016 10:41 PM, Mohammad Hossein Bateni wrote:
>
>> Hello,
>>
>> I have a bunch of simple fonts for Arabic/Persian.  These fonts lack
>> Latin characters, etc., so I use fallbacks to work with them.
>>
>> I just noticed that \high does not work with them, and have not been
>> able to pinpoint the issue.  See the MWE below.
>>
>>
>> \starttypescript [serif][samim][name]
>>   \definefontsynonym[Serif][Samim]
>> \stoptypescript
>>
>> \definetypeface [myfont][rm] [serif][samim][default]
>> \setupbodyfont [myfont]
>>
>> \starttext
>> %\definedfont[Samim*arabic]
>> ۱۲۳\high{۴}۵۶.
>> \stoptext
>>
>>
>> I am using Persian digits because the font lacks Latin digits as I
>> mentioned.  If I use the \definedfont approach, I don't see the
>> character ۴ (argument of \high) at all.  With the typescript approach,
>> the same character /is/ typeset but is /not/ raised; it appears on the
>> baseline but with smaller size.
>>
>> Any ideas why this is happening?  Could it be that some parameters, for
>> instance, \exheight are not properly set/read for this font?  Actually,
>> I looked at the non-math fontdimens in syst-fnt.mkiv, and everything
>> except \slantperpoint (expected) and \exheight (awkward) is non-zero.  I
>> don't know where \exheight comes from—perhaps from the height of glyph
>> for 'x', which the font lacks—however, \emheight is 12pt, although the
>> font also lacks a glyph for 'm'.
>>
>> I am also attaching the font in case that helps.
>>
>
> Normally one sets up a proper bodyfont (and environment if needed) while
> you use just a simple font switch and that one is unrelated to any other
> font setting.
>

Thanks!  But what does a `proper' bodyfont contain beside defining rm, ss,
tt and mm for 'myfont' above (with regular, bold, italic, and bolditalic)?
The above was a MWE but in my real example I am setting up these things
that I mentioned in a larger typescript.  How can I modify the font or the
typescript definitions (or the environment) to get \exheight right?


>
> I'll add two new commands: \sx and \sxx so that you can say:
>
> \setuplow [style=\sx]
> \setuphigh[style=\sx]
>

 If I do this, this will not get attached to the font; right?  For
instance, if I define two bodyfonts 'myfonta' and 'myfontb', and switch
between them in the document, then I have to stick to these two setups if
one font, say 'myfonta', is problematic.  Is that correct?

for such cases. However, as these are derived relative scales they are
> normally not compatible with \tx and txx sizes.
>
> Hans
>
> -
>   Hans Hagen | PRAGMA ADE
>   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>tel: 038 477 53 69 | www.pragma-ade.nl | 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/list
> info/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> 
> ___
___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bug in CONTEXT/LuaTeX or just buggy font

[Hans Hagen]

On 8/9/2016 10:41 PM, Mohammad Hossein Bateni wrote:

Hello,

I have a bunch of simple fonts for Arabic/Persian.  These fonts lack
Latin characters, etc., so I use fallbacks to work with them.

I just noticed that \high does not work with them, and have not been
able to pinpoint the issue.  See the MWE below.


\starttypescript [serif][samim][name]
  \definefontsynonym[Serif][Samim]
\stoptypescript

\definetypeface [myfont][rm] [serif][samim][default]
\setupbodyfont [myfont]

\starttext
%\definedfont[Samim*arabic]
۱۲۳\high{۴}۵۶.
\stoptext


I am using Persian digits because the font lacks Latin digits as I
mentioned.  If I use the \definedfont approach, I don't see the
character ۴ (argument of \high) at all.  With the typescript approach,
the same character /is/ typeset but is /not/ raised; it appears on the
baseline but with smaller size.

Any ideas why this is happening?  Could it be that some parameters, for
instance, \exheight are not properly set/read for this font?  Actually,
I looked at the non-math fontdimens in syst-fnt.mkiv, and everything
except \slantperpoint (expected) and \exheight (awkward) is non-zero.  I
don't know where \exheight comes from—perhaps from the height of glyph
for 'x', which the font lacks—however, \emheight is 12pt, although the
font also lacks a glyph for 'm'.

I am also attaching the font in case that helps.


Normally one sets up a proper bodyfont (and environment if needed) while 
you use just a simple font switch and that one is unrelated to any other 
font setting.


I'll add two new commands: \sx and \sxx so that you can say:

\setuplow [style=\sx]
\setuphigh[style=\sx]

for such cases. However, as these are derived relative scales they are 
normally not compatible with \tx and txx sizes.


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] Bug in CONTEXT/LuaTeX or just buggy font

[Mohammad Hossein Bateni]

Hello,

I have a bunch of simple fonts for Arabic/Persian.  These fonts lack Latin
characters, etc., so I use fallbacks to work with them.

I just noticed that \high does not work with them, and have not been able
to pinpoint the issue.  See the MWE below.


\starttypescript [serif][samim][name]
  \definefontsynonym[Serif][Samim]
\stoptypescript

\definetypeface [myfont][rm] [serif][samim][default]
\setupbodyfont [myfont]

\starttext
%\definedfont[Samim*arabic]
۱۲۳\high{۴}۵۶.
\stoptext


I am using Persian digits because the font lacks Latin digits as I
mentioned.  If I use the \definedfont approach, I don't see the character ۴
(argument of \high) at all.  With the typescript approach, the same
character *is* typeset but is *not* raised; it appears on the baseline but
with smaller size.

Any ideas why this is happening?  Could it be that some parameters, for
instance, \exheight are not properly set/read for this font?  Actually, I
looked at the non-math fontdimens in syst-fnt.mkiv, and everything except
\slantperpoint (expected) and \exheight (awkward) is non-zero.  I don't
know where \exheight comes from—perhaps from the height of glyph for 'x',
which the font lacks—however, \emheight is 12pt, although the font also
lacks a glyph for 'm'.

I am also attaching the font in case that helps.

Thanks,
Hossein


Samim.ttf
Description: application/font-ttf
___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bug with ConTeXt and pgfplot library fillbetween

[Wolfgang Schuster]

Aditya Mahajan 
24. Oktober 2015 um 20:45
On Fri, 23 Oct 2015, Wolfgang Schuster wrote:


Thanks!

What is the easiest way to fix this (without patching tikz)?
Ensure that | has always the same catcode in math mode independant of 
the catcode in text mode like _ and ^.

I thought that

\pushcatcodetable
\usemodule[pgfplots]
\usepgfplotslibrary[fillbetween]
\popcatcodetable

should work, but it does not. Why?

Surrounding by \unprotect ... \protect does work, so I am wondering 
what is the difference between the two?
When you use \unprotect … \protect context changes the catcode table 
between the group but when you only use push and pop this isn’t the case.


Below is a simplified version of your example where the catcode change 
remains even when I try to restore the default settings with 
\catcodetable\ctxcatcodes but I don’t now if this is a bug.


\starttext

\the\catcode`|

\catcode`|=12

\catcodetable\ctxcatcodes

\the\catcode`|

\stoptext

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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bug with ConTeXt and pgfplot library fillbetween

[Mojca Miklavec]

On Sat, Oct 24, 2015 at 8:45 PM, Aditya Mahajan wrote:
>
> What is the easiest way to fix this (without patching tikz)?

It would also make sense to ask about the proper patch for TikZ, so
that we could push the patch upstream.

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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] Bug with ConTeXt and pgfplot library fillbetween

[Akira Kakuto]

\starttext

\the\catcode`|

\catcode`|=12

\catcodetable\ctxcatcodes

\the\catcode`|

\stoptext


mkiv gives 13, and 12.
mkii gives 13, and 13.

Best,
Akira

___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bug with ConTeXt and pgfplot library fillbetween

[Aditya Mahajan]

On Mon, 26 Oct 2015, Wolfgang Schuster wrote:
Below is a simplified version of your example where the catcode change 
remains even when I try to restore the default settings with 
\catcodetable\ctxcatcodes but I don’t now if this is a bug.


\starttext
\the\catcode`|
\catcode`|=12
\catcodetable\ctxcatcodes
\the\catcode`|
\stoptext


This works:

\starttext
\the\catcode`|
\pushcatcodetable
\catcodetable\prtcatcodes
\catcode`|=12
\popcatcodetable
\the\catcode`|
\stoptext

(Note that under \prtcatcode, the catcode of | is 12). 
But replacing \prtcatcodes with \ctxcatcodes does not work.


So, one "proper" fix may be add a new catcodetable, say \tikzcatcodes, for 
all the catcode changes that tikz does.


Aditya___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bug with ConTeXt and pgfplot library fillbetween

[Aditya Mahajan]

On Fri, 23 Oct 2015, Wolfgang Schuster wrote:


Aditya Mahajan 
22. Oktober 2015 um 02:52
Hi,

The following example fails:

\usemodule[pgfplots]
\usepgfplotslibrary[fillbetween]

\starttext
\startformula
  \left. a \right|
\stopformula

\stoptext

with

tex error > tex error on line 7 in file /private/tmp/test.tex: ! Missing 
\endgroup inserted



\endgroup

\Ucheckedstopdisplaymath
\stopdisplaymath ...math \Ucheckedstopdisplaymath
  \par \ifvmode \ifcase 
\c_s...

\strc_formulas_stop_formula ...native \v!formula }
  \dostoptagged 
\dostoptagge...

l.7 \stopformula

This is a weird bug. Only \left. \right| fails; \left| \right| works 
correctly. If I remove the fillbetween library, the error goes away.


Any hints as to what is happening will be appreciated.


The fillbetween library changes the catcode of the bar character.

\starttext

\the\catcode`|

\usemodule[pgfplots]
\usepgfplotslibrary[fillbetween]

\the\catcode`|

\stoptext


Thanks!

What is the easiest way to fix this (without patching tikz)? I thought 
that


\pushcatcodetable
\usemodule[pgfplots]
\usepgfplotslibrary[fillbetween]
\popcatcodetable

should work, but it does not. Why?

Surrounding by \unprotect ... \protect does work, so I am wondering what 
is the difference between the two?


Aditya
___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bug with ConTeXt and pgfplot library fillbetween

[Wolfgang Schuster]

Aditya Mahajan 
22. Oktober 2015 um 02:52
Hi,

The following example fails:

\usemodule[pgfplots]
\usepgfplotslibrary[fillbetween]

\starttext
\startformula
  \left. a \right|
\stopformula

\stoptext

with

tex error > tex error on line 7 in file /private/tmp/test.tex: ! 
Missing \endgroup inserted



\endgroup

\Ucheckedstopdisplaymath
\stopdisplaymath ...math \Ucheckedstopdisplaymath
  \par \ifvmode 
\ifcase \c_s...

\strc_formulas_stop_formula ...native \v!formula }
  \dostoptagged 
\dostoptagge...

l.7 \stopformula

This is a weird bug. Only \left. \right| fails; \left| \right| works 
correctly. If I remove the fillbetween library, the error goes away.


Any hints as to what is happening will be appreciated.


The fillbetween library changes the catcode of the bar character.

\starttext

\the\catcode`|

\usemodule[pgfplots]
\usepgfplotslibrary[fillbetween]

\the\catcode`|

\stoptext


You get the same error when you use \asciimode in your document.

\asciimode

\starttext

\startformula
  \left. a \right|
\stopformula

\stoptext


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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] Bug with ConTeXt and pgfplot library fillbetween

[Aditya Mahajan]

Hi,

The following example fails:

\usemodule[pgfplots]
\usepgfplotslibrary[fillbetween]

\starttext
\startformula
  \left. a \right|
\stopformula

\stoptext

with

tex error   > tex error on line 7 in file /private/tmp/test.tex: ! 
Missing \endgroup inserted



\endgroup

\Ucheckedstopdisplaymath
\stopdisplaymath ...math \Ucheckedstopdisplaymath
  \par \ifvmode \ifcase 
\c_s...

\strc_formulas_stop_formula ...native \v!formula }
  \dostoptagged 
\dostoptagge...

l.7 \stopformula

This is a weird bug. Only \left. \right| fails; \left| \right| works 
correctly. If I remove the fillbetween library, the error goes away.


Any hints as to what is happening will be appreciated.

Thanks,
Aditya


___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Bug in ConTeXt? Conflict in titles, sections and bibliography (was bibliography problems)

[Hans Hagen]

On 3-3-2012 09:44, Jaroslav Hajtmar wrote:

Hello ConTeXist.
I present an bug with which I have been seeing over the last few
versions of Context.
In collaboration with Thomas, who helped me find the perfect minimal
example, I managed to finally find out what is the core of my problem.
But it is perhaps deeper than at first glance. Bibliographic system is
today (last version of standalone) in conflict with results of \title
and \section commands.

I show in the example below, how strange it works ConTeXt, while using
inserting of the bibliography together with title and section commands.


It's not that strange. The criterium=cite is in fact a criterium=here in 
the list resolver. Lists can be called up for each section (or level) 
but as soon as you mess with structure you need to be a bitmore 
explicit. In this case, you can try criterium=local. Of course we could 
make criterium=cite fall back on that in the case of a unnumbered 
structure (which is what title implies) but I'm not so sure of other 
side effects. So, I'm hesitant to change something to solve this 
bordercase.


In general, when using some extra structure, like fontmatter, it gets 
easier to call up (local) lists.


Hans


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] Bug in ConTeXt? Conflict in titles, sections and bibliography (was bibliography problems)

[Jaroslav Hajtmar]

Hello ConTeXist.
I present an bug with which I have been seeing over the last few 
versions of Context.
In collaboration with Thomas, who helped me find the perfect minimal 
example, I managed to finally find out what is the core of my problem. 
But it is perhaps deeper than at first glance. Bibliographic system is 
today (last version of standalone) in conflict with results of \title 
and \section commands.


I show in the example below, how strange it works ConTeXt, while using 
inserting of the bibliography together with title and section commands.


I want show three cases of behavior of ConTeXt:

As you see below then:

1. When document is both without Title and without Section (both 
commands are commented) then you see a problem with list of bibliography 
- list of figures and list of bibliography are mixed.


2. When document is with Title (uncomment \title command) then you see 
that bibliography is not working. You get errors in bibliography links 
and ConTeXt do not include list of bibliography.


3. When document is with Section (uncomment \section command) then you 
see that all is working now without any problems - links are right and 
list of bibliography is correct too.


Additionally, you can track down and how it behaves ConTeXt when 
inserting figure with or without captions (in case 1).


It really is a bug somewhere or doing something wrong?

Thanx Jaroslav


Here is minimal example:

\setupbibtex[database=sample]
\setuppublications[alternative=ams, sorttype=cite]

\starttext

%\section{Section} % When you uncomment this line you see, that 
everything is OK, both bibliography links and list of bibliography works 
fine
\title{Title} % When you uncomment this line you see, that bibliobraphy 
links are broken and ConTeXt do not include list of bibliography



Citations are \cite[hh2010b] and \cite[hh2010a].

\placefigure[force][fig1]{Caption of figure \cite[Eijkhout1991] with 
citation} % get mixing problem

   {\externalfigure[fig1]}

% \placefigure[force, none][fig1]{} % Figure without caption - no 
problem with bibliography (both links and mixing)

%{\externalfigure[fig1]}

%\placefigure[force][fig1]{Caption of figure without citation} % you 
see, that problem does not depend on whether the citation is inserted or not

%   {\externalfigure[fig1]}


\placepublications[criterium=cite]

\stoptext

___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] bug in context/luatex

[Taco Hoekwater]

Yue Wang wrote:
 Hi, Hans:
 
 pdftex and LuaTeX produce different results with the following source
 file. Please check.

Whatever it is exactly (no lbr on my home machine so I can not try),
this is likely a problem with context mkiv, not the luatex engine.

Mkiv usually reads afm files and reencodes the font to (partial)
unicode, instead of using the traditional tfm files. You could 
experiment with

   \ctxlua { fonts.define.method = 2 }

at the very top of your file.

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
___

[NTG-context] bug in context/luatex

[Yue Wang]

Hi, Hans:

pdftex and LuaTeX produce different results with the following source
file. Please check.
I dont know whether it is a bug in ConTeXt  or LuaTeX.

\usetypescriptfile[type-buy]
\usetypescript[lucida][texnansi]
\setupbodyfont[lucida,12pt]
\starttext
`hello'
\stoptext

I use the tfms/map zip you attached in the mailing list together with
the font bought from TUG.
If there is something wrong with my installtion, let me know.

Yue Wang
___
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
___