Re: [LyX/master] DocBook: add more flexibility for floats.

[Scott Kostyshak]

On Sun, Dec 05, 2021 at 10:56:49PM +0100, Thibaut Cuvelier wrote:
> Hi Scott,
> 
> My last two commits should solve this issue
> (489bf46a0345216f1a281617ec2a1ae6019c189f) and improve the support for
> Tufte (e3489d54e3485ef186eb70b06d4372eaa400db98). At least, it works
> locally. Does it work on your side too?

Tests pass now. Thanks for the quick fix, Thibaut!

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add more flexibility for floats.

[Thibaut Cuvelier]

Hi Scott,

My last two commits should solve this issue
(489bf46a0345216f1a281617ec2a1ae6019c189f) and improve the support for
Tufte (e3489d54e3485ef186eb70b06d4372eaa400db98). At least, it works
locally. Does it work on your side too?

All the best,
Thibaut

On Sun, 5 Dec 2021 at 20:02, Scott Kostyshak  wrote:

> On Sun, Sep 19, 2021 at 11:45:17PM +0200, Thibaut Cuvelier wrote:
> > commit 8b6e3d374996cc124a9830c71bc2bb744097a7a2
> > Author: Thibaut Cuvelier 
> > Date:   Mon Sep 20 00:06:20 2021 +0200
> >
> > DocBook: add more flexibility for floats.
> >
> > Intended to fix #12371.
> > ---
>
> Starting with this commit a lot of Tufte ctests are failing.
>
> The problem is that if I open up, e.g., Tufte_Book, there is the following
> output:
>
>   $ lyx lib/examples/Books/Tufte_Book.lyx
>   Floating.cpp (72): Unrecognised float type: margintable
>   Floating.cpp (72): Unrecognised float type: marginfigure
>   $
>
> Thibaut, can you confirm?
>
> Scott
>
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add more flexibility for floats.

[Scott Kostyshak]

On Sun, Sep 19, 2021 at 11:45:17PM +0200, Thibaut Cuvelier wrote:
> commit 8b6e3d374996cc124a9830c71bc2bb744097a7a2
> Author: Thibaut Cuvelier 
> Date:   Mon Sep 20 00:06:20 2021 +0200
> 
> DocBook: add more flexibility for floats.
> 
> Intended to fix #12371.
> ---

Starting with this commit a lot of Tufte ctests are failing.

The problem is that if I open up, e.g., Tufte_Book, there is the following 
output:

  $ lyx lib/examples/Books/Tufte_Book.lyx
  Floating.cpp (72): Unrecognised float type: margintable
  Floating.cpp (72): Unrecognised float type: marginfigure
  $

Thibaut, can you confirm?

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Pavel Sanda]

On Wed, Mar 24, 2021 at 10:15:45PM +0100, Thibaut Cuvelier wrote:
> That's right. I've updated the manual to indicate it. Is this better?

Looks good to me, thanks. Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Thibaut Cuvelier]

On Wed, 24 Mar 2021 at 18:36, Pavel Sanda  wrote:

> On Wed, Mar 24, 2021 at 04:38:01PM +0100, Thibaut Cuvelier wrote:
> > On Wed, 24 Mar 2021 at 16:19, Pavel Sanda  wrote:
> >
> > > On Tue, Mar 23, 2021 at 11:25:55PM +0100, Thibaut Cuvelier wrote:
> > > > I have pushed a new section in d0120078fd. I think the most important
> > > > points for the user are documented there. Comments welcome :)!
> > >
> > > Hmm, even after reading about the prefix options I have no clue in what
> > > conditions or context should I choose either of them...
> > >
> >
> > It's a matter either of taste or of buggy tools (like Pandoc right now,
> but
> > others make similar assumptions about the prefix).
>
> Aha, so the proper context which we could state in the manual basically
> is that buggy docbook postprocessing tools (like currently pandoc)
> might require you to select different prefix for mathml content, right?
>

That's right. I've updated the manual to indicate it. Is this better?
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Pavel Sanda]

On Wed, Mar 24, 2021 at 04:38:01PM +0100, Thibaut Cuvelier wrote:
> On Wed, 24 Mar 2021 at 16:19, Pavel Sanda  wrote:
> 
> > On Tue, Mar 23, 2021 at 11:25:55PM +0100, Thibaut Cuvelier wrote:
> > > I have pushed a new section in d0120078fd. I think the most important
> > > points for the user are documented there. Comments welcome :)!
> >
> > Hmm, even after reading about the prefix options I have no clue in what
> > conditions or context should I choose either of them...
> >
> 
> It's a matter either of taste or of buggy tools (like Pandoc right now, but
> others make similar assumptions about the prefix).

Aha, so the proper context which we could state in the manual basically
is that buggy docbook postprocessing tools (like currently pandoc) 
might require you to select different prefix for mathml content, right?

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

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Scott Kostyshak]

On Tue, Mar 23, 2021 at 11:27:35PM +0100, Thibaut Cuvelier wrote:
> On Tue, 23 Mar 2021 at 22:08, Richard Kimberly Heck 
> wrote:
> 
> > On 3/23/21 4:13 PM, Thibaut Cuvelier wrote:
> >
> > On Tue, 23 Mar 2021 at 15:48, Richard Kimberly Heck 
> > wrote:
> >
> >> On 3/22/21 7:33 PM, Thibaut Cuvelier wrote:
> >> > commit 0f782b0ded08953dbcde48f22d51ba87133bc029
> >> > Author: Thibaut Cuvelier 
> >> > Date:   Tue Mar 23 00:08:50 2021 +0100
> >> >
> >> > DocBook: add a parameter to change the namespace prefix for MathML.
> >>
> >> Any time the syntax of semantics of the LyX file itself changes, it's a
> >> format change, so: (1) Bump the document format; (2) Write a lyx2lyx
> >> routine to remove the new parameter; (3) Do what needs doing with
> >> tex2lyx. See lib/doc/Document.lyx, section 2.2.
> >>
> >
> > I had missed that, thanks for the notice. It should be corrected in the
> > new commit: 7a1e048f. There is nothing to add in tex2lyx, as its behaviour
> > should not change with this new parameter.
> >
> > The one last thing to do, then, is to update the tex2lyx tests. Otherwise,
> > Scott will very soon complain that they are all failing.
> >
> With CMake, according to the docs, it should just be running the
> updatetex2lyxtests target. However, it does not do a lot of things: in one
> hour, it only changed one file. Here is the patch:

I think that is the correct target. When I run that target, it takes 45
seconds and produced the diff that I committed at b2b68c3e. I went ahead
and committed the diff so that we can fix the tests while we work
through this issue.

Does it show which commands it is running in the terminal? If not,
perhaps you can look in the process manager? I attach my log for
comparison.

Scott
scott@tallinn:~/lyxbuilds/master/repo$ cd ../CMakeBuild/
scott@tallinn:~/lyxbuilds/master/CMakeBuild$ time make updatetex2lyxtests

/usr/bin/cmake -S/home/scott/lyxbuilds/master/repo 
-B/home/scott/lyxbuilds/master/CMakeBuild --check-build-system 
CMakeFiles/Makefile.cmake 0
make -f CMakeFiles/Makefile2 updatetex2lyxtests
make[1]: Entering directory '/home/scott/lyxbuilds/master/CMakeBuild'
/usr/bin/cmake -S/home/scott/lyxbuilds/master/repo 
-B/home/scott/lyxbuilds/master/CMakeBuild --check-build-system 
CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/home/scott/lyxbuilds/master/CMakeBuild/CMakeFiles 54
make -f CMakeFiles/Makefile2 
src/tex2lyx/test/CMakeFiles/updatetex2lyxtests.dir/all
make[2]: Entering directory '/home/scott/lyxbuilds/master/CMakeBuild'
make -f src/support/CMakeFiles/support.dir/build.make 
src/support/CMakeFiles/support.dir/depend
make[3]: Entering directory '/home/scott/lyxbuilds/master/CMakeBuild'
cd /home/scott/lyxbuilds/master/CMakeBuild && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /home/scott/lyxbuilds/master/repo /home/scott/lyxbuilds/master/
repo/src/support /home/scott/lyxbuilds/master/CMakeBuild 
/home/scott/lyxbuilds/master/CMakeBuild/src/support 
/home/scott/lyxbuilds/master/CMakeBuild/src/suppo
rt/CMakeFiles/support.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/home/scott/lyxbuilds/master/CMakeBuild'
make -f src/support/CMakeFiles/support.dir/build.make 
src/support/CMakeFiles/support.dir/build
make[3]: Entering directory '/home/scott/lyxbuilds/master/CMakeBuild'
make[3]: Nothing to be done for 'src/support/CMakeFiles/support.dir/build'.
make[3]: Leaving directory '/home/scott/lyxbuilds/master/CMakeBuild'
[  7%] Built target support
make -f CMakeFiles/lyx_version.dir/build.make CMakeFiles/lyx_version.dir/depend
make[3]: Entering directory '/home/scott/lyxbuilds/master/CMakeBuild'
cd /home/scott/lyxbuilds/master/CMakeBuild && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /home/scott/lyxbuilds/master/repo /home/scott/lyxbuilds/master/
repo /home/scott/lyxbuilds/master/CMakeBuild 
/home/scott/lyxbuilds/master/CMakeBuild 
/home/scott/lyxbuilds/master/CMakeBuild/CMakeFiles/lyx_version.dir/Depend
Info.cmake --color=
make[3]: Leaving directory '/home/scott/lyxbuilds/master/CMakeBuild'
make -f CMakeFiles/lyx_version.dir/build.make CMakeFiles/lyx_version.dir/build
make[3]: Entering directory '/home/scott/lyxbuilds/master/CMakeBuild'
/usr/bin/cmake -DTOP_SRC_DIR=/home/scott/lyxbuilds/master/repo 
-DTOP_CMAKE_PATH=/home/scott/lyxbuilds/master/repo/development/cmake 
-DTOP_BINARY_DIR=/home/sco
tt/lyxbuilds/master/CMakeBuild -DLYX_DATE=2021-02-14 -P 
/home/scott/lyxbuilds/master/repo/development/cmake/scripts/LyXGetVersion.cmake
-- Git-hash = 616274458e
-- Created /home/scott/lyxbuilds/master/CMakeBuild/lyx_date.tmp
-- Created /home/scott/lyxbuilds/master/CMakeBuild/lyx_commit_hash.tmp
make[3]: Leaving directory '/home/scott/lyxbuilds/master/CMakeBuild'
[  7%] Built target lyx_version
make -f src/tex2lyx/CMakeFiles/tex2lyx.dir/build.make 
src/tex2lyx/CMakeFiles/tex2lyx.dir/depend
make[3]: Entering directory '/home/scott/lyxbuilds/master/CMakeBuild'
cd /home/scott/lyxbuilds/master/CMakeBuild && /usr/bin/cmake -E cmake_depends 

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Scott Kostyshak]

On Wed, Mar 24, 2021 at 09:03:41AM +0100, Jürgen Spitzmüller wrote:
> Am Dienstag, dem 23.03.2021 um 23:32 -0400 schrieb Richard Kimberly
> Heck:
> > I think those tests are worth having. There have been real bugs, I
> > believe.
> 
> Yes, definitely.

Good to know!

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Thibaut Cuvelier]

On Wed, 24 Mar 2021 at 16:19, Pavel Sanda  wrote:

> On Tue, Mar 23, 2021 at 11:25:55PM +0100, Thibaut Cuvelier wrote:
> > I have pushed a new section in d0120078fd. I think the most important
> > points for the user are documented there. Comments welcome :)!
>
> Hmm, even after reading about the prefix options I have no clue in what
> conditions or context should I choose either of them...
>

It's a matter either of taste or of buggy tools (like Pandoc right now, but
others make similar assumptions about the prefix).
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Pavel Sanda]

On Tue, Mar 23, 2021 at 11:25:55PM +0100, Thibaut Cuvelier wrote:
> I have pushed a new section in d0120078fd. I think the most important
> points for the user are documented there. Comments welcome :)!

Hmm, even after reading about the prefix options I have no clue in what
conditions or context should I choose either of them... 

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

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Jürgen Spitzmüller]

Am Dienstag, dem 23.03.2021 um 23:32 -0400 schrieb Richard Kimberly
Heck:
> I think those tests are worth having. There have been real bugs, I
> believe.

Yes, definitely.

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: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Richard Kimberly Heck]

On 3/23/21 5:39 PM, Scott Kostyshak wrote:

On Tue, Mar 23, 2021 at 05:08:39PM -0400, Richard Kimberly Heck wrote:

On 3/23/21 4:13 PM, Thibaut Cuvelier wrote:

On Tue, 23 Mar 2021 at 15:48, Richard Kimberly Heck mailto:rikih...@lyx.org>> wrote:

 On 3/22/21 7:33 PM, Thibaut Cuvelier wrote:
 > commit 0f782b0ded08953dbcde48f22d51ba87133bc029
 > Author: Thibaut Cuvelier mailto:tcuvel...@lyx.org>>
 > Date:   Tue Mar 23 00:08:50 2021 +0100
 >
 >     DocBook: add a parameter to change the namespace prefix for
 MathML.

 Any time the syntax of semantics of the LyX file itself changes,
 it's a
 format change, so: (1) Bump the document format; (2) Write a lyx2lyx
 routine to remove the new parameter; (3) Do what needs doing with
 tex2lyx. See lib/doc/Document.lyx, section 2.2.


I had missed that, thanks for the notice. It should be corrected in the
new commit: 7a1e048f. There is nothing to add in tex2lyx, as its
behaviour should not change with this new parameter.

The one last thing to do, then, is to update the tex2lyx tests. Otherwise,
Scott will very soon complain that they are all failing.

True :). I would be fine, by the way, if the tests were removed. Have
they caught any bugs? Or rather, are they likely to catch bugs in the
future?


I think those tests are worth having. There have been real bugs, I believe.

Riki


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

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Thibaut Cuvelier]

On Tue, 23 Mar 2021 at 22:08, Richard Kimberly Heck 
wrote:

> On 3/23/21 4:13 PM, Thibaut Cuvelier wrote:
>
> On Tue, 23 Mar 2021 at 15:48, Richard Kimberly Heck 
> wrote:
>
>> On 3/22/21 7:33 PM, Thibaut Cuvelier wrote:
>> > commit 0f782b0ded08953dbcde48f22d51ba87133bc029
>> > Author: Thibaut Cuvelier 
>> > Date:   Tue Mar 23 00:08:50 2021 +0100
>> >
>> > DocBook: add a parameter to change the namespace prefix for MathML.
>>
>> Any time the syntax of semantics of the LyX file itself changes, it's a
>> format change, so: (1) Bump the document format; (2) Write a lyx2lyx
>> routine to remove the new parameter; (3) Do what needs doing with
>> tex2lyx. See lib/doc/Document.lyx, section 2.2.
>>
>
> I had missed that, thanks for the notice. It should be corrected in the
> new commit: 7a1e048f. There is nothing to add in tex2lyx, as its behaviour
> should not change with this new parameter.
>
> The one last thing to do, then, is to update the tex2lyx tests. Otherwise,
> Scott will very soon complain that they are all failing.
>
With CMake, according to the docs, it should just be running the
updatetex2lyxtests target. However, it does not do a lot of things: in one
hour, it only changed one file. Here is the patch:

Index: src/tex2lyx/test/test.lyx.lyx
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===
diff --git a/src/tex2lyx/test/test.lyx.lyx b/src/tex2lyx/test/test.lyx.lyx
--- a/src/tex2lyx/test/test.lyx.lyx (revision
d0120078fd1b36076ee77972de068cd459378e5a)
+++ b/src/tex2lyx/test/test.lyx.lyx (date 1616535391572)
@@ -1,5 +1,5 @@
 #LyX file created by tex2lyx 2.4
-\lyxformat 607
+\lyxformat 608
 \begin_document
 \begin_header
 \save_transient_properties true
@@ -89,6 +89,7 @@
 \html_css_as_file 0
 \html_be_strict false
 \docbook_table_output 0
+\docbook_mathml_prefix 1
 \end_header

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

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Thibaut Cuvelier]

On Tue, 23 Mar 2021 at 21:49, Pavel Sanda  wrote:

> On Tue, Mar 23, 2021 at 09:37:07PM +0100, Thibaut Cuvelier wrote:
> > For now, I made a more explicit tool tip. In which part of the
> > documentation would you add this? I was thinking about adding a new
> section
> > in Additional, after the HTML section (before the LyX server).
>
> Yes, that's good location.
>

I have pushed a new section in d0120078fd. I think the most important
points for the user are documented there. Comments welcome :)!
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Scott Kostyshak]

On Tue, Mar 23, 2021 at 05:08:39PM -0400, Richard Kimberly Heck wrote:
> On 3/23/21 4:13 PM, Thibaut Cuvelier wrote:
> > On Tue, 23 Mar 2021 at 15:48, Richard Kimberly Heck  > > wrote:
> > 
> > On 3/22/21 7:33 PM, Thibaut Cuvelier wrote:
> > > commit 0f782b0ded08953dbcde48f22d51ba87133bc029
> > > Author: Thibaut Cuvelier  > >
> > > Date:   Tue Mar 23 00:08:50 2021 +0100
> > >
> > >     DocBook: add a parameter to change the namespace prefix for
> > MathML.
> > 
> > Any time the syntax of semantics of the LyX file itself changes,
> > it's a
> > format change, so: (1) Bump the document format; (2) Write a lyx2lyx
> > routine to remove the new parameter; (3) Do what needs doing with
> > tex2lyx. See lib/doc/Document.lyx, section 2.2.
> > 
> > 
> > I had missed that, thanks for the notice. It should be corrected in the
> > new commit: 7a1e048f. There is nothing to add in tex2lyx, as its
> > behaviour should not change with this new parameter.
> 
> The one last thing to do, then, is to update the tex2lyx tests. Otherwise,
> Scott will very soon complain that they are all failing.

True :). I would be fine, by the way, if the tests were removed. Have
they caught any bugs? Or rather, are they likely to catch bugs in the
future? The only strong preference I have is that if we keep them, we
try our best to update them. I believe updating them is on the check
list in Development.lyx so I guess the hard thing to remember is to
follow the check list.

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Richard Kimberly Heck]

On 3/23/21 4:13 PM, Thibaut Cuvelier wrote:
On Tue, 23 Mar 2021 at 15:48, Richard Kimberly Heck > wrote:


On 3/22/21 7:33 PM, Thibaut Cuvelier wrote:
> commit 0f782b0ded08953dbcde48f22d51ba87133bc029
> Author: Thibaut Cuvelier mailto:tcuvel...@lyx.org>>
> Date:   Tue Mar 23 00:08:50 2021 +0100
>
>     DocBook: add a parameter to change the namespace prefix for
MathML.

Any time the syntax of semantics of the LyX file itself changes,
it's a
format change, so: (1) Bump the document format; (2) Write a lyx2lyx
routine to remove the new parameter; (3) Do what needs doing with
tex2lyx. See lib/doc/Document.lyx, section 2.2.


I had missed that, thanks for the notice. It should be corrected in 
the new commit: 7a1e048f. There is nothing to add in tex2lyx, as its 
behaviour should not change with this new parameter.


The one last thing to do, then, is to update the tex2lyx tests. 
Otherwise, Scott will very soon complain that they are all failing.


Riki



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

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Pavel Sanda]

On Tue, Mar 23, 2021 at 09:37:07PM +0100, Thibaut Cuvelier wrote:
> For now, I made a more explicit tool tip. In which part of the
> documentation would you add this? I was thinking about adding a new section
> in Additional, after the HTML section (before the LyX server).

Yes, that's good location.
Thanks, Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Thibaut Cuvelier]

On Tue, 23 Mar 2021 at 17:15, Pavel Sanda  wrote:

> On Tue, Mar 23, 2021 at 10:48:22AM -0400, Richard Kimberly Heck wrote:
> > On 3/22/21 7:33 PM, Thibaut Cuvelier wrote:
> > > commit 0f782b0ded08953dbcde48f22d51ba87133bc029
> > > Author: Thibaut Cuvelier 
> > > Date:   Tue Mar 23 00:08:50 2021 +0100
> > >
> > > DocBook: add a parameter to change the namespace prefix for MathML.
> >
> > Any time the syntax of semantics of the LyX file itself changes, it's a
> > format change, so: (1) Bump the document format; (2) Write a lyx2lyx
> > routine to remove the new parameter; (3) Do what needs doing with
> > tex2lyx. See lib/doc/Document.lyx, section 2.2.
>
> Additionaly could you please add some documentation for users?
>
> Someone just looking at the document preferences will probably have no idea
> what the prefix options mean or when they should be used...
>

For now, I made a more explicit tool tip. In which part of the
documentation would you add this? I was thinking about adding a new section
in Additional, after the HTML section (before the LyX server).
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Thibaut Cuvelier]

On Tue, 23 Mar 2021 at 15:48, Richard Kimberly Heck 
wrote:

> On 3/22/21 7:33 PM, Thibaut Cuvelier wrote:
> > commit 0f782b0ded08953dbcde48f22d51ba87133bc029
> > Author: Thibaut Cuvelier 
> > Date:   Tue Mar 23 00:08:50 2021 +0100
> >
> > DocBook: add a parameter to change the namespace prefix for MathML.
>
> Any time the syntax of semantics of the LyX file itself changes, it's a
> format change, so: (1) Bump the document format; (2) Write a lyx2lyx
> routine to remove the new parameter; (3) Do what needs doing with
> tex2lyx. See lib/doc/Document.lyx, section 2.2.
>

I had missed that, thanks for the notice. It should be corrected in the new
commit: 7a1e048f. There is nothing to add in tex2lyx, as its behaviour
should not change with this new parameter.
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Pavel Sanda]

On Tue, Mar 23, 2021 at 10:48:22AM -0400, Richard Kimberly Heck wrote:
> On 3/22/21 7:33 PM, Thibaut Cuvelier wrote:
> > commit 0f782b0ded08953dbcde48f22d51ba87133bc029
> > Author: Thibaut Cuvelier 
> > Date:   Tue Mar 23 00:08:50 2021 +0100
> >
> > DocBook: add a parameter to change the namespace prefix for MathML.
> 
> Any time the syntax of semantics of the LyX file itself changes, it's a
> format change, so: (1) Bump the document format; (2) Write a lyx2lyx
> routine to remove the new parameter; (3) Do what needs doing with
> tex2lyx. See lib/doc/Document.lyx, section 2.2.

Additionaly could you please add some documentation for users?

Someone just looking at the document preferences will probably have no idea
what the prefix options mean or when they should be used...


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

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Richard Kimberly Heck]

On 3/22/21 7:33 PM, Thibaut Cuvelier wrote:
> commit 0f782b0ded08953dbcde48f22d51ba87133bc029
> Author: Thibaut Cuvelier 
> Date:   Tue Mar 23 00:08:50 2021 +0100
>
> DocBook: add a parameter to change the namespace prefix for MathML.

Any time the syntax of semantics of the LyX file itself changes, it's a
format change, so: (1) Bump the document format; (2) Write a lyx2lyx
routine to remove the new parameter; (3) Do what needs doing with
tex2lyx. See lib/doc/Document.lyx, section 2.2.

Riki


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

Re: [LyX/master] DocBook: implement prepended/appended arguments for all kinds of elements.

[Pavel Sanda]

On Sun, Feb 21, 2021 at 04:17:45PM +0100, Thibaut Cuvelier wrote:
> Hi Pavel,
> 
> Sorry, I won't be able to have a look at it before at least a week... Maybe
> a make_tuple might help?

It did, thanks. Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement prepended/appended arguments for all kinds of elements.

[Thibaut Cuvelier]

Hi Pavel,

Sorry, I won't be able to have a look at it before at least a week... Maybe
a make_tuple might help?

On Sun, 21 Feb 2021, 14:20 Pavel Sanda,  wrote:

> On Fri Feb 19 17:38:22 2021 +0100, Thibaut Cuvelier wrote:
>
> commit 358e4ace560f4a6a3a8435ac9959e38a23cb6d56
> Author: Thibaut Cuvelier 
> Date:   Fri Feb 19 17:38:22 2021 +0100
>
> DocBook: implement prepended/appended arguments for all kinds of
> elements.
>
> Previously, it was just in InsetText.
>
> ...
> -   return generatedParagraphs;
> + return std::tuple(prependedParagraphs, generatedParagraphs,
> appendedParagraphs);
>
>
> Hi Thibaut,
>
> older gcc won't compile with the following output, could you have a look?
> Pavel
>
>
>   CXX  Paragraph.o
> Paragraph.cpp: In member function
> 'std::tuple ring, std::allocator >,
> std::allocat
> or,
> std::allocator
> > > >, std::__debug::vector std::char_traits >, std::allocator >, std::allocator std::cha
> r_traits, std::allocator > > >,
> std::__debug::vector,
> std::allocator >, std::allocator std::char_traits, std::allocator > > > >
> lyx::Paragraph::simpleDocBookOnePar(const lyx::Buffer&, const
> lyx::OutputParams&, const lyx::Font&, lyx::pos_type, bool, bool) const':
>
> Paragraph.cpp:3594:19: error: missing template arguments before '(' token
> return std::tuple(prependedParagraphs, generatedParagraphs,
> appendedParagraphs);
>
>
>
>
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement prepended/appended arguments for all kinds of elements.

[Pavel Sanda]

On Fri Feb 19 17:38:22 2021 +0100, Thibaut Cuvelier wrote:

commit 358e4ace560f4a6a3a8435ac9959e38a23cb6d56
Author: Thibaut Cuvelier 
Date:   Fri Feb 19 17:38:22 2021 +0100

DocBook: implement prepended/appended arguments for all kinds of elements.

Previously, it was just in InsetText.

...
-   return generatedParagraphs;
+ return std::tuple(prependedParagraphs, generatedParagraphs, 
appendedParagraphs);


Hi Thibaut, 

older gcc won't compile with the following output, could you have a look?
Pavel


  CXX  Paragraph.o   
Paragraph.cpp: In member function 'std::tuple, std::allocator >, std::allocat
or, std::allocator
> > >, std::__debug::vector, std::allocator >, std::allocator, std::allocator > > >, 
std::__debug::vector, 
std::allocator >, std::allocator, std::allocator > > > > 
lyx::Paragraph::simpleDocBookOnePar(const lyx::Buffer&, const 
lyx::OutputParams&, const lyx::Font&, lyx::pos_type, bool, bool) const':

Paragraph.cpp:3594:19: error: missing template arguments before '(' token
return std::tuple(prependedParagraphs, generatedParagraphs, appendedParagraphs);
 


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

Re: [LyX/master] DocBook: add support for DocBookArgumentAfterMainTag.

[Richard Kimberly Heck]

On 2/17/21 4:50 PM, Thibaut Cuvelier wrote:

commit adc7820d458244a6425f269fd98737c8d42ca18a
Author: Thibaut Cuvelier 
Date:   Sun Feb 14 07:07:04 2021 +0100

 DocBook: add support for DocBookArgumentAfterMainTag.


Any change to alyout means a bump in the layout format and, at least, a 
trivial layout2layout conversion. I.e., the layout files you changed 
will need to have their format number increased by one, and that entails 
the need for a conversion for the other files. (That is all because the 
existing format will not read these layout files.)


Riki


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

Re: [LyX/master] DocBook: mark dates to disallow fonts inside.

[Thibaut Cuvelier]

On Sun, 14 Feb 2021 at 17:13, Richard Kimberly Heck 
wrote:

> On 2/14/21 5:25 AM, Enrico Forestieri wrote:
> > On Sun, Feb 14, 2021 at 06:05:12AM +0100, Thibaut Cuvelier wrote:
> >> commit 5297862855f89ed44e62e7667e83b5fc1fd16e16
> >> Author: Thibaut Cuvelier 
> >> Date:   Sun Feb 14 06:08:36 2021 +0100
> >>
> >> DocBook: mark dates to disallow fonts inside.
> > Shouldn't this be the kind of task to be performed by layout2layout.py?
>
> Yes, probably. Thibaut, this should be reverted and replaced by a
> layout2layout routine. Introduce a dummy format change if need be. Are
> you familiar with how to do that? If not, I can do it.
>

Why would this be handled by layout2layout? It's a very specific case (just
one DocBook tag, dozens others could be treated in the same way; it should
be searched for in any DocBook(.*)Tag): I wouldn't trust myself to write
code that sufficiently generic for this task (you would need to parse, at
some point, the DocBook schema to find elements with a very narrow content
model, like
https://github.com/docbook/docbook/blob/main/src/main/relaxng/docbook/pool.rnc#L3789).
Also, I sincerely doubt anyone has already customised DocBook layouts and
would benefit from any large-scale conversion (this being a very
small-scale change, I believe that the benefits would even be lower).
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: mark dates to disallow fonts inside.

[Richard Kimberly Heck]

On 2/14/21 5:25 AM, Enrico Forestieri wrote:
> On Sun, Feb 14, 2021 at 06:05:12AM +0100, Thibaut Cuvelier wrote:
>> commit 5297862855f89ed44e62e7667e83b5fc1fd16e16
>> Author: Thibaut Cuvelier 
>> Date:   Sun Feb 14 06:08:36 2021 +0100
>>
>> DocBook: mark dates to disallow fonts inside.
> Shouldn't this be the kind of task to be performed by layout2layout.py?

Yes, probably. Thibaut, this should be reverted and replaced by a
layout2layout routine. Introduce a dummy format change if need be. Are
you familiar with how to do that? If not, I can do it.

Riki


>> One more test passes.
>> ---
>>  development/autotests/invertedTests |1 -
>>  lib/layouts/AEA.layout  |2 ++
>>  lib/layouts/aa.layout   |1 +
>>  lib/layouts/amsdefs.inc |1 +
>>  lib/layouts/copernicus.layout   |5 +
>>  lib/layouts/dinbrief.layout |1 +
>>  lib/layouts/europasscv.layout   |4 
>>  lib/layouts/europecv.layout |4 
>>  lib/layouts/frletter.layout |1 +
>>  lib/layouts/ijmpc.layout|2 ++
>>  lib/layouts/ijmpd.layout|2 ++
>>  lib/layouts/jasatex.layout  |1 +
>>  lib/layouts/kluwer.layout   |1 +
>>  lib/layouts/lettre.layout   |1 +
>>  lib/layouts/moderncv.layout |1 +
>>  lib/layouts/scrclass.inc|1 +
>>  lib/layouts/scrlettr.layout |1 +
>>  lib/layouts/scrlttr2.layout |1 +
>>  lib/layouts/stdtitle.inc|1 +
>>  19 files changed, 31 insertions(+), 1 deletions(-)
>>
>> diff --git a/development/autotests/invertedTests 
>> b/development/autotests/invertedTests
>> index 8398440..268aac2 100644
>> --- a/development/autotests/invertedTests
>> +++ b/development/autotests/invertedTests
>> @@ -477,7 +477,6 @@ export/doc(|/de|/es|/fr|/ja|/ru)/Math_docbook5
>>  export/doc(|/de|/es|/fr|/ja|/ru)/UserGuide_docbook5
>>  # - Double inlines (code within code, personname within personname, 
>> emphasis within date, etc.).
>>  export/doc/(es|fr|ja)/Customization_docbook5
>> -export/examples/Articles/Chess/Game_2_docbook5
>>  # - Bicaption module would require some C++ implementation.
>>  export/examples(|/de|/fr|/ja)/Modules/Multilingual_Captions_docbook5
>>  # - European CV: hard to mix items and bibliographies.
>> diff --git a/lib/layouts/AEA.layout b/lib/layouts/AEA.layout
>> index 3493600..07c8b5d 100644
>> --- a/lib/layouts/AEA.layout
>> +++ b/lib/layouts/AEA.layout
>> @@ -73,6 +73,7 @@ Style Publication_Month
>>  DocBookAttr   role='month'
>>  DocBookTagTypeparagraph
>>  DocBookInInfo maybe
>> +DocBookNoFontInside   true
>>  End
>>  
>>  Style Publication_Year
>> @@ -83,6 +84,7 @@ Style Publication_Year
>>  DocBookAttr   role='year'
>>  DocBookTagTypeparagraph
>>  DocBookInInfo maybe
>> +DocBookNoFontInside   true
>>  End
>>  
>>  Style Publication_Volume
>> diff --git a/lib/layouts/aa.layout b/lib/layouts/aa.layout
>> index 1caeee1..55b38e4 100644
>> --- a/lib/layouts/aa.layout
>> +++ b/lib/layouts/aa.layout
>> @@ -262,6 +262,7 @@ Style Date
>>  DocBookTag  date
>>  DocBookTagType  paragraph
>>  DocBookInInfo   always
>> +DocBookNoFontInside true
>>  End
>>  
>>  
>> diff --git a/lib/layouts/amsdefs.inc b/lib/layouts/amsdefs.inc
>> index b1c9c87..0d9e6b0 100644
>> --- a/lib/layouts/amsdefs.inc
>> +++ b/lib/layouts/amsdefs.inc
>> @@ -103,6 +103,7 @@ Style Date
>>  DocBookTagdate
>>  DocBookTagTypeparagraph
>>  DocBookInInfo always
>> +DocBookNoFontInside   true
>>  End
>>  
>>  
>> diff --git a/lib/layouts/copernicus.layout b/lib/layouts/copernicus.layout
>> index 676e5d2..02cff4f 100644
>> --- a/lib/layouts/copernicus.layout
>> +++ b/lib/layouts/copernicus.layout
>> @@ -177,6 +177,7 @@ Style Received
>>  DocBookTag  date
>>  DocBookAttr role='received'
>>  DocBookInInfo   always
>> +DocBookNoFontInside   true
>>  End
>>  
>>  Style Accepted
>> @@ -188,6 +189,7 @@ Style Accepted
>>  DocBookTag  date
>>  DocBookAttr role='accepted'
>>  DocBookInInfo   always
>> +DocBookNoFontInside   true
>>  End
>>  
>>  Style Pubdiscuss
>> @@ -200,6 +202,7 @@ Style Pubdiscuss
>>  DocBookTag  date
>>  DocBookAttr role='pubdiscuss'
>>  DocBookInInfo   always
>> +DocBookNoFontInside   true
>>  End
>>  
>>  Style Revised
>> @@ -212,6 +215,7 @@ Style Revised
>>  DocBookTag  date
>>  DocBookAttr role='revised'
>>  DocBookInInfo   always
>> +DocBookNoFontInside   true
>>  End
>>  
>>  Style Published
>> @@ -224,6 +228,7 @@ Style Published
>>  DocBookTag  date
>>  DocBookAttr role='published'
>>  DocBookInInfo   always
>> +DocBookNoFontInside   true
>>  End
>>  
>>  Style Abstract
>> diff --git a/lib/layouts/dinbrief.layout b/lib/layouts/dinbrief.layout
>> index 

Re: [LyX/master] DocBook: mark dates to disallow fonts inside.

[Enrico Forestieri]

On Sun, Feb 14, 2021 at 06:05:12AM +0100, Thibaut Cuvelier wrote:
> commit 5297862855f89ed44e62e7667e83b5fc1fd16e16
> Author: Thibaut Cuvelier 
> Date:   Sun Feb 14 06:08:36 2021 +0100
> 
> DocBook: mark dates to disallow fonts inside.

Shouldn't this be the kind of task to be performed by layout2layout.py?

> One more test passes.
> ---
>  development/autotests/invertedTests |1 -
>  lib/layouts/AEA.layout  |2 ++
>  lib/layouts/aa.layout   |1 +
>  lib/layouts/amsdefs.inc |1 +
>  lib/layouts/copernicus.layout   |5 +
>  lib/layouts/dinbrief.layout |1 +
>  lib/layouts/europasscv.layout   |4 
>  lib/layouts/europecv.layout |4 
>  lib/layouts/frletter.layout |1 +
>  lib/layouts/ijmpc.layout|2 ++
>  lib/layouts/ijmpd.layout|2 ++
>  lib/layouts/jasatex.layout  |1 +
>  lib/layouts/kluwer.layout   |1 +
>  lib/layouts/lettre.layout   |1 +
>  lib/layouts/moderncv.layout |1 +
>  lib/layouts/scrclass.inc|1 +
>  lib/layouts/scrlettr.layout |1 +
>  lib/layouts/scrlttr2.layout |1 +
>  lib/layouts/stdtitle.inc|1 +
>  19 files changed, 31 insertions(+), 1 deletions(-)
> 
> diff --git a/development/autotests/invertedTests 
> b/development/autotests/invertedTests
> index 8398440..268aac2 100644
> --- a/development/autotests/invertedTests
> +++ b/development/autotests/invertedTests
> @@ -477,7 +477,6 @@ export/doc(|/de|/es|/fr|/ja|/ru)/Math_docbook5
>  export/doc(|/de|/es|/fr|/ja|/ru)/UserGuide_docbook5
>  # - Double inlines (code within code, personname within personname, emphasis 
> within date, etc.).
>  export/doc/(es|fr|ja)/Customization_docbook5
> -export/examples/Articles/Chess/Game_2_docbook5
>  # - Bicaption module would require some C++ implementation.
>  export/examples(|/de|/fr|/ja)/Modules/Multilingual_Captions_docbook5
>  # - European CV: hard to mix items and bibliographies.
> diff --git a/lib/layouts/AEA.layout b/lib/layouts/AEA.layout
> index 3493600..07c8b5d 100644
> --- a/lib/layouts/AEA.layout
> +++ b/lib/layouts/AEA.layout
> @@ -73,6 +73,7 @@ Style Publication_Month
>   DocBookAttr   role='month'
>   DocBookTagTypeparagraph
>   DocBookInInfo maybe
> +DocBookNoFontInside   true
>  End
>  
>  Style Publication_Year
> @@ -83,6 +84,7 @@ Style Publication_Year
>   DocBookAttr   role='year'
>   DocBookTagTypeparagraph
>   DocBookInInfo maybe
> +DocBookNoFontInside   true
>  End
>  
>  Style Publication_Volume
> diff --git a/lib/layouts/aa.layout b/lib/layouts/aa.layout
> index 1caeee1..55b38e4 100644
> --- a/lib/layouts/aa.layout
> +++ b/lib/layouts/aa.layout
> @@ -262,6 +262,7 @@ Style Date
>   DocBookTag  date
>   DocBookTagType  paragraph
>   DocBookInInfo   always
> +DocBookNoFontInside true
>  End
>  
>  
> diff --git a/lib/layouts/amsdefs.inc b/lib/layouts/amsdefs.inc
> index b1c9c87..0d9e6b0 100644
> --- a/lib/layouts/amsdefs.inc
> +++ b/lib/layouts/amsdefs.inc
> @@ -103,6 +103,7 @@ Style Date
>   DocBookTagdate
>   DocBookTagTypeparagraph
>   DocBookInInfo always
> +DocBookNoFontInside   true
>  End
>  
>  
> diff --git a/lib/layouts/copernicus.layout b/lib/layouts/copernicus.layout
> index 676e5d2..02cff4f 100644
> --- a/lib/layouts/copernicus.layout
> +++ b/lib/layouts/copernicus.layout
> @@ -177,6 +177,7 @@ Style Received
>   DocBookTag  date
>   DocBookAttr role='received'
>   DocBookInInfo   always
> +DocBookNoFontInside   true
>  End
>  
>  Style Accepted
> @@ -188,6 +189,7 @@ Style Accepted
>   DocBookTag  date
>   DocBookAttr role='accepted'
>   DocBookInInfo   always
> +DocBookNoFontInside   true
>  End
>  
>  Style Pubdiscuss
> @@ -200,6 +202,7 @@ Style Pubdiscuss
>   DocBookTag  date
>   DocBookAttr role='pubdiscuss'
>   DocBookInInfo   always
> +DocBookNoFontInside   true
>  End
>  
>  Style Revised
> @@ -212,6 +215,7 @@ Style Revised
>   DocBookTag  date
>   DocBookAttr role='revised'
>   DocBookInInfo   always
> +DocBookNoFontInside   true
>  End
>  
>  Style Published
> @@ -224,6 +228,7 @@ Style Published
>   DocBookTag  date
>   DocBookAttr role='published'
>   DocBookInInfo   always
> +DocBookNoFontInside   true
>  End
>  
>  Style Abstract
> diff --git a/lib/layouts/dinbrief.layout b/lib/layouts/dinbrief.layout
> index cdbf258..1c360f4 100644
> --- a/lib/layouts/dinbrief.layout
> +++ b/lib/layouts/dinbrief.layout
> @@ -223,6 +223,7 @@ Style Date
>   DocBookAttr""
>   DocBookTagType paragraph
>   DocBookInInfo  always
> +DocBookNoFontInside   true
>  End
>  
>  # dinbrief does not emphasize the subject line
> diff --git a/lib/layouts/europasscv.layout 

