Additions to documentation toolbar

2020-04-30 Thread Andrew Parsloe

Dear LyX developers,

I've been documenting a LaTeX program recently and have found the 
documentation toolbar useful, but this has highlighted a couple of 
symbols which could usefully be added to the toolbar. One is the section 
mark character § (\S in LaTeX), the other the pilcrow ¶ (\P). At present 
inserting these characters involves Insert > Special Character > Symbols 
and then locating the characters in the character table (which means 
scrolling down or increasing the depth of the dialogue window). They 
would fit perhaps after the information symbol `i'.


Referring to chapter 4 or section 4.3 is fine but it begins to sound 
strained referring to subsection 4.3.2 and just silly referencing 
subsubsection 4.3.2.1. On the other hand, referencing §4.3.2.1 is simple 
and elegant.


Andrew

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Hebrew document template

2020-04-30 Thread Pavel Sanda
On Wed, Apr 29, 2020 at 09:48:13PM +0300, Guy Rutenberg wrote:
> > Would you like to include the example into LyX examples we distribute with
> > the
> > sourcecodes?
> >
> >
> Sure, I think it might be useful.

We have new structure of templates in lyx 2.4.  Given, that the template itself
is seting up hebrew environment rather than particuar document type I thought
to put it into General category.

Juergen, is it OK with you?

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Adding specific content to xhtml output

2020-04-30 Thread Richard Kimberly Heck
On 4/30/20 10:15 AM, Jürgen Spitzmüller wrote:
> Am Donnerstag, den 30.04.2020, 09:56 -0400 schrieb Richard Kimberly
> Heck:
>>> On Thu, Apr 30, 2020 at 07:46:52AM -, Guenter Milde wrote:
>> To know whether they should output or no for different
>> targets (tex
>> vs html).
> Hm. Job for a branch rather?
>>> I think branch is a good idea.
 For convenience, we would want to have target-specific branches
 then:
>>> IMHO better solution is to just add one new textfield into generic
>>> branch
>>> settings where you can fill comma separated list of outputs
>>> targets.
>>> If branch is active & listed target is being used we output the
>>> contents.
>>
>> Or a set of radio buttons?
> GUI-wise I'd propose a checkable list of output formats in another
> QTreeWidget. This would translate into a comma-separated list of output
> formats in the params.

To address Pavel's concern about user-defined formats, we have access to
that info, though we might need some flag to indicate what a 'real'
output format is. Otherwise, we end up with too many listed.


> As to the insets themselves: I understand that we can now bind
> InsetLayouts to branches. This would allow for specific XHTML insets,
> if someone wants this.

Yes, I believe that is possible. If not, it can be made so.

Riki


-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: [LyX/master] Avoid warnings about deprecated copy in gcc 10 too

2020-04-30 Thread Richard Kimberly Heck
On 4/30/20 10:06 AM, Jean-Marc Lasgouttes wrote:
> Le 30/04/2020 à 15:56, Richard Kimberly Heck a écrit :
>> On 4/30/20 6:28 AM, Jean-Marc Lasgouttes wrote:
>>> Le 30/04/2020 à 11:48, Jean-Marc Lasgouttes a écrit :
 commit db5021c42eb5828c3fa0fd786b14eafcf9fed52f
 Author: Jean-Marc Lasgouttes 
 Date:   Thu Apr 30 12:09:17 2020 +0200

   Avoid warnings about deprecated copy in gcc 10 too
>>>
>>> Riki, do you want all the warning-related fixes in branch too?
>>
>> I haven't been doing that myself. But it's not harm.
>
> So it is a 'yes'?

The fixes are welcome but not necessary.

Riki


-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Adding specific content to xhtml output

2020-04-30 Thread Jürgen Spitzmüller
Am Donnerstag, den 30.04.2020, 09:56 -0400 schrieb Richard Kimberly
Heck:
> > On Thu, Apr 30, 2020 at 07:46:52AM -, Guenter Milde wrote:
> > > > > To know whether they should output or no for different
> > > > > targets (tex
> > > > > vs html).
> > > > Hm. Job for a branch rather?
> > I think branch is a good idea.
> > > For convenience, we would want to have target-specific branches
> > > then:
> > IMHO better solution is to just add one new textfield into generic
> > branch
> > settings where you can fill comma separated list of outputs
> > targets.
> > If branch is active & listed target is being used we output the
> > contents.
> 
> 
> Or a set of radio buttons?

GUI-wise I'd propose a checkable list of output formats in another
QTreeWidget. This would translate into a comma-separated list of output
formats in the params.

As to the insets themselves: I understand that we can now bind
InsetLayouts to branches. This would allow for specific XHTML insets,
if someone wants this.

Jürgen


signature.asc
Description: This is a digitally signed message part
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Adding specific content to xhtml output

2020-04-30 Thread Pavel Sanda
On Thu, Apr 30, 2020 at 09:56:00AM -0400, Richard Kimberly Heck wrote:
> On 4/30/20 9:00 AM, Pavel Sanda wrote:
> > On Thu, Apr 30, 2020 at 07:46:52AM -, Guenter Milde wrote:
>  To know whether they should output or no for different targets (tex
>  vs html).
> >>> Hm. Job for a branch rather?
> > I think branch is a good idea.
> >
> >> For convenience, we would want to have target-specific branches then:
> > IMHO better solution is to just add one new textfield into generic branch
> > settings where you can fill comma separated list of outputs targets.
> > If branch is active & listed target is being used we output the contents.
> 
> Or a set of radio buttons?

Option, but less generic (user defined targets won't be covered) and more work 
to do :)

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: [LyX/master] Avoid warnings about deprecated copy in gcc 10 too

2020-04-30 Thread Jean-Marc Lasgouttes

Le 30/04/2020 à 15:56, Richard Kimberly Heck a écrit :

On 4/30/20 6:28 AM, Jean-Marc Lasgouttes wrote:

Le 30/04/2020 à 11:48, Jean-Marc Lasgouttes a écrit :

commit db5021c42eb5828c3fa0fd786b14eafcf9fed52f
Author: Jean-Marc Lasgouttes 
Date:   Thu Apr 30 12:09:17 2020 +0200

  Avoid warnings about deprecated copy in gcc 10 too


Riki, do you want all the warning-related fixes in branch too?


I haven't been doing that myself. But it's not harm.


So it is a 'yes'?

JMarc

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: [LyX/master] Avoid warnings about deprecated copy in gcc 10 too

2020-04-30 Thread Richard Kimberly Heck
On 4/30/20 6:28 AM, Jean-Marc Lasgouttes wrote:
> Le 30/04/2020 à 11:48, Jean-Marc Lasgouttes a écrit :
>> commit db5021c42eb5828c3fa0fd786b14eafcf9fed52f
>> Author: Jean-Marc Lasgouttes 
>> Date:   Thu Apr 30 12:09:17 2020 +0200
>>
>>  Avoid warnings about deprecated copy in gcc 10 too
>
> Riki, do you want all the warning-related fixes in branch too?

I haven't been doing that myself. But it's not harm.

Riki


-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Adding specific content to xhtml output

2020-04-30 Thread Richard Kimberly Heck
On 4/30/20 9:00 AM, Pavel Sanda wrote:
> On Thu, Apr 30, 2020 at 07:46:52AM -, Guenter Milde wrote:
 To know whether they should output or no for different targets (tex
 vs html).
>>> Hm. Job for a branch rather?
> I think branch is a good idea.
>
>> For convenience, we would want to have target-specific branches then:
> IMHO better solution is to just add one new textfield into generic branch
> settings where you can fill comma separated list of outputs targets.
> If branch is active & listed target is being used we output the contents.

Or a set of radio buttons?

Riki


-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Adding specific content to xhtml output

2020-04-30 Thread Pavel Sanda
On Thu, Apr 30, 2020 at 07:46:52AM -, Guenter Milde wrote:
> >> To know whether they should output or no for different targets (tex
> >> vs html).
> 
> > Hm. Job for a branch rather?

I think branch is a good idea.

> For convenience, we would want to have target-specific branches then:

IMHO better solution is to just add one new textfield into generic branch
settings where you can fill comma separated list of outputs targets.
If branch is active & listed target is being used we output the contents.

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Adding specific content to xhtml output

2020-04-30 Thread Guenter Milde
On 2020-04-30, Jürgen Spitzmüller wrote:

> [-- Type: text/plain, Encoding: quoted-printable --]

> Am Mittwoch, den 29.04.2020, 18:42 +0200 schrieb Pavel Sanda:
>> > Why would they need that?


>> To know whether they should output or no for different targets (tex
>> vs html).

> Hm. Job for a branch rather?

For convenience, we would want to have target-specific branches then:

One branch that is automatically active when the target format is HTML, 

one branch that is automatically active when the target format is 
PDF (LuaLaTeX),

one branch that is automatically active when the target format is 
PDF (LuaLaTeX) or DVI (LuaTaTeX),

one branch that is automatically active when the target format is 
PDF (LuaTaTeX), PDF (XeTeX), PDF (pdflatex), or PDF (dvips),

...

Maybe rather in form of a list of output formats where this branch is active.


Advantage: Works not only for ERT

Disadvantage: an additional wrapper (as opposed to an output format setting
to ERT or EBT (evil blue text) for HTML).

Günter

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel