Re: project structure (bug?)

[Steffen Wolfrum <context@st.estfiles.de>]

Am 08.02.2008 um 17:19 schrieb Taco Hoekwater:

> Steffen Wolfrum wrote:
>> Am 08.02.2008 um 16:58 schrieb Taco Hoekwater:
>>
>>>
>>> Steffen Wolfrum wrote:
>>>> Hi,
>>>>
>>>> does it make sense that eg
>>>>
>>>> \clubpenalty=10000
>>>>
>>>> doesn't work when written in a project's environment file?
>>> I think so, yes (technically it is a side-effect).
>>>
>>> This should work even in the environment file:
>>>
>>>    \def\defaultclubpenalty {10000}
>>>    \setdefaultpenalties
>>
>>
>>
>> And all of them like this?
>>
>> \def\defaultclubpenalty {10000}
>> \def\defaultwidowpenalty {10000}
>> \def\defaultdisplaywidowpenalty {10000}
>> \def\defaultbrokenpenalty {0}
>>
>> \setdefaultpenalties
>>
>>
>> I experienced also very interesting differences between setting in
>> environment file \setuplayout[grid=no] and in component \setuplayout
>> [grid=yes]
>> compared to setting in environment file \setuplayout[grid=yes] .
>>
>> As working with grid is in itself quite fragile (and surprising) I
>> guess this is not explainable / avoidable?
>
>
> grid mode has a separate set of defaults, yes. See core-spa.tex
> (easier for me than writing it all down)


What about the difference in writing in
environment file \setuplayout[grid=no] plus in component \setuplayout 
[grid=yes]
compared to setting in environment file \setuplayout[grid=yes]

Why does this make a difference?

Steffen
___________________________________________________________________________________
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
___________________________________________________________________________________