Re: What is missing for LyX 2.4?
On 2023-06-24 12:18, Daniel wrote: On 2023-05-29 08:01, Daniel wrote: On 2023-05-04 12:39, Stephan Witt wrote: Am 04.05.2023 um 11:35 schrieb Jean-Marc Lasgouttes : Le 04/05/2023 à 03:39, Richard Kimberly Heck a écrit : The big issue is the OSX shortcut bug, which I'm still not clear about. I don't think anything else is a must-have. This one can be solved for now by building with Qt5, right? Yes, that’s my plan. Is there anything good enough on Qt6 for macOS that makes this a bad option? I don’t think so. The only bad thing is to not switch major Qt release with „major“ LyX release. Qt 5 has some strange graphical glitches on macOS. For example, suddenly appearing colored lines between tabs. It's not great but I guess there is not much of an alternative. Daniel Also, the button click issues may be related to the Qt version: Ticket #12279, #12418, #12820. It is not clear what the cause is, but it might be good flagging the possibility. Daniel Furthermore, there bug where when one double-clicks on word and instead of selecting the whole word, only the part up to the cursor gets selected. That is quite annoying. And it is a general Qt thing, because it also happens in normal text fields. Wasn't that bug fixed in Qt 6? Daniel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On 2023-05-29 08:01, Daniel wrote: On 2023-05-04 12:39, Stephan Witt wrote: Am 04.05.2023 um 11:35 schrieb Jean-Marc Lasgouttes : Le 04/05/2023 à 03:39, Richard Kimberly Heck a écrit : The big issue is the OSX shortcut bug, which I'm still not clear about. I don't think anything else is a must-have. This one can be solved for now by building with Qt5, right? Yes, that’s my plan. Is there anything good enough on Qt6 for macOS that makes this a bad option? I don’t think so. The only bad thing is to not switch major Qt release with „major“ LyX release. Qt 5 has some strange graphical glitches on macOS. For example, suddenly appearing colored lines between tabs. It's not great but I guess there is not much of an alternative. Daniel Also, the button click issues may be related to the Qt version: Ticket #12279, #12418, #12820. It is not clear what the cause is, but it might be good flagging the possibility. Daniel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Tue, May 02, 2023 at 04:12:02PM +0200, Pavel Sanda wrote: > And yeah, I still didn't have time to look on the -dALLOWPSTRANSPARENCY for > ghostscript > needed since TL-2021. This one should be covered now. P -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On 2023-05-04 12:39, Stephan Witt wrote: Am 04.05.2023 um 11:35 schrieb Jean-Marc Lasgouttes : Le 04/05/2023 à 03:39, Richard Kimberly Heck a écrit : The big issue is the OSX shortcut bug, which I'm still not clear about. I don't think anything else is a must-have. This one can be solved for now by building with Qt5, right? Yes, that’s my plan. Is there anything good enough on Qt6 for macOS that makes this a bad option? I don’t think so. The only bad thing is to not switch major Qt release with „major“ LyX release. Qt 5 has some strange graphical glitches on macOS. For example, suddenly appearing colored lines between tabs. It's not great but I guess there is not much of an alternative. Daniel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Wed, May 10, 2023 at 12:05:05PM +0200, Cor Blom wrote: > I assume that information will be in the release notes Yes. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
Op 10-05-2023 om 11:36 schreef Pavel Sanda: On Wed, May 10, 2023 at 11:13:52AM +0200, Cor Blom wrote: On Wed, May 10, 2023 at 09:26:19AM +0200, Cor Blom wrote: openSUSE does contain GM, but it applies a patch to disable some coders. I Thanks for the info Cor. I guess it's in your hands to add new dependencies for converters that will serve as a workarounds for eps conversion - our only way left AFAICS. Pavel The workaround is to install ImageMagick-config-7-upstream and to remove Imagemagick-config-7-SUSE. If you move to GM, does this mean that IM will stop working? No. But I don't think we are moving to GM because it apparatnetly won't solve the problem once for all. What I meant by workaround was to add e.g. pdftoppm (on debian part of poppler-utils) to runtime dependencies of lyx package. In 2.4 we detect if IM is under ban - in that case we try to add pdftoppm to converters so insetad of IM's eps->png we use eps->pdf->png with help of pdftoppm (see bd0510b08). We need to look on PNG -> EPS path yet. No fiddling with packages on the side of user is necessary then. Pavel I understand. Thanks. I assume that information will be in the release notes, I will find it when I'll do the update to 2.4 and make sure to include the right dependencies. Cor -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Wed, May 10, 2023 at 11:30:58AM +0200, Dr Eberhard Lisse wrote: > On the Mac GraphicsMagic is not available as default, but easily > installed with Homebrew (and I am sure MacPorts and similar ilk). But do we suffer on Mac with IM policy ban? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Wed, May 10, 2023 at 11:13:52AM +0200, Cor Blom wrote: > >On Wed, May 10, 2023 at 09:26:19AM +0200, Cor Blom wrote: > >>openSUSE does contain GM, but it applies a patch to disable some coders. I > > > >Thanks for the info Cor. > > > >I guess it's in your hands to add new dependencies for converters that > >will serve as a workarounds for eps conversion - our only way left AFAICS. > > > >Pavel > > The workaround is to install ImageMagick-config-7-upstream and to remove > Imagemagick-config-7-SUSE. > > If you move to GM, does this mean that IM will stop working? No. But I don't think we are moving to GM because it apparatnetly won't solve the problem once for all. What I meant by workaround was to add e.g. pdftoppm (on debian part of poppler-utils) to runtime dependencies of lyx package. In 2.4 we detect if IM is under ban - in that case we try to add pdftoppm to converters so insetad of IM's eps->png we use eps->pdf->png with help of pdftoppm (see bd0510b08). We need to look on PNG -> EPS path yet. No fiddling with packages on the side of user is necessary then. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On the Mac GraphicsMagic is not available as default, but easily installed with Homebrew (and I am sure MacPorts and similar ilk). I have been using that for years. Something like ln -fs $(brew --prefix)/opt/graphicsmagick/bin/gm /usr/local/bin/convert results in a 'convert' which does the work (as does 'gm convert'), is version independent and work on both Intel and Silicon. el On 09/05/2023 21:38, Pavel Sanda wrote: > On Mon, May 08, 2023 at 05:49:46PM +0200, Pavel Sanda wrote: [...] > On debian only 'gm' binary is avaiable and you need to call 'gm > convert' so we would need to change our configure script to deal wit > this. > > We need to check that opensuse (and fedora?) contain GM, and test it > for some time to see possible side effects. > > But otherwise it seems as a reasonable solution. We could just put > into release notes that we urge all distro maintainers who were can't > do anything with IM bans to give GM as a primary dependency. [...] -- To email me replace 'nospam' with 'el' -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
Op 10-05-2023 om 10:46 schreef Pavel Sanda: On Wed, May 10, 2023 at 09:26:19AM +0200, Cor Blom wrote: openSUSE does contain GM, but it applies a patch to disable some coders. I Thanks for the info Cor. I guess it's in your hands to add new dependencies for converters that will serve as a workarounds for eps conversion - our only way left AFAICS. Pavel The workaround is to install ImageMagick-config-7-upstream and to remove Imagemagick-config-7-SUSE. If you move to GM, does this mean that IM will stop working? Cor -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Wed, May 10, 2023 at 09:26:19AM +0200, Cor Blom wrote: > openSUSE does contain GM, but it applies a patch to disable some coders. I Thanks for the info Cor. I guess it's in your hands to add new dependencies for converters that will serve as a workarounds for eps conversion - our only way left AFAICS. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
Op 09-05-2023 om 21:38 schreef Pavel Sanda: We need to check that opensuse (and fedora?) contain GM, and test it for some time to see possible side effects. openSUSE does contain GM, but it applies a patch to disable some coders. I don't see an easy way for users to get around that as there is with IM, where you can install the upstream config that has all the goods. Cor -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Mon, May 08, 2023 at 05:49:46PM +0200, Pavel Sanda wrote: > On Fri, May 05, 2023 at 12:17:46PM -0400, Richard Kimberly Heck wrote: > > On 5/4/23 12:33, Pavel Sanda wrote: > > >On Thu, May 04, 2023 at 05:00:27PM +0100, José Matos wrote: > > >>>Also as I mentioned in other subthread, would you mind posting the > > >>>current > > >>>version of /etc/ImageMagick-6/policy.xml in fedora (please make sure > > >>>you > > >>>did not tweak the file on your own :)? > > >>The file is /etc/ImageMagick-7/policy.xml and follows attached. > > >Thanks, Fedora clearly choses to walk on the wild side. > > > > This sounds like the biggest issue left. Is GraphicsMagick an option, or > > does it have the same issues? > > Worth checking indeed. But even if it works the only thing left for us to do > is to suggest packagers changing dependencies. I quickly checked and indeed gm convert seem to give the same as IM's convert without being affected by bans in policy.xml. On debian only 'gm' binary is avaiable and you need to call 'gm convert' so we would need to change our configure script to deal wit this. We need to check that opensuse (and fedora?) contain GM, and test it for some time to see possible side effects. But otherwise it seems as a reasonable solution. We could just put into release notes that we urge all distro maintainers who were can't do anything with IM bans to give GM as a primary dependency. What others think? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Fri, May 05, 2023 at 12:17:46PM -0400, Richard Kimberly Heck wrote: > On 5/4/23 12:33, Pavel Sanda wrote: > >On Thu, May 04, 2023 at 05:00:27PM +0100, José Matos wrote: > >>>Also as I mentioned in other subthread, would you mind posting the > >>>current > >>>version of /etc/ImageMagick-6/policy.xml in fedora (please make sure > >>>you > >>>did not tweak the file on your own :)? > >>The file is /etc/ImageMagick-7/policy.xml and follows attached. > >Thanks, Fedora clearly choses to walk on the wild side. > > This sounds like the biggest issue left. Is GraphicsMagick an option, or > does it have the same issues? Worth checking indeed. But even if it works the only thing left for us to do is to suggest packagers changing dependencies. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On 5/4/23 12:33, Pavel Sanda wrote: On Thu, May 04, 2023 at 05:00:27PM +0100, José Matos wrote: Also as I mentioned in other subthread, would you mind posting the current version of /etc/ImageMagick-6/policy.xml in fedora (please make sure you did not tweak the file on your own :)? The file is /etc/ImageMagick-7/policy.xml and follows attached. Thanks, Fedora clearly choses to walk on the wild side. This sounds like the biggest issue left. Is GraphicsMagick an option, or does it have the same issues? Riki [1] http://www.graphicsmagick.org/ -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On 5/4/23 06:39, Stephan Witt wrote: Am 04.05.2023 um 11:35 schrieb Jean-Marc Lasgouttes : Le 04/05/2023 à 03:39, Richard Kimberly Heck a écrit : The big issue is the OSX shortcut bug, which I'm still not clear about. I don't think anything else is a must-have. This one can be solved for now by building with Qt5, right? Yes, that’s my plan. OK, so not a blocker. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Thu, May 04, 2023 at 05:00:27PM +0100, José Matos wrote: > > Also as I mentioned in other subthread, would you mind posting the > > current > > version of /etc/ImageMagick-6/policy.xml in fedora (please make sure > > you > > did not tweak the file on your own :)? > > The file is /etc/ImageMagick-7/policy.xml and follows attached. Thanks, Fedora clearly choses to walk on the wild side. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Thu, May 04, 2023 at 05:06:12PM +0100, José Matos wrote: > On Tue, 2023-05-02 at 16:31 +0200, Pavel Sanda wrote: > > Please edit the page, no one will know better than you. P > > That can be done, the issue is if there is any place where this is > missing. > > The issue here is that since our code tries to be resilient sometimes > that is a bad thing. :-) > > That is some of our code fails and we try an alternative and the > original failure, even if by accident, never gets fixed. > > I hope that you understand what I mean because I agree that the above > text is very hermetic. :-D I do :) Anyway I believe that my original point - that you are the one who can best assess the python situation - still remains valid. If Riki intends(?) to use that wiki page it has to be cleared out at certain moment. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Tue, 2023-05-02 at 16:31 +0200, Pavel Sanda wrote: > Please edit the page, no one will know better than you. P That can be done, the issue is if there is any place where this is missing. The issue here is that since our code tries to be resilient sometimes that is a bad thing. :-) That is some of our code fails and we try an alternative and the original failure, even if by accident, never gets fixed. I hope that you understand what I mean because I agree that the above text is very hermetic. :-D -- José Abílio -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Thu, 2023-05-04 at 11:21 +0200, Pavel Sanda wrote: > On Wed, May 03, 2023 at 09:39:26PM -0400, Richard Kimberly Heck > wrote: > > I'm planning to manage the release. Now that classes are over here, > > I will > > have some time. The big questions are about what still needs doing. > > Great to hear that. So back to the original question - Jose, if you > have a > spare hand, helping with sorting out bugs in trac is probably best > way how > to speed up the process... Got it. > Also as I mentioned in other subthread, would you mind posting the > current > version of /etc/ImageMagick-6/policy.xml in fedora (please make sure > you > did not tweak the file on your own :)? > > Pavel The file is /etc/ImageMagick-7/policy.xml and follows attached. -- José Abílio policy.xml Description: XML document -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
Le 02/05/2023 à 16:12, Pavel Sanda a écrit : One thing I'd like to do before release is to merge Text.cpp Text2.cpp and Text3.cpp into a single file. It is so annoying to try to guess in which file something is defined. Would somebody be against this ? I was wondering myself if we should merge those one day and I support this move. I did that now. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
> Am 04.05.2023 um 11:35 schrieb Jean-Marc Lasgouttes : > > Le 04/05/2023 à 03:39, Richard Kimberly Heck a écrit : >> The big issue is the OSX shortcut bug, which I'm still not clear about. I >> don't think anything else is a must-have. > > This one can be solved for now by building with Qt5, right? Yes, that’s my plan. > Is there anything good enough on Qt6 for macOS that makes this a bad option? I don’t think so. The only bad thing is to not switch major Qt release with „major“ LyX release. Stephan > It might be that the problem will solve itself with time. > > JMarc > > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
Le 04/05/2023 à 03:39, Richard Kimberly Heck a écrit : The big issue is the OSX shortcut bug, which I'm still not clear about. I don't think anything else is a must-have. This one can be solved for now by building with Qt5, right? Is there anything good enough on Qt6 for macOS that makes this a bad option? It might be that the problem will solve itself with time. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Wed, May 03, 2023 at 09:39:26PM -0400, Richard Kimberly Heck wrote: > I'm planning to manage the release. Now that classes are over here, I will > have some time. The big questions are about what still needs doing. Great to hear that. So back to the original question - Jose, if you have a spare hand, helping with sorting out bugs in trac is probably best way how to speed up the process... Also as I mentioned in other subthread, would you mind posting the current version of /etc/ImageMagick-6/policy.xml in fedora (please make sure you did not tweak the file on your own :)? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On 5/3/23 14:43, Scott Kostyshak wrote: It is better to do such thing at the end of development window, so that in the future backports are easier. Would it be crazy to just merge also in 2.3.x? I'm guessing the answer is "yes" but still thought I would ask. It won't matter. There is one more 2.3.x release, and that's the one at the 2.4 release. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On 5/2/23 09:11, Jean-Marc Lasgouttes wrote: One thing I'd like to do before release is to merge Text.cpp Text2.cpp and Text3.cpp into a single file. It is so annoying to try to guess in which file something is defined. Would somebody be against this ? No, that's a great idea. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
Sorry to top-post, but to get to the point: I'm planning to manage the release. Now that classes are over here, I will have some time. The big questions are about what still needs doing. On 5/2/23 06:09, Pavel Sanda wrote: Technically, what we need is to finish 1) sort out remaining bugs with 2.4 target in trac 2) review/ sort out TODOs in wiki https://wiki.lyx.org/Devel/LyX24Road 2) annouce string freeze to and ask translators to do their job The big issue is the OSX shortcut bug, which I'm still not clear about. I don't think anything else is a must-have. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Tue, May 02, 2023 at 03:11:09PM +0200, Jean-Marc Lasgouttes wrote: > One thing I'd like to do before release is to merge Text.cpp Text2.cpp and > Text3.cpp into a single file. It is so annoying to try to guess in which > file something is defined. Would somebody be against this ? Not me. If there is logical organization, at least remaing to Text-[keyword].cpp would be helpful. > It is better to do such thing at the end of development window, so that in > the future backports are easier. Would it be crazy to just merge also in 2.3.x? I'm guessing the answer is "yes" but still thought I would ask. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Tue, May 02, 2023 at 12:09:05PM +0200, Pavel Sanda wrote: > On Sat, Apr 29, 2023 at 08:37:47AM +0100, José Matos wrote: > > Do to this I think that the best is to proceed with 2.4 release. > > Ha! Now I know that 3 years of delay is making even Jose nervous :)) I thought he was going to use the amount of time past as an argument to proceed to a 3.0 release :) > > What are the major roadblocks for 2.4? What needs to be done? > > I remember that at some point Scott volunteered to drive the release > > process. > > From management point of view, largely depends on Americans now. This sounds scary. > Riki was afraid to get stuck due to new duties at his workplace > and as you correctly noted Scott offered that he might have some > capacity from Feb. > So the first thing is likely to get their feedback what they > can/want/plan to do / or assume the command into your hands... I'm open to managing the release, or not managing it. And by "managing it", I really mean "asking other people to do the work" :) Whatever Riki prefers is fine with me. > Technically, what we need is to finish > 1) sort out remaining bugs with 2.4 target in trac > 2) review/ sort out TODOs in wiki https://wiki.lyx.org/Devel/LyX24Road > 2) annouce string freeze to and ask translators to do their job > > > I am available to give one or both hands to the release proceed. > > Triaging remaining bugs is easiest way how to move forward before > we reach some conclusion how to move forward from managerial > point of view and needs to be done anyway... Also going through tickets with 'patch' keyword. I think there are some patches that should go in and just need some feedback. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Tue, May 02, 2023 at 03:21:16PM +0100, José Matos wrote:
> > Technically, what we need is to finish
> > 1) sort out remaining bugs with 2.4 target in trac
> > 2) review/ sort out TODOs in wiki
> > https://wiki.lyx.org/Devel/LyX24Road
>
> FWIW the point there regarding python, as far as I can see, is already
> fixed in 2.4 with the ${python} keyword supported in preferences.
Please edit the page, no one will know better than you. P
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Tue, 2023-05-02 at 12:09 +0200, Pavel Sanda wrote:
> On Sat, Apr 29, 2023 at 08:37:47AM +0100, José Matos wrote:
> > Do to this I think that the best is to proceed with 2.4 release.
>
> Ha! Now I know that 3 years of delay is making even Jose nervous :))
That and the fact that some of our initial assumptions are no longer
valid.
As an example most users are now using python 3 and we can see that in
the error reports.
All those issues have been fixed in 2.4 but they are not fixed in 2.3
to avoid making large changes and at some point it becomes too much
work to decide what has been fixed and what needs to be done.
> > What are the major roadblocks for 2.4? What needs to be done?
> > I remember that at some point Scott volunteered to drive the
> > release
> > process.
>
> From management point of view, largely depends on Americans now.
> Riki was afraid to get stuck due to new duties at his workplace
> and as you correctly noted Scott offered that he might have some
> capacity from Feb.
> So the first thing is likely to get their feedback what they
> can/want/plan to do / or assume the command into your hands...
>
> Technically, what we need is to finish
> 1) sort out remaining bugs with 2.4 target in trac
> 2) review/ sort out TODOs in wiki
> https://wiki.lyx.org/Devel/LyX24Road
FWIW the point there regarding python, as far as I can see, is already
fixed in 2.4 with the ${python} keyword supported in preferences.
> 2) annouce string freeze to and ask translators to do their job
>
> > I am available to give one or both hands to the release proceed.
>
> Triaging remaining bugs is easiest way how to move forward before
> we reach some conclusion how to move forward from managerial
> point of view and needs to be done anyway...
>
> Pavel
--
José Abílio
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Tue, May 02, 2023 at 03:11:09PM +0200, Jean-Marc Lasgouttes wrote: > Le 02/05/2023 ?? 12:09, Pavel Sanda a écrit : > >Technically, what we need is to finish > >1) sort out remaining bugs with 2.4 target in trac > >2) review/ sort out TODOs in wiki https://wiki.lyx.org/Devel/LyX24Road > >2) annouce string freeze to and ask translators to do their job > > What is the status of the imagemagick mess? My multiple grievances on debian bug tracker were completely ignored so we are left on own to detect IM being under ban and try workarounds (current solution) or display warning which would suggest to spam distro maintainers to do something about it and thus increase the pressure. (I am currently aware of debian, and suse paranoia, Jose what is the fedora take on IM policy now?). - We have currently covered eps->png via non-IM eps->pdf->png workaround (bd0510b08) - We currently don't have PNG -> EPS (#12646, didn't have time to look yet) And yeah, I still didn't have time to look on the -dALLOWPSTRANSPARENCY for ghostscript needed since TL-2021. > One thing I'd like to do before release is to merge Text.cpp Text2.cpp and > Text3.cpp into a single file. It is so annoying to try to guess in which > file something is defined. Would somebody be against this ? I was wondering myself if we should merge those one day and I support this move. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
Le 02/05/2023 à 12:09, Pavel Sanda a écrit : Technically, what we need is to finish 1) sort out remaining bugs with 2.4 target in trac 2) review/ sort out TODOs in wiki https://wiki.lyx.org/Devel/LyX24Road 2) annouce string freeze to and ask translators to do their job What is the status of the imagemagick mess? One thing I'd like to do before release is to merge Text.cpp Text2.cpp and Text3.cpp into a single file. It is so annoying to try to guess in which file something is defined. Would somebody be against this ? It is better to do such thing at the end of development window, so that in the future backports are easier. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: What is missing for LyX 2.4?
On Sat, Apr 29, 2023 at 08:37:47AM +0100, José Matos wrote: > Do to this I think that the best is to proceed with 2.4 release. Ha! Now I know that 3 years of delay is making even Jose nervous :)) > What are the major roadblocks for 2.4? What needs to be done? > I remember that at some point Scott volunteered to drive the release > process. >From management point of view, largely depends on Americans now. Riki was afraid to get stuck due to new duties at his workplace and as you correctly noted Scott offered that he might have some capacity from Feb. So the first thing is likely to get their feedback what they can/want/plan to do / or assume the command into your hands... Technically, what we need is to finish 1) sort out remaining bugs with 2.4 target in trac 2) review/ sort out TODOs in wiki https://wiki.lyx.org/Devel/LyX24Road 2) annouce string freeze to and ask translators to do their job > I am available to give one or both hands to the release proceed. Triaging remaining bugs is easiest way how to move forward before we reach some conclusion how to move forward from managerial point of view and needs to be done anyway... Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
