On Sat, May 19, 2001 at 01:12:36AM +0200, ben wrote:
> Hi Jose!
>
> Jose Abilio Oliveira Matos a écrit :
>
> > Hi Ben,
> > after thinking for a while I have decide to change the current standard
> > layout from para to simpara, as it more closely reflects the structure of
> > LyX usage.
> >
> > What do you think?
> > This will probably help you, since para can have block elements inside and
> > simpara can't.
>
> Are you sure that it will not introduce some restrictions? At the translation
> point of view, there is no real change, since para and simpara are already
> changed to the Standard layout. :-)
How do you deal with formalpara? What do you do to the title?
There is no restrictions since the difference between para and simpara is
that allows block elements, while simpara doesn't.
I still use para at other places as a convinient wrapper for content that
needs it.
How do you translate:
<para>
this is a simple paragraph with itemized lists:
<itemizedlist>
<listitem> <para>one</para></listitem>
<listitem> <para>two</para></listitem>
</itemizedlist>
and some other content...
</para>
I ask this as here you have para in 2 different roles?
> > The question in the docbook-apps is related to the the location of the
> > entities, am I right?
>
> Yes, yes, yes! And the common/ docbook location too.
>
> > If that's the case I have one possible solution that is taken from the
> > relyx case.
> >
> > you could have a file, called config.in where you have:
> >
> > ent_location=@ENT-LOCATION@
> >
> > that is parsed, and replaced at configuration time.
> >
> > I hope this helps,
>
> Well, I've thought to such possibilities, but I would prefer an install in
> which the stylesheets are not changed. If it is not possible, your solution
> seems to be a good one, but the patch should concern very few stylesheets.
ReLyX has this issue as it needs to know the location of the Text library,
IIRC.
> BG
--
José