Re: [LyX/master] DocBook: implement svglobal.

[Scott Kostyshak]

On Tue, Nov 17, 2020 at 09:16:04PM +0100, Thibaut Cuvelier wrote:
> On Tue, 17 Nov 2020 at 19:06, Kornel Benko  wrote:
> 
> > Am Tue, 17 Nov 2020 11:53:25 -0500
> > schrieb Scott Kostyshak :
> >
> > > On Mon, Nov 16, 2020 at 07:46:12PM +0100, Thibaut Cuvelier wrote:
> > > > commit c6fe1fbe5fbf93cfdef73d52423d61fb72047d88
> > > > Author: Thibaut Cuvelier 
> > > > Date:   Mon Nov 16 20:15:34 2020 +0100
> > > >
> > > > DocBook: implement svglobal.
> > > > ---
> > > >  development/autotests/invertedTests  |4 +++-
> > > >  development/autotests/suspendedTests |   10 +-
> > > >  lib/layouts/svcommon.inc |7 ++-
> > > >  lib/layouts/svglobal.layout  |   15 +++
> > > >  lib/layouts/svglobal3.layout |   14 ++
> > > >  src/output_docbook.cpp   |7 ---
> > > >  6 files changed, 51 insertions(+), 6 deletions(-)
> > >
> > > I'm not sure if it was this commit or a different recent one, but now a
> > bunch of the
> > > Springers_Global_Template tests are failing.
> > >
> > > To reproduce manually, open
> > > lib/templates/Articles/Springers_Global_Journal_Template_%28V._3%29.lyx
> > on the terminal
> > > and look at the warnings. I get the following:
> > >
> > > $ lyx
> > lib/templates/Articles/Springers_Global_Journal_Template_%28V._3%29.lyx
> > > LyX: Unknown InsetLayout tag [around line 67 of
> > > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> > 'DocBookInInfo'
> > > context: ''] LyX: Unknown InsetLayout tag [around line 68 of
> > > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> > 'always' context:
> > > ''] LyX: Unknown InsetLayout tag [around line 78 of
> > > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> > 'DocBookInInfo'
> > > context: ''] LyX: Unknown InsetLayout tag [around line 79 of
> > > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> > 'always' context:
> > > ''] LyX: Unknown InsetLayout tag [around line 95 of
> > > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> > 'DocBookInInfo'
> > > context: ''] LyX: Unknown InsetLayout tag [around line 96 of
> > > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> > 'always' context:
> > > '']
> > >
> > > Scott
> >
> > Missing in src/insets/InsetLayout.cpp:133 ff?
> >
> 
> Thanks for having a look at that! I am currently enhancing quite a bit the
> Springer layouts (DocBook-wise) with new features on the C++ side,

Nice!

> but
> that's still a work in progress… It should be fixed in my WIP patch, but
> it's too WIP for pushing right now…

Good to know. Can you revert this commit then and then put it back in when your 
patch is ready?

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement svglobal.

[Thibaut Cuvelier]

On Tue, 17 Nov 2020 at 19:06, Kornel Benko  wrote:

> Am Tue, 17 Nov 2020 11:53:25 -0500
> schrieb Scott Kostyshak :
>
> > On Mon, Nov 16, 2020 at 07:46:12PM +0100, Thibaut Cuvelier wrote:
> > > commit c6fe1fbe5fbf93cfdef73d52423d61fb72047d88
> > > Author: Thibaut Cuvelier 
> > > Date:   Mon Nov 16 20:15:34 2020 +0100
> > >
> > > DocBook: implement svglobal.
> > > ---
> > >  development/autotests/invertedTests  |4 +++-
> > >  development/autotests/suspendedTests |   10 +-
> > >  lib/layouts/svcommon.inc |7 ++-
> > >  lib/layouts/svglobal.layout  |   15 +++
> > >  lib/layouts/svglobal3.layout |   14 ++
> > >  src/output_docbook.cpp   |7 ---
> > >  6 files changed, 51 insertions(+), 6 deletions(-)
> >
> > I'm not sure if it was this commit or a different recent one, but now a
> bunch of the
> > Springers_Global_Template tests are failing.
> >
> > To reproduce manually, open
> > lib/templates/Articles/Springers_Global_Journal_Template_%28V._3%29.lyx
> on the terminal
> > and look at the warnings. I get the following:
> >
> > $ lyx
> lib/templates/Articles/Springers_Global_Journal_Template_%28V._3%29.lyx
> > LyX: Unknown InsetLayout tag [around line 67 of
> > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> 'DocBookInInfo'
> > context: ''] LyX: Unknown InsetLayout tag [around line 68 of
> > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> 'always' context:
> > ''] LyX: Unknown InsetLayout tag [around line 78 of
> > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> 'DocBookInInfo'
> > context: ''] LyX: Unknown InsetLayout tag [around line 79 of
> > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> 'always' context:
> > ''] LyX: Unknown InsetLayout tag [around line 95 of
> > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> 'DocBookInInfo'
> > context: ''] LyX: Unknown InsetLayout tag [around line 96 of
> > file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token:
> 'always' context:
> > '']
> >
> > Scott
>
> Missing in src/insets/InsetLayout.cpp:133 ff?
>

Thanks for having a look at that! I am currently enhancing quite a bit the
Springer layouts (DocBook-wise) with new features on the C++ side, but
that's still a work in progress… It should be fixed in my WIP patch, but
it's too WIP for pushing right now…
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement svglobal.

[Kornel Benko]

Am Tue, 17 Nov 2020 11:53:25 -0500
schrieb Scott Kostyshak :

> On Mon, Nov 16, 2020 at 07:46:12PM +0100, Thibaut Cuvelier wrote:
> > commit c6fe1fbe5fbf93cfdef73d52423d61fb72047d88
> > Author: Thibaut Cuvelier 
> > Date:   Mon Nov 16 20:15:34 2020 +0100
> > 
> > DocBook: implement svglobal.
> > ---
> >  development/autotests/invertedTests  |4 +++-
> >  development/autotests/suspendedTests |   10 +-
> >  lib/layouts/svcommon.inc |7 ++-
> >  lib/layouts/svglobal.layout  |   15 +++
> >  lib/layouts/svglobal3.layout |   14 ++
> >  src/output_docbook.cpp   |7 ---
> >  6 files changed, 51 insertions(+), 6 deletions(-)  
> 
> I'm not sure if it was this commit or a different recent one, but now a bunch 
> of the
> Springers_Global_Template tests are failing.
> 
> To reproduce manually, open
> lib/templates/Articles/Springers_Global_Journal_Template_%28V._3%29.lyx on 
> the terminal
> and look at the warnings. I get the following:
> 
> $ lyx lib/templates/Articles/Springers_Global_Journal_Template_%28V._3%29.lyx
> LyX: Unknown InsetLayout tag [around line 67 of
> file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 
> 'DocBookInInfo'
> context: ''] LyX: Unknown InsetLayout tag [around line 68 of
> file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 
> 'always' context:
> ''] LyX: Unknown InsetLayout tag [around line 78 of
> file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 
> 'DocBookInInfo'
> context: ''] LyX: Unknown InsetLayout tag [around line 79 of
> file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 
> 'always' context:
> ''] LyX: Unknown InsetLayout tag [around line 95 of
> file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 
> 'DocBookInInfo'
> context: ''] LyX: Unknown InsetLayout tag [around line 96 of
> file /tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 
> 'always' context:
> '']
> 
> Scott

Missing in src/insets/InsetLayout.cpp:133 ff?

Kornel


pgpslK7MJUWt0.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement svglobal.

[Scott Kostyshak]

On Mon, Nov 16, 2020 at 07:46:12PM +0100, Thibaut Cuvelier wrote:
> commit c6fe1fbe5fbf93cfdef73d52423d61fb72047d88
> Author: Thibaut Cuvelier 
> Date:   Mon Nov 16 20:15:34 2020 +0100
> 
> DocBook: implement svglobal.
> ---
>  development/autotests/invertedTests  |4 +++-
>  development/autotests/suspendedTests |   10 +-
>  lib/layouts/svcommon.inc |7 ++-
>  lib/layouts/svglobal.layout  |   15 +++
>  lib/layouts/svglobal3.layout |   14 ++
>  src/output_docbook.cpp   |7 ---
>  6 files changed, 51 insertions(+), 6 deletions(-)

I'm not sure if it was this commit or a different recent one, but now a bunch 
of the Springers_Global_Template tests are failing.

To reproduce manually, open 
lib/templates/Articles/Springers_Global_Journal_Template_%28V._3%29.lyx on the 
terminal and look at the warnings. I get the following:

$ lyx lib/templates/Articles/Springers_Global_Journal_Template_%28V._3%29.lyx
LyX: Unknown InsetLayout tag [around line 67 of file 
/tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 
'DocBookInInfo' context: '']
LyX: Unknown InsetLayout tag [around line 68 of file 
/tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 'always' 
context: '']
LyX: Unknown InsetLayout tag [around line 78 of file 
/tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 
'DocBookInInfo' context: '']
LyX: Unknown InsetLayout tag [around line 79 of file 
/tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 'always' 
context: '']
LyX: Unknown InsetLayout tag [around line 95 of file 
/tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 
'DocBookInInfo' context: '']
LyX: Unknown InsetLayout tag [around line 96 of file 
/tmp/lyx_tmpdir.OHpSZAHguvwA/converturdJfp.layout current token: 'always' 
context: '']

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement Elsevier.

[Thibaut Cuvelier]

On Mon, 16 Nov 2020 at 13:09, Kornel Benko  wrote:

> Am Mon, 16 Nov 2020 05:39:51 +0100 (CET)
> schrieb Thibaut Cuvelier :
>
> > commit d64b3f5397fd50d23bc04d7130f5f5b55d79d7b0
> > Author: Thibaut Cuvelier 
> > Date:   Mon Nov 16 06:09:03 2020 +0100
> >
> > DocBook: implement Elsevier.
> > ---
> >  development/autotests/invertedTests |6 +++
> >  lib/layouts/aa.layout   |1 +
> >  lib/layouts/elsart.layout   |   70
> +++
> >  lib/layouts/elsarticle.layout   |   52 -
> >  lib/layouts/theorems.inc|2 +-
> >  5 files changed, 127 insertions(+), 4 deletions(-)
>
> Nice progress.
> Now there are 24 failed tests left (out of 373).
> OTOH, from the successful are 137 inverted.
>
> Are you planing to uninvert some of the inverted in the future? If so, you
> could mark them
> in suspendedTests too (that is: additionally to invertedTests).
>

Usually, inverted tests are marked as such because of slight validation
problems of the resulting DocBook file. However, fixing these issues would
take a very long time and would mostly consist of adding a lot of code for
just one layout… I am considering this for common cases (like layout
arguments that could be converted to XML attributes or the positioning of
acknowledgements), but not in the short term. I will mark them as suspended
too next time!

Mostly, the output is close to valid DocBook, and it could go through the
usual publication chains and still yield some valid results (e.g., viable
ePub).
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement Elsevier.

[Kornel Benko]

Am Mon, 16 Nov 2020 05:39:51 +0100 (CET)
schrieb Thibaut Cuvelier :

> commit d64b3f5397fd50d23bc04d7130f5f5b55d79d7b0
> Author: Thibaut Cuvelier 
> Date:   Mon Nov 16 06:09:03 2020 +0100
> 
> DocBook: implement Elsevier.
> ---
>  development/autotests/invertedTests |6 +++
>  lib/layouts/aa.layout   |1 +
>  lib/layouts/elsart.layout   |   70 
> +++
>  lib/layouts/elsarticle.layout   |   52 -
>  lib/layouts/theorems.inc|2 +-
>  5 files changed, 127 insertions(+), 4 deletions(-)

Nice progress.
Now there are 24 failed tests left (out of 373).
OTOH, from the successful are 137 inverted.

Are you planing to uninvert some of the inverted in the future? If so, you 
could mark them
in suspendedTests too (that is: additionally to invertedTests).

Kornel


pgp4_dAGVx4vx.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement European CV.

[Kornel Benko]

Am Sat, 14 Nov 2020 17:32:30 +0100
schrieb Thibaut Cuvelier :

> > > This must be a mistake. Please revert, we do not want to have Windows 
> > > settings on
> > > other platforms.
> > >
> > >       Kornel
> > 
> > Never mind, done at c6e6b6de.
> > 
> Indeed, this was a mistake, thanks for dealing with it! (And sorry about 
> that…)
> 

You could try to write a module, say 
development/cmake/modules/LyxInitWindows.cmake
and in the CMakeLists.txt use
if(WIN32)
include(LyxInitWindows)
endif()

Kornel


pgpuLGENQJ7lh.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement European CV.

[Thibaut Cuvelier]

On Sat, 14 Nov 2020 at 12:58, Kornel Benko  wrote:

> Am Sat, 14 Nov 2020 09:55:12 +0100
> schrieb Kornel Benko :
>
> > Am Sat, 14 Nov 2020 05:17:20 +0100 (CET)
> > schrieb Thibaut Cuvelier :
> >
> > > index c9bde3e..dcc05da 100644
> > > --- a/CMakeLists.txt
> > > +++ b/CMakeLists.txt
> > > @@ -6,9 +6,37 @@
> > >
> > >  cmake_minimum_required(VERSION 3.1.0)
> > >
> > > +## set PATH=C:/Strawberry/perl/bin/;%PATH%
> > > +## set PATH=C:\Users\Thibaut\Anaconda3;%PATH%
> > > +## set PATH=C:\Program Files\CMake\bin;%PATH%
> > > +## D:
> > > +## cd LyX\lyx-unstable\cmake-build-debug
> > > +## ctest -j4 -R .*docbook5
> > > +
> > > +set(CMAKE_CXX_STANDARD 17)
> > >  set(GNUWIN32_DIR D:/LyX/lyx-unstable/lyx-windows-deps-msvc2017)
> > > +set(LYX_USE_QT "QT5")
> > > +set(LYX_REQUIRE_SPELLCHECK true)
> > > +set(LYX_ENABLE_EXPORT_TESTS 1)
> > > +
> > > +set(QT_DIR D:/Qt/5.15.0/msvc2019_64)
> > > +set(QT5_DIR D:/Qt/5.15.0/msvc2019_64)
> > > +set(QT_MKSPECS_DIR D:/Qt/5.15.0/msvc2019_64/mkspecs)
> > > +set(Qt5Concurrent_DIR
> D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Concurrent)
> > > +set(Qt5Core_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Core)
> > > +set(Qt5Gui_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Gui)
> > > +set(Qt5Svg_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Svg)
> > > +set(Qt5Widgets_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Widgets)
> > > +set(Qt5WinExtras_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5WinExtras)
> > > +
> > and so on ...
> >
> > This must be a mistake. Please revert, we do not want to have Windows
> settings on other
> > platforms.
> >
> >   Kornel
>
> Never mind, done at c6e6b6de.
>

Indeed, this was a mistake, thanks for dealing with it! (And sorry about
that…)
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement European CV.

[Kornel Benko]

Am Sat, 14 Nov 2020 09:55:12 +0100
schrieb Kornel Benko :

> Am Sat, 14 Nov 2020 05:17:20 +0100 (CET)
> schrieb Thibaut Cuvelier :
> 
> > index c9bde3e..dcc05da 100644
> > --- a/CMakeLists.txt
> > +++ b/CMakeLists.txt
> > @@ -6,9 +6,37 @@
> >  
> >  cmake_minimum_required(VERSION 3.1.0)
> >  
> > +## set PATH=C:/Strawberry/perl/bin/;%PATH%
> > +## set PATH=C:\Users\Thibaut\Anaconda3;%PATH%
> > +## set PATH=C:\Program Files\CMake\bin;%PATH%
> > +## D:
> > +## cd LyX\lyx-unstable\cmake-build-debug
> > +## ctest -j4 -R .*docbook5
> > +
> > +set(CMAKE_CXX_STANDARD 17)
> >  set(GNUWIN32_DIR D:/LyX/lyx-unstable/lyx-windows-deps-msvc2017)
> > +set(LYX_USE_QT "QT5")
> > +set(LYX_REQUIRE_SPELLCHECK true)
> > +set(LYX_ENABLE_EXPORT_TESTS 1)
> > +
> > +set(QT_DIR D:/Qt/5.15.0/msvc2019_64)
> > +set(QT5_DIR D:/Qt/5.15.0/msvc2019_64)
> > +set(QT_MKSPECS_DIR D:/Qt/5.15.0/msvc2019_64/mkspecs)
> > +set(Qt5Concurrent_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Concurrent)
> > +set(Qt5Core_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Core)
> > +set(Qt5Gui_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Gui)
> > +set(Qt5Svg_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Svg)
> > +set(Qt5Widgets_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Widgets)
> > +set(Qt5WinExtras_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5WinExtras)
> > +  
> and so on ...
> 
> This must be a mistake. Please revert, we do not want to have Windows 
> settings on other
> platforms.
> 
>   Kornel

Never mind, done at c6e6b6de.

Kornel


pgpgVj2Gc_dZy.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: implement European CV.

[Kornel Benko]

Am Sat, 14 Nov 2020 05:17:20 +0100 (CET)
schrieb Thibaut Cuvelier :

