Attached are 4 patches for branch:
- chkconfig: I was informed that we must look for some additional language packages so that users
can compile Greek and Russian/Ukrainian directly after installing LyX
- configure: check for some more popular editors (I also check for them in the installer) a
Am 24.11.2012 20:16, schrieb Jean-Marc Lasgouttes:
Le 24/11/2012 19:24, Richard Heck a écrit :
Implement multiline command type? We do not have it, but LaTeX does
accept that.
Could we work around it by defining an environment here, in place of the
command? So that what's in the environment b
Le 24/11/2012 19:24, Richard Heck a écrit :
Implement multiline command type? We do not have it, but LaTeX does
accept that.
Could we work around it by defining an environment here, in place of the
command? So that what's in the environment becomes the argument to the
command?
This is not ver
On 11/24/2012 12:05 PM, Jean-Marc Lasgouttes wrote:
Le 24/11/2012 15:25, Uwe Stöhr a écrit :
I have a question regarding layouts:
For modernCV I have the case that an itemize needs to be within another
command, e.g.
\cvlistitem{Another single item.\begin{itemize}\item
Sub-item.\end{itemize}}
Jean-Marc Lasgouttes wrote:
> 1/ use your shiny new combo for Layout box (to avoid doubly-defined stuff)
This is the long-term plan indeed.
> 2/ put your code into a namespace, presumably lyx::frontend.
Pavel did so, thankfully.
Jürgen
Le 24/11/2012 15:25, Uwe Stöhr a écrit :
I have a question regarding layouts:
For modernCV I have the case that an itemize needs to be within another
command, e.g.
\cvlistitem{Another single item.\begin{itemize}\item
Sub-item.\end{itemize}}
So I need to nest the itemize into the \cvlistitem. b
Le 24/11/2012 09:35, Jürgen Spitzmüller a écrit :
Pavel Sanda wrote:
Not directly related, but are you able to compile the current trunk via
monolithic build?
I didn't try. I read this message, but I don't know how to fix that.
1/ use your shiny new combo for Layout box (to avoid doubly-defi
Uwe Stöhr wrote:
> OK, but then one has to keep the label short and the tooltip has to be
> different than the label. I first tried to keep them identic to save
> translation work.
But then it would not make sense to have two strings. We should use the
tooltips to give the users some hints. Have
Am 24.11.2012 16:39, schrieb Jürgen Spitzmüller:
"Opt" and "Req" are too vague. This is what my work is all about.
Find strings that are suitable for both the menu and the button.
OK, but then one has to keep the label short and the tooltip has to be different than the label. I
first tried t
Jürgen Spitzmüller wrote:
> Uwe Stöhr wrote:
> > - if I have a mandatory argument, the label of the collapsible inset still
> > has the name "opt". This is confusing and I fear that users think they
> > can
> > omit it. I therefore propose to change it to "required" or "req"
>
> This is a bug. It
Uwe Stöhr wrote:
> And I thought that is why we have the tooltip so that the user can always
> see what an argument is for.
No, the tooltip is the place to giv e some short usage explanation.
Jürgen
Uwe Stöhr wrote:
> But this would look ugly. For example when I have
>
> LabelString "Left item summary"
>
> Its size is OK for the insert menu entry, but for the label of the
> collapsible, this would make some documents quite unreadable. (in my
> particular case a command has 4 man
Am 24.11.2012 16:20, schrieb Uwe Stöhr:
Its size is OK for the insert menu entry, but for the label of the collapsible,
this would make some
documents quite unreadable. (in my particular case a command has 4 mandatory
arguments, thus also a
"Left item text" and "Right item summary". (modernCV)
Am 24.11.2012 16:00, schrieb Jürgen Spitzmüller:
This is a bug. It should neither display "opt" nor "req", but the labelstring.
I'll have a look.
But this would look ugly. For example when I have
LabelString "Left item summary"
Its size is OK for the insert menu entry, but for th
Uwe Stöhr wrote:
> - if I have a mandatory argument, the label of the collapsible inset still
> has the name "opt". This is confusing and I fear that users think they can
> omit it. I therefore propose to change it to "required" or "req"
This is a bug. It should neither display "opt" nor "req", b
I have a question regarding layouts:
For modernCV I have the case that an itemize needs to be within another
command, e.g.
\cvlistitem{Another single item.\begin{itemize}\item Sub-item.\end{itemize}}
So I need to nest the itemize into the \cvlistitem. but how is this done? I can nest an itemiz
Am 24.11.2012 09:36, schrieb Jürgen Spitzmüller:
Am Samstag 24 November 2012, 01:02:44 schrieb Uwe Stöhr:
- remove styles that cannot be written into the main text, but have to be
inserted in the preamble
You are aware of the InPreamble tag?
Not yet. I'll revert my change and have a look.
Am Samstag 24 November 2012, 01:02:44 schrieb Uwe Stöhr:
> - remove styles that cannot be written into the main text, but have to be
> inserted in the preamble
You are aware of the InPreamble tag?
Jürgen
Pavel Sanda wrote:
> Not directly related, but are you able to compile the current trunk via
> monolithic build?
I didn't try. I read this message, but I don't know how to fix that.
Jürgen
Richard Heck wrote:
> For the lyx2lyx conversion: Would it be possible for us to convert the
> arguments we know about to the new format? E.g., if it's a short title,
> and we know it is? I suspect this could be done for all of "our" insets
> that take arguments, and would be happy to do the wor
20 matches
Mail list logo
