Re: Adding specific content to xhtml output
On Thu, Apr 30, 2020 at 10:51:52AM -0400, Richard Kimberly Heck wrote: > > 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. Yes, we would need some sort of flag to know what we want to list. Looks as an overkill to me, but don't have strong opinion about it. 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
On 2020-04-30, Pavel Sanda wrote: > 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 :) We might want a branch to be active for a set or related output formats like all LaTeX based exports (dvi, dvi3, eps2, eps3, latex, luatex, dviluatex, pdflatex, platex, pdftex, pstex, xetex, pdf, pdf2, pdf3, pdf4, pdf5, pdf6, pdf7, pdf8, ps). Günter -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Adding specific content to xhtml output
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: Adding specific content to xhtml output
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
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: Adding specific content to xhtml output
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
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
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
Re: Adding specific content to xhtml output
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? 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
On 4/29/20 12:42 PM, Pavel Sanda wrote: > On Wed, Apr 29, 2020 at 05:31:55PM +0200, Jürgen Spitzmüller wrote: >> Am Mittwoch, den 29.04.2020, 10:45 -0400 schrieb Richard Kimberly Heck: >>> Probably the cleanest thing would be to have ERT insets have a >>> setting for output format. I.e., LaTeX, DocBook, HTML, etc. But I'm >>> not entirely >> Why would they need that? > To know whether they should output or no for different targets (tex vs html). Yes, of course we don't want to output LaTeX ERT when exporting XHTML, so these are now just ignored in that case. 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
On Wed, Apr 29, 2020 at 05:31:55PM +0200, Jürgen Spitzmüller wrote: > Am Mittwoch, den 29.04.2020, 10:45 -0400 schrieb Richard Kimberly Heck: > > Probably the cleanest thing would be to have ERT insets have a > > setting for output format. I.e., LaTeX, DocBook, HTML, etc. But I'm > > not entirely > > Why would they need that? To know whether they should output or no for different targets (tex vs html). 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
Am Mittwoch, den 29.04.2020, 10:45 -0400 schrieb Richard Kimberly Heck: > Probably the cleanest thing would be to have ERT insets have a > setting for output format. I.e., LaTeX, DocBook, HTML, etc. But I'm > not entirely Why would they need that? Jürgen > > sure. 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
On 4/29/20 3:47 AM, Pavel Sanda wrote: > On Sun, Apr 26, 2020 at 03:19:02AM -0400, Richard Kimberly Heck wrote: >> On 12/3/19 9:59 AM, Pavel Sanda wrote: >>> Hi, >>> >>> I guess this is mainly question on Riki - is there some sane way how to add >>> specific html >>> content to xhtml output in similar way as we do with ERT/preamble settings? >>> >>> Specifically I need to add couple lines in section. I guess the >>> simple answer >>> is no, because I checked, but there might be some workaround through module >>> machinery >>> I am not aware of... >>> Knowing how to add ERT equivalent in the text might would be useful as well. >> Hi, missed this one. At the moment, no. You can probably do ERT-ish >> stuff with passthru, but for , not so much. It shouldn't be >> terribly hard, so if you need it I can get to it for 2.4. Definitely a >> format change, though. > Should I file bug about it? > It may also need little discussion about the way its done. Should completely > new > insets be done or insets like ERT be just extended to allow html snippets? Probably the cleanest thing would be to have ERT insets have a setting for output format. I.e., LaTeX, DocBook, HTML, etc. But I'm not entirely sure. 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
On Sun, Apr 26, 2020 at 03:19:02AM -0400, Richard Kimberly Heck wrote: > On 12/3/19 9:59 AM, Pavel Sanda wrote: > > Hi, > > > > I guess this is mainly question on Riki - is there some sane way how to add > > specific html > > content to xhtml output in similar way as we do with ERT/preamble settings? > > > > Specifically I need to add couple lines in section. I guess the > > simple answer > > is no, because I checked, but there might be some workaround through module > > machinery > > I am not aware of... > > Knowing how to add ERT equivalent in the text might would be useful as well. > > Hi, missed this one. At the moment, no. You can probably do ERT-ish > stuff with passthru, but for , not so much. It shouldn't be > terribly hard, so if you need it I can get to it for 2.4. Definitely a > format change, though. Should I file bug about it? It may also need little discussion about the way its done. Should completely new insets be done or insets like ERT be just extended to allow html snippets? 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
On 12/3/19 9:59 AM, Pavel Sanda wrote: > Hi, > > I guess this is mainly question on Riki - is there some sane way how to add > specific html > content to xhtml output in similar way as we do with ERT/preamble settings? > > Specifically I need to add couple lines in section. I guess the simple > answer > is no, because I checked, but there might be some workaround through module > machinery > I am not aware of... > Knowing how to add ERT equivalent in the text might would be useful as well. Hi, missed this one. At the moment, no. You can probably do ERT-ish stuff with passthru, but for , not so much. It shouldn't be terribly hard, so if you need it I can get to it for 2.4. Definitely a format change, though. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Adding specific content to xhtml output
Hi, I guess this is mainly question on Riki - is there some sane way how to add specific html content to xhtml output in similar way as we do with ERT/preamble settings? Specifically I need to add couple lines in section. I guess the simple answer is no, because I checked, but there might be some workaround through module machinery I am not aware of... Knowing how to add ERT equivalent in the text might would be useful as well. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
