On Fri, Apr 07, 2006 at 08:52:13PM +0200, Georg Baum wrote:
> Am Freitag, 7. April 2006 15:18 schrieb Helge Hafting:
> > If I understand correctly, the existing mechanism for
> > thin space, interword space, protected space and hfill in non-math text
> > should be removed, to be replaced with what I make?
>
> You should probably rename InsetSpace to InsetHSpace and use that as a
> base.
>
I have already started using vspace as a base, but the end result
should be the same.
> > I will of course make the new thinspace etc. look like
> > the stuff it replaces, but now you'll be able to click on
> > a hfill or thinspace and turn it into a qquad or 2.5em space instead.
>
> Very good.
>
> > The space types I have in the dialog currently, is:
> > default \hspace{\defskipamount}
> > \negthinspace
> > \thinspace
> > interword '\ '
> > protected '~'
> > \quad
> > \qquad
> > \enspace
> > \enskip
> > \hspace{\smallskipamount}
> > \hspace{\medskipamount}
> > \hspace{\bigskipamount}
> > \hfill
> > \hspace{user supplied length}
> >
> > The question - do we want *all* of these?
>
> I am not sure. The inset should be able to read and write arbitrary
> lengths (including \hspace{\myuserdefinedlength}), and you should be able
> to change these lengths in the dialog. Then we can always add new lengths
> later without a file format change.
Ok. So I should not special-case these lengths, but simply let
the writer use \hspace{\anythingwithabackslash}, thereby supporting
\medskipamount as well as \myuserdefinedlength implicitly. And if they use
\invalidlength or \undefinedlength they get to keep the pieces . . .
Helge Hafting
