Frank Mittelbach skrev:
> > Depends on whether you look at it graphically or semantically. For
> > designing a general API, I think you really need to look at it
> > semantically.
> yes agreed, but we can only go semantically up to a certain level, otherwise
> you need to specify 100+ arguments and still haven't covered all
> what i'm currently thinking might be reasonable is
> - subtitle (which is text that is semantically related to main title)
> - motto/quote text (text which is semantically unrelated to main title)
> and support both.
> - text credits (which is author copyright or similar info but not
> semantically specified further)
> if more control is needed then that type is not specialized enough to support
This suggests you're open to using a different object type in some
cases? Indeed, that's not a bad idea: A document class with _very_
special heading needs can be expected to use its own object type for
headings (in addition to the basic definition of instances, this would
require redefining all sectioning commands and defining new templates
for the new type, but it is perfectly doable). Packages meant to
configure standard headings will then not work off the self for this
class, but it is still as configurable as the standard headings.
If we're clear that completely bypassing a subsystem such as the
heading templates is OK also in LaTeX3 (though this comes at the cost
of having to reimplement a bunch of stuff yourself), then it's not the
end of the world if there are things that the standard heading object
type cannot accomplish. It's better that it does 90% of all things well
and elegantly, than that it does 99.99% of all things with an API only
wizards can comprehend.