LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Javier Bezos <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Tue, 28 Dec 1999 21:23:46 +0100
text/plain (61 lines)
> > >have to study them a bit further but i was wondering about the paragraph
> > >action
> > >which seems to be intended to run the whole set of all entries in a
> > >paragraph.
> >
> > Not necessary. Just define, say, section to be of style JB1, and
> > subsection of style JB2. That's all. If there are no new bugs, that
> > should work.
>I tried that after Xmas but not with much success. would you care to provide
>us with a (working:-) example? perhaps i'm simply to stupid to get it right.

!Ah! The sychronizations problems which I thought I solved. :-( That's
closely related to a problem with templates which I explained in a
message-- the fact that the parameters are used with an intermediate:

I then said:
>The template way is (very, very simplified)
>  \def\@it{#1}
>  \def\it{\@it}}
>This extra level has many implications, because we cannot
>define \it literally (ie, exactly as given by the argument)

Take the following declarations:

\DeclareInstance{contentsobject}{section}{JB1}{ % the usual way
 ... irrelevant}
\DeclareInstance{contentsobject}{subsection}{JB2}{  % grouped
 ... irrelevant }

The very first subsection after a section begins a group, which is
not ended until the very first section after a series of sections
comes--the \endgroup is *in the section code* and the attributes
for it are deleted! That does not happen in the original
implementation because parameters are used literally (and hence
never deleted). In its very, very simplified equivalent:


I cannot figure out how to fix that with reworking a lot of code,
but perhaps redefining all of parameters to itself but globally
could work. (I mean


and so on.) May attributes be assigned globally in templates?