> index c9bde3e..dcc05da 100644
> --- a/CMakeLists.txt
> +++ b/CMakeLists.txt
> @@ -6,9 +6,37 @@
>  
>  cmake_minimum_required(VERSION 3.1.0)
>  
> +## set PATH=C:/Strawberry/perl/bin/;%PATH%
> +## set PATH=C:\Users\Thibaut\Anaconda3;%PATH%
> +## set PATH=C:\Program Files\CMake\bin;%PATH%
> +## D:
> +## cd LyX\lyx-unstable\cmake-build-debug
> +## ctest -j4 -R .*docbook5
> +
> +set(CMAKE_CXX_STANDARD 17)
>  set(GNUWIN32_DIR D:/LyX/lyx-unstable/lyx-windows-deps-msvc2017)
> +set(LYX_USE_QT "QT5")
> +set(LYX_REQUIRE_SPELLCHECK true)
> +set(LYX_ENABLE_EXPORT_TESTS 1)
> +
> +set(QT_DIR D:/Qt/5.15.0/msvc2019_64)
> +set(QT5_DIR D:/Qt/5.15.0/msvc2019_64)
> +set(QT_MKSPECS_DIR D:/Qt/5.15.0/msvc2019_64/mkspecs)
> +set(Qt5Concurrent_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Concurrent)
> +set(Qt5Core_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Core)
> +set(Qt5Gui_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Gui)
> +set(Qt5Svg_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Svg)
> +set(Qt5Widgets_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5Widgets)
> +set(Qt5WinExtras_DIR D:/Qt/5.15.0/msvc2019_64/lib/cmake/Qt5WinExtras)
> +
and so on ...

This must be a mistake. Please revert, we do not want to have Windows settings 
on other
platforms.

Kornel


pgpGkvkUGuh3S.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: restore the old DocBook support.

[Pavel Sanda]

On Wed, Oct 07, 2020 at 05:08:26AM +0200, Thibaut Cuvelier wrote:
> commit 1a054e45711f30dfdf197a4d2ead4b3365318208
> Author: Thibaut Cuvelier 
> Date:   Wed Oct 7 05:33:56 2020 +0200
> 
> DocBook: restore the old DocBook support.
> ---
>  lib/layouts/db_stdclass.inc|   39 
>  lib/layouts/db_stdstruct.inc   |   21 +++
>  lib/layouts/db_stdtitle.inc|   88 
> 
>  lib/layouts/docbook-book.layout|3 +
>  lib/layouts/docbook.layout |   14 +

These files likely need Makefile.am changes...

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

Re: [LyX/master] DocBook: allow KOMA-Script documents to be generated as DocBook

[Pavel Sanda]

On Mon, Aug 31, 2020 at 03:43:01AM +0200, Thibaut Cuvelier wrote:
> To continue on this, here is the result of Additional.lyx (from the doc) in
> DocBook. Additional.xml is the raw output from LyX, Additional2.xml has
> just two validity issues corrected. I join both a PDF and an EPUB3 output,
> so that you see what you can achieve. All documents were generated from
> within Oxygen XML, which should be calling in particular
> https://github.com/docbook/xslt10-stylesheets/blob/master/xsl/epub3/README
> for EPUB3.

I did not look for details but bullet points seem to be quite broken in my epub
reader (wrong new line just just after bullet glyph in many cases).
If those are corrected it would be IMHO good enough to introduce the conversion
chain from docbook to epub and thus offer epub as an alternative output
target.

The pdf looks very impressive on a first sight. Our priumary chains is 
latex->pdf
so it does not make sense to introduce this pdf output to lyx output; but hey,
it proves quite convincingly that created docbook representation does not miss
lyx document structure (I can't quickly judge this based on xml output).

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

Re: [LyX/master] DocBook: bug fixing with several bibliographic references at once.

[Kornel Benko]

Am Sat, 15 Aug 2020 22:59:19 +0200
schrieb Thibaut Cuvelier :

> On Sat, 15 Aug 2020 at 09:26, Jürgen Spitzmüller  wrote:
> 
> > Am Samstag, den 01.08.2020, 03:26 +0200 schrieb Thibaut Cuvelier:
> > > @@ -627,7 +628,7 @@ void InsetCitation::latex(otexstream & os,
> > > OutputParams const & runparams) const
> > >
> > > // check if we have to do a qualified list
> > >
> > > vector keys =
> > > getVectorFromString(cleanupWhitespace(key));
> > >
> > > bool const qualified = cs.hasQualifiedList
> > >
> > > -   && (!getParam("pretextlist").empty()
> > >
> > > +   && (!getParam("F").empty()
> >
> > I take it this went in by accident. In any case it is wrong and also
> > causes an assertion. I'll revert it.
> >
> > Thibaut, if there is a rationale behind it, please let me know so we
> > can figure out the correct way.
> >
> 
>  It may be due to an attempt to solve a problem when many references are
> present in a single inset, but testing your code shows no regression on
> bibliography_precooked_aastex
> .
> I suppose there was no real reason to correct it in the first place.

It led to a crash of a testcase. (Exporting
American_Psychological_Association_%28APA%29,_v._7.lyx)

Kornel


pgpHXem6m5yog.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: bug fixing with several bibliographic references at once.

[Thibaut Cuvelier]

On Sat, 15 Aug 2020 at 09:26, Jürgen Spitzmüller  wrote:

> Am Samstag, den 01.08.2020, 03:26 +0200 schrieb Thibaut Cuvelier:
> > @@ -627,7 +628,7 @@ void InsetCitation::latex(otexstream & os,
> > OutputParams const & runparams) const
> >
> > // check if we have to do a qualified list
> >
> > vector keys =
> > getVectorFromString(cleanupWhitespace(key));
> >
> > bool const qualified = cs.hasQualifiedList
> >
> > -   && (!getParam("pretextlist").empty()
> >
> > +   && (!getParam("F").empty()
>
> I take it this went in by accident. In any case it is wrong and also
> causes an assertion. I'll revert it.
>
> Thibaut, if there is a rationale behind it, please let me know so we
> can figure out the correct way.
>

 It may be due to an attempt to solve a problem when many references are
present in a single inset, but testing your code shows no regression on
bibliography_precooked_aastex
.
I suppose there was no real reason to correct it in the first place.
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: bug fixing with several bibliographic references at once.

[Jürgen Spitzmüller]

Am Samstag, den 01.08.2020, 03:26 +0200 schrieb Thibaut Cuvelier:
> @@ -627,7 +628,7 @@ void InsetCitation::latex(otexstream & os,
> OutputParams const & runparams) const
> 
> // check if we have to do a qualified list
> 
> vector keys =
> getVectorFromString(cleanupWhitespace(key));
> 
> bool const qualified = cs.hasQualifiedList
> 
> -   && (!getParam("pretextlist").empty()
> 
> +   && (!getParam("F").empty()

I take it this went in by accident. In any case it is wrong and also
causes an assertion. I'll revert it.

Thibaut, if there is a rationale behind it, please let me know so we
can figure out the correct way.

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: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Thibaut Cuvelier]

On Mon, 3 Aug 2020 at 23:06, Scott Kostyshak  wrote:

> On Mon, Aug 03, 2020 at 11:02:28PM +0200, Thibaut Cuvelier wrote:
> > On Mon, 3 Aug 2020 at 19:45, Scott Kostyshak  wrote:
> >
> > > On Mon, Aug 03, 2020 at 12:08:51PM -0400, Richard Kimberly Heck wrote:
> > > > On 8/3/20 10:57 AM, Thibaut Cuvelier wrote:
> > > > > On Mon, 3 Aug 2020 at 16:41, Scott Kostyshak  > > > > <mailto:skost...@lyx.org>> wrote:
> > > > >
> > > > > On Mon, Aug 03, 2020 at 04:29:57PM +0200, Kornel Benko wrote:
> > > > > > Am Mon,  3 Aug 2020 15:39:49 +0200 (CEST)
> > > > > > schrieb Thibaut Cuvelier  > > > > <mailto:tcuvel...@lyx.org>>:
> > > > > >
> > > > > > > commit 5ccd63eff6731a972f1d65d855859a65fe8e3a5b
> > > > > > > Author: Thibaut Cuvelier  > > > > <mailto:tcuvel...@lyx.org>>
> > > > > > > Date:   Mon Aug 3 16:04:26 2020 +0200
> > > > > > >
> > > > > > > DocBook: add a layout tag to tell whether an item is
> the
> > > > > abstract or not.
> > > > > > > ---
> > > > > > >  .../docbook/bibliography_precooked_aastex.xml  |  221
> > > > > -
> > > > > > >  lib/layouts/aastex.layout  |3
> -
> > > > > > >  lib/layouts/stdstruct.inc  |3
> +-
> > > > > > >  lib/scripts/layout2layout.py   |2
> +-
> > > > > > >  src/Layout.cpp |8
> +
> > > > > > >  src/Layout.h   |9
> +-
> > > > > > >  src/output_docbook.cpp |  265
> > > > > 
> > > > > > >  src/xml.h  |2
> +
> > > > > > >  8 files changed, 283 insertions(+), 230 deletions(-)
> > > > > >
> > > > > > Thibaut, could you please test the exports before commit?
> > > > > >
> > > > > > Some of the last commits are the reason for
> > > > > >
> > > > > > 1.) extrem slowness
> > > > > > 2.) many endless loops
> > > > > > 3.) 54% tests passed, 162 tests failed out of 350
> > > > >
> > > > > +1
> > > > > An alternative would be to do work on a branch, then when you
> are
> > > > > ready
> > > > > do all the testing at once and then after the testing looks
> good
> > > merge
> > > > > to master.
> > > > >
> > > > > I think that some projects are not as strict, but here on
> master
> > > > > we like
> > > > > to keep it useable. This makes it easier to test master.
> Also, it
> > > > > makes
> > > > > it easier to bisect other bugs that have nothing to do with a
> > > commit
> > > > > that broke something else.
> > > > >
> > > > > Thank you very much to Thibaut for all of your work!
> > > > >
> > > > > And thank you to Kornel for spending so much time on the tests.
> > > > >
> > > > >
> > > > > Working on a branch would be the best solution, indeed. May I do a
> > > > > force push to remove those commits from master?
> > > >
> > > > Just revert them, I'd think.
> > >
> > > +1
> > >
> > > For a branch, if Thibaut would like to share the branch before pushing,
> > > perhaps the "features" remote would be the right place? In normal
> times,
> > > I would be interested in pulling your branch (from features), and
> > > running the tests to see if there are any regressions. However, these
> > > days I do not have the time to offer this.
> > >
> >
> > I've just reverted many commits, and put them back in a branch locally.
> > However, the Git server does not accept new branches (or I'm doing
> > something wrong):
> >
> > $ git push --set-upstream official feature/docbook
> > Enumerating objects: 104, done.
> > Counting objects: 100% (104/104), done.
> > Delta compression using up to 12 threads
> > Compressing objects: 100% (87/87), done.
> > Writing objects: 100% (87/87), 15.74 KiB | 848.00 KiB/s, done.
> > Total 87 (delta 76), reused 0 (delta 0), pack-reused 0
> > remote: C refs/heads/feature/docbook lyx tcuvelier DENIED by fallthru
> > remote: error: hook declined to update refs/heads/feature/docbook
> > To git.lyx.org:lyx
> >  ! [remote rejected]   feature/docbook -> feature/docbook (hook
> > declined)
> > error: failed to push some refs to 'git.lyx.org:lyx'
>
> Thanks for being responsive to feedback and for your time on that,
> Thibaut. I'm not sure how to set up your access for the features remote.
> I have the following settings:
>
> featuresg...@git.lyx.org:features.git (fetch)
> featuresg...@git.lyx.org:features.git (push)
>
> I don't know if this information is up-to-date:
>
> https://wiki.lyx.org/Devel/LyXGit#toc3


I didn't get that there was a separate repository. I just pushed a new
branch for this:

$ git ls-remote features
8b5abcce1c633be06d66413e95b22896523a9194refs/heads/features/docbook
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Kornel Benko]

Am Tue, 4 Aug 2020 11:43:57 +0200
schrieb Kornel Benko :

> Am Tue, 4 Aug 2020 01:04:06 -0400
> schrieb Richard Kimberly Heck :
> 
> > >>> Working on a branch would be the best solution, indeed. May I do a
> > >>> force push to remove those commits from master? 
> > >> Just revert them, I'd think.
> > > +1
> > >
> > > For a branch, if Thibaut would like to share the branch before pushing,
> > > perhaps the "features" remote would be the right place? 
> > 
> > Yes, that would be the easiest thing. Then people can give feedback
> > along the way.
> > 
> > Riki
> >   
> 
> It would help, if your patches would not be sooo huge. In that case I could 
> run the
> tests and send you the results. Repeating unless the change does not create 
> failures.
> 
> For you it would be easy to find the cause, because of the small patch.
> 
> Then the patch can be committed.
> 
> Repeat this procedure with the next snippet.
> 
>   Kornel


So, after the last reversions, the failed list is cleaner, but surprisingly not 
empty.
97% tests passed, 12 tests failed out of 350

The following tests FAILED:
1717 - export/doc/Customization_docbook5 (Failed)
1789 - export/doc/EmbeddedObjects_docbook5 (Failed)
2064 - export/doc/de/Customization_docbook5 (Failed)
2118 - export/doc/de/EmbeddedObjects_docbook5 (Failed)
2280 - export/doc/es/Customization_docbook5 (Failed)
2334 - export/doc/es/EmbeddedObjects_docbook5 (Failed)
2514 - export/doc/fr/Customization_docbook5 (Failed)
2568 - export/doc/fr/EmbeddedObjects_docbook5 (Failed)
2892 - export/doc/ja/Additional_docbook5 (Failed)
2907 - export/doc/ja/Customization_docbook5 (Failed)
2952 - export/doc/ja/EmbeddedObjects_docbook5 (Failed)
3869 - export/examples/Graphics_and_Insets/XY-Pic_docbook5 (Failed)
Errors while running CTest

Please Thibaut, we should try to resolve these cases first.

Start with export/doc/Customization_docbook5

Opening and ending tag mismatch: listitem line 1699 and varlistentry -> book(1),
chapter(5), section(3), section(7), variablelist(1), varlistentry(35), 
listitem(1),
para(1)
Opening and ending tag mismatch: para line 1787 and listitem -> book(1), 
chapter(5),
section(3), section(7), variablelist(1), varlistentry(35), listitem(1), para(1)
Opening and ending tag mismatch: listitem line 1786 and varlistentry -> book(1),
chapter(5), section(3), section(7), variablelist(1), varlistentry(35), 
listitem(1),
para(1)
Opening and ending tag mismatch: varlistentry line 1784 and variablelist -> 
book(1),
chapter(5), section(3), section(7), variablelist(1), varlistentry(35), 
listitem(1),
para(1)
Opening and ending tag mismatch: varlistentry line 1697 and section -> book(1),
chapter(5), section(3), section(7), variablelist(1), varlistentry(35), 
listitem(1),
para(1)
Opening and ending tag mismatch: variablelist line 1348 and section -> book(1),
chapter(5), section(3), section(7), variablelist(1), varlistentry(35), 
listitem(1),
para(1)
Opening and ending tag mismatch: section line 1338 and chapter -> book(1), 
chapter(5),
section(3), section(7), variablelist(1), varlistentry(35), listitem(1), para(1)
Opening and ending tag mismatch: section line 822 and book -> book(1), 
chapter(5),
section(3), section(7), variablelist(1), varlistentry(35), listitem(1), para(1)
Premature end of data in tag chapter line 607 -> book(1), chapter(5), 
section(3),
section(7), variablelist(1), varlistentry(35), listitem(1), para(1)
Premature end of data in tag book line 4 -> book(1), chapter(5), section(3), 
section(7),
variablelist(1), varlistentry(35), listitem(1), para(1)


Message of perl xml-parser:
mismatched tag at line 1764, column 2, byte 124052
at /usr/lib/x86_64-linux-gnu/perl5/5.26/XML/Parser.pm line 187.


Would be nice, if the xml output were formatted (indented). It is extremely 
hard to see
the missed tags.

Kornel




pgppnWyuKkw9M.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Kornel Benko]

Am Tue, 4 Aug 2020 01:04:06 -0400
schrieb Richard Kimberly Heck :

> >>> Working on a branch would be the best solution, indeed. May I do a
> >>> force push to remove those commits from master?   
> >> Just revert them, I'd think.  
> > +1
> >
> > For a branch, if Thibaut would like to share the branch before pushing,
> > perhaps the "features" remote would be the right place?   
> 
> Yes, that would be the easiest thing. Then people can give feedback
> along the way.
> 
> Riki
> 

It would help, if your patches would not be sooo huge. In that case I could run 
the tests
and send you the results. Repeating unless the change does not create failures.

For you it would be easy to find the cause, because of the small patch.

Then the patch can be committed.

Repeat this procedure with the next snippet.

Kornel


pgpqc89i1IOD2.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Richard Kimberly Heck]

On 8/3/20 5:06 PM, Scott Kostyshak wrote:
> On Mon, Aug 03, 2020 at 11:02:28PM +0200, Thibaut Cuvelier wrote:
>> On Mon, 3 Aug 2020 at 19:45, Scott Kostyshak  wrote:
>>
>>> On Mon, Aug 03, 2020 at 12:08:51PM -0400, Richard Kimberly Heck wrote:
>>>> On 8/3/20 10:57 AM, Thibaut Cuvelier wrote:
>>>>> On Mon, 3 Aug 2020 at 16:41, Scott Kostyshak >>>> <mailto:skost...@lyx.org>> wrote:
>>>>>
>>>>> On Mon, Aug 03, 2020 at 04:29:57PM +0200, Kornel Benko wrote:
>>>>> > Am Mon,  3 Aug 2020 15:39:49 +0200 (CEST)
>>>>> > schrieb Thibaut Cuvelier >>>> <mailto:tcuvel...@lyx.org>>:
>>>>> >
>>>>> > > commit 5ccd63eff6731a972f1d65d855859a65fe8e3a5b
>>>>> > > Author: Thibaut Cuvelier >>>> <mailto:tcuvel...@lyx.org>>
>>>>> > > Date:   Mon Aug 3 16:04:26 2020 +0200
>>>>> > >
>>>>> > > DocBook: add a layout tag to tell whether an item is the
>>>>> abstract or not.
>>>>> > > ---
>>>>> > >  .../docbook/bibliography_precooked_aastex.xml  |  221
>>>>> -
>>>>> > >  lib/layouts/aastex.layout  |3 -
>>>>> > >  lib/layouts/stdstruct.inc  |3 +-
>>>>> > >  lib/scripts/layout2layout.py   |2 +-
>>>>> > >  src/Layout.cpp |8 +
>>>>> > >  src/Layout.h   |9 +-
>>>>> > >  src/output_docbook.cpp |  265
>>>>> 
>>>>> > >  src/xml.h  |2 +
>>>>> > >  8 files changed, 283 insertions(+), 230 deletions(-)
>>>>> >
>>>>> > Thibaut, could you please test the exports before commit?
>>>>> >
>>>>> > Some of the last commits are the reason for
>>>>> >
>>>>> > 1.) extrem slowness
>>>>> > 2.) many endless loops
>>>>> > 3.) 54% tests passed, 162 tests failed out of 350
>>>>>
>>>>> +1
>>>>> An alternative would be to do work on a branch, then when you are
>>>>> ready
>>>>> do all the testing at once and then after the testing looks good
>>> merge
>>>>> to master.
>>>>>
>>>>> I think that some projects are not as strict, but here on master
>>>>> we like
>>>>> to keep it useable. This makes it easier to test master.  Also, it
>>>>> makes
>>>>> it easier to bisect other bugs that have nothing to do with a
>>> commit
>>>>> that broke something else.
>>>>>
>>>>> Thank you very much to Thibaut for all of your work!
>>>>>
>>>>> And thank you to Kornel for spending so much time on the tests.
>>>>>
>>>>>
>>>>> Working on a branch would be the best solution, indeed. May I do a
>>>>> force push to remove those commits from master?
>>>> Just revert them, I'd think.
>>> +1
>>>
>>> For a branch, if Thibaut would like to share the branch before pushing,
>>> perhaps the "features" remote would be the right place? In normal times,
>>> I would be interested in pulling your branch (from features), and
>>> running the tests to see if there are any regressions. However, these
>>> days I do not have the time to offer this.
>>>
>> I've just reverted many commits, and put them back in a branch locally.
>> However, the Git server does not accept new branches (or I'm doing
>> something wrong):
>>
>> $ git push --set-upstream official feature/docbook
>> Enumerating objects: 104, done.
>> Counting objects: 100% (104/104), done.
>> Delta compression using up to 12 threads
>> Compressing objects: 100% (87/87), done.
>> Writing objects: 100% (87/87), 15.74 KiB | 848.00 KiB/s, done.
>> Total 87 (delta 76), reused 0 (delta 0), pack-reused 0
>> remote: C refs/heads/feature/docbook lyx tcuvelier DENIED by fallthru
>> remote: error: hook declined to update refs/heads/feature/docbook
>> To git.lyx.org:lyx
>>  ! [remote rejected]   feature/docbook -> feature/docbook (hook
>> declined)
>> error: failed to push some refs to 'git.lyx.org:lyx'
> Thanks for being responsive to feedback and for your time on that,
> Thibaut. I'm not sure how to set up your access for the features remote.
> I have the following settings:
>
> features  g...@git.lyx.org:features.git (fetch)
> features  g...@git.lyx.org:features.git (push)
>
> I don't know if this information is up-to-date:
>
> https://wiki.lyx.org/Devel/LyXGit#toc3

