Re: XML stream writer library

2021-01-04 Thread Richard Kimberly Heck
On 1/4/21 5:10 PM, Pavel Sanda wrote:
> On Mon, Jan 04, 2021 at 09:48:42PM +0100, Thibaut Cuvelier wrote:
>> My recommendation, based on a quite long study of XML libraries (i.e.
>> several years, but quite far from full-time): either use QXmlStreamWriter
>> (which is mostly a SAX implementation in C++) or write our own.
>> QXmlStreamWriter is almost 4k-line long, but it can substantially be
>> simplified in our case (
>> https://github.com/qt/qtbase/blob/54875be84de059374920e4c0deacd13a41caaa13/src/corelib/serialization/qxmlstream.cpp).
>>
>>
>> TinyXML2 (https://github.com/leethomason/tinyxml2), pugixml (
>> https://github.com/zeux/pugixml), and Xerces-C++ (
>> https://xerces.apache.org/xerces-c/) are only DOM-based. There are quite a
>> few C libraries, like libxml2, that can be SAX-like, but C libraries are
>> horrible to use (http://www.xmlsoft.org/examples/testWriter.c).

I did some searching and, yes, I see the problem. Word is that recent
versions of libxml and libxml2 have dependencies on Gnome libraries that
we don't want.

I'll let you know if I get any answers to my question on the Fedora list.


> I do not dare to make any qualified recommendation between the choices
> above. But thinking aloud -- if there de facto isn't an alternative
> to QXmlStreamWriter, would it be hard to separate that class from
> the rest of Qt, fork and include it as an internal lyx routine?
> We would have full control over that code without unnecessary surprises
> of Qt's development.

I was going to suggest something in this spirit.

If, as our usual policy has been, we confine QXmlStreamWrapper to
support/, then what that basically means is writing our own LyX API as a
kind of wrapper around the Qt stuff. (Thibaut, if you haven't already,
you might look at how the FileName class. Much of it is a wrapper around
QFile.) Some, even many, of the routines might just directly call the Qt
equivalent (probably after a call to toqstr, from qstring_helpers). This
would be a relatively quick way to get something that worked and was
easy to use, and work on adapting DocBook and HTML export to this code
could proceed.

At that point, we could then write our own XML backend, possibly
adapting it from the Qt code. There are quite a few dependencies there,
but I'll guess some of them we do not need (e.g., the QApplication and
QFile dependencies). Our we build a lightweight library from scratch.
(It does seem like maybe there's a general need for that.) With the
already functioning backend from QXmlStreamWrapper, it would be easy to
test our own code and make sure it was producing the same output.

Riki


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


Re: XML stream writer library

2021-01-04 Thread Pavel Sanda
On Mon, Jan 04, 2021 at 09:48:42PM +0100, Thibaut Cuvelier wrote:
> My recommendation, based on a quite long study of XML libraries (i.e.
> several years, but quite far from full-time): either use QXmlStreamWriter
> (which is mostly a SAX implementation in C++) or write our own.
> QXmlStreamWriter is almost 4k-line long, but it can substantially be
> simplified in our case (
> https://github.com/qt/qtbase/blob/54875be84de059374920e4c0deacd13a41caaa13/src/corelib/serialization/qxmlstream.cpp).
> 
> 
> TinyXML2 (https://github.com/leethomason/tinyxml2), pugixml (
> https://github.com/zeux/pugixml), and Xerces-C++ (
> https://xerces.apache.org/xerces-c/) are only DOM-based. There are quite a
> few C libraries, like libxml2, that can be SAX-like, but C libraries are
> horrible to use (http://www.xmlsoft.org/examples/testWriter.c).

I do not dare to make any qualified recommendation between the choices
above. But thinking aloud -- if there de facto isn't an alternative
to QXmlStreamWriter, would it be hard to separate that class from
the rest of Qt, fork and include it as an internal lyx routine?
We would have full control over that code without unnecessary surprises
of Qt's development.

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


Re: Problem with standard regex

2021-01-04 Thread Yuriy Skalko

Thanks. I am not so sure that 'from_ascii()' is the better choice comparing to
'from_utf8()' though.


Maybe it will be better, but I cannot remember seeing exceptions with 
`what`-messages not in plain English. Feel free to update.



BTW, I tested the regexes with Russian documents, and found an error in 
Additional.lyx

Correction attached.


Really, that was missed out. Please commit it.



Is the regex handling (with enabled format) now to your liking?

Kornel


I've tested the regexes (with and without format). Now there are no 
problems with Cyrillic in any practical regexes I can think of. Thanks 
for advsearch that is really usable now, Kornel!



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


Re: XML stream writer library

2021-01-04 Thread Yuriy Skalko

TinyXML2 (https://github.com/leethomason/tinyxml2), pugixml (
https://github.com/zeux/pugixml), and Xerces-C++ (
https://xerces.apache.org/xerces-c/) are only DOM-based. There are quite a
few C libraries, like libxml2, that can be SAX-like, but C libraries are
horrible to use (http://www.xmlsoft.org/examples/testWriter.c).


There are several C++ wrappers for libxml2 on GitHub. Maybe they can be 
useful:


https://github.com/libxmlplusplus/libxmlplusplus
https://github.com/rioki/libxmlmm


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


Re: XML stream writer library

2021-01-04 Thread Thibaut Cuvelier
On Mon, 4 Jan 2021 at 20:30, Richard Kimberly Heck  wrote:

> On 1/3/21 3:37 PM, Lorenzo Bertini wrote:
>
> Hello list,
>
> In 12055 , discussing the merge of
> some MathMLStream and XmlStream components, we were contemplating the
> possibility of using an external library to handle XML streams, for example
> with indentation and tag insertion. One of the candidates was
> QXmlStreamWriter  class,
> but with the talk about removing unnecessary Qt components we thought to
> ask the list.
>
> Lest us know what do you think it's the best course, and if you know of
> other libraries we should look.
>
> As I mention in the bug, I looked over various XML libraries a while ago,
> when I was thinking about the long-standing idea of converting LyX's own
> format to XML. There seemed to be a myriad of options, and I never settled
> upon one. But it looks like there's a general feeling that we don't want to
> get too married to Qt---any more than we already are. That is in part
> because Qt seems to break itself fairly frequently (especially on OSX) and
> partly because they keep changing their attitude towards open source. There
> was some thing not long ago about how recent updates would only be
> available to paid subscribers right away, or something like that.
>
> So I'd generally suggest searching around for good, well-maintained XML
> libraries, maybe asking on Stack Exchange what people like. I'll send an
> email to the Fedora list and see what suggestions pop up.
>
There are multiple issues here. What is needed to generate HTML and DocBook
is a simple SAX writer, not a parser. I've done plenty of research about
it, there's no XML library that does that. Most of them are using a DOM,
which is a total waste of memory for such an application: it stores a
complete XML tree in memory before serialising it. With SAX, you just need
a string backend, which is much more lightweight (by several factors). In
this case, as the content is generated without ever looking back, SAX is
the best choice.

You have more choices in the Java world, and the standard library is often
enough (well, the standard extensions javax and JAXP). If you need a good
XML tool, chances are it will be written in Java, especially if it's open
source (Saxon for XSLT or XQuery, eXist or MarkLogic for XML database).

On the other hand, if you want to represent a complete LyX document and
work on it, you'd rather go for DOM, as you will always have the whole
structure in memory: you may want to edit things at any point in the
document. (Unless there is never an operation on the file structures, and
only on the set of insets of the document)

My recommendation, based on a quite long study of XML libraries (i.e.
several years, but quite far from full-time): either use QXmlStreamWriter
(which is mostly a SAX implementation in C++) or write our own.
QXmlStreamWriter is almost 4k-line long, but it can substantially be
simplified in our case (
https://github.com/qt/qtbase/blob/54875be84de059374920e4c0deacd13a41caaa13/src/corelib/serialization/qxmlstream.cpp).


TinyXML2 (https://github.com/leethomason/tinyxml2), pugixml (
https://github.com/zeux/pugixml), and Xerces-C++ (
https://xerces.apache.org/xerces-c/) are only DOM-based. There are quite a
few C libraries, like libxml2, that can be SAX-like, but C libraries are
horrible to use (http://www.xmlsoft.org/examples/testWriter.c).
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: [LyX/master] Remove elipses after 'Open'

2021-01-04 Thread Richard Kimberly Heck
On 1/4/21 2:40 PM, Jean-Marc Lasgouttes wrote:
> Le 04/01/2021 à 19:52, Richard Kimberly Heck a écrit :
>> Some guy named Lasgouttes said they preferred it that way:
>> https://www.lyx.org/trac/ticket/12019
>
> Yes, in the case of a button that opens a directory in the OS. Not for
> the File menu!

I really misread that bug report! Reverted then and fixed.

Riki


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


Re: [LyX/master] Remove elipses after 'Open'

2021-01-04 Thread Jean-Marc Lasgouttes

Le 04/01/2021 à 19:52, Richard Kimberly Heck a écrit :

Some guy named Lasgouttes said they preferred it that way:
https://www.lyx.org/trac/ticket/12019


Yes, in the case of a button that opens a directory in the OS. Not for 
the File menu!


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


Re: XML stream writer library

2021-01-04 Thread Richard Kimberly Heck
On 1/3/21 3:37 PM, Lorenzo Bertini wrote:
>
> Hello list,
>
> In 12055 , discussing the merge
> of some MathMLStream and XmlStream components, we were contemplating
> the possibility of using an external library to handle XML streams,
> for example with indentation and tag insertion. One of the candidates
> was QXmlStreamWriter 
> class, but with the talk about removing unnecessary Qt components we
> thought to ask the list.
>
> Lest us know what do you think it's the best course, and if you know
> of other libraries we should look.
>
As I mention in the bug, I looked over various XML libraries a while
ago, when I was thinking about the long-standing idea of converting
LyX's own format to XML. There seemed to be a myriad of options, and I
never settled upon one. But it looks like there's a general feeling that
we don't want to get too married to Qt---any more than we already are.
That is in part because Qt seems to break itself fairly frequently
(especially on OSX) and partly because they keep changing their attitude
towards open source. There was some thing not long ago about how recent
updates would only be available to paid subscribers right away, or
something like that.

So I'd generally suggest searching around for good, well-maintained XML
libraries, maybe asking on Stack Exchange what people like. I'll send an
email to the Fedora list and see what suggestions pop up.

Riki


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


Re: Virtual meetings

2021-01-04 Thread Richard Kimberly Heck
On 1/3/21 3:38 PM, Pavel Sanda wrote:
> On Wed, Dec 30, 2020 at 09:25:28PM +0100, Pavel Sanda wrote:
>> On Wed, Dec 30, 2020 at 05:32:50PM +0100, Jean-Marc Lasgouttes wrote:
>>> Le 30 décembre 2020 11:25:48 GMT+01:00, Pavel Sanda  a écrit 
>>> :
 I would prefer using zoom because it will just work. My experiments with
 alternatives for transatlantic meetings did not go exactly well.

 Pavel
>>> I will not be available before next week.
>> I created the week of 02-11 with roughly two slots 4pm-7pm & 7pm-10pm CET
>> perhaps people interested in dev meeting could indicate their availablity?
>> (Or write back how to change the poll.)
>>
>> https://xoyondo.com/dp/4Qydsa7iZwRHyOn
> I would suggest we meet Mon 11 Jan, 5pm CET (4pm UTC, 11am EST) unless
> there is a better proposal.

That works for me.


> I could send zoom invitiation if you all are ok with that. Otherwise suggest
> your tool and manage the managment side of the meeting.

Also fine by me.

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


Re: Connection issues with www.lyx.org

2021-01-04 Thread Richard Kimberly Heck
On 1/4/21 12:51 PM, Jürgen Spitzmüller wrote:
> Am Montag, dem 04.01.2021 um 17:30 +0100 schrieb Jean-Marc Lasgouttes:
>> PS: only 96 unread comments from Riki left in my lyx-bugs folder! I 
>> should be OK for next Monday :)
> Yes, we were all provided with a basket full of candy :-)
>
> Happy New Year @all, BTW.

And to you.

My plan is to go through all the bugs back to when 2.3.0 was released,
which was about #11000. Older ones I've looked at only if they had
milestones attached.

One thing I might try to do along the way is propose some hopefully
sensible way of using the Priority field, especially, so we can keep
better track of what really needs doing and what is on trac just because
it was reported. The more I look at the bug reports, the less useful, in
some ways, I'm finding trac to be.

Riki


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


Re: [LyX/master] Remove elipses after 'Open'

2021-01-04 Thread Richard Kimberly Heck
On 1/3/21 2:19 PM, Jean-Marc Lasgouttes wrote:
> Le 03/01/2021 à 20:13, Richard Kimberly Heck a écrit :
>> commit 8871229f5f0cab072e587282d5e6a32a14da481f
>> Author: Richard Kimberly Heck 
>> Date:   Sun Jan 3 14:13:29 2021 -0500
>>
>>  Remove elipses after 'Open'
>
> Why is that?

Some guy named Lasgouttes said they preferred it that way:
https://www.lyx.org/trac/ticket/12019

Riki



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


Re: Question about trac search

2021-01-04 Thread Richard Kimberly Heck
On 1/4/21 4:47 AM, Yu Jin wrote:
> Am Mo., 4. Jan. 2021 um 10:39 Uhr schrieb Yu Jin  >:
>
> I am trying to search for bugs in Trac. I have chosen only "new"
> status in the filters, but the result also shows fixedinstable,
> reopened and even closed bugs in some cases. See attached.
> What am I doing wrong?
>
> Ah found, it was
> (status AND  cc) OR (Assignee)
> need
> (status AND cc) OR (Assignee AND status)
> kinda repeated unnecessarily, but I guess it can't be helped.
> Or is there a way to
> (cc OR assignee) and (status)
> ?

Trac search is very primitive, I'm afraid.

Riki


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


Re: [LyX/master] Arabic Beamer template

2021-01-04 Thread Richard Kimberly Heck
On 1/4/21 4:19 AM, Pavel Sanda wrote:
> On Mon, Jan 04, 2021 at 01:23:34AM +0100, Richard Kimberly Heck wrote:
>> commit 469d3270aee7b7b812f1e212af02f6746c15f7a8
>> Author: Richard Kimberly Heck 
>> Date:   Sun Jan 3 19:23:39 2021 -0500
>>
>> Arabic Beamer template
>> ---
>>  lib/templates/ar/Presentations/Beamer.lyx | 1316 
>> +
>>  1 files changed, 1316 insertions(+), 0 deletions(-)
> Makefile.am entry missing?

Can you check I did that right? I'm pretty clueless about Makefiles.

Riki


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


Re: LyX 2.4.0-alpha1

2021-01-04 Thread José Abílio Matos
On Monday, January 4, 2021 5:02:24 PM WET Jean-Marc Lasgouttes wrote:
> It should be fixed now at 69eb262721b445, a wildcard was missing.
> 
> Please test when you have the occasion.
> 
> JMarc

Actually I went the other way, I brought the big brother to the fight. :-)

I am now using gcc9 to compile the code in epel7. :-)
-- 
José Abílio-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Connection issues with www.lyx.org

2021-01-04 Thread Jürgen Spitzmüller
Am Montag, dem 04.01.2021 um 17:30 +0100 schrieb Jean-Marc Lasgouttes:
> PS: only 96 unread comments from Riki left in my lyx-bugs folder! I 
> should be OK for next Monday :)

Yes, we were all provided with a basket full of candy :-)

Happy New Year @all, BTW.

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 2.3.6.1 Tarballs and Binaries

2021-01-04 Thread Pavel Sanda
On Mon, Jan 04, 2021 at 06:13:13PM +0100, Yu Jin wrote:
> > BTW, Eugene, I would either drop "For more information about LyX for
> > Windows, see our wiki page."
> > from our download page or update the wiki, whatever seem more appropriate
> > to you.
> >
> 
> Ok, drop it then... I have no access to it.

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


Re: LyX 2.3.6.1 Tarballs and Binaries

2021-01-04 Thread Yu Jin
Am Mo., 4. Jan. 2021 um 13:34 Uhr schrieb Pavel Sanda :

> On Wed, Dec 30, 2020 at 08:43:59PM +0100, Yu Jin wrote:
> > Am Di., 29. Dez. 2020 um 17:59 Uhr schrieb Richard Kimberly Heck <
> > rikih...@lyx.org>:
> >
> > > The fix for bug #12056, which prevented inclusion of TeX files,
> warrants
> > > a quick re-release. I've also included the fix for #11746, which caused
> > > problems on Gnome Wayland on Fedora.
> > >
> > > Tarballs here:
> > >
> > > http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/
> > >
> > > Please prepare binaries.
> > >
> >
> > Uploaded to my GDrive as usual.
>
> BTW, Eugene, I would either drop "For more information about LyX for
> Windows, see our wiki page."
> from our download page or update the wiki, whatever seem more appropriate
> to you.
>

Ok, drop it then... I have no access to it.
-- 
Eugene
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: LyX 2.4.0-alpha1

2021-01-04 Thread Jean-Marc Lasgouttes

Le 04/01/2021 à 16:44, José Abílio Matos a écrit :

[root@centos7 ~]# g++ -dumpfullversion

g++: fatal error: no input files

compilation terminated.

[root@centos7 ~]# rpm -qf /usr/bin/g++

gcc-c++-4.8.5-44.el7.x86_64


It should be fixed now at 69eb262721b445, a wildcard was missing.

Please test when you have the occasion.

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


Re: Compilation error with MSVC 19

2021-01-04 Thread Jean-Marc Lasgouttes

Le 04/01/2021 à 17:30, Thibaut Cuvelier a écrit :
On Mon, 4 Jan 2021 at 15:05, Jean-Marc Lasgouttes > wrote:


I really wonder why this is not the default yet.


The only sensible answer is "backward compatibility"… They still 
advertise pre-C++98 by default!


Spooky.

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


Re: Compilation error with MSVC 19

2021-01-04 Thread Thibaut Cuvelier
On Mon, 4 Jan 2021 at 15:05, Jean-Marc Lasgouttes 
wrote:

> Le 30/12/2020 à 09:01, Yuriy Skalko a écrit :
> > I think the right way will be using only standard-compliant
> > "__cplusplus" in sources and adding the option "/Zc:__cplusplus" for
> > MSVC compiler in the build scripts so it handle __cplusplus in
> > standard-compliant way:
> >
> >
> https://docs.microsoft.com/en-us/cpp/build/reference/zc-cplusplus?view=msvc-160
>
> I really wonder why this is not the default yet.
>

The only sensible answer is "backward compatibility"… They still advertise
pre-C++98 by default!
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Connection issues with www.lyx.org

2021-01-04 Thread Jean-Marc Lasgouttes

Le 04/01/2021 à 17:22, Kornel Benko a écrit :

Am Mon, 4 Jan 2021 17:21:12 +0100
schrieb Kornel Benko :


Am Mon, 4 Jan 2021 17:14:43 +0100
schrieb Jean-Marc Lasgouttes :


Am I the only one seeing these? It is in particular when submitting
comments to trac.

JMarc


Maybe a clash with others. Something is posted there 40 seconds ago
"#11350Fixed cursor drawn in workare when resizing"

Kornel


But that was you :(
Kornel



Indeed! The changes are correctly recorded, but I get an error instead 
of the updated bug.


JMarc

PS: only 96 unread comments from Riki left in my lyx-bugs folder! I 
should be OK for next Monday :)


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


Re: Drop QT4 from master

2021-01-04 Thread Jean-Marc Lasgouttes

Le 04/01/2021 à 17:25, Thibaut Cuvelier a écrit :
On Mon, 4 Jan 2021 at 14:56, Jean-Marc Lasgouttes > wrote:


Le 29/12/2020 à 09:42, Yuriy Skalko a écrit :
 > Seems like boost::regex has the same issues as std::regex:
 >

https://www.boost.org/doc/libs/1_75_0/libs/regex/doc/html/boost_regex/unicode.html



 >
 > As I understand the ICU library is the only ultimate solution for
 > Unicode support.

Qt relies on ICU, it would be nice to be able to use the bundled
library
directly.


Not all builds of Qt rely on ICU, unfortunately. For macOS and Windows, 
mostly, Qt uses the native libraries, which allow them to get rid of 
several megabytes of ICU. That means that binaries for macOS and Windows 
would have to use custom Qt builds, I'm not sure the maintainers will 
have the time to do it (it also raises the entry bar for new maintainers).


I stand corrected, then. I would be happy to replace our current iconv 
with something more modern, but I do not trust Qt stuff, which is too 
UTF16-centered and has issues.


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


Re: Drop QT4 from master

2021-01-04 Thread Thibaut Cuvelier
On Mon, 4 Jan 2021 at 14:56, Jean-Marc Lasgouttes 
wrote:

> Le 29/12/2020 à 09:42, Yuriy Skalko a écrit :
> > Seems like boost::regex has the same issues as std::regex:
> >
> https://www.boost.org/doc/libs/1_75_0/libs/regex/doc/html/boost_regex/unicode.html
> >
> > As I understand the ICU library is the only ultimate solution for
> > Unicode support.
>
> Qt relies on ICU, it would be nice to be able to use the bundled library
> directly.
>

Not all builds of Qt rely on ICU, unfortunately. For macOS and Windows,
mostly, Qt uses the native libraries, which allow them to get rid of
several megabytes of ICU. That means that binaries for macOS and Windows
would have to use custom Qt builds, I'm not sure the maintainers will have
the time to do it (it also raises the entry bar for new maintainers).
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Connection issues with www.lyx.org

2021-01-04 Thread Kornel Benko
Am Mon, 4 Jan 2021 17:21:12 +0100
schrieb Kornel Benko :

> Am Mon, 4 Jan 2021 17:14:43 +0100
> schrieb Jean-Marc Lasgouttes :
> 
> > Am I the only one seeing these? It is in particular when submitting 
> > comments to trac.
> > 
> > JMarc  
> 
> Maybe a clash with others. Something is posted there 40 seconds ago 
> "#11350   Fixed cursor drawn in workare when resizing"
> 
>   Kornel

But that was you :(
Kornel


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


Re: Connection issues with www.lyx.org

2021-01-04 Thread Kornel Benko
Am Mon, 4 Jan 2021 17:14:43 +0100
schrieb Jean-Marc Lasgouttes :

> Am I the only one seeing these? It is in particular when submitting 
> comments to trac.
> 
> JMarc

Maybe a clash with others. Something is posted there 40 seconds ago 
"#11350 Fixed cursor drawn in workare when resizing"

Kornel


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


Connection issues with www.lyx.org

2021-01-04 Thread Jean-Marc Lasgouttes
Am I the only one seeing these? It is in particular when submitting 
comments to trac.


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


Re: Problem with standard regex

2021-01-04 Thread Kornel Benko
Am Mon, 4 Jan 2021 15:47:59 +0200
schrieb Yuriy Skalko :

> > Thanks, you are right. But since the exception may not be only from regex, 
> > 'ex.what()'
> > alone feels better.
> > 
> > Please commit.
> > 
> > Kornel  
> 
> Committed at e8099942c7.
> 
> 
> Yuriy

Thanks. I am not so sure that 'from_ascii()' is the better choice comparing to
'from_utf8()' though.

BTW, I tested the regexes with Russian documents, and found an error in 
Additional.lyx
Correction attached.

Is the regex handling (with enabled format) now to your liking?

Kornel
diff --git a/lib/doc/ru/Additional.lyx b/lib/doc/ru/Additional.lyx
index 25ab01e0fc..2a226873ce 100644
--- a/lib/doc/ru/Additional.lyx
+++ b/lib/doc/ru/Additional.lyx
@@ -19066,11 +19066,11 @@ status open
 \end_layout
 
 \begin_layout Standard
 \begin_inset CommandInset include
 LatexCommand input
-filename "C:/Program Files (x86)/LyX 2.3/Resources/doc/SpecialParagraphShape.tex"
+filename "../SpecialParagraphShape.tex"
 literal "true"
 
 \end_inset
 
 


pgpYERfLUwoeI.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 2.4.0-alpha1

2021-01-04 Thread Jean-Marc Lasgouttes

Le 04/01/2021 à 16:44, José Abílio Matos a écrit :

On Monday, January 4, 2021 2:02:30 PM WET Jean-Marc Lasgouttes wrote:

 > Strangely enough, the test is present. Assuming your configure script is
 > updated, could you send the output of
 >    g++ -dumpversion
 > and
 >    g++ -dumpfullversion
 > ?

[root@centos7 ~]# g++ -dumpversion

4.8.5

[root@centos7 ~]# g++ -dumpfullversion

g++: fatal error: no input files

compilation terminated.

[root@centos7 ~]# rpm -qf /usr/bin/g++

gcc-c++-4.8.5-44.el7.x86_64


Thanks, I will fix the issue.

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


Re: LyX 2.4.0-alpha1

2021-01-04 Thread José Abílio Matos
On Monday, January 4, 2021 2:02:30 PM WET Jean-Marc Lasgouttes wrote:
> Strangely enough, the test is present. Assuming your configure script is
> updated, could you send the output of
>g++ -dumpversion
> and
>g++ -dumpfullversion
> ?
> 
> JMarc

[root@centos7 ~]# g++ -dumpversion
4.8.5
[root@centos7 ~]# g++ -dumpfullversion
g++: fatal error: no input files
compilation terminated.
[root@centos7 ~]# rpm -qf /usr/bin/g++
gcc-c++-4.8.5-44.el7.x86_64

-- 
José Abílio-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: LyX 2.4.0-alpha1

2021-01-04 Thread José Abílio Matos
On Monday, January 4, 2021 2:02:30 PM WET Jean-Marc Lasgouttes wrote:
> 
> Strangely enough, the test is present. Assuming your configure script is
> updated,

I will answer this in two parts. :-)
I would assume that the configure script is updated as I am compiling from the 
tar balls created by Riki for alpha 1.

> could you send the output of
>g++ -dumpversion
> and
>g++ -dumpfullversion
> ?
> 
> JMarc

I asked in the Fedora EPEL's list for this output as I do not have CentOS or 
RHEL installed (either version 7 or any other). As soon as I have a feedback I 
will answer this part.

Thank you. :-)
-- 
José Abílio-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: [LyX/master] Remove elipses after 'Open'

2021-01-04 Thread José Abílio Matos
On Sunday, January 3, 2021 7:19:11 PM WET Jean-Marc Lasgouttes wrote:
> > Remove elipses after 'Open'
> 
> Why is that?
> 
> JMarc

I agree with Jean-Marc.

Open always launches a pop up and so it always has ellipses in every program I 
tried. :-)

-- 
José Abílio-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Compilation error with MSVC 19

2021-01-04 Thread Jean-Marc Lasgouttes

Le 30/12/2020 à 09:01, Yuriy Skalko a écrit :
I think the right way will be using only standard-compliant 
"__cplusplus" in sources and adding the option "/Zc:__cplusplus" for 
MSVC compiler in the build scripts so it handle __cplusplus in 
standard-compliant way:


https://docs.microsoft.com/en-us/cpp/build/reference/zc-cplusplus?view=msvc-160 


I really wonder why this is not the default yet.

JMarc

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


Re: LyX 2.4.0-alpha1

2021-01-04 Thread Jean-Marc Lasgouttes

Le 02/01/2021 à 07:37, Yu Jin a écrit :
Since there were no other proposals I just compiled in C++17 mode. I 
didn't increase the Version Build number (still Installer-1), because I 
thought that makes the most sense for testing releases, also for the 
registry. Uploaded as usual.


Wise decision. There is no point to compile in C++20 now since we do not 
support any of it yet.


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


Re: LyX 2.4.0-alpha1

2021-01-04 Thread Jean-Marc Lasgouttes

Le 30/12/2020 à 10:18, José Abílio Matos a écrit :

On Wednesday, December 30, 2020 8:47:51 AM WET Richard Kimberly Heck wrote:

 > I am fairly clueless about such things. Fortunately, there are other 
people


 > who know more. JMarc? Enrico? Yuriy? Anyone?

 >

 > Riki


To be clear, we decided that the minimum requirement for compiling LyX 
is gcc 4.9 and that is clearly stated in the README:



" What do I need to compile LyX from the source distribution?


     * A C++11 compiler. Development is being done mainly with gcc/g++,

   but clang and MSVC are known to work too. As of LyX 2.4.0, you

   need at least gcc 4.9."


My point was about the configure part where there is no warning.


Strangely enough, the test is present. Assuming your configure script is 
updated, could you send the output of

  g++ -dumpversion
and
  g++ -dumpfullversion
?

JMarc

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


Re: Drop QT4 from master

2021-01-04 Thread Jean-Marc Lasgouttes

Le 29/12/2020 à 09:42, Yuriy Skalko a écrit :

Seems like boost::regex has the same issues as std::regex:
https://www.boost.org/doc/libs/1_75_0/libs/regex/doc/html/boost_regex/unicode.html 

As I understand the ICU library is the only ultimate solution for 
Unicode support.


Qt relies on ICU, it would be nice to be able to use the bundled library 
directly.


JMarc

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


Re: Problem with standard regex

2021-01-04 Thread Yuriy Skalko
Thanks, you are right. But since the exception may not be only from regex, 
'ex.what()'

alone feels better.

Please commit.

Kornel


Committed at e8099942c7.


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


Re: LyX 2.3.6.1 Tarballs and Binaries

2021-01-04 Thread Pavel Sanda
On Wed, Dec 30, 2020 at 08:43:59PM +0100, Yu Jin wrote:
> Am Di., 29. Dez. 2020 um 17:59 Uhr schrieb Richard Kimberly Heck <
> rikih...@lyx.org>:
> 
> > The fix for bug #12056, which prevented inclusion of TeX files, warrants
> > a quick re-release. I've also included the fix for #11746, which caused
> > problems on Gnome Wayland on Fedora.
> >
> > Tarballs here:
> >
> > http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/
> >
> > Please prepare binaries.
> >
> 
> Uploaded to my GDrive as usual.

BTW, Eugene, I would either drop "For more information about LyX for Windows, 
see our wiki page."
from our download page or update the wiki, whatever seem more appropriate to 
you.

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


Re: Problem with standard regex

2021-01-04 Thread Kornel Benko
Am Mon, 4 Jan 2021 12:23:47 +0200
schrieb Yuriy Skalko :

> >> Further investigating shows the error in my own code (out of range access).
> >> The following exception was catched in the try {} section in findAdv(), so 
> >> the only
> >> message was: "Invalid regular expression!". This was misleading.
> > 
> > 
> > Indeed that's not very helpful. Ideally it would say *why* it is not valid.
> 
> Maybe append additional exception message to that generic "Invalid..." 
> message as in attached patch?
> 
> 
> Yuriy

Thanks, you are right. But since the exception may not be only from regex, 
'ex.what()'
alone feels better.

Please commit.

Kornel


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


Re: Problem with standard regex

2021-01-04 Thread Yuriy Skalko

Further investigating shows the error in my own code (out of range access).
The following exception was catched in the try {} section in findAdv(), so 
the only

message was: "Invalid regular expression!". This was misleading.



Indeed that's not very helpful. Ideally it would say *why* it is not valid.


Maybe append additional exception message to that generic "Invalid..." 
message as in attached patch?



Yuriy
diff --git a/src/lyxfind.cpp b/src/lyxfind.cpp
index c728af1cef..9bd77e739f 100644
--- a/src/lyxfind.cpp
+++ b/src/lyxfind.cpp
@@ -4115,9 +4115,9 @@ bool findAdv(BufferView * bv, FindAndReplaceOptions const 
& opt)
match_len = findForwardAdv(cur, matchAdv);
else
match_len = findBackwardsAdv(cur, matchAdv);
-   } catch (...) {
+   } catch (exception & ex) {
// This may only be raised by lyx::regex()
-   bv->message(_("Invalid regular expression!"));
+   bv->message(_("Invalid regular expression!") + ' ' + ex.what());
return false;
}
 
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Question about trac search

2021-01-04 Thread Yu Jin
Am Mo., 4. Jan. 2021 um 10:39 Uhr schrieb Yu Jin :

> I am trying to search for bugs in Trac. I have chosen only "new" status in
> the filters, but the result also shows fixedinstable, reopened and even
> closed bugs in some cases. See attached.
> What am I doing wrong?
>
Ah found, it was
(status AND  cc) OR (Assignee)
need
(status AND cc) OR (Assignee AND status)
kinda repeated unnecessarily, but I guess it can't be helped.
Or is there a way to
(cc OR assignee) and (status)
?
-- 
Eugene
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Question about trac search

2021-01-04 Thread Yu Jin
I am trying to search for bugs in Trac. I have chosen only "new" status in
the filters, but the result also shows fixedinstable, reopened and even
closed bugs in some cases. See attached.
What am I doing wrong?
-- 
Eugene
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: [LyX/master] Arabic Beamer template

2021-01-04 Thread Pavel Sanda
On Mon, Jan 04, 2021 at 01:23:34AM +0100, Richard Kimberly Heck wrote:
> commit 469d3270aee7b7b812f1e212af02f6746c15f7a8
> Author: Richard Kimberly Heck 
> Date:   Sun Jan 3 19:23:39 2021 -0500
> 
> Arabic Beamer template
> ---
>  lib/templates/ar/Presentations/Beamer.lyx | 1316 
> +
>  1 files changed, 1316 insertions(+), 0 deletions(-)

Makefile.am entry missing?
P
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: Virtual meetings

2021-01-04 Thread Pavel Sanda
* Plan 2.4 release
* Donate page and alternative donation pathways
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel