Timeout while loading pages on www.lyx.org
Dear developers I get a timeout while loading https://www.lyx.org/AdditionalSoftware Am I alone to see this ? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Cannot select a report class with Wayland
Dear devs, I just used the fresh official 2.4.0 release to type in a report and I was unable to select the desired class from the list, which displays only down to Japanese reports (same with 2.3.8). Works fine with Xorg... I doubt that devlopers can do anything about it :-(( -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX 2.4.0 Released!
Le 01/06/2024 à 01:30, Richard Kimberly Heck a écrit : Public release of LyX version 2.4.0 Congratulatiuons to all devs for achieving this great improvement of LyX! -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: 2.4.0 To Be Released Friday!
Le 31/05/2024 à 18:19, Jean-Pierre Chrétien a écrit : Le 31/05/2024 à 18:01, Richard Kimberly Heck a écrit : On 5/31/24 02:58, Jürgen Spitzmüller wrote: Am Donnerstag, dem 30.05.2024 um 21:59 -0400 schrieb Richard Kimberly Heck: I'm happy to keep doing it. If anyone would like to take over, though, I'd be happy to pass the baton. Excellent. You are doing an outstanding job. And congrats to the release. I think it is a real milestone on many respects. A lot of that is your doing. That's credit, not blame! It's such a milestone that I thought about suggesting we call it 3.0. +1 -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: 2.4.0 To Be Released Friday!
Le 31/05/2024 à 18:01, Richard Kimberly Heck a écrit : On 5/31/24 02:58, Jürgen Spitzmüller wrote: Am Donnerstag, dem 30.05.2024 um 21:59 -0400 schrieb Richard Kimberly Heck: I'm happy to keep doing it. If anyone would like to take over, though, I'd be happy to pass the baton. Excellent. You are doing an outstanding job. And congrats to the release. I think it is a real milestone on many respects. A lot of that is your doing. That's credit, not blame! It's such a milestone that I thought about suggesting we call it 3.0. +1 -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: A bug with comments within equations?
Le 27/05/2024 à 13:18, fcana...@gmail.com a écrit :
\documentclass{article}
\begin{document}
\[
x = y.
% u= v.
\]
\end{document}
It's actually worse than not showing correctly in the work area. Consider:
\[
x = y.
% u= v.
u= v.
\]
Daniel
Indeed. It can be observed not only when importing but also when pasting LaTeX
from another source into LyX.
The LyX rendering is not correct, but the file is right :
\begin_inset Formula
\[
x=y.%u=v.
u=v.
\]
\end_inset
and thus, the pdf output is correct.
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: 2.4.0 Tarballs
Le 26/05/2024 à 04:46, Richard Kimberly Heck a écrit : Here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/ Let's have a day or two of testing. Assuming all goes well, we can build binaries early next week, and release at the end of the week. Builds and runs fine on Debian stable. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New 2.3.8 Tarballs
Le 10/05/2024 à 10:51, Pavel Sanda a écrit : On Fri, May 10, 2024 at 10:38:01AM +0200, JP wrote: Sure, I will do it ASAP. Thanks. You should be able to commit any new files into wiki-uploads.git repository. Just create new directory in LyX/Manuals Completed, I added the Japanese manuals and left the Spanish ones as they are, users will see when opening them that they are still 2.3.X manuals. And the page reads "Released with 2.4.0", not "2.4.0 manuals". -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: TESTING Tarballs for 2.4.0
Le 13/05/2024 à 23:48, Richard Kimberly Heck a écrit : Hi, all, Tarballs for 2.4.0 are here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/ Please test. Please let me know if I forgot to do or include anything. Compiles and works fine on Debian stable. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New 2.3.8 Tarballs
Le 10/05/2024 à 10:51, Pavel Sanda a écrit : On Fri, May 10, 2024 at 10:38:01AM +0200, JP wrote: Sure, I will do it ASAP. Thanks. You should be able to commit any new files into wiki-uploads.git repository. Just create new directory in LyX/Manuals So I cloned locally wiki-uploads and committed the manuals in a 2.4 directory. Two problems: - I do not see directory 2.4 there https://git.lyx.org/gitweb/?p=wiki-uploads.git;a=tree;f=LyX/Manuals;h=ff50f62b09e435ac1083bf149f4379245af74c02;hb=4fa520e50b8a16ac7eccfe0d8517399ffcaa467a but I see it perfectly from the wiki itself: https://wiki.lyx.org/uploads/LyX/Manuals/ - I updated the wiki password a month ago, but the new password does not seem to work properly. Can you remind it to me? -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New 2.3.8 Tarballs
Le 09/05/2024 à 18:40, Richard Kimberly Heck a écrit : Updated tarballs here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ Sorry to those of you who already built the binaries. We'll have to rebuild. The utf8 errors are gone, only the cprotect fatal error in the note if 6.6.1 remains, but it can't be easily solved AFAIU. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Final 2.3.8 Tarballs
Le 07/05/2024 à 09:41, Pavel Sanda a écrit :
On Mon, May 06, 2024 at 09:49:07PM -0400, Richard Kimberly Heck wrote:
PS The only difference from the previous tarballs is removal of an old
remark about Python on OSX from ANNOUNCE.
Riki, please double check on the error spotted by Jean-Pierre before releasing.
I am too busy this week, to look deeper.
In fact, there are two different issues when importing 2.4.x UserGuide in 2.3.8:
- a set of unavailable Unicode characters (CJK brackets and guillemets, codes
U+300{ABCDEF}), section 3.9.4.2);
- an error in url https://en.wikipedia.org/wiki/ASCII#Character_set, note3 in
section 6.6.1: the # symbol triggers an hyperref error
! Illegal parameter number in definition of \Hy@tempa.
The latter is more boring, as it stops compilation.
The UserGuide compiles fine both with lyx-2.4.0~devel and lyx-2.3.8.
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: 2.3.8 Tarballs
Le 02/05/2024 à 22:47, Richard Kimberly Heck a écrit :
Here:
http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/
Please check that they build and run properly, especially export to and from
2.4.x.
When we've verified all is well, I'll give the signal to build binaries for
real.
On Debian stable:
Configuration
Host type: x86_64-pc-linux-gnu
Special build flags: build=release std-regex use-hunspell use-enchant
Bundled libraries:boost hunspell
C++ Compiler:g++ (12.2.0)
C++ Compiler flags: -fPIC -O2 -std=c++14
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.8
I still get warnings about unary_function:
BranchList.cpp:30:38: warning: ‘template struct
std::unary_function’ is deprecated [-Wdeprecated-declarations]
30 | class BranchNamesEqual : public std::unary_function
| ^~
In file included from /usr/include/c++/12/string:48,
from ./support/strfwd.h:42,
from support/docstring.h:16,
from BranchList.h:17,
from BranchList.cpp:14:
/usr/include/c++/12/bits/stl_function.h:117:12: note: declared here
117 | struct unary_function
|^~
Format.cpp:62:33: warning: ‘template struct
std::unary_function’ is deprecated [-Wdeprecated-declarations]
62 | class FormatNamesEqual : public unary_function {
| ^~
In file included from /usr/include/c++/12/functional:49,
from Format.cpp:12:
/usr/include/c++/12/bits/stl_function.h:117:12: note: declared here
117 | struct unary_function
|^~
Format.cpp:76:38: warning: ‘template struct
std::unary_function’ is deprecated [-Wdeprecated-declarations]
76 | class FormatExtensionsEqual : public unary_function {
| ^~
/usr/include/c++/12/bits/stl_function.h:117:12: note: declared here
117 | struct unary_function
|^~
Format.cpp:90:32: warning: ‘template struct
std::unary_function’ is deprecated [-Wdeprecated-declarations]
90 | class FormatMimeEqual : public unary_function {
|^~
/usr/include/c++/12/bits/stl_function.h:117:12: note: declared here
117 | struct unary_function
|^~
IndicesList.cpp:30:37: warning: ‘template struct
std::unary_function’ is deprecated [-Wdeprecated-declarations]
30 | class IndexNamesEqual : public std::unary_function
| ^~
In file included from /usr/include/c++/12/string:48,
from ./support/strfwd.h:42,
from support/docstring.h:16,
from IndicesList.h:17,
from IndicesList.cpp:13:
/usr/include/c++/12/bits/stl_function.h:117:12: note: declared here
117 | struct unary_function
|^~
IndicesList.cpp:46:38: warning: ‘template struct
std::unary_function’ is deprecated [-Wdeprecated-declarations]
46 | class IndexHasShortcut : public std::unary_function
| ^~
/usr/include/c++/12/bits/stl_function.h:117:12: note: declared here
117 | struct unary_function
|^~
But compilation succeeds.
Next step, open the 2.4.x French UserGuide with 2.3.8. There compilation fails
on missing Unicode characters :
! LaTeX Error: Unicode character 「 (U+300C)
not set up for use with LaTeX.
and the following characters 「 」 『 』 《 》in section 3.9.4.2.
Finally compilation stops with this :
Runaway argument?
{\printnomenclature {}\printindex \end {document}
! File ended while scanning use of \@settodim.
\par
<*> UserGuide.tex
I suspect you have forgotten a `}', causing me
to read past where you wanted me to stop.
I'll try to recover; but if the error is serious,
you'd better type `E' or `X' now and fix your file.
! Emergency stop.
Same with English UserGuide. This seems local to the file, right?
lyx-2.4.0~devel opens and compiles the 2.3.8 French UserGuide flawlessly.
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Utilisation de Bookmark sous Lyx (Latex) a l'image de word en lien avec BD ou tableur
Le 26/04/2024 à 11:03, Eddy Modave a écrit : Bonjour Scott, Les signets ne correspond pas à ma demande, si je peux être plus claire ce serait une fonction "Publipostage" exemple d'une lettre type avec les informations d'adresse (Nom, Prenom etc...) Les deux variables "NOM" & "Prenom" seraient issues d'une DB ou d'un fichier excel ! J'espère avoir été plus précis dans ma demande :) La classe LaTeX lettre.cls fait ça. Elle est accessible depuis LyX via Fichier>Nouveau avec modèle>Lettre en français (lettre) ( c'est moi qui ai fait les dernières modifications du format lettre.layout de Alain Castera). On peut enchaîner plusieurs lettres dans un même fichier LyX grâce au style « Fin de lettre » mais je n'ai jamais testé si la mécanisme de publipostage de la classe fonctionne avec LyX. Vous pouvez essayer après avoir lu la doc de lettre.cls :-) -- Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
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
Additional.lyx: subsections 10.8, 10.9 and 10.10
Dear doc maintainers, While updating the translation of the French Additional.lyx manual, I saw that in the original manual these three subsections, which were previously in a section entitled "Lyx Features needing Extra Software", appear now in section "The lyx Server". This mistake was introduced with commit 7b447915c2464effea8bae1c0701745fbc30ea5f I restored chapter 11 as before. -- Jean-Pierre -- lyx-docs mailing list lyx-docs@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-docs
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: Traduction de acknowledgment
Le 31/01/2023 à 17:26, Jean-Pierre Chrétien a écrit : Bonjour Suite à une discussion au sujet de l'orthographe de ce mot en anglais britannique et en anglais américain, un développeur a attiré l'attention sur la polysémie de ce mot en LyX : il désigne soit les remerciements traditionnels dans un livre, un article ou un mémoire, soit un type de théorème. Dans ce dernier cas, « Remerciement » n'a aucun sens, j'ai remplacé par « Constatation ». Qu'en pensez-vous ? Une autre suggestion ? Ma question est devenue sans objet, le type de théorème Acknowledgment avait été ajouté par erreur. Il a été supprimé de LyX, et la polysémie a donc disparu. -- Merci pour vos contributions Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
Re: fr/Tutorial.lyx : LyX et la typographie française
Le 09/02/2023 à 15:28, Jean-Marc Lasgouttes a écrit : Bonjour, Bonjour, Je suis tombé hier sur la section 5.4 du manuel d'apprentissage, et il me semble qu'elle pourrait être toilettée. - les distributions babel récentes n'utilisent plus frenchb.ldf mais french.ldf, Oui, frenchb.ldf renvoie à french.ldf avec un message d'avertisement. ainsi que \frenchsetup (depuis la version 3.3b de 2017) ; je ne suis pas sûr que l'utilisation de \AtBeginDocument soit encore nécessaire Je pense que tu as raison, il n'y a aucune référence à cette commande dans frenchb.doc - on peut indiquer l'URL http://daniel.flipo.free.fr/babel-french/ pour le site Non, Daniel lui-même recommande de se référer à CTAN, via par exemple %texdoc frenchb - à propos de œ, je pense qu'on peut simplifier ; à priori la référence à la page wikipedia suffit, non ? Le note de bas de page me para bine, et l'exemple programmation d'un raccourci clavier est inutile, mais c'est un exemple de programmation de raccourci clavier :-) - le style de guillemets est choisi automatiquement avec la langue J'ai ajouté cette information. En outre, je me suis rendu compte que Français (Canadien) était remplacé par Français (Acadien), j'ai modifié aussi le fichier fr.po. -- Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
Re: Traduction de acknowledgment
Le 01/02/2023 à 06:18, Béryl a écrit : Le 31/01/2023 à 17:26, Jean-Pierre Chrétien a écrit : Bonjour Suite à une discussion au sujet de l'orthographe de ce mot en anglais britannique et en anglais américain, un développeur a attiré l'attention sur la polysémie de ce mot en LyX : il désigne soit les remerciements traditionnels dans un livre, un article ou un mémoire, soit un type de théorème. Dans ce dernier cas, « Remerciement » n'a aucun sens, j'ai remplacé par « Constatation ». Qu'en pensez-vous ? Une autre suggestion ? Bonjour Jean-Pierre, Je ne suis pas compétent pour juger d'un terme anglais. DeepL me renvoie : remerciement, reconnaissance ou accusé de réception. Linguee rajoute dans des cas plus rares : acquittement, quittance. Je ne retrouve "constatation" que dans un cas : The despair provoked by this acknowledgment should give us creativity and courage to challenge the spirit of competition... Traduit par : Le désespoir que nous inspire cette constatation devrait nous donner la créativité et le courage de remettre en question... Oui, c'est cet exemple qui m'a poussé à retenir Constatation. -- Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
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
Traduction de acknowledgment
Bonjour Suite à une discussion au sujet de l'orthographe de ce mot en anglais britannique et en anglais américain, un développeur a attiré l'attention sur la polysémie de ce mot en LyX : il désigne soit les remerciements traditionnels dans un livre, un article ou un mémoire, soit un type de théorème. Dans ce dernier cas, « Remerciement » n'a aucun sens, j'ai remplacé par « Constatation ». Qu'en pensez-vous ? Une autre suggestion ? -- Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
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
Re: Initialisation des numéros de notes en bas de page.
Le 28/01/2023 à 08:56, Béryl a écrit :
Amis lyxiens, bonjour !
Mon bouquin écrit sous Lyx contient plusieurs chapitres à la numérotation
automatique (déclarés "Chapitre", donc), sauf l'épilogue que je n'ai pas voulu
numéroter donc déclaré "Chapitre*".
Les numéros de notes en bas de pages sont initialisés automatiquement entre
chaque chapitre numérotés, mais pas en passant sur un "Chapitre*".
D'où ma question : existe-t-il une astuce (ERT ou autre) pour initialiser le
numéro des notes en bas de page ?
Un \setcounter{footnote} en ERT au bon endroit ?
--
Jean-Pierre
--
lyx-fr mailing list
lyx-fr@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-fr
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: Graphique ou Image ?
Le 09/10/2022 à 16:57, Jean-Marc Lasgouttes a écrit : Bonjour, J’ai récemment lancé ma femme sur LyX, et à un moment elle m’a dit « je ne trouve pas comment insérer une image ». En effet, il faut faire Insérer>Graphique. C’est une traduction assez littérale de la version en anglaise, mais il est vrai qu’en français, « graphique » a une autre sens. Jean-Pierre, est qu’il y aurait beaucoup de boulot à changer Graphique en Image ? J’imagine que c’est dans les menus, les dialogues et la documentation. Finalement j'ai fait un compromis en mettant un avertissement dans la doc: Avertissement: dans le document, on utilise « graphique » en tant que raccourci de « objet graphique »: graphique, diagramme, image, schéma, etc. et en mettant graphique/image dans l'interface. -- Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
Re: Graphique ou Image ?
Le 10/10/2022 à 18:05, Béryl a écrit : Le 10/10/2022 à 17:45, Jean-Pierre Chrétien a écrit : « fer en haut » a été remplacé par « calé en haut » depuis lyx-2.3 (peut-être dans une version mineure, je me souviens plus). Idem pour « fer à gauche » et « fer à droite ». LyX ne peut plus rouiller :-) Quelle version utilisez-vous ? J'utilise la 2.3.6.1 compilée par mes soins sur une Manjaro KDE et une Kubuntu. Et je vois toujours "Fer en haut" ou "Fer à gauche" pour les passages à la ligne ou les paragraphes. J'ai du éliminer les fers en prévision de la dernière version mineure, donc sur 2.3.7dev, la version courante de 2.3 sur git. La suppression de « fer » ne doit effectivement apparaître qui si on travaille sur cette version. Voir la discussion sur lyx-fr ici : https://www.mail-archive.com/lyx-fr@lists.lyx.org/msg02665.html et suivants. -- Jean-Pierre -- Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
Re: Graphique ou Image ?
Le 09/10/2022 à 19:30, Béryl a écrit :
Le 09/10/2022 à 16:57, Jean-Marc Lasgouttes a écrit :
Bonjour,
J’ai récemment lancé ma femme sur LyX, et à un moment elle m’a dit « je ne
trouve pas comment insérer une image ».
En effet, il faut faire Insérer>Graphique. C’est une traduction assez
littérale de la version en anglaise, mais il est vrai qu’en français,
« graphique » a une autre sens.
Jean-Pierre, est qu’il y aurait beaucoup de boulot à changer Graphique en
Image ? J’imagine que c’est dans les menus, les dialogues et la documentation.
Qu’en pensez-vous ?
Y a-t-il d’autres mots qui vous ont paru bizarres ?
JMarc
Bonjour,
Je n'avais pas vraiment fait attention, mais c'est vrai qu'en se mettant à la
place de quelqu'un venant de LibreOffice et autre cela peut sembler bizarre, en
effet.
Je n'ai jamais fouillé le code de Lyx (sauf quand j'avais des soucis de
compilation par le passé) et je ne sais pas comment son gérées les traductions.
Si ce sont de simple fichiers, n'y a-t-il pas moyen de le changer localement et
re-compiler ?
La traduction (de l'interface, pas de la doc) utilise un utilitaire dénommé
gettext : tout ce qui est surchargé par _() dans le code -- _('Texte à
traduire') par exemple -- est collecté dans un fichier qu'il suffit ensuite
d'utiliser pour engendrer les traductions dans les différentes langues. C'est
dans ce fichier qu'il y a 33 occurrences de « graphique » en français.
Sinon, comme autre bizarrerie, je n'ai jamais compris la différence entre "Saut
de page (justifié)" et "Saut de page (fer en haut)"...
« fer en haut » a été remplacé par « calé en haut » depuis lyx-2.3 (peut-être
dans une version mineure, je me souviens plus). Idem pour « fer à gauche » et «
fer à droite ». LyX ne peut plus rouiller :-)
Quelle version utilisez-vous ?
--
Jean-Pierre
--
Jean-Pierre
--
lyx-fr mailing list
lyx-fr@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-fr
Re: Graphique ou Image ?
Le 09/10/2022 à 20:10, Jean-Marc Lasgouttes a écrit :
Le 09/10/2022 à 18:16, Jean-Pierre Chrétien a écrit :
Jean-Pierre, est qu’il y aurait beaucoup de boulot à changer Graphique en
Image ? J’imagine que c’est dans les menus, les dialogues et la documentation.
Il y a 228 occurrences de ' graphique' dans le cade de master (l'espace évite
bibliographique et typographique).
En faisant
git grep -i '\<&*g&*r&*a&*p&*h&*i&*q&*u&*e'
ou plus simplement
git grep -i '\
find master -type f -exec grep -i ' graphique' {} \; |wc -l
En regardant de plus près les resultat non résumé en nombre de lignes, je vois
que ça ratisse large, il y a des ligne comptées deux fois.
Plus précisément :
$ find master/lib/doc/fr/ -type f -exec grep -i ' graphique' {} \; |wc
=> 113 occurrences dans le documentation francophone.
$ grep ' graphique' master/po/fr.po |wc -l
=> 33 occurrences dans fr.po
113 + 33 = 146, on n'est pas loin :-)
--
Jean-Pierre
--
lyx-fr mailing list
lyx-fr@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-fr
Re: Graphique ou Image ?
Le 09/10/2022 à 16:57, Jean-Marc Lasgouttes a écrit : Bonjour, J’ai récemment lancé ma femme sur LyX, et à un moment elle m’a dit « je ne trouve pas comment insérer une image ». En effet, il faut faire Insérer>Graphique. C’est une traduction assez littérale de la version en anglaise, mais il est vrai qu’en français, « graphique » a une autre sens. Jean-Pierre, est qu’il y aurait beaucoup de boulot à changer Graphique en Image ? J’imagine que c’est dans les menus, les dialogues et la documentation. Il y a 228 occurrences de ' graphique' dans le cade de master (l'espace évite bibliographique et typographique). Ceci dit, image est ambigu aussi pour ceux qui affichent des courbes ou des schémas à mon avis. Et le problème du genre complique la substitution. Est-ce que modifier le tootip et le menu d'insertion en Insérer>Image/graphique et une explication dans le Manuel d'apprentissage sur la sémantique de graphique en LyX ne suffirait pas ? Y a-t-il d’autres mots qui vous ont paru bizarres ? Rien qui me vienne à l'esprit. -- Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
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: pour tester le pouriellisage
Le 17/03/2022 à 16:39, Jean-Marc Lasgouttes a écrit : Le 17/03/2022 à 15:56, pierre delobel a écrit : Bonjour a tous je ne fais pas une réponse pour changer les entetes et tester le nouveau filtre. Je vous souhaite à tous une tres bonne journée bon courage aux trop peu de développeurs pour cette version 2.4 ; serait elle maudite ? Bonjour, Maudite, je ne sais pas. Ce n'est pas que le développement tourne mal, c'est plutôt qu'on manque de bras. Bonjour Jean-Marc Les docs de la 2.4 sont à peu près à jour, et l'interface aussi. Comment puis-je aider ? Si j'ai bien compris, c'est José qui a la clé du problème Python. Et pour ImageMagick, que faut-il faire exactement ? Une beta est sortie en mai 2021, puis plus rien, c'est bizarre quand même. -- Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
Re: Re : Re: crochets peu lisibles
Le 21/02/2022 à 13:46, luciecharr...@sfr.fr a écrit : Merci pour votre réponse. Oui je parle bien du pdf. Dans Lyx les crochets sont bien lisibles. C’est dans les formules de maths écrites dans l’insert obtenu avec Ctrl+M ou dans le texte « normal » avec police par défaut suivant les réglages indiqués . Dans le texte normal en sélectionnant chasse fixe les crochets sont lisibles. Ci-joint le résultat pdf avec Latin Modern, New Century Schoolbook et Latin Modern + les crochets en chasse fixe. Ça vaut vraiment le coup de marquer tous les crochets en chasse fixe ? C'est beaucoup de travail non ? -- Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
Re: crochets peu lisibles
Le 21/02/2022 à 09:01, luciecharr...@sfr.fr a écrit : Bonjour, Dans mes documents, les crochets pour les intervalles [ et ] sont peu lisibles, les barres horizontales sont petites. La classe du document est Book (classe standard). Dans les paramètres pour la police, j'ai : Famille implicite : implicite Taille de base : implicite Encodage de police LaTeX : implicite Romain : Latin modern roman Sans empattement : Latin modern sans Chasse fixe : Latin modern typewriter Maths : automatique Y-a-t-il moyen d'avoir des crochets avec des barres horizontales plus longues et ainsi mieux visibles ? Bonjour Vous parles bien de l'apparence du pdf, pas de la fenêtre LyX ? Et dans quelle famille ? Romain, sans empattement, chasse fixe ? Si c'est en romain, New Century Schoolbook me semble afficher des crochets plus lisibles, mais il faut que la police en général vous plaise. -- Jean-Pierre -- lyx-fr mailing list lyx-fr@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-fr
Re: [LyX/master] de.po
Le 17/02/2022 à 08:21, Juergen Spitzmueller a écrit : commit a179395bd9600dd9d632a2662027c031a8318502 Author: Juergen Spitzmueller Date: Thu Feb 17 08:53:52 2022 +0100 de.po [snip] -#: src/LaTeX.cpp:1096 +#: src/LaTeX.cpp:439 +msgid "" +"The index processor did not run successfully. Please check the output of " +"View > Messages!" Hello Jürgen, Should no this read View > Messages Pane ? -- Jean-Pierre -- lyx-cvs mailing list lyx-cvs@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-cvs
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