I would expect it to be, but if not, we can fix it.

Riki


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

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Richard Kimberly Heck]

On 8/3/20 1:44 PM, Scott Kostyshak wrote:
> On Mon, Aug 03, 2020 at 12:08:51PM -0400, Richard Kimberly Heck wrote:
>> On 8/3/20 10:57 AM, Thibaut Cuvelier wrote:
>>> On Mon, 3 Aug 2020 at 16:41, Scott Kostyshak >> > wrote:
>>>
>>> On Mon, Aug 03, 2020 at 04:29:57PM +0200, Kornel Benko wrote:
>>> > Am Mon,  3 Aug 2020 15:39:49 +0200 (CEST)
>>> > schrieb Thibaut Cuvelier >> >:
>>> >
>>> > > commit 5ccd63eff6731a972f1d65d855859a65fe8e3a5b
>>> > > Author: Thibaut Cuvelier >> >
>>> > > Date:   Mon Aug 3 16:04:26 2020 +0200
>>> > >
>>> > >     DocBook: add a layout tag to tell whether an item is the
>>> abstract or not.
>>> > > ---
>>> > >  .../docbook/bibliography_precooked_aastex.xml      |  221
>>> -
>>> > >  lib/layouts/aastex.layout                          |    3 -
>>> > >  lib/layouts/stdstruct.inc                          |    3 +-
>>> > >  lib/scripts/layout2layout.py                       |    2 +-
>>> > >  src/Layout.cpp                                     |    8 +
>>> > >  src/Layout.h                                       |    9 +-
>>> > >  src/output_docbook.cpp                             |  265
>>> 
>>> > >  src/xml.h                                          |    2 +
>>> > >  8 files changed, 283 insertions(+), 230 deletions(-)
>>> >
>>> > Thibaut, could you please test the exports before commit?
>>> >
>>> > Some of the last commits are the reason for
>>> >
>>> > 1.) extrem slowness
>>> > 2.) many endless loops
>>> > 3.) 54% tests passed, 162 tests failed out of 350
>>>
>>> +1
>>> An alternative would be to do work on a branch, then when you are
>>> ready
>>> do all the testing at once and then after the testing looks good merge
>>> to master.
>>>
>>> I think that some projects are not as strict, but here on master
>>> we like
>>> to keep it useable. This makes it easier to test master.  Also, it
>>> makes
>>> it easier to bisect other bugs that have nothing to do with a commit
>>> that broke something else.
>>>
>>> Thank you very much to Thibaut for all of your work!
>>>
>>> And thank you to Kornel for spending so much time on the tests.
>>>
>>>
>>> Working on a branch would be the best solution, indeed. May I do a
>>> force push to remove those commits from master? 
>> Just revert them, I'd think.
> +1
>
> For a branch, if Thibaut would like to share the branch before pushing,
> perhaps the "features" remote would be the right place? 

Yes, that would be the easiest thing. Then people can give feedback
along the way.

Riki


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

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Scott Kostyshak]

On Mon, Aug 03, 2020 at 11:02:28PM +0200, Thibaut Cuvelier wrote:
> On Mon, 3 Aug 2020 at 19:45, Scott Kostyshak  wrote:
> 
> > On Mon, Aug 03, 2020 at 12:08:51PM -0400, Richard Kimberly Heck wrote:
> > > On 8/3/20 10:57 AM, Thibaut Cuvelier wrote:
> > > > On Mon, 3 Aug 2020 at 16:41, Scott Kostyshak  > > > <mailto:skost...@lyx.org>> wrote:
> > > >
> > > > On Mon, Aug 03, 2020 at 04:29:57PM +0200, Kornel Benko wrote:
> > > > > Am Mon,  3 Aug 2020 15:39:49 +0200 (CEST)
> > > > > schrieb Thibaut Cuvelier  > > > <mailto:tcuvel...@lyx.org>>:
> > > > >
> > > > > > commit 5ccd63eff6731a972f1d65d855859a65fe8e3a5b
> > > > > > Author: Thibaut Cuvelier  > > > <mailto:tcuvel...@lyx.org>>
> > > > > > Date:   Mon Aug 3 16:04:26 2020 +0200
> > > > > >
> > > > > > DocBook: add a layout tag to tell whether an item is the
> > > > abstract or not.
> > > > > > ---
> > > > > >  .../docbook/bibliography_precooked_aastex.xml  |  221
> > > > -
> > > > > >  lib/layouts/aastex.layout  |3 -
> > > > > >  lib/layouts/stdstruct.inc  |3 +-
> > > > > >  lib/scripts/layout2layout.py   |2 +-
> > > > > >  src/Layout.cpp |8 +
> > > > > >  src/Layout.h   |9 +-
> > > > > >  src/output_docbook.cpp |  265
> > > > 
> > > > > >  src/xml.h  |2 +
> > > > > >  8 files changed, 283 insertions(+), 230 deletions(-)
> > > > >
> > > > > Thibaut, could you please test the exports before commit?
> > > > >
> > > > > Some of the last commits are the reason for
> > > > >
> > > > > 1.) extrem slowness
> > > > > 2.) many endless loops
> > > > > 3.) 54% tests passed, 162 tests failed out of 350
> > > >
> > > > +1
> > > > An alternative would be to do work on a branch, then when you are
> > > > ready
> > > > do all the testing at once and then after the testing looks good
> > merge
> > > > to master.
> > > >
> > > > I think that some projects are not as strict, but here on master
> > > > we like
> > > > to keep it useable. This makes it easier to test master.  Also, it
> > > > makes
> > > > it easier to bisect other bugs that have nothing to do with a
> > commit
> > > > that broke something else.
> > > >
> > > > Thank you very much to Thibaut for all of your work!
> > > >
> > > > And thank you to Kornel for spending so much time on the tests.
> > > >
> > > >
> > > > Working on a branch would be the best solution, indeed. May I do a
> > > > force push to remove those commits from master?
> > >
> > > Just revert them, I'd think.
> >
> > +1
> >
> > For a branch, if Thibaut would like to share the branch before pushing,
> > perhaps the "features" remote would be the right place? In normal times,
> > I would be interested in pulling your branch (from features), and
> > running the tests to see if there are any regressions. However, these
> > days I do not have the time to offer this.
> >
> 
> I've just reverted many commits, and put them back in a branch locally.
> However, the Git server does not accept new branches (or I'm doing
> something wrong):
> 
> $ git push --set-upstream official feature/docbook
> Enumerating objects: 104, done.
> Counting objects: 100% (104/104), done.
> Delta compression using up to 12 threads
> Compressing objects: 100% (87/87), done.
> Writing objects: 100% (87/87), 15.74 KiB | 848.00 KiB/s, done.
> Total 87 (delta 76), reused 0 (delta 0), pack-reused 0
> remote: C refs/heads/feature/docbook lyx tcuvelier DENIED by fallthru
> remote: error: hook declined to update refs/heads/feature/docbook
> To git.lyx.org:lyx
>  ! [remote rejected]   feature/docbook -> feature/docbook (hook
> declined)
> error: failed to push some refs to 'git.lyx.org:lyx'

Thanks for being responsive to feedback and for your time on that,
Thibaut. I'm not sure how to set up your access for the features remote.
I have the following settings:

featuresg...@git.lyx.org:features.git (fetch)
featuresg...@git.lyx.org:features.git (push)

I don't know if this information is up-to-date:

https://wiki.lyx.org/Devel/LyXGit#toc3

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Thibaut Cuvelier]

On Mon, 3 Aug 2020 at 19:45, Scott Kostyshak  wrote:

> On Mon, Aug 03, 2020 at 12:08:51PM -0400, Richard Kimberly Heck wrote:
> > On 8/3/20 10:57 AM, Thibaut Cuvelier wrote:
> > > On Mon, 3 Aug 2020 at 16:41, Scott Kostyshak  > > <mailto:skost...@lyx.org>> wrote:
> > >
> > > On Mon, Aug 03, 2020 at 04:29:57PM +0200, Kornel Benko wrote:
> > > > Am Mon,  3 Aug 2020 15:39:49 +0200 (CEST)
> > > > schrieb Thibaut Cuvelier  > > <mailto:tcuvel...@lyx.org>>:
> > > >
> > > > > commit 5ccd63eff6731a972f1d65d855859a65fe8e3a5b
> > > > > Author: Thibaut Cuvelier  > > <mailto:tcuvel...@lyx.org>>
> > > > > Date:   Mon Aug 3 16:04:26 2020 +0200
> > > > >
> > > > > DocBook: add a layout tag to tell whether an item is the
> > > abstract or not.
> > > > > ---
> > > > >  .../docbook/bibliography_precooked_aastex.xml  |  221
> > > -
> > > > >  lib/layouts/aastex.layout  |3 -
> > > > >  lib/layouts/stdstruct.inc  |3 +-
> > > > >  lib/scripts/layout2layout.py   |2 +-
> > > > >  src/Layout.cpp |8 +
> > > > >  src/Layout.h   |9 +-
> > > > >  src/output_docbook.cpp |  265
> > > 
> > > > >  src/xml.h  |2 +
> > > > >  8 files changed, 283 insertions(+), 230 deletions(-)
> > > >
> > > > Thibaut, could you please test the exports before commit?
> > > >
> > > > Some of the last commits are the reason for
> > > >
> > > > 1.) extrem slowness
> > > > 2.) many endless loops
> > > > 3.) 54% tests passed, 162 tests failed out of 350
> > >
> > > +1
> > > An alternative would be to do work on a branch, then when you are
> > > ready
> > > do all the testing at once and then after the testing looks good
> merge
> > > to master.
> > >
> > > I think that some projects are not as strict, but here on master
> > > we like
> > > to keep it useable. This makes it easier to test master.  Also, it
> > > makes
> > > it easier to bisect other bugs that have nothing to do with a
> commit
> > > that broke something else.
> > >
> > > Thank you very much to Thibaut for all of your work!
> > >
> > > And thank you to Kornel for spending so much time on the tests.
> > >
> > >
> > > Working on a branch would be the best solution, indeed. May I do a
> > > force push to remove those commits from master?
> >
> > Just revert them, I'd think.
>
> +1
>
> For a branch, if Thibaut would like to share the branch before pushing,
> perhaps the "features" remote would be the right place? In normal times,
> I would be interested in pulling your branch (from features), and
> running the tests to see if there are any regressions. However, these
> days I do not have the time to offer this.
>

I've just reverted many commits, and put them back in a branch locally.
However, the Git server does not accept new branches (or I'm doing
something wrong):

$ git push --set-upstream official feature/docbook
Enumerating objects: 104, done.
Counting objects: 100% (104/104), done.
Delta compression using up to 12 threads
Compressing objects: 100% (87/87), done.
Writing objects: 100% (87/87), 15.74 KiB | 848.00 KiB/s, done.
Total 87 (delta 76), reused 0 (delta 0), pack-reused 0
remote: C refs/heads/feature/docbook lyx tcuvelier DENIED by fallthru
remote: error: hook declined to update refs/heads/feature/docbook
To git.lyx.org:lyx
 ! [remote rejected]   feature/docbook -> feature/docbook (hook
declined)
error: failed to push some refs to 'git.lyx.org:lyx'
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Scott Kostyshak]

On Mon, Aug 03, 2020 at 12:08:51PM -0400, Richard Kimberly Heck wrote:
> On 8/3/20 10:57 AM, Thibaut Cuvelier wrote:
> > On Mon, 3 Aug 2020 at 16:41, Scott Kostyshak  > > wrote:
> >
> > On Mon, Aug 03, 2020 at 04:29:57PM +0200, Kornel Benko wrote:
> > > Am Mon,  3 Aug 2020 15:39:49 +0200 (CEST)
> > > schrieb Thibaut Cuvelier  > >:
> > >
> > > > commit 5ccd63eff6731a972f1d65d855859a65fe8e3a5b
> > > > Author: Thibaut Cuvelier  > >
> > > > Date:   Mon Aug 3 16:04:26 2020 +0200
> > > >
> > > >     DocBook: add a layout tag to tell whether an item is the
> > abstract or not.
> > > > ---
> > > >  .../docbook/bibliography_precooked_aastex.xml      |  221
> > -
> > > >  lib/layouts/aastex.layout                          |    3 -
> > > >  lib/layouts/stdstruct.inc                          |    3 +-
> > > >  lib/scripts/layout2layout.py                       |    2 +-
> > > >  src/Layout.cpp                                     |    8 +
> > > >  src/Layout.h                                       |    9 +-
> > > >  src/output_docbook.cpp                             |  265
> > 
> > > >  src/xml.h                                          |    2 +
> > > >  8 files changed, 283 insertions(+), 230 deletions(-)
> > >
> > > Thibaut, could you please test the exports before commit?
> > >
> > > Some of the last commits are the reason for
> > >
> > > 1.) extrem slowness
> > > 2.) many endless loops
> > > 3.) 54% tests passed, 162 tests failed out of 350
> >
> > +1
> > An alternative would be to do work on a branch, then when you are
> > ready
> > do all the testing at once and then after the testing looks good merge
> > to master.
> >
> > I think that some projects are not as strict, but here on master
> > we like
> > to keep it useable. This makes it easier to test master.  Also, it
> > makes
> > it easier to bisect other bugs that have nothing to do with a commit
> > that broke something else.
> >
> > Thank you very much to Thibaut for all of your work!
> >
> > And thank you to Kornel for spending so much time on the tests.
> >
> >
> > Working on a branch would be the best solution, indeed. May I do a
> > force push to remove those commits from master? 
> 
> Just revert them, I'd think.

+1

For a branch, if Thibaut would like to share the branch before pushing,
perhaps the "features" remote would be the right place? In normal times,
I would be interested in pulling your branch (from features), and
running the tests to see if there are any regressions. However, these
days I do not have the time to offer this.

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Richard Kimberly Heck]

On 8/3/20 10:57 AM, Thibaut Cuvelier wrote:
> On Mon, 3 Aug 2020 at 16:41, Scott Kostyshak  > wrote:
>
> On Mon, Aug 03, 2020 at 04:29:57PM +0200, Kornel Benko wrote:
> > Am Mon,  3 Aug 2020 15:39:49 +0200 (CEST)
> > schrieb Thibaut Cuvelier  >:
> >
> > > commit 5ccd63eff6731a972f1d65d855859a65fe8e3a5b
> > > Author: Thibaut Cuvelier  >
> > > Date:   Mon Aug 3 16:04:26 2020 +0200
> > >
> > >     DocBook: add a layout tag to tell whether an item is the
> abstract or not.
> > > ---
> > >  .../docbook/bibliography_precooked_aastex.xml      |  221
> -
> > >  lib/layouts/aastex.layout                          |    3 -
> > >  lib/layouts/stdstruct.inc                          |    3 +-
> > >  lib/scripts/layout2layout.py                       |    2 +-
> > >  src/Layout.cpp                                     |    8 +
> > >  src/Layout.h                                       |    9 +-
> > >  src/output_docbook.cpp                             |  265
> 
> > >  src/xml.h                                          |    2 +
> > >  8 files changed, 283 insertions(+), 230 deletions(-)
> >
> > Thibaut, could you please test the exports before commit?
> >
> > Some of the last commits are the reason for
> >
> > 1.) extrem slowness
> > 2.) many endless loops
> > 3.) 54% tests passed, 162 tests failed out of 350
>
> +1
> An alternative would be to do work on a branch, then when you are
> ready
> do all the testing at once and then after the testing looks good merge
> to master.
>
> I think that some projects are not as strict, but here on master
> we like
> to keep it useable. This makes it easier to test master.  Also, it
> makes
> it easier to bisect other bugs that have nothing to do with a commit
> that broke something else.
>
> Thank you very much to Thibaut for all of your work!
>
> And thank you to Kornel for spending so much time on the tests.
>
>
> Working on a branch would be the best solution, indeed. May I do a
> force push to remove those commits from master? 

Just revert them, I'd think.

Riki


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

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Thibaut Cuvelier]

On Mon, 3 Aug 2020 at 16:41, Scott Kostyshak  wrote:

> On Mon, Aug 03, 2020 at 04:29:57PM +0200, Kornel Benko wrote:
> > Am Mon,  3 Aug 2020 15:39:49 +0200 (CEST)
> > schrieb Thibaut Cuvelier :
> >
> > > commit 5ccd63eff6731a972f1d65d855859a65fe8e3a5b
> > > Author: Thibaut Cuvelier 
> > > Date:   Mon Aug 3 16:04:26 2020 +0200
> > >
> > > DocBook: add a layout tag to tell whether an item is the abstract
> or not.
> > > ---
> > >  .../docbook/bibliography_precooked_aastex.xml  |  221
> -
> > >  lib/layouts/aastex.layout  |3 -
> > >  lib/layouts/stdstruct.inc  |3 +-
> > >  lib/scripts/layout2layout.py   |2 +-
> > >  src/Layout.cpp |8 +
> > >  src/Layout.h   |9 +-
> > >  src/output_docbook.cpp |  265
> 
> > >  src/xml.h  |2 +
> > >  8 files changed, 283 insertions(+), 230 deletions(-)
> >
> > Thibaut, could you please test the exports before commit?
> >
> > Some of the last commits are the reason for
> >
> > 1.) extrem slowness
> > 2.) many endless loops
> > 3.) 54% tests passed, 162 tests failed out of 350
>
> +1
> An alternative would be to do work on a branch, then when you are ready
> do all the testing at once and then after the testing looks good merge
> to master.
>
> I think that some projects are not as strict, but here on master we like
> to keep it useable. This makes it easier to test master.  Also, it makes
> it easier to bisect other bugs that have nothing to do with a commit
> that broke something else.
>
> Thank you very much to Thibaut for all of your work!
>
> And thank you to Kornel for spending so much time on the tests.
>

