LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Mailing list for the LaTeX3 project <[log in to unmask]>
Achim Blumensath <[log in to unmask]>
Tue, 18 Jan 2000 21:03:47 CET
Mailing list for the LaTeX3 project <[log in to unmask]>
text/plain (48 lines)
Frank Mittelbach wrote:
> As promised this is the first installment of templates and code for
> galley formatting, the rest will hopefully follow in couple of days.
> I think that this document already serves as a good introduction to the
> high-level aspects of the new galley mechanism and though one can't make
> use of the code without the low-level interfaces I hope that the
> documentation will spawn a lively discussion. A lot of issues and
> requests for comments are already added into the documentation.

Here are my first impressions:

o Name of parameters. At the moment the old LaTeX2e names like \hsize,
  \@totalleftmargin, etc. are used so that old code does still work.
  IMHO one should introduce new names right from the start while keeping
  the old versions in addition. Otherwise, you get in trouble when
  the interface is finally cleaned up since all LaTeX2e* code using the
  galley package has to be rewritten as well.

o pshape template. Perhaps it would be a good idea to add two arguments
  to the pshape template for the horizontal and vertical dimension
  (where the exact meaning depends on the template). Say, a template
  for a rectangular cutout could interpret the horizontal dimension
  as width of the cotout and the vertical dimension as number of lines
  to be indented.

o hyphenation template. This template should IMHO be dropped. The only
  important parameters it sets are (ex)hyphenpenalty which can be moved
  to the linebreak template.

o justification template. I'm not quiet sure how the galley templates
  are intented to be used -- the package only defines the templates
  themselve no commands to use them. But I think that the justification
  templates shouldn't be able to choose whether they affect all
  paragraphs or only the next one. Instead the user should be able to
  tell the system which case is desired everywhere such a template is

o As mentioned in the item above, the user-level interface is missing.

                                _                             | \_____/ |
    //  Achim Blumensath       | \  _                        \O/ \___/\ |
   //   [log in to unmask]   |-< /_\                       =o=  \ /\ \|
 \X/    (p^2 - m^2)\psi = 0    |_/ \_                        /"\   o----|