Bug in language conversion ?
Dear Developers
When I select section 4.10.1.1 in the French copy of Additional.lyx and convert
it to French, I see that the optional argument of the list items remain
untranslated. This trigger compilation errors like :
Missing \endscname inserted
because of the \foreignlanguage{} encapsulating the argument of the optional
command.
This happens also at other places, where optional arguments are not translated.
I can provide a more complete record about Additional.
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX 2.4 RC4
Le 25/03/2024 à 12:58, Pavel Sanda a écrit : On Sun, Mar 24, 2024 at 06:36:57PM -0400, Richard Kimberly Heck wrote: http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/ Looks ok on debian oldstable. Pavel Same with Debian stable. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Changes in Additional.lyx
Hello Riki, While translating Additional.lyx in French, I made a couple of minor changes in the original English manual (around 10). I did not mark them as CT as we are close to release, but I keep a local AdditionalCT.lyx file up to date, to be published later for other translators if needed. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
AASTeX upgrade
Hello Riki As you must have seen, while upgrading AASTeX to version 6.3.1 (AASTeX version 6.2 is outdated since 2021), I triggered a string change. I am sorry for this, I was not aware that simply changing or adding a file name would trigger a string change. Should I revert my changes and wait for 2.4.1 ? -- Regards Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: aastex version has changed
Le 05/03/2024 à 14:18, Pavel Sanda a écrit : On Tue, Mar 05, 2024 at 12:32:46PM +0100, Jean-Pierre Chrétien wrote: I hope thet the upgrade is complete, I will see about the compilation warnings in template and example. Not yet. Filename is aastex63.layout while your makefile entry says aastex631.layout... ;) I don't understand, here is what I see in lib/Makefile.am : layouts/aastex.layout \ layouts/aastex6.layout \ layouts/aastex62.layout \ layouts/aastex63.layout \ I was about to normalize the template and example file names to be like the preceding versions, but Jürgen was faster... I took care not to update the layout with new constructs in aastex63.cls and aastex631.cls to avoid to break the string freeze, but I do not see where a change of file names breaks it... Sorry to have been clumsy. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: aastex version has changed
Le 05/03/2024 à 11:44, Pavel Sanda a écrit : Jean-Pierre, please also change lib/Makefile.am so the correct file names appears there. Otherwise we won't be able to pack the new tarballs. Done, thanks for the reminder. I added the layout file as well, it was in my .lyx dir. I hope thet the upgrade is complete, I will see about the compilation warnings in template and example. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: aastex version has changed
Le 29/02/2024 à 19:01, Jean-Pierre Chrétien a écrit : [...] A couple of new options could be inserted in the doc, but currently I will just update the version number, knowing that the layout and the exemple and template files should be updated also. I can do this as well if you like, and I can edit the English version of Additional.lyx. Done, I just committed an updated version of Additional.lyx and updated versions of the aastex template and example. If these files (version 6.2) are in the set of cmake texts, They should be failing as aastex62.cls is not distributed anymore. I changed the names of template and example files by replacing 6.2 with 631. However, compilation of the files fail due to bibliographic references not found. I do not understand why currently, but hopefully I will. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Assertion with lyx-2.4.0~devel
Dear developers I had again an assertion with the attached log (seems to be the same that happened with the macro pasting). That time I lost all the work that I had done before my previous save of the file, the .lyx~ file contains less matter than the .lyx file. There is no emergency file corresponding to the one I was working on, but there is one of a test file that I had opened to check the class I was working on. My current version of lyx-2.4.0~devel does not include the recent patch from Jean-Marc, that I only tested with the src/lyx file in my build dir. Jean-Marc, do you think that your patch cured this ? I will install this last version now and proceed with editing. I'll keep you posted if it happens again. The assertion happened when I was doing routine edition of the Additional manual, in the A article subsubsection. The assertion only closed the French Additional.lyx file on which I was working, not the original English version with CT which remained open. Of course, I may have attempted to insert a math macro by mistake, but this mistake would need an opening of the Math menu, which is not very liable in the context of my editions. -- Jean-Pierre CoordCache.cpp (25): break on pointer: 0x5618c219daf0 hint: dim size: 10 ( 1) lyx-2.4.0~devel: lyx::doAssertWithCallstack(bool) ( 2) lyx-2.4.0~devel: lyx::doBufErr(char const*, char const*, long) ( 3) lyx-2.4.0~devel: lyx::lyxbreaker(void const*, char const*, int) ( 4) lyx-2.4.0~devel: lyx::Inset::dimension(lyx::BufferView const&) const ( 5) lyx-2.4.0~devel: lyx::BufferView::coordOffset(lyx::DocIterator const&) const ( 6) lyx-2.4.0~devel: lyx::BufferView::getPos(lyx::DocIterator const&) const ( 7) lyx-2.4.0~devel: lyx::BufferView::checkCursorScrollOffset() ( 8) lyx-2.4.0~devel: lyx::BufferView::draw(lyx::frontend::Painter&, bool) ( 9) lyx-2.4.0~devel: lyx::BufferView::updatePosCache() ( 10) lyx-2.4.0~devel: lyx::BufferView::updateMetrics(lyx::Update::flags&) ( 11) lyx-2.4.0~devel: lyx::BufferView::processUpdateFlags(lyx::Update::flags) ( 12) lyx-2.4.0~devel: lyx::frontend::GuiApplication::updateCurrentView(lyx::FuncRequest const&, lyx::DispatchResult&) ( 13) lyx-2.4.0~devel: lyx::frontend::GuiApplication::dispatch(lyx::FuncRequest const&) ( 14) lyx-2.4.0~devel: lyx::dispatch(lyx::FuncRequest const&) ( 15) lyx-2.4.0~devel: lyx::frontend::Action::action() ( 16) lyx-2.4.0~devel: lyx-2.4.0~devel(+0x884eaf) [0x5618bea97eaf] ( 17) /lib/x86_64-linux-gnu/libQt5Core.so.5: /lib/x86_64-linux-gnu/libQt5Core.so.5(+0x2e8f7c) [0x7f17efce8f7c] ( 18) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QAction::triggered(bool) ( 19) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QAction::activate(QAction::ActionEvent) ( 20) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: /lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x2e3b62) [0x7f17f0ae3b62] ( 21) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: /lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x2eb994) [0x7f17f0aeb994] ( 22) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QWidget::event(QEvent*) ( 23) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, QEvent*) ( 24) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*) ( 25) lyx-2.4.0~devel: lyx::frontend::GuiApplication::notify(QObject*, QEvent*) ( 26) /lib/x86_64-linux-gnu/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, QEvent*) ( 27) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ( 28) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: /lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x1be025) [0x7f17f09be025] ( 29) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: /lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x1c0f60) [0x7f17f09c0f60] ( 30) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, QEvent*) ( 31) lyx-2.4.0~devel: lyx::frontend::GuiApplication::notify(QObject*, QEvent*) ( 32) /lib/x86_64-linux-gnu/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, QEvent*) ( 33) /lib/x86_64-linux-gnu/libQt5Gui.so.5: QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) ( 34) /lib/x86_64-linux-gnu/libQt5Gui.so.5: QWindowSystemInterface::sendWindowSystemEvents(QFlags) ( 35) /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5(+0x6deca) [0x7f17ec2fbeca] ( 36) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x299) [0x7f17ef51c7a9] ( 37) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x54a38) [0x7f17ef51ca38] ( 38) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f17ef51cacc] ( 39) /lib/x86_64-linux-gnu/libQt5Core.so.5: QEventDispatcherGlib::processEvents(QFlags) ( 40) /lib/x86_64-linux-gnu/libQt5Core.so.5: QEventLoop::exec(QFlags) ( 41)
aastex version has changed
Dear developers, Since TL 2022 at least, aastex version is now 6.31, so aastex631.cls is required to run templates and models. That's the file I get with TL 2023. Looking at the revision history on the AAS site, I see this : New in AASTeX v6.3 1. New interactive command to highlight interactive figures 2. Changes to collaboration to increase options for truncated author lists 3. New anonymous style to keep the authors, affiliations and acknowledgments from showing in the compiled pdf for dual anonymous review 4. Adoption of IAU approved syntax for nominal solar and planetary units 5. The movetableright command to help center wide, portrait tables 6. Updated aasjournal.bst file New in AASTeX v6.3.1 1. Bug fix in the Anonymous style option 2. Improved equation numbering with the linenumbers option 3. Depreciate the old acknowledgment command 4. De-emphasize the RNAAS style option 5. Added psj command for the Planetary Science Journal A couple of new options could be inserted in the doc, but currently I will just update the version number, knowing that the layout and the exemple and template files should be updated also. I can do this as well if you like, and I can edit the English version of Additional.lyx. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Font sizes with Wayland
Dear developers I was quite bored by the small size of fonts in the upper area of the LyX window (menus and such) with Wayland. I did not find a way to increase them, might be a window manager tuning, I guess. Recently I switched back to a classical Xorg window manager ans I was quite pleased to see the usual fonts sizes I has before Wayland became the implicit WM on Debian. Just to let you know, no action required. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Can't create a macro with 2.4.0~devel
Le 27/02/2024 à 07:51, Jean-Marc Lasgouttes a écrit : Indeed, insetAllowed forbids it for some reason. However the insertion is not guarded correctly. I do not want to fix this now, I have first to fix the crash The copy works and the crash is gone. Thanks! -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Can't create a macro with 2.4.0~devel
Le 27/02/2024 à 07:18, Jürgen Spitzmüller a écrit : Am Montag, dem 26.02.2024 um 17:44 +0100 schrieb Jean-Pierre Chrétien: Le 26/02/2024 à 16:14, Jean-Marc Lasgouttes a écrit : Now I have to understand why it crashes. I tried in a fresh lyx file with a single table. LyX crashes with the same trace as the one I posted previously, I guess that you can reproduce. Interestingly, I cannot paste macro definitions into tables. If I try to paste the inset from 22.3 of Mathed (\Godelnum), nothing is pasted and LyX does not crash. Sure, I noticed that when I tried to paste the macro from English Math.lyx to French one. Crash happened then when I tried to create the macro. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Can't create a macro with 2.4.0~devel
Le 26/02/2024 à 16:14, Jean-Marc Lasgouttes a écrit : Now I have to understand why it crashes. I tried in a fresh lyx file with a single table. LyX crashes with the same trace as the one I posted previously, I guess that you can reproduce. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Can't create a macro with 2.4.0~devel
Le 26/02/2024 à 09:31, Jean-Pierre Chrétien a écrit : Dera developers While updating the French Math manuel, I can't inset the math macro required in section 22.3. LyX crashes with this trace in the command shell: Forget about it, subsection 22.3 was inserted in the table ending section 22.2. If I paste it in the right place, I can insert( a macro all right. However, If I try to insert a macro in the table, LyX crashes... -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Can't create a macro with 2.4.0~devel
Dera developers While updating the French Math manuel, I can't inset the math macro required in section 22.3. LyX crashes with this trace in the command shell: CoordCache.cpp (25): break on pointer: 0x55cb032bfee0 hint: dim size: 157 ( 1) lyx-2.4.0~devel: lyx::doAssertWithCallstack(bool) ( 2) lyx-2.4.0~devel: lyx::doBufErr(char const*, char const*, long) ( 3) lyx-2.4.0~devel: lyx::lyxbreaker(void const*, char const*, int) ( 4) lyx-2.4.0~devel: lyx::Inset::dimension(lyx::BufferView const&) const ( 5) lyx-2.4.0~devel: lyx::BufferView::coordOffset(lyx::DocIterator const&) const ( 6) lyx-2.4.0~devel: lyx::BufferView::getPos(lyx::DocIterator const&) const ( 7) lyx-2.4.0~devel: lyx::BufferView::checkCursorScrollOffset() ( 8) lyx-2.4.0~devel: lyx::BufferView::draw(lyx::frontend::Painter&, bool) ( 9) lyx-2.4.0~devel: lyx::BufferView::updatePosCache() ( 10) lyx-2.4.0~devel: lyx::BufferView::updateMetrics(lyx::Update::flags&) ( 11) lyx-2.4.0~devel: lyx::BufferView::processUpdateFlags(lyx::Update::flags) ( 12) lyx-2.4.0~devel: lyx::frontend::GuiApplication::updateCurrentView(lyx::FuncRequest const&, lyx::DispatchResult&) ( 13) lyx-2.4.0~devel: lyx::frontend::GuiApplication::dispatch(lyx::FuncRequest const&) ( 14) lyx-2.4.0~devel: lyx::dispatch(lyx::FuncRequest const&) ( 15) lyx-2.4.0~devel: lyx::frontend::Action::action() ( 16) lyx-2.4.0~devel: lyx-2.4.0~devel(+0x884eaf) [0x55caff028eaf] ( 17) /lib/x86_64-linux-gnu/libQt5Core.so.5: /lib/x86_64-linux-gnu/libQt5Core.so.5(+0x2e8f7c) [0x7fb0feee8f7c] ( 18) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QAction::triggered(bool) ( 19) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QAction::activate(QAction::ActionEvent) ( 20) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: /lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x2e3b62) [0x7fb0ffce3b62] ( 21) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: /lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x2eb994) [0x7fb0ffceb994] ( 22) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QWidget::event(QEvent*) ( 23) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, QEvent*) ( 24) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*) ( 25) lyx-2.4.0~devel: lyx::frontend::GuiApplication::notify(QObject*, QEvent*) ( 26) /lib/x86_64-linux-gnu/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, QEvent*) ( 27) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ( 28) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: /lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x1be025) [0x7fb0ffbbe025] ( 29) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: /lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x1c0f60) [0x7fb0ffbc0f60] ( 30) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, QEvent*) ( 31) lyx-2.4.0~devel: lyx::frontend::GuiApplication::notify(QObject*, QEvent*) ( 32) /lib/x86_64-linux-gnu/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, QEvent*) ( 33) /lib/x86_64-linux-gnu/libQt5Gui.so.5: QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) ( 34) /lib/x86_64-linux-gnu/libQt5Gui.so.5: QWindowSystemInterface::sendWindowSystemEvents(QFlags) ( 35) /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5(+0x6deca) [0x7fb0fb4fbeca] ( 36) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x299) [0x7fb0fe71c7a9] ( 37) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x54a38) [0x7fb0fe71ca38] ( 38) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fb0fe71cacc] ( 39) /lib/x86_64-linux-gnu/libQt5Core.so.5: QEventDispatcherGlib::processEvents(QFlags) ( 40) /lib/x86_64-linux-gnu/libQt5Core.so.5: QEventLoop::exec(QFlags) ( 41) /lib/x86_64-linux-gnu/libQt5Core.so.5: QCoreApplication::exec() ( 42) lyx-2.4.0~devel: lyx::frontend::GuiApplication::exec() ( 43) lyx-2.4.0~devel: lyx::LyX::exec(int&, char**) ( 44) lyx-2.4.0~devel: lyx-2.4.0~devel(main+0x45) [0x55cafea8655e] ( 45) /lib/x86_64-linux-gnu/libc.so.6: /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7fb0fea4624a] ( 46) /lib/x86_64-linux-gnu/libc.so.6: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7fb0fea46305] ( 47) lyx-2.4.0~devel: lyx-2.4.0~devel(_start+0x21) [0x55cafea86451] Assertion triggered in void lyx::doAssertWithCallstack(bool) by failing check "false" in file ../../../master/src/support/lassert.cpp:45 Buffer.cpp (1657): /ext/lyx/master/lib/doc/fr/Math.lyx.emergency Abandon (core dumped) -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Refrerences to trac in the documentation
Le 12/02/2024 à 21:33, Pavel Sanda a écrit : On Mon, Feb 12, 2024 at 05:01:32PM +0100, Jean-Pierre Chrétien wrote: BTW, I will update the reference of the documentation in trac with https://git.lyx.org/gitweb/?p=lyx.git;a=tree;f=lib/doc;hb=HEAD Where exactly in the trac do you want to make that change? Here : 3.2.2 Joining the Documentation Team. The LyX Documentation Project, like anything else in the LyX project, can always use assistance! If you're interested in contributing to the Documentation Project, you need to do the following: 1. Get the latest LyX source code from [https://www.lyx.org/trac/browser/lyxgit/lib/doc?rev=master ] Trac is longer recommended to browse lyxgit, right ? I see, you mean in documentation not in trac. It's not that simple, we are currently working on transition of trac itself so in medium term this link might be working again. Or not ;) In any case I would not change the documentation yet. Currently I just added the lint to git.lyx.org in the French Intro.lyx. My question was rather to know if https://git.lyx.org/gitweb/?p=lyx.git;a=tree;f=lib/doc;hb=HEAD is the correct way to point to the documentation in git.lyx.org. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Message when I run git pull with a pending commit
Le 12/02/2024 à 21:39, Pavel Sanda a écrit : On Mon, Feb 12, 2024 at 04:56:40PM +0100, Jean-Pierre Chrétien wrote: which means : I prefer english messages in verbatin so I can google them :) Anyway, what "git status" returns? Intro.lyx is currently modified. $git st Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) modified: lib/doc/fr/Intro.lyx When I run git add lib/doc/fr/Intro.lyx Changes to be committed: (use "git restore --staged ..." to unstage) modified: lib/doc/fr/Intro.lyx Then I run 'git commit' and 'git pv' to rebase before push, and here is your warning in English : Warning: File deleted from disk The file /ext/lyx/master/lib/doc/fr/Intro.lyx has been deleted from disk! Rebasing (1/2) Rebasing (2/2) Warning: File deleted from disk The file /ext/lyx/master/lib/doc/fr/Intro.lyx has been deleted from disk! Successfully rebased and updated refs/heads/master. Then ls -l lib/doc/fr/Intro.lyx -rw-r--r-- 1 jp jp 58800 Feb 13 16:44 lib/doc/fr/Intro.lyx I had left Intro.lyx open in the LyX window, and I get a popup window with the same warning about the deleted file (attached screenshot 1) and the file has changed status from saved to modified with a warning (attached screnshot 2). If I save the file as IntroSave.lyx, there is no difference : $ diff lib/doc/fr/Intro.lyx lib/doc/fr/IntroSave.lyx $ So the incorrect warning message is reproducible, and I do not see what I am doing wrong. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Refrerences to trac in the documentation (was: Message when I run git pull with a pending commit)
Here I change the subject for what concerns th change from trac to git.lyx.org. Sorry if it is not the correct procedure. Would it be better located in lyx-docs ? I understood that cross-posting is not a good practice. Le 12/02/2024 à 16:45, Jean-Pierre Chrétien a écrit : BTW, I will update the reference of the documentation in trac with https://git.lyx.org/gitweb/?p=lyx.git;a=tree;f=lib/doc;hb=HEAD Where exactly in the trac do you want to make that change? Here : 3.2.2 Joining the Documentation Team. The LyX Documentation Project, like anything else in the LyX project, can always use assistance! If you're interested in contributing to the Documentation Project, you need to do the following: 1. Get the latest LyX source code from [https://www.lyx.org/trac/browser/lyxgit/lib/doc?rev=master ] Trac is longer recommended to browse lyxgit, right ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Message when I run git pull with a pending commit
Le 12/02/2024 à 13:31, Pavel Sanda a écrit : Isn't it possible that you just had 2 lyx windows opened on the same file? Or commited changes from different computer? No, none of these possibilities. I run all lyx-related stuff from my Debian bookworm box. Here is the message in French : $ git pv remote: Énumération des objets: 31, fait. remote: Décompte des objets: 100% (31/31), fait. remote: Compression des objets: 100% (19/19), fait. remote: Total 19 (delta 15), réutilisés 0 (delta 0), réutilisés du pack 0 Dépaquetage des objets: 100% (19/19), 311.03 Kio | 709.00 Kio/s, fait. Depuis git.lyx.org:lyx 8a32c34c5f..db897c1f4a master -> origin/master = [à jour]1.1.5fix_x -> origin/1.1.5fix_x = [à jour]1.1.6fix_x -> origin/1.1.6fix_x = [à jour]1.2.x -> origin/1.2.x = [à jour]1.3.x -> origin/1.3.x = [à jour]1.4.x -> origin/1.4.x = [à jour]1.5.x -> origin/1.5.x = [à jour]1.6.x -> origin/1.6.x = [à jour]2.0.x -> origin/2.0.x = [à jour]2.1.x -> origin/2.1.x = [à jour]2.2.1-staging -> origin/2.2.1-staging = [à jour]2.2.2-staging -> origin/2.2.2-staging = [à jour]2.2.3-staging -> origin/2.2.3-staging = [à jour]2.2.x -> origin/2.2.x = [à jour]2.3.0-alpha1-x -> origin/2.3.0-alpha1-x = [à jour]2.3.1-1-> origin/2.3.1-1 = [à jour]2.3.1-staging -> origin/2.3.1-staging = [à jour]2.3.2-1-> origin/2.3.2-1 = [à jour]2.3.2-2-> origin/2.3.2-2 = [à jour]2.3.2-staging -> origin/2.3.2-staging = [à jour]2.3.4-2-> origin/2.3.4-2 = [à jour]2.3.4-3-> origin/2.3.4-3 = [à jour]2.3.4-4-> origin/2.3.4-4 = [à jour]2.3.5.2-> origin/2.3.5.2 = [à jour]2.3.6.1-> origin/2.3.6.1 = [à jour]2.3.6.2-> origin/2.3.6.2 29f2a7ed66..f45c3e032a 2.3.x -> origin/2.3.x = [à jour]bugs/13017 -> origin/bugs/13017 * [nouvelle étiquette]2.4.0-RC3 -> 2.4.0-RC3 Changements de 8a32c34c5f8e296bcb40bb81c861c31b8367427c sur db897c1f4ab95290ea611bcd98eb5da387b6dcfb : po/de.gmo | Bin 653300 -> 653451 bytes po/sk.gmo | Bin 636496 -> 636629 bytes po/uk.gmo | Bin 816896 -> 816902 bytes po/uk.po | 65 + 4 files changed, 41 insertions(+), 24 deletions(-) Warning: Fichier effacé sur le disque Le fichier /ext/lyx/master/lib/doc/Customization.lyx a été effacé sur le disque ! Rebasage (1/1) Rebasage et mise à jour de refs/heads/master avec succès. which means : File /ext/lyx/master/lib/doc/Customization.lyx has been erased on disk! Rebase (1/1) Rebase and update of refs/heads/master successful. Then : $ ls /ext/lyx/master/lib/doc/Customization.lyx /ext/lyx/master/lib/doc/Customization.lyx and $ git push Énumération des objets: 9, fait. Décompte des objets: 100% (9/9), fait. Compression par delta en utilisant jusqu'à 6 fils d'exécution Compression des objets: 100% (5/5), fait. Écriture des objets: 100% (5/5), 475 octets | 475.00 Kio/s, fait. Total 5 (delta 4), réutilisés 0 (delta 0), réutilisés du pack 0 To git.lyx.org:lyx db897c1f4a..085fe133db master -> master I have this in gitconfig : [pull] rebase = true [alias] pv = pull -v -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Message when I run git pull with a pending commit
Le 12/02/2024 à 13:37, Pavel Sanda a écrit : On Mon, Feb 12, 2024 at 11:02:07AM +0100, Jean-Pierre Chrétien wrote: Since the update of the git server (thanks a lot, Pavel!), I get a message telling me that the file pending to be committed has been erased on my disk. Happily this is not true, but a bit disturbing. This message is coming from git, right? I see possibility that you committed the file, resaved the .lyx file within lyx and then got this message while workign with git. LyX is internally saving to a new file and moves away the old one, so if git is tracking the file handle instead of content (though I find this would be strange) it would explain the message. I will answer to this later. BTW, I will update the reference of the documentation in trac with https://git.lyx.org/gitweb/?p=lyx.git;a=tree;f=lib/doc;hb=HEAD Where exactly in the trac do you want to make that change? Here : 3.2.2 Joining the Documentation Team. The LyX Documentation Project, like anything else in the LyX project, can always use assistance! If you're interested in contributing to the Documentation Project, you need to do the following: 1. Get the latest LyX source code from [https://www.lyx.org/trac/browser/lyxgit/lib/doc?rev=master ] Trac is longer recommended to browse lyxgit, right ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Message when I run git pull with a pending commit
Le 12/02/2024 à 11:21, Jean-Pierre Chrétien a écrit : Le 12/02/2024 à 11:13, Jean-Pierre Chrétien a écrit : Le 12/02/2024 à 11:11, Pavel Sanda a écrit : On Mon, Feb 12, 2024 at 11:02:07AM +0100, Jean-Pierre Chrétien wrote: Since the update of the git server (thanks a lot, Pavel!), I get a message telling me that the file pending to be committed has been erased on my disk. Happily this is not true, but a bit disturbing. Disturbing indeed. Can you send me the exact error message, possibly in english? OK, I will retry a commit with my locale on C. Alas, no message when I committed a small change in French Intro.lyx, but there were no updates of the local tree with git pull, so I will wait to have some before retrying. I tried to use the chage I made to French Intro.lyx, but of course it did not work as the remote and local file are identical. I have to wait commits from other developers, I keep you posted. BTW, I will update the reference of the documentation in trac with : https://git.lyx.org/gitweb/?p=lyx.git;a=tree;f=lib/doc;hb=HEAD Is that correct ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Message when I run git pull with a pending commit
Le 12/02/2024 à 11:13, Jean-Pierre Chrétien a écrit : Le 12/02/2024 à 11:11, Pavel Sanda a écrit : On Mon, Feb 12, 2024 at 11:02:07AM +0100, Jean-Pierre Chrétien wrote: Since the update of the git server (thanks a lot, Pavel!), I get a message telling me that the file pending to be committed has been erased on my disk. Happily this is not true, but a bit disturbing. Disturbing indeed. Can you send me the exact error message, possibly in english? OK, I will retry a commit with my locale on C. Alas, no message when I committed a small change in French Intro.lyx, but there were no updates of the local tree with git pull, so I will wait to have some before retrying. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Message when I run git pull with a pending commit
Le 12/02/2024 à 11:11, Pavel Sanda a écrit : On Mon, Feb 12, 2024 at 11:02:07AM +0100, Jean-Pierre Chrétien wrote: Since the update of the git server (thanks a lot, Pavel!), I get a message telling me that the file pending to be committed has been erased on my disk. Happily this is not true, but a bit disturbing. Disturbing indeed. Can you send me the exact error message, possibly in english? OK, I will retry a commit with my locale on C. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Message when I run git pull with a pending commit
Le 12/02/2024 à 11:02, Jean-Pierre Chrétien a écrit : Dear developers Since the update of the git server (thanks a lot, Pavel!), I get a message telling me that the file pending to be committed has been erased on my disk. Happily this is not true, but a bit disturbing. As I had the file sill open in LyX, I see that it's status has been changed to "modified" and I get the same message in a child window. If I reload the file, all is OK once I agree to replace the loaded file by the one on disk. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Message when I run git pull with a pending commit
Dear developers Since the update of the git server (thanks a lot, Pavel!), I get a message telling me that the file pending to be committed has been erased on my disk. Happily this is not true, but a bit disturbing. Do you see this ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
2.3.8dev compilation
Dear developers Compiling 2.3.8dev from recent git pull, I get these deprecation warnings : ../../../../2.3.x/src/frontends/qt4/GuiDocument.cpp:172:18: warning: ‘template struct std::binary_function’ is deprecated [-Wdeprecated-declarations] 172 | : public binary_function ../../2.3.x/src/BiblioInfo.cpp:1152:29: warning: ‘template_Arg2, class _Result> struct std::binary_function’ is deprecated [-Wdeprecated-declarations] 1152 | class compareNoCase: public binary_function ../../2.3.x/src/BranchList.cpp:30:38: warning: ‘template_Result> struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 30 | class BranchNamesEqual : public std::unary_function ../../2.3.x/src/Format.cpp:61:33: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 61 | class FormatNamesEqual : public unary_function ../../2.3.x/src/Format.cpp:75:38: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 75 | class FormatExtensionsEqual : public unary_function ../../2.3.x/src/Format.cpp:89:32: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 89 | class FormatMimeEqual : public unary_function ./../2.3.x/src/IndicesList.cpp:30:37: warning: ‘template_Result> struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 30 | class IndexNamesEqual : public std::unary_function ../../2.3.x/src/IndicesList.cpp:46:38: warning: ‘template_Result> struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 46 | class IndexHasShortcut : public std::unary_function ../../2.3.x/src/Lexer.cpp:139:18: warning: ‘templateclass _Result> struct std::binary_function’ is deprecated [-Wdeprecated-declarations] 139 | : public binary_function ../../2.3.x/src/lyxfind.cpp:75:28: warning: ‘templateclass _Result> struct std::binary_function’ is deprecated [-Wdeprecated-declarations] 75 | class MatchString : public binary_function ../../2.3.x/src/TextClass.cpp:75:33: warning: ‘template_Result> struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 75 | class LayoutNamesEqual : public unary_function ../../2.3.x/src/insets/InsetCommandParams.cpp:596:41: warning: ‘std::const_mem_fun_ref_t<_Ret, _Tp> std::mem_fun_ref(_Ret (_Tp::*)() const) [with _Ret = bool; _Tp = lyx::ParamInfo::ParamData]’ is deprecated: use 'std::mem_fn' instead [-Wdeprecated-declarations] 596 | not1(mem_fun_ref(::ParamData::isOptional))); Harmless I guess, but should be removed before 2.4.0/2.3.8. Up to date Debian bookworm Configuration Host type: x86_64-pc-linux-gnu Special build flags: build=development std-regex warnings assertions stdlib-debug use-hunspell use-enchant Bundled libraries:boost hunspell C++ Compiler:g++ (12.2.0) C++ Compiler flags: -Wall -Wextra -fPIC -g -O -std=c++14 -Wno-deprecated-copy C++ Compiler user flags: Linker flags: Linker user flags: Qt Frontend: Qt version: 5.15.8 Packaging: posix LyX binary dir: /usr/local/bin LyX files dir: /usr/local/share/lyx-2.3.8dev -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: RC1!!
Le 11/01/2024 à 17:34, Pavel Sanda a écrit : On Thu, Jan 11, 2024 at 11:14:01AM -0500, Richard Kimberly Heck wrote: Please build binaries. Compiles and runs on oldstable debian. P Same on Debian stable. I just commited on master an update of French Intro.lyx, I hope it was possible to do so. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
List of available classes
Dear developers, While updating the French version of Additional.lyx, I wanted to check the availability of KOMA-Script Report. However, I can't scroll down the list of classes further than the Japanese reports, I do not even see the Report (standard class). lyx-2.4.0-RC1-devel recompiled after an update of the files at 8e619462. In addition, the fonts of the menu bars are very small as well as those of the lists of classes window. Where could I tune these fonts ? -- Regards Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Deprecated functions with lyx-2.3.7dev
Dear developers,
I recompiled lyx-2.3.7dev to cope with the problem of hunspell library missing
with Debian bookstorm, and I got a bunch of warnings about std:unary and
std:binary deprecated functions declared in in stl_function.h.
There ois also one similar warning about mem_fun_ref.
../../2.3.x/src/TextClass.cpp:75:33: warning: ‘template_Result> struct std::unary_function’ is deprecated [-Wdeprecated-declarations]
75 | class LayoutNamesEqual : public unary_function {
| ^~
In file included from /usr/include/c++/12/string:48,
from ../../2.3.x/src/support/strfwd.h:42,
from ../../2.3.x/src/support/docstring.h:16,
from ../../2.3.x/src/Citation.h:15,
from ../../2.3.x/src/TextClass.h:13,
from ../../2.3.x/src/TextClass.cpp:17:
/usr/include/c++/12/bits/stl_function.h:117:12: note: declared here
117 | struct unary_function
Configuration
Host type: x86_64-pc-linux-gnu
Special build flags: build=development std-regex warnings assertions
stdlib-debug use-hunspell use-enchant
Bundled libraries:boost hunspell
C++ Compiler:g++ (12.2.0)
C++ Compiler flags: -Wall -Wextra -fPIC -g -O -std=c++14
-Wno-deprecated-copy
C++ Compiler user flags:
Linker flags:
Linker user flags:
Qt Frontend:
Qt version: 5.15.8
Packaging: posix
LyX binary dir: /usr/local/bin
LyX files dir: /usr/local/share/lyx
on Debian bookworm.
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Don't hide menus
Le 14/10/2023 à 03:52, Daniel a écrit : On 2023-10-13 18:07, Daniel wrote: On 2023-10-13 17:24, Jürgen Spitzmüller wrote: Am Freitag, dem 13.10.2023 um 17:08 +0200 schrieb Daniel: I have not noticed that. I usually find that disabled menus are easy to disregard when I do not explicitly try to discover some function. And typically I have greater problems with disregarding stuff than other people. Hello Daniel, So, if I understand correctly, you would like that the LyX UI be modified to fit your peculiarities. Usually people having the same wish fill an enhancement ticket and wait for developers to have time to investigate if the enhancement is liable to improve LyX for everybody. They do not harass developers directly on the list. Moreover, I do not understand why you are so keen to have LyX UI behave like Word UI. If you like Word UI so much, just use Word. My 2cts. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Beta 5 Tarballs
Le 31/08/2023 à 07:15, Richard Kimberly Heck a écrit : Apoligies to Stephan, who built beta 4. I'm calling this beta 5 to avoid problems with the version numbers. Here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/ Compiles and runs fine on Debian stable: Version Qt (à l'exécution) : 5.15.8 sur la plate-forme wayland Version Qt (à la compilation): 5.15.8 Version OS (à la compilation) : Debian GNU/Linux 12 (bookworm) Python détecté : python3 -tt Just one repeated warning at runtime: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Warnings during compilation of 2.3.8dev
Dear developers, I had to recompile 2.3.8dev becaus the then enchant bug (see https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg219915.html) With : Configuration Host type: x86_64-pc-linux-gnu Special build flags: build=development std-regex warnings assertions stdlib-debug use-enchant Bundled libraries:boost C++ Compiler:g++ (12.2.0) C++ Compiler flags: -Wall -Wextra -fPIC -g -O -std=c++14 -Wno-deprecated-copy C++ Compiler user flags: Linker flags: Linker user flags: Qt Frontend: Qt version: 5.15.8 Packaging: posix LyX binary dir: /usr/local/bin LyX files dir: /usr/local/share/lyx-2.3.8dev I get warnings : binary_function: 4 occurences ../../../../2.3.x/src/frontends/qt4/GuiDocument.cpp:172:18: warning: ‘template struct std::binary_function’ is deprecated [-Wdeprecated-declarations] 172 | : public binary_function /usr/include/c++/12/bits/stl_function.h:131:12: note: declared here 131 | struct binary_function unary_function: 7 occurences ../../2.3.x/src/BranchList.cpp:30:38: warning: ‘template_Result> struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 30 | class BranchNamesEqual : public std::unary_function /usr/include/c++/12/bits/stl_function.h:117:12: note: declared here 117 | struct unary_function others: ../../2.3.x/src/LyXRC.cpp: In function ‘void lyx::actOnUpdatedPrefs(const LyXRC&, const LyXRC&)’: ../../2.3.x/src/LyXRC.cpp:3077:42: warning: comparison between two arrays [-Warray-compare] 3077 | || lyxrc_orig.font_sizes != lyxrc_new.font_sizes |~~^~~ ../../2.3.x/src/insets/InsetCommandParams.cpp: In member function ‘lyx::docstring lyx::InsetCommandParams::getFirstNonOptParam() const’: ../../2.3.x/src/insets/InsetCommandParams.cpp:596:41: warning: ‘std::const_mem_fun_ref_t<_Ret, _Tp> std::mem_fun_ref(_Ret (_Tp::*)() const) [with _Ret = bool; _Tp = lyx::ParamInfo::ParamData]’ is deprecated: use 'std::mem_fn' instead [-Wdeprecated-declarations] 596 | not1(mem_fun_ref(::ParamData::isOptional))); | ~~~^~~ /usr/include/c++/12/bits/stl_function.h:1389:5: note: declared here 1389 | mem_fun_ref(_Ret (_Tp::*__f)() const) | ^~~ -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Customization ctests now failing on master
Le 12/08/2023 à 12:43, Jürgen Spitzmüller a écrit : I think the approach is sane enough. Since we haven't heard many reports about this bug recently, the case seems to be rather seldom (I suppose French users avoid prettyref). Thanks for solving this issue, Jürgen. I think that there are not many prettyref users in general, since refstyle is much more powerful. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Change of enchant version with bookworm
Le 03/07/2023 à 11:26, Jean-Marc Lasgouttes a écrit : I guess this is a Debian issue, you might want to create a bug report for them. Done -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Change of enchant version with bookworm
Dear Developers I upgraded recentlt my Debian to bookworm (aka Debian 12) and got this with all my versions of lyx: error while loading shared libraries: libenchant.so.1: cannot open shared object file: No such file or directory SEmmes that the version of enchant changed (enchant-2 now): $ find /usr/lib -name 'libenchant*' /usr/lib/x86_64-linux-gnu/libenchant-2.so.2 /usr/lib/x86_64-linux-gnu/libenchant-2.so.2.3.3 /usr/lib/x86_64-linux-gnu/libenchant-2.so Recompilation fixes the issue. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Quotes in stats
Le 08/05/2023 à 21:42, Pavel Sanda a écrit : On Mon, May 08, 2023 at 06:06:48PM +0200, Jean-Pierre Chrétien wrote: Le 08/05/2023 ?? 15:45, Pavel Sanda a écrit : On Mon, May 08, 2023 at 03:21:05PM +0200, Jean-Pierre Chrétien wrote: So, it is clear that the French guillemets counts for 2 characters (one if blanks excluded), Well, I would presume that even if we output space, it's sort of typographic adjustment and not blank as a character but as you wish, I can easily return 2 chars instead of 1 for guillemets. In fact, it is a thin space... And we are back to square one :) Let me put it in different way: if you are to submit some short french text in web text form (say an article abstract) - so there are no fancy typographic options. Or you are putting french comment to your source code containing someone's quotation. Would you rather add guillemets with normal space or you'd rather put no space at all? For HTML pages, I used to insert &ńbsp; after « and before » ( and before : : ! ?). -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Quotes in stats
Le 08/05/2023 à 15:45, Pavel Sanda a écrit : On Mon, May 08, 2023 at 03:21:05PM +0200, Jean-Pierre Chrétien wrote: So, it is clear that the French guillemets counts for 2 characters (one if blanks excluded), Well, I would presume that even if we output space, it's sort of typographic adjustment and not blank as a character but as you wish, I can easily return 2 chars instead of 1 for guillemets. In fact, it is a thin space... What libreoffice/word think about this situation? libreoffice finds 34 words instead of 28, ,which I do not understand. EWhenounting the number of characters excluding blanks, it finds 249 instaed of 247... but for the : ; ? and ! characters, it would be necessary to count 2 characters if the punctuation sign is not preceded by a blank. This is getting more tricky, because we generaly do look on the context when we counting the characters (except of catching blanks/.?/etc around words). In that case too, the blank character si a thin space. -- Jean-Pierre ponctuation.odt Description: application/vnd.oasis.opendocument.text -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Quotes in stats
Le 08/05/2023 à 15:21, Jean-Pierre Chrétien a écrit : Le 08/05/2023 à 14:43, Pavel Sanda a écrit : On Mon, May 08, 2023 at 02:17:41PM +0200, Jean-Pierre Chrétien wrote: In French, the guillemets are inserted as characters ?? and ?? (automatically translated from typed character "), but they are associated to a protected space, so in ?? exemple ??, there are 9 characters without blanks and 11 with blanks. But this protected space is added by user or it's LyX's doing? LyX does the job, the spaces appear in the LyX window. Same stuff for punctuation marks : ; ? and !, which are all preceded by a protected space in French. the space is added by Lyx, but it does not need to appear in the LyX window. But it is weirder than it looks: if the user types in a space before : ; ? and !, LyX does not add anything, but makes it a protected space if it is not one. So, it is clear that the French guillemets counts for 2 characters (one if blanks excluded), but for the : ; ? and ! characters, it would be necessary to count 2 characters if the punctuation sign is not preceded by a blank. I suppose that you count characters in the output from the analysis of the characters in the LyX window, is this correct ? Attached is an example file. -- Jean-Pierre ponctuation.lyx Description: application/lyx -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Quotes in stats
Le 08/05/2023 à 14:43, Pavel Sanda a écrit : On Mon, May 08, 2023 at 02:17:41PM +0200, Jean-Pierre Chrétien wrote: In French, the guillemets are inserted as characters ?? and ?? (automatically translated from typed character "), but they are associated to a protected space, so in ?? exemple ??, there are 9 characters without blanks and 11 with blanks. But this protected space is added by user or it's LyX's doing? LyX does the job, the spaces appear in the LyX window. Same stuff for punctuation marks : ; ? and !, which are all preceded by a protected space in French. the space is added by Lyx, but it does not need to appear in the LyX window. But it is weirder than it looks: if the user types in a space before : ; ? and !, LyX does not add anything, but makes it a protected space if it is not one. So, it is clear that the French guillemets counts for 2 characters (one if blanks excluded), but for the : ; ? and ! characters, it would be necessary to count 2 characters if the punctuation sign is not preceded by a blank. I suppose that you count characters in the output from the analysis of the characters in the LyX window, is this correct ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Quotes in stats
Le 08/05/2023 à 14:02, Pavel Sanda a écrit :
Hi,
I almost submitted abstract overflowing in characters, because we do not count
quotes in statistics.
Attached is the patch fixing it.
Just to make sure, isn't some of the types below to be counted as more than 1
character?
* e``english'' (`inner quotation')
* s''swedish'' ('inner quotation')
* g,,german`` (,inner quotation`)
* p,,polish'' (,inner quotation')
* c<>()
* a>>danish<< (>inner quotation<)
* q"plain" ('inner quotation')
* b`british'(``inner quotation'')
* w>>swedishg>> ('inner quotation') ["g" = Guillemets]
* f<> (``inner quotation'')
* i<> (<>) ["in" = Imprimerie Nationale]
In French, the guillemets are inserted as characters « and » (automatically
translated from typed character "), but they are associated to a protected
space, so in « exemple », there are 9 characters without blanks and 11 with blanks.
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
lyx-2.4.0dev chaaged name ?
Dear developers, I gave a bash scripts which remerges strings after a git sync. Recently it failed because the name of the version suffix changed from dev to -beta3-devel. Was this intended ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone running LyX on Wayland?
Le 13/03/2023 à 09:45, Jean-Pierre Chrétien a écrit : Le 13/03/2023 à 09:38, Jean-Pierre Chrétien a écrit : In addition I get this: Warning: Failed to produce 1 preview snippet(s) Not in addition, I get this one whatever the value of QT_QPA_PLATFORM. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone running LyX on Wayland?
Le 13/03/2023 à 09:38, Jean-Pierre Chrétien a écrit : Le 13/03/2023 à 02:25, Scott Kostyshak a écrit : I get the following messages in the terminal: QSocketNotifier: Can only be used with threads started with QThread qt.qpa.wayland: Wayland does not support QWindow::requestActivate() I never get the last message that you mention. In fact, I get your last message if I load the UserGuide (and I get it several times): qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() In addition I get this: Warning: Failed to produce 1 preview snippet(s) -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone running LyX on Wayland?
Le 13/03/2023 à 02:25, Scott Kostyshak a écrit : I get the following messages in the terminal: QSocketNotifier: Can only be used with threads started with QThread qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Does anyone else get these with Wayland? No,; but I used to regularly get this: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. If I comply to the request, I get this: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. QSocketNotifier: Can only be used with threads started with QThread I must run XDG_SESSION_TYPE= QT_QPA_PLATFORM=wayland lyx-2.4.0dev to get rid of the first message. I never get the last message that you mention. Debian bullseye, QT 5.15.2 Should I try to compile with QT6 ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Error messages
Le 22/02/2023 à 10:52, Jean-Pierre Chrétien a écrit : Dear developers When I open the original UserGuide with 2.4.0dev, I see this in the calling command window: Warning: dvipng failed to generate images from lyxpreviewOuMJqr.dvi... fallback to legacy method Warning: epstopdf failed on page 1, file lyxpreviewOuMJqr.001 Warning: epstopdf failed on page 2, file lyxpreviewOuMJqr.002 [...] snip Warning: epstopdf failed on page 109, file lyxpreviewOuMJqr.109 Warning: epstopdf failed on page 110, file lyxpreviewOuMJqr.110 Warning: Now trying to obtain failed previews through pdflatex Warning: Failed to produce 1 preview snippet(s) When I open the French version, I get only the last line. Any clue ? Ping :-) -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Acknowledgments
Le 27/02/2023 à 12:01, Jürgen Spitzmüller a écrit : Am Montag, dem 27.02.2023 um 11:39 +0100 schrieb Jean-Pierre Chrétien: It seems that the Acknowledgments theorem style has disappeared from branch, but I see a couple of 'Acknowledgements' remaining in fr.po. That's correct, these are mostly acknowledgment sections of articles. Some still use British spelling (I didn't want to touch that if the output was concerned). Thanks for the explanation. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Acknowledgments
Dear Developers, It seems that the Acknowledgments theorem style has disappeared from branch, but I see a couple of 'Acknowledgements' remaining in fr.po. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Error messages
Dear developers When I open the original UserGuide with 2.4.0dev, I see this in the calling command window: Warning: dvipng failed to generate images from lyxpreviewOuMJqr.dvi... fallback to legacy method Warning: epstopdf failed on page 1, file lyxpreviewOuMJqr.001 Warning: epstopdf failed on page 2, file lyxpreviewOuMJqr.002 [...] snip Warning: epstopdf failed on page 109, file lyxpreviewOuMJqr.109 Warning: epstopdf failed on page 110, file lyxpreviewOuMJqr.110 Warning: Now trying to obtain failed previews through pdflatex Warning: Failed to produce 1 preview snippet(s) When I open the French version, I get only the last line. Any clue ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] French docs: remove unicode thin spaces
Le 19/02/2023 à 17:44, Jean-Marc Lasgouttes a écrit : Le 19/02/2023 à 17:31, Scott Kostyshak a écrit : On Sun, Feb 19, 2023 at 01:12:54PM +0100, Jean-Marc Lasgouttes wrote: Le 18/02/2023 à 21:40, Scott Kostyshak a écrit : commit 07a7e847d6d4af4b19d4daa5066b192cac2bc07f Author: Scott Kostyshak Date: Sat Feb 18 16:40:50 2023 -0500 French docs: remove unicode thin spaces This feels wrong. French typography does require these thin spaces. What should have been done is replacing that by quote insets, unless Jean-Pierre had a reason for using raw guillemets. Am I missing something? Thanks for catching this. Let me know what is best and I will go back through the related commits and fix what I changed. Also let me know if I should revert in the meantime. Let's wait for Jean-Pierre's take on this. It seems that I typed the French guillemets as I do in plain text documents, that is with the character « or » and a plain space, instead of simply typing in " which creates French guillemets in French docs. Sorry for this and thanks to Scott for detecting this. I restored the correct typography at 12ef26d388. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Acknowledgment vs. Acknowledgement
Le 31/01/2023 à 07:52, Jürgen Spitzmüller a écrit : Am Montag, dem 30.01.2023 um 15:26 -0500 schrieb Richard Kimberly Heck: Yes, it's fine with me. Done. While doing it, it occurred to me that the acknowledgment strings in their different uses might need disambiguation. The theorem type "Acknowledgment" has not the same semantics than the "Acknowledgment[s]" in some of the article classes, right? The latter is to display gratefulness to grant sponsors and colleagues (i.e., credits), but I can't imagine the theorem type has that function. It is more to acknowledge (and maybe critically challenge) an argument, right? To German, acknowledgment could be translated as (a) Danksagung (credits), (b) Würdigung (respect), (c) Eingeständnis (admission), or (d) Erwiderung (reply). Which one is it? I'd tip (b) or (d). True, I've found a translation for French. But xx.po for 2.3 should be edited as well IMHO. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Update lyx-2.4 docs
Le 29/01/2023 à 17:37, Jürgen Spitzmüller a écrit : Am Sonntag, dem 29.01.2023 um 17:23 +0100 schrieb Jean-Pierre Chrétien: I would like to search easily what has been updated since (but for the new index features that I have already updated in the UserGuide). Is it possible to search for modifications after a given date in the documents ? I could search for changes in Trac, but is is quite lengthy. Document > Track Changes > Accept and Reject Changes. This dialog has the change dates (not ideal for sure). Thanks, but it would be much faster if this info was automatically displayed when you go to the next modification. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Update lyx-2.4 docs
Dear Developers, I performed a first update of the French 2.4 documentation around 20 months ago. I would like to search easily what has been updated since (but for the new index features that I have already updated in the UserGuide). Is it possible to search for modifications after a given date in the documents ? I could search for changes in Trac, but is is quite lengthy. -- Regards Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
What version of fr.po in lyx-2.4.0-beta2 ?
Dear devs I compiled and ran fine beta2. The UserGuide copiles fine, but a bunch of 13 messages "Negative width" on the terminal after compilation completion. My question is about fr.po. While compiling, I saw that there were some translations missing, a msgfmt check gives: 8051 translated messages, 16 fuzzy translations, 4 untranslated messages. I do not understand this status, the current fr.po version has 8059 translated messages, 1 untranslated message. I do not find in the history of fr.po a file having the data of the beta2 one. Any clue ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Cross reference inset
Dear Devs I think there is something fishy with this inset, when the 'Alphabetically' sort keys are used : the selected entry has nothing in common with the one selected, if you select a fresh one. The only correct behavior is with the sort key by occurrence. Do you see the same behavior ? lyx-2.4.0dev, recent update. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Shortcut conflict
Hello, While translating the new index features, I see this when I open the UserGuide in an English locale : frontends/qt/Menus.cpp (761): Menu warning: menu entries "Close Inset|C" and "Custom Page Formatting|C" share the same shortcut. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Missing icons
Le 06/08/2022 à 18:55, Jean-Pierre Chrétien a écrit : Dear Developers, With the latest 2.4.0dev version, I do not see anymore the icons for "Find and Replace", "Find and Replace (advanced)" and "Toggle outline", but the plain text. Problem solved. Thanks, Jürgen. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Missing icons
Dear Developers, With the latest 2.4.0dev version, I do not see anymore the icons for "Find and Replace", "Find and Replace (advanced)" and "Toggle outline", but the plain text. See attached screenshot. -- Jean-Pierre-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Wrong commit ?
Le 31/07/2022 à 19:16, Kornel Benko a écrit : Am Sun, 31 Jul 2022 18:48:01 +0200 schrieb Jean-Pierre Chrétien : Dear Developers, While committing a very minor change in the French UserGuide, I had a warning about the fact that I was in "Detached HEAD mode". I committed nevertheless, but I see in the log that there is something fishy: $ git log commit 4c72d8aeac01c53e27732999108f249356e67c5c (HEAD -> master, origin/master, origin/HEAD) Author: jpc Date: Sun Jul 31 18:28:23 2022 +0200 Info in French UserGuide commit c04192526187c1b3bfe7d7dcabd9cd6c50084642 Author: Pavel Sanda Date: Sun Jul 31 11:13:53 2022 +0200 pyupgrade related fixes to python scripts #2. Patch from Jose. https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg21.html Is my commit in the right place? What should I do to return to normal behavior? Should I run $git switch - Maybe $ git checkout master ? from what I understand from the inline explanations? Looks OK here. commit 4c72d8ae Author: jpc AuthorDate: Sun Jul 31 18:28:23 2022 +0200 Commit: jpc CommitDate: Sun Jul 31 18:29:23 2022 +0200 Info in French UserGuide What bugs me is the (HEAD -> master, origin/master, origin/HEAD) part, which is not present usually. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Wrong commit ?
Dear Developers, While committing a very minor change in the French UserGuide, I had a warning about the fact that I was in "Detached HEAD mode". I committed nevertheless, but I see in the log that there is something fishy: $ git log commit 4c72d8aeac01c53e27732999108f249356e67c5c (HEAD -> master, origin/master, origin/HEAD) Author: jpc Date: Sun Jul 31 18:28:23 2022 +0200 Info in French UserGuide commit c04192526187c1b3bfe7d7dcabd9cd6c50084642 Author: Pavel Sanda Date: Sun Jul 31 11:13:53 2022 +0200 pyupgrade related fixes to python scripts #2. Patch from Jose. https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg21.html Is my commit in the right place? What should I do to return to normal behavior? Should I run $git switch - from what I understand from the inline explanations? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Update fr.po and a couple of shortcuts defined with non-existing letters
Le 13/06/2022 à 12:48, Kornel Benko a écrit : Am Mon, 13 Jun 2022 09:07:12 +0200 (CEST) schrieb jpc : Normal Space|w" You missed #: lib/ui/stdmenus.inc:454 msgid "Normal Space|w" Thanks, I did not check stdmenus.inc Also there is wrong translation in fr.po to "Espace large négative insécable (−5/18 em)a" (missing '|'?) but probably in conflict with "Dimension réglable|a" Right, corrected and shortcut conflicts solved. I have a question : with Debian stable, when I open the InsetSpace context menu, the selection is controlled by check-boxes. In that case, shortcuts are not useful. Is it different on other platforms where the shortcuts would be welcome ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Make space names more standard
Le 12/06/2022 à 13:07, Juergen Spitzmueller a écrit : commit b2a7b715a2c6f0d9f26a180c15e1570308dc6d6c Author: Daniel Ramoeller Date: Wed Jun 8 08:20:37 2022 +0200 Make space names more standard Fix for bug #12547. - "Interword" becomes "Normal" - "Protected" becomes "Non-Breaking" Plus a minor fixes to the "Horizontal Space Settings" dialog: - Indicate that when "Non-Breaking" is disabled, the space will be non-breaking While translating in French, I saw that a couple of original English shortcuts letters were not found in the string: Item "Normal Space|w" Item "Half Quad Space (1/2 em)|k" Item "Non-Breaking Half Quad Space (1/2 em)|E" I updated these to Item "Normal Space|e" Item "Half Quad Space (1/2 em)|S" Item "Non-Breaking Half Quad Space (1/2 em)|k" with hopefully no shortcuts conflicts. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Revert "Add UI for selecting backing store drawing strategy"
Le 13/01/2022 à 17:29, Jean-Pierre Chrétien a écrit : Le 13/01/2022 à 16:46, Jean-Marc Lasgouttes a écrit : commit 854fbc52621f3ecdced7cada98d72da8e8e35428 Author: Jean-Marc Lasgouttes Date: Thu Jan 13 17:09:42 2022 +0100 Revert "Add UI for selecting backing store drawing strategy" Effectivement... J'avais soumis la traduction. Je suppose que le message traduit en français va disparaître avec le message original ? Sorry for the noise, this was intended for Jean-Marc only. :-( -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Revert "Add UI for selecting backing store drawing strategy"
Le 13/01/2022 à 16:46, Jean-Marc Lasgouttes a écrit : commit 854fbc52621f3ecdced7cada98d72da8e8e35428 Author: Jean-Marc Lasgouttes Date: Thu Jan 13 17:09:42 2022 +0100 Revert "Add UI for selecting backing store drawing strategy" Effectivement... J'avais soumis la traduction. Je suppose que le message traduit en français va disparaître avec le message original ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Performance regression in export to LaTeX?
Le 20/12/2021 à 12:16, Jürgen Spitzmüller a écrit : Am Montag, dem 20.12.2021 um 10:21 +0100 schrieb Jürgen Spitzmüller: Tried again and (once more) ended up at commit 26ea1e14966c092a7b87c75c19b83a369e79aeb8 Author: Juergen Spitzmueller Date: Sun Apr 22 19:06:46 2018 +0200 Align fontenc with document fonts I'll check if we can do something. c2f2ba57f1275c should address this one. Now : real0m11,354s user0m9,962s sys 0m1,044s -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Performance regression in export to LaTeX?
Le 19/12/2021 à 15:45, Jürgen Spitzmüller a écrit : Am Sonntag, dem 19.12.2021 um 15:03 +0100 schrieb Jürgen Spitzmüller: So it's the cprotection checks that seem to cost time. Need to check whether this can be optimized. After 61b8afd893ec we're back at real0m19,685s user0m15,633s sys 0m3,025s Recompiling after 61b8afd893ec leads here to real0m13,374s user0m11,999s sys 0m1,012s instead of real0m31,623s user0m22,924s sys0m1,532s (which includes 9s of lyx reconfiguration, that means thet real must be rather 22s). To be compared to the 2.3.x result real0m9,749s user0m8,459s sys0m1,320s So the ratio is now 10/13 instead of a little over 2. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Performance regression in export to LaTeX?
Le 18/12/2021 à 03:23, Scott Kostyshak a écrit : If I do time lyx -e pdflatex UserGuide.lyx I get big differences in timings if I do the above with master versus with 2.3.0. I'm not sure these differences necessarily mean a regression. I've definitely compiled master with different compile flags. Does anyone else see differences when comparing 2.3.0 (or 2.3.x) to master with the above command? Hello Scott, Here I must run time -e pdf2 UserGuide.lyx With 2.3.7dev: real0m9,749s user0m8,459s sys 0m1,320s With 2.4.0dev (up to date): real0m31,623s user0m22,924s sys 0m1,532s Ration ~ 3 -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Export to 2.3.x of French linguistics manual fails to compile on 2.3.x
Le 08/12/2021 à 10:22, Jürgen Spitzmüller a écrit : Am Mittwoch, dem 08.12.2021 um 09:51 +0100 schrieb Jürgen Spitzmüller: The other is the reversion with language switches. Might be more difficult, I'll check. I forgot that language switches in glosses do not work. In the long run, we should probably allow language switches in LyX (for spell checking) but output no language markup to LaTeX. Something like an OmitLangSwitch layout tag. Thanks for checking and fixing things, Jürgen. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Upgrade from buster to bullseye
Le 11/11/2021 à 13:23, Jean-Marc Lasgouttes a Editing policy.html was the trick. Thanks to all of you who helped. Do you have rsvg-convert installed? Is it used in this situation? I installed librsvg2-bin, reconfigured lyx-2.3.7dev, removed files from the cache and again, compilation of the UserGuide went flawlessly with calls to rsvg. The rsvg path is actually easier on Debian that editing the ImageMagick policy file. I never use Debian install of LyX because it requires to install Texlive as well (and I install it separately from tug.org), but is librsvg2-bin in the Lyx dependencies ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Upgrade from buster to bullseye
Le 11/11/2021 à 11:52, Jean-Pierre Chrétien a écrit : Le 10/11/2021 à 14:32, Jean-Marc Lasgouttes a écrit : Le 10/11/2021 à 14:07, Jean-Pierre Chrétien a écrit : You need to enable "files" debug level. This not very informative, in fact I would like to see the conversion command to be able to test it from the console. I should (from Converter::convert, l. 661): LYXERR(Debug::FILES, "Calling " << command); What do you have as output? No Converter.cpp reference, so the message is not triggered. All references are to ConverterCache.cpp, so I guess that I should clean the cache, but I do not remember how... I found a cache directory in my personal LyX dir, so I removed the contents ans bingo! compilation of the UserGuide works flawlessly. ConverterCache.cpp (401): not in cache. Looking for python v2.x or 3.x ... Examining /opt/texlive/2021/bin/x86_64-linux/pythontex Examining /usr/bin/python2 Found Python 2.7.18 Converter.cpp (430): No converter defined! I use convertDefault.py: /usr/bin/python2 -tt "/usr/local/share/lyx-2.3.7dev/scripts/convertDefault.py" svgz "/tmp/lyx_tmpdir.XrMxvxhYnibI/lyx_tmpbuf0/0_usr_local_share_lyx-2_3_7dev_images_buffer-new.svgz" pdf "/tmp/lyx_tmpdir.XrMxvxhYnibI/lyx_tmpbuf0/0_usr_local_share_lyx-2_3_7dev_images_buffer-new.pdf" ConverterCache.cpp (270): /usr/local/share/lyx-2.3.7dev/images/buffer-new.svgz pdf6 /tmp/lyx_tmpdir.XrMxvxhYnibI/lyx_tmpbuf0/0_usr_local_share_lyx-2_3_7dev_images_buffer-new.pdf Editing policy.html was the trick. Thanks to all of you who helped. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Upgrade from buster to bullseye
Le 10/11/2021 à 14:32, Jean-Marc Lasgouttes a écrit : Le 10/11/2021 à 14:07, Jean-Pierre Chrétien a écrit : You need to enable "files" debug level. This not very informative, in fact I would like to see the conversion command to be able to test it from the console. I should (from Converter::convert, l. 661): LYXERR(Debug::FILES, "Calling " << command); What do you have as output? No Converter.cpp reference, so the message is not triggered. All references are to ConverterCache.cpp, so I guess that I should clean the cache, but I do not remember how... -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Upgrade from buster to bullseye
Le 09/11/2021 à 12:22, Pavel Sanda a écrit : On Tue, Nov 09, 2021 at 11:28:30AM +0100, Jean-Pierre Chrétien wrote: I edited /etc/ImageMagick-6/policy.xml without success, here is the log of the first file to convert, extracted from lyx-2.3.7dev -dbg graphics Can show the current content of that config? File attached. This is the original bullseye file in which I changed lines 93, 96, 97. How can I display the conversion process from svgz to pdf6 itself? You need to enable "files" debug level. This not very informative, in fact I would like to see the conversion command to be able to test it from the console. -- Jean-Pierre ]> -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Upgrade from buster to bullseye
Le 08/11/2021 à 21:57, Pavel Sanda a écrit :
Yes, this is default imagemagick policy on debian now.
First introduced in buster to overcome ghostscritp security issues, then
reverted
in testing (forthcoming bullseye) and then reintroduced again. I tried to
explain
the situation in couple debian bugs but no one seem to care.
I did not get these messages with buster, maybe I upgraded from etch after the
reversion to testing.
The situation is very unfortunate, because this default policy ban on
postscript conversions can not be overriden by user setting and if you
don't have root access on the machine you work, you can't use
postscript anymore.
I edited /etc/ImageMagick-6/policy.xml without success, here is the log of the
first file to convert, extracted from lyx-2.3.7dev -dbg graphics
insets/InsetGraphics.cpp (119): findTargetFormat: PDF mode
insets/InsetGraphics.cpp (742): we have: from svgz to pdf6
insets/InsetGraphics.cpp (748): the orig file is:
/usr/local/share/lyx-2.3.7dev/images/buffer-new.svgz
insets/InsetGraphics.cpp (794): The original file is
/usr/local/share/lyx-2.3.7dev/images/buffer-new.svgz
A copy has been made and convert is to be called with:
file to convert =
/tmp/lyx_tmpdir.ukkrIUtySeWW/lyx_tmpbuf0/0_usr_local_share_lyx-2_3_7dev_images_buffer-new.svgz
from svgz to pdf6
insets/InsetGraphics.cpp (924): InsetGraphics::latex outputting:
\includegraphics[width=1em]{0_usr_local_share_lyx-2_3_7dev_images_buffer-new.pdf}
With 2.4.0dev (wich works all right), I get this :
insets/InsetGraphics.cpp (117): findTargetFormat: PDF mode
insets/InsetGraphics.cpp (735): we have: from svgz to pdf6
insets/InsetGraphics.cpp (741): the orig file is:
/usr/local/share/lyx-2.4.0dev/images/buffer-new.svgz
insets/InsetGraphics.cpp (787): The original file is
/usr/local/share/lyx-2.4.0dev/images/buffer-new.svgz
A copy has been made and convert is to be called with:
file to convert =
/tmp/lyx_tmpdir.HrwLplbmyPtA/lyx_tmpbuf0/export_buffer-new_svgz_c835ff7b1cb15ad019ad9820ad3e422677e2fb0ffb807224b41310571151427e.svgz
from svgz to pdf6
insets/InsetGraphics.cpp (916): InsetGraphics::latex outputting:
\includegraphics[width=1em]{export_buffer-new_svgz_c835ff7b1cb15ad019ad9820ad3e422677e2fb0ffb807224b41310571151427e.pdf}
How can I display the conversion process from svgz to pdf6 itself?
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Upgrade from buster to bullseye
Le 08/11/2021 à 21:57, Pavel Sanda a écrit : On Mon, Nov 08, 2021 at 11:03:25AM +0100, Jean-Pierre Chrétien wrote: On 2.3.x, I first checked the fr.po file status and when I ran the make lyx-2.3.7dev.pot-update in the po dir of the build directory, I got in the following error: /bin/sh: 1: /usr/bin/python: not found make: *** [Makefile:774 : qt4_l10n.pot] Erreur 127 So I created a link: sudo ln -s /usr/bin/python3 /usr/bin/python and the problem was solved. This is actually not correct way how to solve this under bullseye. "python" is gone for good and scripts should use either python2 or python3 binary. I was quite aware that my workaround was not the correct solution. However, as make lyx-2.3.7dev.pot-update fails because of missing python while make lyx-2.4.0dev.pot-update succeeds, is it possible to cherry-pick the python management from master ? If you insist on using "python" you should install specific package (IIRC "python") via: apt install python It is not me who insists, it is lyx-2.3.7dev :-) -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Upgrade from buster to bullseye
Le 08/11/2021 à 14:12, Kornel Benko a écrit : For ubuntu/debian it was sufficient to modify the imagemagic policy. Like: $ cp /etc/ImageMagick-6/policy.xml ~/.config/ImageMagick/. and add/modify policies for PS, PDF and EPS in ~/.config/ImageMagick/policy.xml to I removen rsvh-conbert, reconfigured, created and edited ~/.config/ImageMagick/policy.xml and now, same behavior as with rsvg-convert, latex does not find the files. I'm lost. What is broken now ? I will recompile lyx-2.3.7dev from scratch. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Upgrade from buster to bullseye
Le 08/11/2021 à 11:20, Jean-Marc Lasgouttes a écrit : Le 08/11/2021 à 11:03, Jean-Pierre Chrétien a écrit : Dear developers I upgraded my Debian yesterday and I tested compilation and execution of master and 2.3.7dev. Compilation and display of the UserGuide run flawlessly on master. On 2.3.x, I first checked the fr.po file status and when I ran the make lyx-2.3.7dev.pot-update in the po dir of the build directory, I got in the following error: /bin/sh: 1: /usr/bin/python: not found make: *** [Makefile:774 : qt4_l10n.pot] Erreur 127 This is for José, right? I guess so. So I created a link: sudo ln -s /usr/bin/python3 /usr/bin/python and the problem was solved. The I compiled lyx-2.3.7dev all right with QT5 (QT4 fails). However, when compiling the pdf of the UserGuide, none of the svgz icons could be converted, so the padf dispaly failed with a pdf image not found. Here is first of the error messages: convert-im6.q16: attempt to perform an operation not allowed by the security policy `PDF' @ error/constitute.c/IsCoderAuthorized/421. /usr/local/share/lyx-2.3.7dev/scripts/convertDefault.py ERROR Execution of "convert" failed. Do you have rsvg-convert intalled (in librsvg2-bin package here). No I hadn't. So I installed librsvg2-bin, reconfigured LyX and it seems that the situation is worse : the conversion does not even seem to take place. This "convert" situation is really horrible, I do not understand that there is no workaround yet. As the problem seems to be gone with master, I guess that such a workaround won't be needed in the (near?) future. But why is the behavior different between 2.3.7 and 2.4.0? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Upgrade from buster to bullseye
Dear developers I upgraded my Debian yesterday and I tested compilation and execution of master and 2.3.7dev. Compilation and display of the UserGuide run flawlessly on master. On 2.3.x, I first checked the fr.po file status and when I ran the make lyx-2.3.7dev.pot-update in the po dir of the build directory, I got in the following error: /bin/sh: 1: /usr/bin/python: not found make: *** [Makefile:774 : qt4_l10n.pot] Erreur 127 So I created a link: sudo ln -s /usr/bin/python3 /usr/bin/python and the problem was solved. The I compiled lyx-2.3.7dev all right with QT5 (QT4 fails). However, when compiling the pdf of the UserGuide, none of the svgz icons could be converted, so the padf dispaly failed with a pdf image not found. Here is first of the error messages: convert-im6.q16: attempt to perform an operation not allowed by the security policy `PDF' @ error/constitute.c/IsCoderAuthorized/421. /usr/local/share/lyx-2.3.7dev/scripts/convertDefault.py ERROR Execution of "convert" failed. support/Systemcall.cpp (276): Systemcall: 'python -tt "/usr/local/share/lyx-2.3.7dev/scripts/convertDefault.py" svgz "/tmp/lyx_tmpdir.ISfQxXhtSZQG/lyx_tmpbuf0/0_usr_local_share_lyx-2_3_7dev_images_buffer-view.svgz" pdf "/tmp/lyx_tmpdir.ISfQxXhtSZQG/lyx_tmpbuf0/0_usr_local_share_lyx-2_3_7dev_images_buffer-view.pdf"' finished with exit code 1 -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Makefile in po
Le 18/10/2021 à 13:55, Jean-Marc Lasgouttes a écrit : Le 18/10/2021 à 12:12, Jean-Pierre Chrétien a écrit : Le 18/10/2021 à 11:46, Jean-Marc Lasgouttes a écrit : Le 18/10/2021 à 10:53, Jean-Pierre Chrétien a écrit : Hello The files Makefile disappeared from the po directory, both in master and 2.3.x. I need them to remerge strings. I ran ./autogen.sh with no success. what's wrong here ? Hi Jean-Pierre, Did you run ./configure too? Sure, lyx compiles fine in both cases. Bot po contains only Makefile.in.in Makevars Makevars.template Towards the end of the configure run, I see: config.status: executing po-directories commands config.status: creating po/POTFILES config.status: creating po/Makefile Don't you see that? Sure. Stupid of me, I was looking for Makefile in master/po, not in /po. Sorry for the noise. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: DeprecationWarning when installing master
Le 18/10/2021 à 13:22, Jean-Pierre Chrétien a écrit : Dear developers I get this : $ sudo make install-strip >>make.log -c:2: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses With some context : /usr/bin/install -c -m 644 ../../../master/lib/lyx2lyx/lyx2lyx lyx2lyx_version.py ../../../master/lib/lyx2lyx/lyx2lyx_lang.py ../../../master/lib/lyx2lyx/generate_encoding_info.py ../../../master/lib/lyx2lyx/parser_tools.py ../../../master/lib/lyx2lyx/lyx2lyx_tools.py ../../../master/lib/lyx2lyx/unicode_symbols.py ../../../master/lib/lyx2lyx/LyX.py ../../../master/lib/lyx2lyx/lyx_0_06.py ../../../master/lib/lyx2lyx/lyx_0_08.py ../../../master/lib/lyx2lyx/lyx_0_10.py ../../../master/lib/lyx2lyx/lyx_0_12.py ../../../master/lib/lyx2lyx/lyx_1_0.py ../../../master/lib/lyx2lyx/lyx_1_1.py ../../../master/lib/lyx2lyx/lyx_1_1_5.py ../../../master/lib/lyx2lyx/lyx_1_1_6_0.py ../../../master/lib/lyx2lyx/lyx_1_1_6_3.py ../../../master/lib/lyx2lyx/lyx_1_2.py ../../../master/lib/lyx2lyx/lyx_1_3.py ../../../master/lib/lyx2lyx/lyx_1_4.py ../../../master/lib/lyx2lyx/lyx_1_5.py ../../../master/lib/lyx2lyx/lyx_1_6.py ../../../master/lib/lyx2lyx/lyx_2_0.py ../../../master/lib/lyx2lyx/lyx_2_1.py ../../../master/lib/lyx2lyx/lyx_2_2.py ../../../master/lib/lyx2lyx/lyx_2_3.py ../../../master/lib/lyx2lyx/lyx_2_4.py ../../../master/lib/lyx2lyx/profiling.py ../../../master/lib/lyx2lyx/test_parser_tools.py '/usr/local/share/lyx-2.4.0dev/lyx2lyx' -c:2: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses Byte-compiling python modules... lyx2lyx_version.pylyx2lyx_lang.pygenerate_encoding_info.pyparser_tools.pylyx2lyx_tools.pyunicode_symbols.pyLyX.pylyx_0_06.pylyx_0_08.pylyx_0_10.pylyx_0_12.pylyx_1_0.pylyx_1_1.pylyx_1_1_5.pylyx_1_1_6_0.pylyx_1_1_6_3.pylyx_1_2.pylyx_1_3.pylyx_1_4.pylyx_1_5.pylyx_1_6.pylyx_2_0.pylyx_2_1.pylyx_2_2.pylyx_2_3.pylyx_2_4.pyprofiling.pytest_parser_tools.py -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
DeprecationWarning when installing master
Dear developers I get this : $ sudo make install-strip >>make.log -c:2: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses -- Regards Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Makefile in po
Le 18/10/2021 à 11:46, Jean-Marc Lasgouttes a écrit : Le 18/10/2021 à 10:53, Jean-Pierre Chrétien a écrit : Hello The files Makefile disappeared from the po directory, both in master and 2.3.x. I need them to remerge strings. I ran ./autogen.sh with no success. what's wrong here ? Hi Jean-Pierre, Did you run ./configure too? Sure, lyx compiles fine in both cases. Bot po contains only Makefile.in.in Makevars Makevars.template -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Makefile in po
Hello The files Makefile disappeared from the po directory, both in master and 2.3.x. I need them to remerge strings. I ran ./autogen.sh with no success. what's wrong here ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Master regression example with emph and comment
Le 25/09/2021 à 20:04, Scott Kostyshak a écrit :
The attached example compiles fine with 2.3.x. On master, the \emph is not closed after
"regardless" as what happens on 2.3.x.
Right, the comment is encapsulated in the \emph command.
With 2.3.7, the command is closed all right before the comment, but there is
still a harmless {} after the comment.
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Fwd: [LyX/master] Add hint about the need of Acrobat DC
Hello Riki This one is candidate for stable. Jean-Pierre Message transféré Sujet : [LyX/master] Add hint about the need of Acrobat DC Date : Tue, 6 Jul 2021 18:38:01 +0200 (CEST) De : jpc Répondre à : lyx-devel@lists.lyx.org Pour : lyx-...@lists.lyx.org commit 27092c2af02d1f54d108a4d7159e6edcbb245ae0 Author: jpc Date: Tue Jul 6 18:51:30 2021 +0200 Add hint about the need of Acrobat DC --- lib/examples/Modules/PDF_Form.lyx | 29 -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: PDF Form
Le 02/07/2021 à 12:40, Dr Eberhard Lisse a écrit :
Jean-Pierre
I just use the 'PDF Form' Module (which requires/loads hyperref) and the
Insert->Custom Insets
offers a number of choices such as
TextField.
Then you can put stuff like
width=9cm, charsize=9pt, bordercolor={0.94 0.97 1.0},
backgroundcolor={0.94 0.97 1.0}, name=company
That seems to work in any PDF Viewer, Preview and Skim on the Mac.
Hello Eberhard,
OK, but my concern was with the JS dynamic forms described in section 5 of the
PDF-Form.lyx manual of the examples directory.
Could you confirm that the forms display correctly in this section and
specifically that
- if you select "unlimited" in the radio button combo box, the "From" and
"Until" fields disappear;
- if you type in a A in the bottom field, you get a warning (the field id
dedicated to numbers).
You must have insdljs.sty installed (that is package acrotex).
--
Thanks for your reply
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
PDF Form
Dear Developers A French user draw my attention on the fact that the dynamic forms documented in section 5 of the PDF_Form.lyx manual (in examples/Modules) did not work as described. After installing insdljs.sty, I could display the examples in the output. It took me a while to understand that they would only work with acroread, which is not available in Linux since 2013 (I tried Okular first). I was able to install this last version on my Linux box: the checkNumber function works and the radio button displays correctly, but the forms do not disappear when I check "unlimited". I'm going to document the need for Acrobat DC in the lyx file, but I would like to know if the forms disappear in that case. Is it the case for any of you ? If not, I will ask on the users' list. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Revert "Fix bug #10263"
Le 13/06/2021 à 18:33, Kornel Benko a écrit :
Am Sun, 13 Jun 2021 11:42:59 -0400
schrieb Scott Kostyshak :
On Sat, May 29, 2021 at 01:47:41PM -0400, Scott Kostyshak wrote:
On Fri, May 28, 2021 at 10:48:51AM -0400, Scott Kostyshak wrote:
On Tue, Apr 13, 2021 at 10:13:16AM +0200, Jean-Marc Lasgouttes wrote:
commit 441c6a93590698c3c57982c8b80179d6809fb106
Author: Jean-Marc Lasgouttes
Date: Mon Apr 12 20:44:58 2021 +0200
Revert "Fix bug #10263"
A series of commits, culminating at 812ff7de, pushed a few days later,
fixes the bug at its root. This one is not needed anymore to fix
This reverts commit 001f5a47861f04c985323677dfd17ef15b8c33a7
---
src/insets/InsetFoot.h |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/src/insets/InsetFoot.h b/src/insets/InsetFoot.h
index 1e4b0d2..0c3f65a 100644
--- a/src/insets/InsetFoot.h
+++ b/src/insets/InsetFoot.h
@@ -45,10 +45,6 @@ private:
///
Inset * clone() const override { return new InsetFoot(*this); }
///
- bool inheritFont() const override { return true; }
- ///
- bool allowMultiPar() const override { return true; }
- ///
docstring custom_label_;
///
bool intitle_;
--
The following ctest started failing with this commit:
export/doc/ja/Tutorial_pdf5_systemF
The diff between the "bad" (current master) and "good" (current master
with this commit reverted) is as follows:
$ diff good.tex bad.tex
61c61
< \author{\LyX
プロジェクトチーム\thanks{なにかコメントや間違いの修正がある場合には，\protect\LyX
文書化メーリングリスト(\protect\href{mailto:lyx-d...@lists.lyx.org}{lyx-d...@lists.lyx.org})までお知らせ下さい．この文書の翻訳は，当初人見光太郎氏が行った貢献に基づいています．}}
---
\author{\LyX プロジェクトチーム\thanks{{\normalsize
なにかコメントや間違いの修正がある場合には，\protect\LyX
文書化メーリングリスト(\protect\href{mailto:lyx-d...@lists.lyx.org}{lyx-d...@lists.lyx.org})までお知らせ下さい．この文書の翻訳は，当初人見光太郎氏が行った貢献に基づいています．}}}
$
I have no idea why the {\normalsize ...} would cause the failure. Does
anyone know the problem?
Note that we are already aware of several other Japanese documents that
do not compile with non-TeX fonts:
export/doc/ja/(Additional|LaTeXConfig|Math|UserGuide).*_systemF
so it would not be surprising if we need to add Tutorial.lyx to the list.
By the way, if this report does not lead to a fix in LyX or a bug
report, we should log this wasted time in
development/autotests/ctests-costs-benefits.txt.
I think the French Powerdot example might also have a footnote where
this commit changes behavior. If I remove the footnote, compilation
succeeds. I did not do a bisect on that document but it feels like a
similar issue.
Does anyone know what the core issue is? Here is the LaTeX code causing
the problem after this commit:
\thanks{{\normalsize Traduction française Jean-Pierre
Chrétien, }{\normalsize\texttt{}}}{\normalsize},
novembre
2009.}}}
Do we need to adapt lyx2lyx perhaps? Or is this a LyX LaTeX export
issue?
Scott
This compiles also if changing the font inside the footnote (Teletype->default)
Hello
The French Powerdot file was a mess because the Footnote which gives info about
the translator exported to LaTeX as \thanks, splitting the content in two pieces
and leaving spurious parentheses at the end.
I dissolved the Footnote inset and made the content a LyX note, compiles fine
now.
Committed at 5b0b3f053e
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: ctests for French User Guide are failing
Le 28/05/2021 à 14:24, Scott Kostyshak a écrit :
On Fri, May 28, 2021 at 08:51:08AM +0200, Jean-Pierre Chrétien wrote:
Le 28/05/2021 à 02:14, Scott Kostyshak a écrit :
The following ctests for the French User Guide on current master are failing
for me:
export/doc/fr/UserGuide_lyx22 (Failed)
export/doc/fr/UserGuide_lyx23 (Failed)
export/doc/fr/UserGuide_dvi (Failed)
export/doc/fr/UserGuide_dvi3_texF (Failed)
export/doc/fr/UserGuide_pdf (Failed)
DEFAULTOUTPUT_export/doc/fr/UserGuide_pdf2 (Failed)
export/doc/fr/UserGuide_pdf3 (Failed)
export/doc/fr/UserGuide_pdf5_texF (Failed)
Should be fixed now.
Works well. Thanks for the quick fix, Jean-Pierre!
The error that made the tests fail is quite peculiar. I copied the new escape
sequences at the end of section 6.8.1 from the English UserGuide without marking
it as French, and I got this error:
! Paragraph ended before \bbl@foreign@x was complete.
When I look at the code, I do not see any missing parenthesis.
eux\foreignlanguage{english}{.\nomenclature{%@, %|, %!, %"}{The quote sign in
TeX code is output by writing ' %"{}%"{} '.}}
The error disappears when I mark the index entry as French, and the new code is:
.\nomenclature{%@, %|, %!, %"}{The quote sign in TeX code is output by writing '
%"{}%"{} '.}
Could this be a hidden bug affecting language embedding of index entries?
I'll try to build a MWE.
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: ctests for French User Guide are failing
Le 28/05/2021 à 02:14, Scott Kostyshak a écrit : The following ctests for the French User Guide on current master are failing for me: export/doc/fr/UserGuide_lyx22 (Failed) export/doc/fr/UserGuide_lyx23 (Failed) export/doc/fr/UserGuide_dvi (Failed) export/doc/fr/UserGuide_dvi3_texF (Failed) export/doc/fr/UserGuide_pdf (Failed) DEFAULTOUTPUT_export/doc/fr/UserGuide_pdf2 (Failed) export/doc/fr/UserGuide_pdf3 (Failed) export/doc/fr/UserGuide_pdf5_texF (Failed) Should be fixed now. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Dynamic insets
Le 18/05/2021 à 07:52, Jürgen Spitzmüller a écrit : Am Montag, dem 17.05.2021 um 16:07 +0200 schrieb Jean-Pierre Chrétien: Finally, it seems that not all menu entries appear in dynamic insets. What are exactly those which are liable to do so (the list in the inset parameters is not very explicit)? And is it done everywhere where it can be in the English docs? If not, is this a target to achieve? Probably all should use info insets. Is it correct to state that all the recognised strings are given in the LFUNS mùanual, under 'dialog-show' ? As a conclusion, where is the dynamic inset feature documented? I do not remember to have translated it. User Guide A.4.4 Thanks, indeed, it needs to be translated in French. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Dynamic insets
Dear Developers Following a discussion on lyx-docs about the Text Style menu, I g=have a couple of questions about the dynamic insets feature. First of all, the advantages of such a feature, as far as menus are concerned, is twofold: A/ the menu names appears translated in the UI language when the reader opens a manual; B/ any change in the po file is corrected automagically in the docs. Initially I thought that the translation in the language of the UI should not appear in the pdf export, but I understood that it was easy to create a PDF in English by changing the locale before calling LyX. Then I wondered if the UI should be dynamic in the translated manuals, as a reader of the e.g. French manual will have the UI in French. But feature B remains an incentive to keep it dynamic there also. I'm not sure to have it a all places, I will check that. Finally, it seems that not all menu entries appear in dynamic insets. What are exactly those which are liable to do so (the list in the inset parameters is not very explicit)? And is it done everywhere where it can be in the English docs? If not, is this a target to achieve? As a conclusion, where is the dynamic inset feature documented? I do not remember to have translated it. -- Regards Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Clipboard
Le 04/05/2021 à 18:36, Scott Kostyshak a écrit : On Tue, May 04, 2021 at 06:31:43PM +0200, Jean-Pierre Chrétien wrote: Le 04/05/2021 à 15:17, Kornel Benko a écrit : Am Tue, 4 May 2021 14:14:47 +0200 schrieb Jean-Pierre Chrétien : Le 14/04/2021 à 18:49, Scott Kostyshak a écrit : In that case, it could be that the fix referenced above actually made things worse for you. You could try to revert the commit 7a158055 on the 2.3.x branch and see if that makes the terminal message go away for you. If you do that, please let me know if it helps things because that means we should fix something. [...] However, it turns out that I reverted globally instead of locally, sorry. No problem, we've all done that before. I guess I should have simply patched the local files, right? Or is there a git command to revert locally only? The clipboard message is still there, but I got this message when starting LyX: $ invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor:: Le délai d’attente est dépassé (g-io-error-quark, 24) So I will come back to lyx-2.4.0 with your patches... -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Clipboard
Le 04/05/2021 à 15:17, Kornel Benko a écrit : Am Tue, 4 May 2021 14:14:47 +0200 schrieb Jean-Pierre Chrétien : Le 14/04/2021 à 18:49, Scott Kostyshak a écrit : In that case, it could be that the fix referenced above actually made things worse for you. You could try to revert the commit 7a158055 on the 2.3.x branch and see if that makes the terminal message go away for you. If you do that, please let me know if it helps things because that means we should fix something. Hello SCott In fact, I get the message also with master while working on the French docs: . frontends/qt/GuiClipboard.cpp (92): No timely response from clipboard, perhaps process holding clipboard is frozen? What is the commit to revert on master ? commit 7a158055fe6c05763f88ddb61a9c02b42614091d Author: Scott Kostyshak Date: Fri Mar 27 21:23:08 2020 -0400 ... (cherry picked from commit af4ee1a487c4d899b71df02ba57c2f024fea6786) (cherry picked from commit 23abb5aaa36af07aadfa5e565869104778ba0d6d) Got this by 'git show 7a158055'. Thanks for the info and the hint, Kornel. However, it turns out that I reverted globaélly instead of locally, sorry. What shoulsd I do to restore the commits in the master repo? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Clipboard
Le 14/04/2021 à 18:49, Scott Kostyshak a écrit : In that case, it could be that the fix referenced above actually made things worse for you. You could try to revert the commit 7a158055 on the 2.3.x branch and see if that makes the terminal message go away for you. If you do that, please let me know if it helps things because that means we should fix something. Hello SCott In fact, I get the message also with master while working on the French docs: . frontends/qt/GuiClipboard.cpp (92): No timely response from clipboard, perhaps process holding clipboard is frozen? What is the commit to revert on master ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Clipboard
Le 13/04/2021 à 19:58, Scott Kostyshak a écrit : On Tue, Apr 13, 2021 at 06:35:22PM +0200, Jean-Pierre Chrétien wrote: Dear Developers While working with lyx-2.3.7dev compiled with QT5.11.3, I see this in the terminal : $ frontends/qt4/GuiClipboard.cpp (92): No timely response from clipboard, perhaps process holding clipboard is frozen? I see it when I come back to the terminal window, so I do not know when it happens. Any clue? Do you use a clipboard manager? If so, which one? I use CopyQ and I often see that message in the terminal. I think it's also related that sometimes I select something in LyX and the selection is broken. Does this ever happen to you? It is much better in my experience after the fix for #11715 (which is in the version of LyX you're using) but I still see it sometimes. Hello SCott, No I don't use a clipboard manager. What puzzles me is that the message mentions Qt4... If you don't use a clipboard manager, then I'm not sure. LyX does some tricks regarding the clipboard because it does not want to constantly export code whenever the selection changes (that would be expensive), so it tries to wait until an application requests the selection. Sure, but it is the first time I see this message. Of course, I do not use any more LyX to produce documents as I used to do before I retired. I'll keep an aye on my terminal. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Clipboard
Dear Developers While working with lyx-2.3.7dev compiled with QT5.11.3, I see this in the terminal : $ frontends/qt4/GuiClipboard.cpp (92): No timely response from clipboard, perhaps process holding clipboard is frozen? I see it when I come back to the terminal window, so I do not know when it happens. Any clue? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Wayland
Le 31/03/2021 à 17:12, Jean-Marc Lasgouttes a écrit : Le 29/03/2021 à 15:38, Jean-Pierre Chrétien a écrit : Le 29/03/2021 à 11:00, Jean-Marc Lasgouttes a écrit : What happens if you do what they say? I see the same with Ubuntu. $ export QT_QPA_PLATFORM=wayland $ lyx-2.3.7dev Using Wayland-EGL Using the 'xdg-shell-v6' shell integration And the window fonts are very small, the header is blue and the shortcut symbols for the control of the window are unreadable (and in fact only closing is functional). Could you try some other Qt applications in wayland mode to see whether the problem is wayland configuration in debian or LyX itself? I do not see any difference with VLC of FileZilla, seems to be LyX-related. i see there are other wayland plugins, should I test them ? I guess now you know why LyX runs in X mode by default under wayland :) Sure. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Wayland
Le 29/03/2021 à 10:22, Jean-Pierre Chrétien a écrit : Dear developers With master git print 779f0a74, I get this when I start Lyx : Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. Debian Buster Gnome Wayland, indeed. Same message with branch. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Wayland
Dear developers With master git print 779f0a74, I get this when I start Lyx : Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. Debina Buster Gnome Wayland, indeed. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX compilation fails after reinstalling OS
Le 12/03/2021 à 18:17, Pavel Sanda a écrit : On Fri, Mar 12, 2021 at 06:12:18PM +0100, Jean-Pierre Chrétien wrote: Dear developers I had to reinstall my Debian buster after a big mistake while using rsync. Now here is what I get when I run the config command in the build dir: ../master/configure --with-version-suffix --with-included-hunspell checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for QT_CORE... yes checking for QT_FRONTEND... checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... no checking for Qt library name... failed, retrying with Qt4 checking for QT_CORE... yes Package QtCore was not found in the pkg-config search path. Perhaps you should add the directory containing `QtCore.pc' to the PKG_CONFIG_PATH environment variable No package 'QtCore' found Package QtCore was not found in the pkg-config search path. Perhaps you should add the directory containing `QtCore.pc' to the PKG_CONFIG_PATH environment variable No package 'QtCore' found checking for QT_FRONTEND... checking for X... libraries , headers checking for gethostbyname... (cached) yes checking for connect... (cached) yes checking for remove... (cached) yes checking for shmat... (cached) yes checking for IceConnectionNumber in -lICE... (cached) no checking for Qt library name... (cached) failed configure: error: cannot compile a simple Qt executable. Check you have the right $QTDIR. Looking in the log for what causes the "checking for Qt library name... failed", I see : configure:10708: checking for Qt library name configure:10747: g++ -o conftest -I/usr/lib/x86_64-linux-gnu/qt5/include -I/usr /lib/x86_64-linux-gnu/qt5/include/Qt -I/usr/lib/x86_64-linux-gnu/qt5/include/QtC ore -I/usr/lib/x86_64-linux-gnu/qt5/include/QtGui -I/usr/lib/x86_64-linux-gnu/qt 5/include/QtWidgets -I/usr/lib/x86_64-linux-gnu/qt5/include/QtSvg -I/usr/lib/x86 _64-linux-gnu/qt5/include/QtConcurrent -I/usr/lib/x86_64-linux-gnu/qt5/include/Q tMacExtras -L/usr/lib/x86_64-linux-gnu/qt5/lib conftest.cpp-lX11 -lQt5C ore >&5 conftest.cpp:36:11: fatal error: qglobal.h: No such file or directory #include When I look at the contents of the qt5 dir, I see this : $ ls /usr/lib/x86_64-linux-gnu/qt5/ bin libexec mkspecs plugins qml qt.conf No include there, I must have missed some qt5 package when I reinstalled. So in which qt5 package are the includes located ? Sorry for the lengthy mail, and thanks for your help. Did you run debian's apt-get build-dep lyx before compiling? Here is what apt-get installs: $ sudo apt-get build-dep lyx [snip] Les NOUVEAUX paquets suivants seront installés : dh-python libboost-dev libboost-filesystem-dev libboost-filesystem1.67-dev libboost-iostreams-dev libboost-iostreams1.67-dev libboost-regex-dev libboost-regex1.67-dev libboost-signals-dev libboost-signals1.67-dev libboost-signals1.67.0 libboost-system1.67-dev libboost-test-dev libboost-test1.67-dev libboost-test1.67.0 libboost-timer1.67.0 libboost1.67-dev libenchant-dev libmagic-dev libmythes-dev libqt5svg5-dev So the boost libs were missing. I can compile all right now, thanks a lot. Let's continue discussion on lyx-devel this really does not belong to this list. Sure, sorry. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Insert menu
Le 26/01/2021 à 09:37, José Abílio Matos a écrit : One striking example for me is the case of Portuguese books where the TOC was placed at the end. The idea is that in this case you can interpret the TOC as some kind of index. Actually it even received the name of index while the index was called "remissive index". Personally I do not like because when I go to a book I like to see the structure of the book and the TOC conveys that. Nowadays most book in Portuguese have the TOC at front but I can see a different interpretation to have it at the end. In French, the TOC is usually in the endmatter. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