Working on a branch would be the best solution, indeed. May I do a force
push to remove those commits from master?
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Scott Kostyshak]

On Mon, Aug 03, 2020 at 04:29:57PM +0200, Kornel Benko wrote:
> Am Mon,  3 Aug 2020 15:39:49 +0200 (CEST)
> schrieb Thibaut Cuvelier :
> 
> > commit 5ccd63eff6731a972f1d65d855859a65fe8e3a5b
> > Author: Thibaut Cuvelier 
> > Date:   Mon Aug 3 16:04:26 2020 +0200
> > 
> > DocBook: add a layout tag to tell whether an item is the abstract or 
> > not.
> > ---
> >  .../docbook/bibliography_precooked_aastex.xml  |  221 -
> >  lib/layouts/aastex.layout  |3 -
> >  lib/layouts/stdstruct.inc  |3 +-
> >  lib/scripts/layout2layout.py   |2 +-
> >  src/Layout.cpp |8 +
> >  src/Layout.h   |9 +-
> >  src/output_docbook.cpp |  265 
> > 
> >  src/xml.h  |2 +
> >  8 files changed, 283 insertions(+), 230 deletions(-)
> 
> Thibaut, could you please test the exports before commit?
> 
> Some of the last commits are the reason for
> 
> 1.) extrem slowness
> 2.) many endless loops
> 3.) 54% tests passed, 162 tests failed out of 350

+1
An alternative would be to do work on a branch, then when you are ready
do all the testing at once and then after the testing looks good merge
to master.

I think that some projects are not as strict, but here on master we like
to keep it useable. This makes it easier to test master.  Also, it makes
it easier to bisect other bugs that have nothing to do with a commit
that broke something else.

Thank you very much to Thibaut for all of your work!

And thank you to Kornel for spending so much time on the tests.

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a layout tag to tell whether an item is the abstract or not.

[Kornel Benko]

Am Mon,  3 Aug 2020 15:39:49 +0200 (CEST)
schrieb Thibaut Cuvelier :

> commit 5ccd63eff6731a972f1d65d855859a65fe8e3a5b
> Author: Thibaut Cuvelier 
> Date:   Mon Aug 3 16:04:26 2020 +0200
> 
> DocBook: add a layout tag to tell whether an item is the abstract or not.
> ---
>  .../docbook/bibliography_precooked_aastex.xml  |  221 -
>  lib/layouts/aastex.layout  |3 -
>  lib/layouts/stdstruct.inc  |3 +-
>  lib/scripts/layout2layout.py   |2 +-
>  src/Layout.cpp |8 +
>  src/Layout.h   |9 +-
>  src/output_docbook.cpp |  265 
> 
>  src/xml.h  |2 +
>  8 files changed, 283 insertions(+), 230 deletions(-)

Thibaut, could you please test the exports before commit?

Some of the last commits are the reason for

1.) extrem slowness
2.) many endless loops
3.) 54% tests passed, 162 tests failed out of 350

Kornel


pgpVv2wQw0VyE.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: fix XML in comments (-- forbidden for some historical reason).

[Richard Kimberly Heck]

On 7/31/20 10:07 PM, Thibaut Cuvelier wrote:
> On Sat, 1 Aug 2020 at 03:51, Thibaut Cuvelier  > wrote:
>
> On Sat, 1 Aug 2020 at 01:01, Kornel Benko  > wrote:
>
> Am Sat, 1 Aug 2020 00:42:20 +0200
> schrieb Thibaut Cuvelier  >:
>
> > On Sat, 1 Aug 2020 at 00:28, Kornel Benko  > wrote:
> >
> > > Am Fri, 31 Jul 2020 23:37:33 +0200 (CEST)
> > > schrieb Thibaut Cuvelier  >:
> > >
> > > > commit 85946aae2b94fedf5ce9bd35e91ba500986b5121
> > > > Author: Thibaut Cuvelier  >
> > > > Date:   Sat Aug 1 00:02:36 2020 +0200
> > > >
> > > >     DocBook: fix XML in comments (-- forbidden for some
> historical
> > > reason).
> > > > ---
> > > >  autotests/export/docbook/deutsches_ert.lyx |   14 +-
> > > >  autotests/export/docbook/deutsches_ert.xml |    2 +-
> > > >  src/insets/InsetERT.cpp                    |   14 --
> > > >  src/xml.cpp                                |   80
> > > ++-
> > > >  src/xml.h                                  |    5 +-
> > > >  5 files changed, 68 insertions(+), 47 deletions(-)
> > >
> > > Cannot compile ...
> > > I get now
> > > /usr2/src/lyx/lyx-git/src/xml.cpp:78:79: error: explicit
> qualification in
> > > declaration of
> > > ‘lyx::docstring lyx::xml::escapeString(const docstring&,
> > > lyx::XMLStream::EscapeSettings)’
> > > docstring xml::escapeString(docstring const & raw,
> > > XMLStream::EscapeSettings e) ^
> > > src/CMakeFiles/lyx2.4.dir/build.make:1441: recipe for target
> > >
> 'src/CMakeFiles/lyx2.4.dir/usr2/src/lyx/lyx-git/src/xml.cpp.o'
> failed
> > >
> >
> > Is the new version better?
>
> Looks good :)
> Now the remaining problematic case is
>         3718 -
>        
> 
> export/examples/Articles/American_Astronomical_Society_%28AASTeX_v._6.2%29_docbook5
>         (Failed)
> ('\'' in param)
> ...
> Newell, E. B.,
> and O'Neil, E. J. 1978,
> , 37, 27   xml:id='Ortolani et al.
> (1985)'>Ortolani, S., Rosino, L., and Sandage, A. 1985, , 90, 473
> 
> ...
>
> (Mark, this is from the examples directory (not templates dir
> with the same filename))
>
>
> That one is fixed too, thanks! 
>
>
> Still on that American_Astronomical_Society test case, I try to
> improve things a bit. The main choke point for now is appendices: why
> is there a layout Appendix, which does not work like the usual "start
> of appendix". Maybe the constructor ofParagraphParameters should just
> check whether the LaTeX command is \appendix?

Just to chime in: Great work, both of you. I hope to be able to adapt
some of this to the XHTML output once it stabilizes. (Mostly the font
stuff.)(

Riki



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

Re: [LyX/master] DocBook: fix XML in comments (-- forbidden for some historical reason).

[Thibaut Cuvelier]

On Sat, 1 Aug 2020 at 03:51, Thibaut Cuvelier  wrote:

> On Sat, 1 Aug 2020 at 01:01, Kornel Benko  wrote:
>
>> Am Sat, 1 Aug 2020 00:42:20 +0200
>> schrieb Thibaut Cuvelier :
>>
>> > On Sat, 1 Aug 2020 at 00:28, Kornel Benko  wrote:
>> >
>> > > Am Fri, 31 Jul 2020 23:37:33 +0200 (CEST)
>> > > schrieb Thibaut Cuvelier :
>> > >
>> > > > commit 85946aae2b94fedf5ce9bd35e91ba500986b5121
>> > > > Author: Thibaut Cuvelier 
>> > > > Date:   Sat Aug 1 00:02:36 2020 +0200
>> > > >
>> > > > DocBook: fix XML in comments (-- forbidden for some historical
>> > > reason).
>> > > > ---
>> > > >  autotests/export/docbook/deutsches_ert.lyx |   14 +-
>> > > >  autotests/export/docbook/deutsches_ert.xml |2 +-
>> > > >  src/insets/InsetERT.cpp|   14 --
>> > > >  src/xml.cpp|   80
>> > > ++-
>> > > >  src/xml.h  |5 +-
>> > > >  5 files changed, 68 insertions(+), 47 deletions(-)
>> > >
>> > > Cannot compile ...
>> > > I get now
>> > > /usr2/src/lyx/lyx-git/src/xml.cpp:78:79: error: explicit
>> qualification in
>> > > declaration of
>> > > ‘lyx::docstring lyx::xml::escapeString(const docstring&,
>> > > lyx::XMLStream::EscapeSettings)’
>> > > docstring xml::escapeString(docstring const & raw,
>> > > XMLStream::EscapeSettings e) ^
>> > > src/CMakeFiles/lyx2.4.dir/build.make:1441: recipe for target
>> > > 'src/CMakeFiles/lyx2.4.dir/usr2/src/lyx/lyx-git/src/xml.cpp.o' failed
>> > >
>> >
>> > Is the new version better?
>>
>> Looks good :)
>> Now the remaining problematic case is
>> 3718 -
>>
>> export/examples/Articles/American_Astronomical_Society_%28AASTeX_v._6.2%29_docbook5
>> (Failed)
>> ('\'' in param)
>> ...
>> Newell, E. B., and O'Neil,
>> E. J. 1978,
>> , 37, 27  Ortolani, S., Rosino, L., and Sandage, A. 1985, , 90,
>> 473
>> 
>> ...
>>
>> (Mark, this is from the examples directory (not templates dir with the
>> same filename))
>>
>
> That one is fixed too, thanks!
>

Still on that American_Astronomical_Society test case, I try to improve
things a bit. The main choke point for now is appendices: why is there a
layout Appendix, which does not work like the usual "start of appendix".
Maybe the constructor of ParagraphParameters should just check whether the
LaTeX command is \appendix?
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: fix XML in comments (-- forbidden for some historical reason).

[Thibaut Cuvelier]

On Sat, 1 Aug 2020 at 01:01, Kornel Benko  wrote:

> Am Sat, 1 Aug 2020 00:42:20 +0200
> schrieb Thibaut Cuvelier :
>
> > On Sat, 1 Aug 2020 at 00:28, Kornel Benko  wrote:
> >
> > > Am Fri, 31 Jul 2020 23:37:33 +0200 (CEST)
> > > schrieb Thibaut Cuvelier :
> > >
> > > > commit 85946aae2b94fedf5ce9bd35e91ba500986b5121
> > > > Author: Thibaut Cuvelier 
> > > > Date:   Sat Aug 1 00:02:36 2020 +0200
> > > >
> > > > DocBook: fix XML in comments (-- forbidden for some historical
> > > reason).
> > > > ---
> > > >  autotests/export/docbook/deutsches_ert.lyx |   14 +-
> > > >  autotests/export/docbook/deutsches_ert.xml |2 +-
> > > >  src/insets/InsetERT.cpp|   14 --
> > > >  src/xml.cpp|   80
> > > ++-
> > > >  src/xml.h  |5 +-
> > > >  5 files changed, 68 insertions(+), 47 deletions(-)
> > >
> > > Cannot compile ...
> > > I get now
> > > /usr2/src/lyx/lyx-git/src/xml.cpp:78:79: error: explicit qualification
> in
> > > declaration of
> > > ‘lyx::docstring lyx::xml::escapeString(const docstring&,
> > > lyx::XMLStream::EscapeSettings)’
> > > docstring xml::escapeString(docstring const & raw,
> > > XMLStream::EscapeSettings e) ^
> > > src/CMakeFiles/lyx2.4.dir/build.make:1441: recipe for target
> > > 'src/CMakeFiles/lyx2.4.dir/usr2/src/lyx/lyx-git/src/xml.cpp.o' failed
> > >
> >
> > Is the new version better?
>
> Looks good :)
> Now the remaining problematic case is
> 3718 -
>
> export/examples/Articles/American_Astronomical_Society_%28AASTeX_v._6.2%29_docbook5
> (Failed)
> ('\'' in param)
> ...
> Newell, E. B., and O'Neil,
> E. J. 1978,
> , 37, 27  Ortolani, S., Rosino, L., and Sandage, A. 1985, , 90,
> 473
> 
> ...
>
> (Mark, this is from the examples directory (not templates dir with the
> same filename))
>

That one is fixed too, thanks!
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: fix XML in comments (-- forbidden for some historical reason).

[Kornel Benko]

Am Sat, 1 Aug 2020 00:42:20 +0200
schrieb Thibaut Cuvelier :

> On Sat, 1 Aug 2020 at 00:28, Kornel Benko  wrote:
> 
> > Am Fri, 31 Jul 2020 23:37:33 +0200 (CEST)
> > schrieb Thibaut Cuvelier :
> >
> > > commit 85946aae2b94fedf5ce9bd35e91ba500986b5121
> > > Author: Thibaut Cuvelier 
> > > Date:   Sat Aug 1 00:02:36 2020 +0200
> > >
> > > DocBook: fix XML in comments (-- forbidden for some historical
> > reason).
> > > ---
> > >  autotests/export/docbook/deutsches_ert.lyx |   14 +-
> > >  autotests/export/docbook/deutsches_ert.xml |2 +-
> > >  src/insets/InsetERT.cpp|   14 --
> > >  src/xml.cpp|   80
> > ++-
> > >  src/xml.h  |5 +-
> > >  5 files changed, 68 insertions(+), 47 deletions(-)
> >
> > Cannot compile ...
> > I get now
> > /usr2/src/lyx/lyx-git/src/xml.cpp:78:79: error: explicit qualification in
> > declaration of
> > ‘lyx::docstring lyx::xml::escapeString(const docstring&,
> > lyx::XMLStream::EscapeSettings)’
> > docstring xml::escapeString(docstring const & raw,
> > XMLStream::EscapeSettings e) ^
> > src/CMakeFiles/lyx2.4.dir/build.make:1441: recipe for target
> > 'src/CMakeFiles/lyx2.4.dir/usr2/src/lyx/lyx-git/src/xml.cpp.o' failed
> >
> 
> Is the new version better?

Looks good :)
Now the remaining problematic case is
3718 -

export/examples/Articles/American_Astronomical_Society_%28AASTeX_v._6.2%29_docbook5
(Failed)
('\'' in param)
...
Newell, E. B., and O'Neil, E. J. 
1978,
, 37, 27  Ortolani, S., Rosino, L., and Sandage, A. 1985, , 90, 473

...

(Mark, this is from the examples directory (not templates dir with the same 
filename))

Kornel




pgpliMT0FCL1g.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: fix XML in comments (-- forbidden for some historical reason).

[Thibaut Cuvelier]

On Sat, 1 Aug 2020 at 00:28, Kornel Benko  wrote:

> Am Fri, 31 Jul 2020 23:37:33 +0200 (CEST)
> schrieb Thibaut Cuvelier :
>
> > commit 85946aae2b94fedf5ce9bd35e91ba500986b5121
> > Author: Thibaut Cuvelier 
> > Date:   Sat Aug 1 00:02:36 2020 +0200
> >
> > DocBook: fix XML in comments (-- forbidden for some historical
> reason).
> > ---
> >  autotests/export/docbook/deutsches_ert.lyx |   14 +-
> >  autotests/export/docbook/deutsches_ert.xml |2 +-
> >  src/insets/InsetERT.cpp|   14 --
> >  src/xml.cpp|   80
> ++-
> >  src/xml.h  |5 +-
> >  5 files changed, 68 insertions(+), 47 deletions(-)
>
> Cannot compile ...
> I get now
> /usr2/src/lyx/lyx-git/src/xml.cpp:78:79: error: explicit qualification in
> declaration of
> ‘lyx::docstring lyx::xml::escapeString(const docstring&,
> lyx::XMLStream::EscapeSettings)’
> docstring xml::escapeString(docstring const & raw,
> XMLStream::EscapeSettings e) ^
> src/CMakeFiles/lyx2.4.dir/build.make:1441: recipe for target
> 'src/CMakeFiles/lyx2.4.dir/usr2/src/lyx/lyx-git/src/xml.cpp.o' failed
>

Is the new version better?
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: fix XML in comments (-- forbidden for some historical reason).

[Kornel Benko]

Am Fri, 31 Jul 2020 23:37:33 +0200 (CEST)
schrieb Thibaut Cuvelier :

> commit 85946aae2b94fedf5ce9bd35e91ba500986b5121
> Author: Thibaut Cuvelier 
> Date:   Sat Aug 1 00:02:36 2020 +0200
> 
> DocBook: fix XML in comments (-- forbidden for some historical reason).
> ---
>  autotests/export/docbook/deutsches_ert.lyx |   14 +-
>  autotests/export/docbook/deutsches_ert.xml |2 +-
>  src/insets/InsetERT.cpp|   14 --
>  src/xml.cpp|   80 ++-
>  src/xml.h  |5 +-
>  5 files changed, 68 insertions(+), 47 deletions(-)

Cannot compile ...
I get now
/usr2/src/lyx/lyx-git/src/xml.cpp:78:79: error: explicit qualification in 
declaration of
‘lyx::docstring lyx::xml::escapeString(const docstring&, 
lyx::XMLStream::EscapeSettings)’
docstring xml::escapeString(docstring const & raw, XMLStream::EscapeSettings e) 
^
src/CMakeFiles/lyx2.4.dir/build.make:1441: recipe for target
'src/CMakeFiles/lyx2.4.dir/usr2/src/lyx/lyx-git/src/xml.cpp.o' failed

Kornel


pgpKQEuAD64SK.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: allow KOMA-Script documents to be generated as DocBook

[Pavel Sanda]

On Tue, Jul 28, 2020 at 05:20:44AM +0200, Thibaut Cuvelier wrote:
> Using the docbook-xsl package to do so is not exactly straightforward, it
> seems, but it's doable. The main problem is that XSLT 1 does not allow to
> generate multiple files nor ZIP archives, so you have to find workarounds???
> https://github.com/docbook/xslt10-stylesheets/blob/master/xsl/epub3/README
> gives the three steps to generating an ePub 3 (plus an extra step for
> checking its validity). It's a thin customisation layer on top of the rest
> of the XSLT package, meaning that it should work well out of the box.
> The dependencies to use this are: either xsltproc or both Java and Saxon 6
> (both toolchains are available for macOS, Linux, and Windows), plus a ZIP
> utility.
> I really think this is a reasonable way to get ePub 3 documents, but with
> many dependencies that are probably not OK to ship with/require for LyX.

Thanks for the link. On a first sight it seems rather easy, because we could
just add dependency requirement for xslt10-stylesheets (most distributions seem
to have it) and directly ship just some python script which does the three
steps mentioned above (we might need to package xslt10-stylesheets for
windows).

But the devil is usually in the details, so it might take quite some work to
tune the results to be usable.

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

Re: [LyX/master] DocBook: allow KOMA-Script documents to be generated as DocBook

[Thibaut Cuvelier]

On Mon, 27 Jul 2020 at 17:44, Pavel Sanda  wrote:

> On Wed, Jul 22, 2020 at 07:28:35PM +0200, Thibaut Cuvelier wrote:
> > On Tue, 21 Jul 2020 at 09:09, Richard Kimberly Heck 
> > wrote:
> >
> > > On 7/20/20 8:35 PM, Thibaut Cuvelier wrote:
> > > > commit c9f8469c00da790f2a80cf55089a3c1a48b755c3
> > > > Author: Thibaut Cuvelier 
> > > > Date:   Tue Jul 21 02:59:57 2020 +0200
> > > >
> > > > DocBook: allow KOMA-Script documents to be generated as DocBook
> > >
> > > This is really excellent.
> > >
> > > Just out of curiosity: Is there an easy way to go from DocBook to EPub?
> > > We have been trying (well, more hoping) to get a good EPub export to
> > > work for a while.
> > >
> >
> > Yes, there are at least three (open source) ways:
> > - with the Java XSLT engine Saxon (
> > https://www.saxonica.com/welcome/welcome.xml): using the outdated
> version 6
> > (the last one that fully supports XSLT 1.0) and
> > https://github.com/docbook/xslt10-stylesheets, this is probably the
> > preferred way to get ePubs from DocBook
> > - Ubuntu has
> http://manpages.ubuntu.com/manpages/trusty/man1/dbtoepub.1.html
> > - RedHat/Fedora used to develop Publican, a tool that can also produce
> > ePub: https://sourceware.org/publican/en-US/Publican/4.2/ (abandoned
> since
> > RHEL 8)
>
> Maybe I am confused, but when I look on debian repository I see docbook-xsl
> package which likely stems from the "preferred" github repo.
> https://packages.debian.org/stretch/docbook-xsl
>
> However the description page does not list epub as its native output
> format
> and instead lists dbtoepub as suggested dependency (your 4th link) which
> is likely the real conversion mechanism(?).
>
> dbtoepub itself is there termed as an alpha-quality implementation
> https://packages.debian.org/stretch/dbtoepub
> so I wonder whether we actually have some reasonable conversion mechanism
> at hand?
>

Using the docbook-xsl package to do so is not exactly straightforward, it
seems, but it's doable. The main problem is that XSLT 1 does not allow to
generate multiple files nor ZIP archives, so you have to find workarounds…
https://github.com/docbook/xslt10-stylesheets/blob/master/xsl/epub3/README
gives the three steps to generating an ePub 3 (plus an extra step for
checking its validity). It's a thin customisation layer on top of the rest
of the XSLT package, meaning that it should work well out of the box.
The dependencies to use this are: either xsltproc or both Java and Saxon 6
(both toolchains are available for macOS, Linux, and Windows), plus a ZIP
utility.
I really think this is a reasonable way to get ePub 3 documents, but with
many dependencies that are probably not OK to ship with/require for LyX.

On the other hand, dbtoepub seems to be based on
https://github.com/docbook/xslt10-stylesheets/tree/master/xsl/epub, which
adds a ton of dependencies and code. It also seems not to get the same
level of maintenance as the rest of the XSLT code. Oxygen (a reference XML
editor) uses most of this code, but with a supplementary Ant layer (
https://ant.apache.org/); however, this code is not open source.
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: allow KOMA-Script documents to be generated as DocBook

[Pavel Sanda]

On Wed, Jul 22, 2020 at 07:28:35PM +0200, Thibaut Cuvelier wrote:
> On Tue, 21 Jul 2020 at 09:09, Richard Kimberly Heck 
> wrote:
> 
> > On 7/20/20 8:35 PM, Thibaut Cuvelier wrote:
> > > commit c9f8469c00da790f2a80cf55089a3c1a48b755c3
> > > Author: Thibaut Cuvelier 
> > > Date:   Tue Jul 21 02:59:57 2020 +0200
> > >
> > > DocBook: allow KOMA-Script documents to be generated as DocBook
> >
> > This is really excellent.
> >
> > Just out of curiosity: Is there an easy way to go from DocBook to EPub?
> > We have been trying (well, more hoping) to get a good EPub export to
> > work for a while.
> >
> 
> Yes, there are at least three (open source) ways:
> - with the Java XSLT engine Saxon (
> https://www.saxonica.com/welcome/welcome.xml): using the outdated version 6
> (the last one that fully supports XSLT 1.0) and
> https://github.com/docbook/xslt10-stylesheets, this is probably the
> preferred way to get ePubs from DocBook
> - Ubuntu has http://manpages.ubuntu.com/manpages/trusty/man1/dbtoepub.1.html
> - RedHat/Fedora used to develop Publican, a tool that can also produce
> ePub: https://sourceware.org/publican/en-US/Publican/4.2/ (abandoned since
> RHEL 8)

Maybe I am confused, but when I look on debian repository I see docbook-xsl
package which likely stems from the "preferred" github repo.
https://packages.debian.org/stretch/docbook-xsl

However the description page does not list epub as its native output format 
and instead lists dbtoepub as suggested dependency (your 4th link) which
is likely the real conversion mechanism(?).

dbtoepub itself is there termed as an alpha-quality implementation 
https://packages.debian.org/stretch/dbtoepub
so I wonder whether we actually have some reasonable conversion mechanism
at hand?

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

Re: [LyX/master] DocBook: solve issue with formulae within font tags.

[Kornel Benko]

Am Mon, 27 Jul 2020 04:56:48 +0200 (CEST)
schrieb Thibaut Cuvelier :

> commit 8dd2e7e6816a714b2c19eb7466dcb80fa582a0e4
> Author: Thibaut Cuvelier 
> Date:   Sun Jul 26 23:23:02 2020 +0200
> 
> DocBook: solve issue with formulae within font tags.
> 
> This is not valid DocBook either!

After these last commits there are many more assertions.
(Previously 19, now 200)
All of them:
support/lassert.cpp (51): ASSERTION false VIOLATED
IN /usr2/src/lyx/lyx-git/src/Paragraph.cpp:3250

with curr_fam == lyx::ESINT_FAMILY

Kornel


pgp4Gds7bCjFC.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: allow KOMA-Script documents to be generated as DocBook

[Thibaut Cuvelier]

On Tue, 21 Jul 2020 at 09:09, Richard Kimberly Heck 
wrote:

> On 7/20/20 8:35 PM, Thibaut Cuvelier wrote:
> > commit c9f8469c00da790f2a80cf55089a3c1a48b755c3
> > Author: Thibaut Cuvelier 
> > Date:   Tue Jul 21 02:59:57 2020 +0200
> >
> > DocBook: allow KOMA-Script documents to be generated as DocBook
>
> This is really excellent.
>
> Just out of curiosity: Is there an easy way to go from DocBook to EPub?
> We have been trying (well, more hoping) to get a good EPub export to
> work for a while.
>

Yes, there are at least three (open source) ways:
- with the Java XSLT engine Saxon (
https://www.saxonica.com/welcome/welcome.xml): using the outdated version 6
(the last one that fully supports XSLT 1.0) and
https://github.com/docbook/xslt10-stylesheets, this is probably the
preferred way to get ePubs from DocBook
- Ubuntu has http://manpages.ubuntu.com/manpages/trusty/man1/dbtoepub.1.html
- RedHat/Fedora used to develop Publican, a tool that can also produce
ePub: https://sourceware.org/publican/en-US/Publican/4.2/ (abandoned since
RHEL 8)
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: allow KOMA-Script documents to be generated as DocBook

[Richard Kimberly Heck]

On 7/20/20 8:35 PM, Thibaut Cuvelier wrote:
> commit c9f8469c00da790f2a80cf55089a3c1a48b755c3
> Author: Thibaut Cuvelier 
> Date:   Tue Jul 21 02:59:57 2020 +0200
>
> DocBook: allow KOMA-Script documents to be generated as DocBook

This is really excellent.

Just out of curiosity: Is there an easy way to go from DocBook to EPub?
We have been trying (well, more hoping) to get a good EPub export to
work for a while.

Riki


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

Re: [LyX/master] DocBook: avoid skipping paragraphs in .

[Kornel Benko]

Am Mon, 20 Jul 2020 03:18:25 +0200 (CEST)
schrieb Thibaut Cuvelier :

> commit e0a4dfa7d32dca9e78cb92f092800ea819f77e69
> Author: Thibaut Cuvelier 
> Date:   Mon Jul 20 03:41:44 2020 +0200
> 
> DocBook: avoid skipping paragraphs in .
> ---
>  autotests/export/docbook/issue5165.lyx |  102 
> 
>  autotests/export/docbook/issue5165.xml |   12 
>  src/output_docbook.cpp |9 +++
>  3 files changed, 123 insertions(+), 0 deletions(-)
> 

Time to add the docbook exports to the tests I suppose.

Kornel


pgpTTDo2GqY8k.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Lyx to Docbook

[Richard Heck]

Lars Olesen wrote:
 How do I translate a lyx document to docbook
Open DocumentSettingsDocumentClass. In the Document Class drop box,
choose DocBook (article) or whatever. Choose OK. (You may get some
conversion errors depending upon the document.) Now look under
FileExport. You should see DocBook... as an option.
 - and the other way around?
FileImportDocBook

Richard


-- 
==
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==
Get my public key from http://sks.keyserver.penguin.de
Hash: 0x1DE91F1E66FFBDEC
Learn how to sign your email using Thunderbird and GnuPG at:
http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto

Re: Lyx to Docbook

[Richard Heck]

Lars Olesen wrote:
> How do I translate a lyx document to docbook
Open Document>Settings>DocumentClass. In the Document Class drop box,
choose "DocBook (article)" or whatever. Choose OK. (You may get some
conversion errors depending upon the document.) Now look under
File>Export. You should see "DocBook..." as an option.
> - and the other way around?
File>Import>DocBook

Richard


-- 
==
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==
Get my public key from http://sks.keyserver.penguin.de
Hash: 0x1DE91F1E66FFBDEC
Learn how to sign your email using Thunderbird and GnuPG at:
http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto

Re: LyX and DocBook: Permission to include parts of LyX Documentation

[Angus Leeming]

Chris Karakas wrote:
 So either the User Guide is NOT GPL, by force of the missing Disclaimer
 as argued above, or if it is, I will have to change from the GFDL to GPL
 if I include some pieces of it in my software...er, documentation.
 
 Is this what the authors of the User Guide intended? Hard to believe, but
 the facts are different...I'm stymied.

The question of whether you are allowed to include snippets of GPLed stuff 
in a GFDLed document must have come up many times in the past. I see a 
mailing list at http://www.opensource.org/licenses/ where you can probably 
find some more informed opinion than mine:

license-discuss-subscribe at opensource.org

Incidentally, the contents of this web page 
(http://www.opensource.org/licenses/) are licensed under other licenses 
that you might consider.

-- 
Angus

Re: LyX and DocBook: Permission to include parts of LyX Documentation

[Angus Leeming]

Chris Karakas wrote:
> So either the User Guide is NOT GPL, by force of the missing Disclaimer
> as argued above, or if it is, I will have to change from the GFDL to GPL
> if I include some pieces of it in my software...er, documentation.
> 
> Is this what the authors of the User Guide intended? Hard to believe, but
> the facts are different...I'm stymied.

The question of whether you are allowed to include snippets of GPLed stuff 
in a GFDLed document must have come up many times in the past. I see a 
mailing list at http://www.opensource.org/licenses/ where you can probably 
find some more informed opinion than mine:

license-discuss-subscribe at opensource.org

Incidentally, the contents of this web page 
(http://www.opensource.org/licenses/) are licensed under other licenses 
that you might consider.

-- 
Angus

LyX and DocBook: Permission to include parts of LyX Documentation

[Chris Karakas]

Hello,

(maybe I'm asking in the wrong list, please guide me to the right one, if this 
is the case)

I am preparing the next version of my document

Document processing with LyX and SGML

to be seen in

http://www.karakas-online.de/mySGML/

Among many corrections and improvements, I am writing a chapter on 
Localization. I am currently putting the pieces of this puzzle together 
(there are so many tools involved - keyboard, LyX, sed, awk, Perl, Openjade, 
Jadetex, Pdfjadetex, TeX, LaTeX, lynx, DSSSL stylesheets...) and each one plays 
its role in font encoding, character set, keyboard map, input 
encoding...you name it.

I would like to include the sections:

- Setting up the X keyboard
- International support

(including their subsections) from the lyX User Guide in my document. I will 
give Credit to the LyX Documentation Team, or whoever holds the rights on it, 
in whatever form you deem appropriate (I currently plan an SGML info box at 
the start of the Localization chapter and an entry in the Credits section 
(http://www.karakas-online.de/mySGML/credits.html)).

My question is:

Am I allowed to do it? Who decides? What is the licence of the LyX User Guide? 

I am using LyX 1.2.0, so I am referring to the User Guide that came with that 
version. However, I would like to be able to use updated versions of those 
chapters, should my version of LyX change and/or new insights are gained.

My document is under the GNU Free Documentation Licence, so including those 
sections would (preferably) mean that they can be changed freely in the future, 
as the author and future readers add their experiences with those subjects. Is 
this O.K?

In a synthetic work like this, being able to put pieces together from other 
sources, without having to rephrase just to convey the same technical 
information,  is a great help and would be greatly appreciated.

Chris

-- 
Regards

Chris Karakas
http://www.karakas-online.de

Re: LyX and DocBook: Permission to include parts of LyX Documentation

[Angus Leeming]

Chris Karakas wrote:

 Am I allowed to do it? 

Yes, so long as your licence is compatible with the GPL.

 Who decides? What is the licence of the LyX User Guide?

GPL. LyX has one licence only ATM.

-- 
Angus

Re: LyX and DocBook: Permission to include parts of LyX Documentation

[Chris Karakas]

Angus Leeming [EMAIL PROTECTED] schrieb am 02.03.05 16:41:25:
 
 Chris Karakas wrote:
 
  Am I allowed to do it? 
 
 Yes, so long as your licence is compatible with the GPL.

Thanks for answering!

GPL you say? Now if only someone could assure me that the statement

GPL is compatible with GFDL

holds true...sigh. I am afraid, if you take it up to the letter, they are NOT.

For a piece of code (say, a .lyx file containing the documentation) to be under 
the GPL licence, it *must*:

- Contain a Copyright Notice
- Contain a Disclaimer
- Come with source code

etc...

Now the LyX User's Guide does NOT contain the Disclaimer

#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; see the file COPYING.  If not, write to
# the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.
#

so the LyX User Guide is NOT under the GPL!

You think I'm kidding? I am not - I've seen cases where the FSF said this 
software is NOT under the GPL, because it does not contain the Disclaimer. See 

http://phpnuke.org/modules.php?name=Newsfile=articlesid=6966

PHP-Nuke was seen as non-GPL-compliant by FSF, because it did not comply with 
section 2(c) of the GPL (like the LyX User's Guide, it did not contain the 
Disclaimer). The author had to explicitly include the Disclaimer in the footer 
of each page generated by his script.

Furthermore, the GFDL has the notion of the invariant chapters, which cannot 
be altered, while with the GPL you can change almost everything.

So here we are, with a piece of documentation that is not GPLed, but was 
intented to be, and someone who wants to copy it under the GFDL, which is 
compatible with the GPL in the sense of free software, but not compatible with 
it in the legal sense...

What do we do now? Suggestions?

Chris

-- 
Regards

Chris Karakas
http://www.karakas-online.de

Re: LyX and DocBook: Permission to include parts of LyX Documentation

[Angus Leeming]

Chris Karakas wrote:
 GPL you say? Now if only someone could assure me that the statement
 
 GPL is compatible with GFDL
 
 holds true...sigh. I am afraid, if you take it up to the letter, they are
 NOT.
 
 For a piece of code (say, a .lyx file containing the documentation) to be
 under the GPL licence, it *must*:
 
 - Contain a Copyright Notice
 - Contain a Disclaimer
 - Come with source code
 
 etc...
 
 Now the LyX User's Guide does NOT contain the Disclaimer

This can be added. Use a comment environment or a note inset (depending on 
your version of LyX).

 so the LyX User Guide is NOT under the GPL!

 Furthermore, the GFDL has the notion of the invariant chapters, which
 cannot be altered, while with the GPL you can change almost everything.

Clearly the GFDL is compatible with the GPL in the sense that you can 
include snippets of my GPLed code in your document. Thereafter your 
readers cannot alter the document (GFDLed) even though they could alter 
the source code.

The same holds true here. Include your extract from the LyX document, 
tweak it to your heart's content (as allowed by the GPL) and licence it 
under the GFDL allowing no further modification.

No?

Maybe you should ask the FSF if this interpretation of their licences 
holds true.

-- 
Angus

Re: LyX and DocBook: Permission to include parts of LyX Documentation

[Chris Karakas]

Angus Leeming [EMAIL PROTECTED] schrieb am 02.03.05 19:05:33:
 
 Chris Karakas wrote:
  
  Now the LyX User's Guide does NOT contain the Disclaimer
 
 This can be added. Use a comment environment or a note inset (depending on 
 your version of LyX).
 

I know, but the Disclaimer is not there. This means that, strictly speaking, 
the User Guide is not under the GPL, even if the intention was there to set it 
under the GPL. If you add it today, this will remove this obstacle only for the 
User Guide that you will distribute starting from today, not for the version I 
got a few years ago.

So first problem still remains: I need a piece of the User Guide, but its 
licence is unclear (not GPL in the strict legal sense).

  Furthermore, the GFDL has the notion of the invariant chapters, which
  cannot be altered, while with the GPL you can change almost everything.
 
 Clearly the GFDL is compatible with the GPL in the sense that you can 
 include snippets of my GPLed code in your document. Thereafter your 
 readers cannot alter the document (GFDLed) even though they could alter 
 the source code.
 

Yes, but altering the source code can be seen as altering the document, you 
know...

You say they can change the source code, no problem, I might be tempted to 
say they took a part of my document and changed it, although I declared it as 
invariant.  See the contradiction? It depends on how you see the piece, as 
documentation under the GFDL, or as software under the GPL.

The consequence is that such sections cannot be declared invariant under the 
GFDL (not that I intented to do so...).

See below for more complications of this duality principle of 
documentation=code.

 The same holds true here. Include your extract from the LyX document, 
 tweak it to your heart's content (as allowed by the GPL) and licence it 
 under the GFDL allowing no further modification.
 
 No?
 

You consider the sections I want to borrow as being software. From this 
point of view, I will take your software and expand it, putting extra 
software pieces around it (those pieces I call sections and chapters, but 
that's irrelevant to this point of view). I will take that piece of software 
(LyX commands like \begin_inset etc. that ultimately drive a program (LyX) to 
do something (display the User Guide on the screen)), and produce a derivative 
work - add my LyX commands around it, that cause some extra functionality to 
be executed (I call it display some extra chapters above and below, but 
naming of software operations does not change their software nature...so it's 
irrelevant how *I* call it, it remains a software derivative work).  
Derivative works of GPLed software must be set under the GPL. So I am forced to 
abandon my GFDL licence for the GPL - and this for my whole book! :shock:

So either the User Guide is NOT GPL, by force of the missing Disclaimer as 
argued above, or if it is, I will have to change from the GFDL to GPL if I 
include some pieces of it in my software...er, documentation. 

Is this what the authors of the User Guide intended? Hard to believe, but the 
facts are different...I'm stymied.

Chris

-- 
Regards

Chris Karakas
http://www.karakas-online.de

LyX and DocBook: Permission to include parts of LyX Documentation

[Chris Karakas]

Hello,

(maybe I'm asking in the wrong list, please guide me to the right one, if this 
is the case)

I am preparing the next version of my document

Document processing with LyX and SGML

to be seen in

http://www.karakas-online.de/mySGML/

Among many corrections and improvements, I am writing a chapter on 
"Localization". I am currently putting the pieces of this puzzle together 
(there are so many tools involved - keyboard, LyX, sed, awk, Perl, Openjade, 
Jadetex, Pdfjadetex, TeX, LaTeX, lynx, DSSSL stylesheets...) and each one plays 
its role in "font encoding", "character set", "keyboard map", "input 
encoding"...you name it.

I would like to include the sections:

- Setting up the X keyboard
- International support

(including their subsections) from the lyX User Guide in my document. I will 
give Credit to the LyX Documentation Team, or whoever holds the rights on it, 
in whatever form you deem appropriate (I currently plan an SGML "info" box at 
the start of the "Localization" chapter and an entry in the Credits section 
(http://www.karakas-online.de/mySGML/credits.html)).

My question is:

Am I allowed to do it? Who decides? What is the licence of the LyX User Guide? 

I am using LyX 1.2.0, so I am referring to the User Guide that came with that 
version. However, I would like to be able to use updated versions of those 
chapters, should my version of LyX change and/or new insights are gained.

My document is under the GNU Free Documentation Licence, so including those 
sections would (preferably) mean that they can be changed freely in the future, 
as the author and future readers add their experiences with those subjects. Is 
this O.K?

In a synthetic work like this, being able to put pieces together from other 
sources, without having to rephrase just to convey the same technical 
information,  is a great help and would be greatly appreciated.

Chris

-- 
Regards

Chris Karakas
http://www.karakas-online.de

Re: LyX and DocBook: Permission to include parts of LyX Documentation

[Angus Leeming]

Chris Karakas wrote:

> Am I allowed to do it? 

Yes, so long as your licence is compatible with the GPL.

> Who decides? What is the licence of the LyX User Guide?

GPL. LyX has one licence only ATM.

-- 
Angus

Re: LyX and DocBook: Permission to include parts of LyX Documentation

[Chris Karakas]

Angus Leeming <[EMAIL PROTECTED]> schrieb am 02.03.05 16:41:25:
> 
> Chris Karakas wrote:
> 
> > Am I allowed to do it? 
> 
> Yes, so long as your licence is compatible with the GPL.

Thanks for answering!

GPL you say? Now if only someone could assure me that the statement

"GPL is compatible with GFDL"

holds true...sigh. I am afraid, if you take it up to the letter, they are NOT.

For a piece of code (say, a .lyx file containing the documentation) to be under 
the GPL licence, it *must*:

- Contain a Copyright Notice
- Contain a Disclaimer
- Come with source code

etc...

Now the LyX User's Guide does NOT contain the Disclaimer

#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; see the file COPYING.  If not, write to
# the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.
#

so the LyX User Guide is NOT under the GPL!

You think I'm kidding? I am not - I've seen cases where the FSF said "this 
software is NOT under the GPL, because it does not contain the Disclaimer". See 

http://phpnuke.org/modules.php?name=News=article=6966

PHP-Nuke was seen as non-GPL-compliant by FSF, because it did not comply with 
section 2(c) of the GPL (like the LyX User's Guide, it did not contain the 
Disclaimer). The author had to explicitly include the Disclaimer in the footer 
of each page generated by his script.

Furthermore, the GFDL has the notion of the "invariant chapters", which cannot 
be altered, while with the GPL you can change almost everything.

So here we are, with a piece of documentation that is not GPLed, but was 
intented to be, and someone who wants to copy it under the GFDL, which is 
compatible with the GPL in the sense of free software, but not compatible with 
it in the legal sense...

What do we do now? Suggestions?

Chris

-- 
Regards

Chris Karakas
http://www.karakas-online.de

Re: LyX and DocBook: Permission to include parts of LyX Documentation

[Angus Leeming]

Chris Karakas wrote:
> GPL you say? Now if only someone could assure me that the statement
> 
> "GPL is compatible with GFDL"
> 
> holds true...sigh. I am afraid, if you take it up to the letter, they are
> NOT.
> 
> For a piece of code (say, a .lyx file containing the documentation) to be
> under the GPL licence, it *must*:
> 
> - Contain a Copyright Notice
> - Contain a Disclaimer
> - Come with source code
> 
> etc...
> 
> Now the LyX User's Guide does NOT contain the Disclaimer

This can be added. Use a comment environment or a note inset (depending on 
your version of LyX).

> so the LyX User Guide is NOT under the GPL!

> Furthermore, the GFDL has the notion of the "invariant chapters", which
> cannot be altered, while with the GPL you can change almost everything.

Clearly the GFDL is compatible with the GPL in the sense that you can 
include snippets of my GPLed code in your document. Thereafter your 
readers cannot alter the document (GFDLed) even though they could alter 
the source code.

The same holds true here. Include your extract from the LyX document, 
tweak it to your heart's content (as allowed by the GPL) and licence it 
under the GFDL allowing no further modification.

No?

Maybe you should ask the FSF if this interpretation of their licences 
holds true.

-- 
Angus

Re: LyX and DocBook: Permission to include parts of LyX Documentation

[Chris Karakas]

Angus Leeming <[EMAIL PROTECTED]> schrieb am 02.03.05 19:05:33:
> 
> Chris Karakas wrote:
> > 
> > Now the LyX User's Guide does NOT contain the Disclaimer
> 
> This can be added. Use a comment environment or a note inset (depending on 
> your version of LyX).
> 

I know, but the Disclaimer is not there. This means that, strictly speaking, 
the User Guide is not under the GPL, even if the intention was there to set it 
under the GPL. If you add it today, this will remove this obstacle only for the 
User Guide that you will distribute starting from today, not for the version I 
got a few years ago.

So first problem still remains: I need a piece of the User Guide, but its 
licence is unclear (not GPL in the strict legal sense).

> > Furthermore, the GFDL has the notion of the "invariant chapters", which
> > cannot be altered, while with the GPL you can change almost everything.
> 
> Clearly the GFDL is compatible with the GPL in the sense that you can 
> include snippets of my GPLed code in your document. Thereafter your 
> readers cannot alter the document (GFDLed) even though they could alter 
> the source code.
> 

Yes, but altering the source code can be seen as altering the document, you 
know...

You say "they can change the source code, no problem", I might be tempted to 
say "they took a part of my document and changed it, although I declared it as 
invariant".  See the contradiction? It depends on how you see the piece, as 
"documentation under the GFDL", or as "software under the GPL".

The consequence is that such sections cannot be declared invariant under the 
GFDL (not that I intented to do so...).

See below for more complications of this "duality principle" of 
"documentation=code".

> The same holds true here. Include your extract from the LyX document, 
> tweak it to your heart's content (as allowed by the GPL) and licence it 
> under the GFDL allowing no further modification.
> 
> No?
> 

You consider the sections I want to "borrow" as being "software". From this 
point of view, I will take your software and "expand" it, putting extra 
software pieces around it (those pieces I call "sections" and "chapters", but 
that's irrelevant to this point of view). I will take that piece of software 
(LyX commands like \begin_inset etc. that ultimately drive a program (LyX) to 
do something (display the User Guide on the screen)), and produce a "derivative 
work" - add my LyX commands around it, that cause some extra "functionality" to 
be "executed" (I call it "display some extra chapters above and below", but 
naming of software operations does not change their software nature...so it's 
irrelevant how *I* call it, it remains a "software derivative work").  
Derivative works of GPLed software must be set under the GPL. So I am forced to 
abandon my GFDL licence for the GPL - and this for my whole book! :shock:

So either the User Guide is NOT GPL, by force of the missing Disclaimer as 
argued above, or if it is, I will have to change from the GFDL to GPL if I 
include some pieces of it in my software...er, documentation. 

Is this what the authors of the User Guide intended? Hard to believe, but the 
facts are different...I'm stymied.

Chris

-- 
Regards

Chris Karakas
http://www.karakas-online.de

lyx-1.0.4pre8 DocBook support

[Horst G Kausch]

Hi,

I have now built lyx-1.0.4pre8 and tested DocBook support again. I am now
also using the cvs version of sgmltools (pre 2.0.3). 

1) The Code environment now works for me.

2) Nested lists still cause trouble, as Jose said in his email.

3) Double quotes use the wrong iso-entities: They currently use 
   ldquor; and rdquor; This results in German style double quotes. 
   It should be ldquo; and rdquo; for English style double quotes.
   [I may have complained earlier about ldquo; unknown -- that was with
DocBook-3.0. For DocBook-3.1 ldquo; and rdquo; seem to be the right 
choice.]

4) How does one do Literals embedded in text (i.e. without starting a new 
   paragraph)? I tried the Literal environment: it changed the whole
   paragraph to Literal. The SGML produced is then incorrect: literal
   appears by itself; according to the DTD it should be embedded inside a
   para or simpara.

I attach a sample document (sample.lyx, sample.sgml and sample.dvi).

Horst

   



#This file was created by hgk Tue Sep 28 02:44:21 1999
#LyX 1.0 (C) 1995-1999 Matthias Ettrich and the LyX Team
\lyxformat 2.15
\textclass docbook
\language default
\inputencoding default
\fontscheme default
\graphics default
\paperfontsize default
\spacing single 
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default

\layout SGML


\begin_inset Info Here goes the information about the article:
  * title
  * date
  * author
+ first name
+ last name
 * abstract
\end_inset 


\layout Title
\added_space_top vfill \added_space_bottom vfill 
Docbook with LyX
\layout Date

28 September 1999
\layout Author

\begin_deeper 
\layout SGML
\align center 

\size normal 

\begin_inset Info The author name is always composed of:
  * first name
  * surname

It is always possible to have more than one author.
\end_inset 


\layout FirstName

Horst Günter
\layout Surname

Kausch
\end_deeper 
\layout Abstract

This is a sample document illustrating some of the features/bugs of DocBook
 support in LyX.
\layout Section

Problem Areas
\layout Subsection

The CODE environment
\layout Standard

A few lines from a program listing:
\layout Code

#++
\layout Code

Test the Alg package domains
\layout Code

++#
\layout Code

read("projects/alg/FreeMon.mu");
\layout Code

read("projects/alg/FreeAlg.mu");
\layout Code


\protected_separator 

\layout Code

s := [ J0, Jp, Jm ];
\layout Code

# this means J0  Jp  Jp  Jm!
\layout Code

t := FreeAlgebra(Dom::Rational, s);
\layout Code


\protected_separator 

\layout Code

t::info();
\layout Standard

Hope that works -- YES!
\layout Subsection

Nested itemize environments
\layout Itemize

entry 1
\layout Itemize

entry 2
\begin_deeper 
\layout Itemize

entry 2.1
\layout Itemize

entry 2.2
\end_deeper 
\layout Itemize

entry 3
\layout Standard

Does this work? NO!
\layout Subsection

Quotes
\layout Standard

Single `quotes', German style double 
\begin_inset Quotes gld
\end_inset 

quotes
\begin_inset Quotes grd
\end_inset 

 and English style double 
\begin_inset Quotes eld
\end_inset 

quotes
\begin_inset Quotes erd
\end_inset 

.
\layout Subsection

Literals
\layout Standard

Try a literal: 
\layout Literal

This is a literal.
 
\layout Standard

How does one enter `inline' literals?
\the_end


!doctype article public "-//OASIS//DTD DocBook V3.1//EN"

!-- DocBook file was created by LyX 1.0 (C) 1995-1999
by hgk Tue Sep 28 02:44:25 1999
 --
 article

  artheader
   title
  Docbook with LyX
  /title
  date
  28 September 1999
  /date
  author
  

  firstname
  Horst Günter
  /firstname
  surname
  Kausch
  /surname
  /author
  abstract
  para
  This is a sample document illustrating some of the features/bugs of DocBook support 
in LyX.
  /para
  /abstract
  /artheader
  sect1
   title
  Problem Areas
  /title
   sect2
title
   The CODE environment
   /title
   para
   A few lines from a program listing:
   /para
   programlisting
#++
Test the Alg package domains
++#
read("projects/alg/FreeMon.mu");
read("projects/alg/FreeAlg.mu");


s := [ J0, Jp, Jm ];
# this means J0  Jp  Jp  Jm!
t := FreeAlgebra(Dom::Rational, s);


t::info();
   /programlisting
   para
   Hope that works -- YES!
   /para
   /sect2
   sect2
title
   Nested itemize environments
   /title
   itemizedlist
listitem
para
   entry 1
/para
/listitem
listitem
para
   entry 2
/para
/listitem
   listitem
itemizedlist
 listitem
 para
entry 2.1
 /para
 /listitem
 

Re: lyx-1.0.4pre8 DocBook support

[Jose Abilio Oliveira Matos]

On Tue, Sep 28, 1999 at 12:51:49PM +0100, Horst G Kausch wrote:
 Hi,
 
 I have now built lyx-1.0.4pre8 and tested DocBook support again. I am now
 also using the cvs version of sgmltools (pre 2.0.3). 
 
 1) The Code environment now works for me.

  Great.
 
 2) Nested lists still cause trouble, as Jose said in his email.

  If you could try the last cvs version, all this problems have been
fixed.
 
 3) Double quotes use the wrong iso-entities: They currently use 
ldquor; and rdquor; This results in German style double quotes. 
It should be ldquo; and rdquo; for English style double quotes.
[I may have complained earlier about ldquo; unknown -- that was with
 DocBook-3.0. For DocBook-3.1 ldquo; and rdquo; seem to be the right 
 choice.]

  I will look into that. I will search the several quotes and their
iso entities representation.
 
 4) How does one do Literals embedded in text (i.e. without starting a new 
paragraph)? I tried the Literal environment: it changed the whole
paragraph to Literal. The SGML produced is then incorrect: literal
appears by itself; according to the DTD it should be embedded inside a
para or simpara.

  If that happens it is a bug, the literal layout should correspond to
the literallayout tag. This is easy to correct, go to 
lyx/lib/layout/docbook.layout and change the Literal latexname to literallayout.

  BTW, lyx doesn't support the inline literal. This was a strategic decision,
while lyx doesn't support inline styles. I could use the tt font to represent that,
but there are very few cases where literal is the right choice.

 I attach a sample document (sample.lyx, sample.sgml and sample.dvi).

  Thanks for the report, I will fix all the above bugs.
 
 Horst
 

-- 
José

lyx-1.0.4pre8 DocBook support

[Horst G Kausch]

Hi,

I have now built lyx-1.0.4pre8 and tested DocBook support again. I am now
also using the cvs version of sgmltools (pre 2.0.3). 

1) The Code environment now works for me.

2) Nested lists still cause trouble, as Jose said in his email.

3) Double quotes use the wrong iso-entities: They currently use 
and  This results in German style double quotes. 
   It should be  and  for English style double quotes.
   [I may have complained earlier about  unknown -- that was with
DocBook-3.0. For DocBook-3.1  and  seem to be the right 
choice.]

4) How does one do Literals embedded in text (i.e. without starting a new 
   paragraph)? I tried the Literal environment: it changed the whole
   paragraph to Literal. The SGML produced is then incorrect: 
   appears by itself; according to the DTD it should be embedded inside a
or .

I attach a sample document (sample.lyx, sample.sgml and sample.dvi).

Horst

   



#This file was created by  Tue Sep 28 02:44:21 1999
#LyX 1.0 (C) 1995-1999 Matthias Ettrich and the LyX Team
\lyxformat 2.15
\textclass docbook
\language default
\inputencoding default
\fontscheme default
\graphics default
\paperfontsize default
\spacing single 
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default

\layout SGML


\begin_inset Info Here goes the information about the article:
  * title
  * date
  * author
+ first name
+ last name
 * abstract
\end_inset 


\layout Title
\added_space_top vfill \added_space_bottom vfill 
Docbook with LyX
\layout Date

28 September 1999
\layout Author

\begin_deeper 
\layout SGML
\align center 

\size normal 

\begin_inset Info The author name is always composed of:
  * first name
  * surname

It is always possible to have more than one author.
\end_inset 


\layout FirstName

Horst Günter
\layout Surname

Kausch
\end_deeper 
\layout Abstract

This is a sample document illustrating some of the features/bugs of DocBook
 support in LyX.
\layout Section

Problem Areas
\layout Subsection

The CODE environment
\layout Standard

A few lines from a program listing:
\layout Code

#++
\layout Code

Test the Alg package domains
\layout Code

++#
\layout Code

read("projects/alg/FreeMon.mu");
\layout Code

read("projects/alg/FreeAlg.mu");
\layout Code


\protected_separator 

\layout Code

s := [ J0, Jp, Jm ];
\layout Code

# this means J0 < Jp & Jp < Jm!
\layout Code

t := FreeAlgebra(Dom::Rational, s);
\layout Code


\protected_separator 

\layout Code

t::info();
\layout Standard

Hope that works -- YES!
\layout Subsection

Nested itemize environments
\layout Itemize

entry 1
\layout Itemize

entry 2
\begin_deeper 
\layout Itemize

entry 2.1
\layout Itemize

entry 2.2
\end_deeper 
\layout Itemize

entry 3
\layout Standard

Does this work? NO!
\layout Subsection

Quotes
\layout Standard

Single `quotes', German style double 
\begin_inset Quotes gld
\end_inset 

quotes
\begin_inset Quotes grd
\end_inset 

 and English style double 
\begin_inset Quotes eld
\end_inset 

quotes
\begin_inset Quotes erd
\end_inset 

.
\layout Subsection

Literals
\layout Standard

Try a literal: 
\layout Literal

This is a literal.
 
\layout Standard

How does one enter `inline' literals?
\the_end





 

  
   
  Docbook with LyX
  
  
  28 September 1999
  
  
  

  
  Horst Günter
  
  
  Kausch
  
  
  
  
  This is a sample document illustrating some of the features/bugs of DocBook support 
in LyX.
  
  
  
  
   
  Problem Areas
  
   

   The CODE environment
   
   
   A few lines from a program listing:
   
   
#++
Test the Alg package domains
++#
read("projects/alg/FreeMon.mu");
read("projects/alg/FreeAlg.mu");


s := [ J0, Jp, Jm ];
# this means J0 < Jp & Jp < Jm!
t := FreeAlgebra(Dom::Rational, s);


t::info();
   
   
   Hope that works -- YES!
   
   
   

   Nested itemize environments
   
   


   entry 1




   entry 2


   

 
 
entry 2.1
 
 
 
 
entry 2.2
 
 




   entry 3


   
   
   Does this work? NO!
   
   
   

   Quotes
   
   
   Single `quotes', German style double quotes and English style 
double quotes.
   
   
   

   Literals
   
   
   Try a literal: 
   
   
   This is a literal. 
   
   
   How does one enter `inline' literals?
   
   
  


 

 sample.dvi

Re: lyx-1.0.4pre8 DocBook support

[Jose Abilio Oliveira Matos]

On Tue, Sep 28, 1999 at 12:51:49PM +0100, Horst G Kausch wrote:
> Hi,
> 
> I have now built lyx-1.0.4pre8 and tested DocBook support again. I am now
> also using the cvs version of sgmltools (pre 2.0.3). 
> 
> 1) The Code environment now works for me.

  Great.
 
> 2) Nested lists still cause trouble, as Jose said in his email.

  If you could try the last cvs version, all this problems have been
fixed.
 
> 3) Double quotes use the wrong iso-entities: They currently use 
> and  This results in German style double quotes. 
>It should be  and  for English style double quotes.
>[I may have complained earlier about  unknown -- that was with
> DocBook-3.0. For DocBook-3.1  and  seem to be the right 
> choice.]

  I will look into that. I will search the several quotes and their
iso entities representation.
 
> 4) How does one do Literals embedded in text (i.e. without starting a new 
>paragraph)? I tried the Literal environment: it changed the whole
>paragraph to Literal. The SGML produced is then incorrect: 
>appears by itself; according to the DTD it should be embedded inside a
> or .

  If that happens it is a bug, the literal layout should correspond to
the literallayout tag. This is easy to correct, go to 
lyx/lib/layout/docbook.layout and change the Literal latexname to literallayout.

  BTW, lyx doesn't support the inline literal. This was a strategic decision,
while lyx doesn't support inline styles. I could use the tt font to represent that,
but there are very few cases where literal is the right choice.

> I attach a sample document (sample.lyx, sample.sgml and sample.dvi).

  Thanks for the report, I will fix all the above bugs.
 
> Horst
> 

-- 
José