Am Sonntag, dem 04.08.2024 um 20:58 +0100 schrieb Tomasz Kołodziejski:
> Fair point with semicolons. New patch attached.
Thanks, committed to master and stable.
> I didn't bother with the accelerators as I don't use them and I
> didn't quite have time to carefully consider which ones would make
>
Am Sonntag, dem 04.08.2024 um 12:33 -0400 schrieb Richard Kimberly
Heck:
> The obvious thing to do would to be to go back to displaying "Ref:
> LABEL", or whatever. But I'm wondering whether we can do better. The
> LABEL is going to be the same for every one of the cross-references,
> which are
Am Montag, dem 05.08.2024 um 09:44 -0400 schrieb Scott Kostyshak:
> The small change of behavior I noticed when comparing 2.3.x to 2.4.x
> is that in 2.3.x, the relevant outliner item is second to last; and
> in 2.4.x it is last.
>
> I am picky about a lot of things, but this isn't one of them. I
Am Montag, dem 05.08.2024 um 17:33 +0100 schrieb Tomasz Kołodziejski:
> Would you expect running make at top level to have built this as
> well?
No, I wouldn't. We only commit gmo files from time to time as they are
rather big.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://
Am Montag, dem 05.08.2024 um 18:14 -0400 schrieb Richard Kimberly Heck:
> I thought about this, but then realized that anything other than
>
> TYPE: LABEL
>
> which we used to have, will make it impossible to filter the way one
> would naturally want to do: on the label itself. So I've done
Am Dienstag, dem 06.08.2024 um 11:36 -0400 schrieb Richard Kimberly
Heck:
> Yes, I agree. But having 15 entries that look like "2.3" isn't any
> better. Prior to this change, we got a mix of "2.3" and "Ref: LABEL",
> but that's due to a bug which I'm about to fix.
I totally agree. I was just resp
Am Dienstag, dem 06.08.2024 um 18:51 + schrieb Richard Kimberly
Heck:
> Author: Richard Kimberly Heck
> Date: Tue Aug 6 14:50:29 2024 -0400
>
> Restore obvious shortcut
Note that this was changed due to a shortcut conflict which now is
probably back.
--
Jürgen
signature.asc
Descrip
Am Dienstag, dem 06.08.2024 um 21:01 +0200 schrieb Jürgen Spitzmüller:
> Note that this was changed due to a shortcut conflict which now is
> probably back.
Though not in this particular position, so that's OK. We now just have
two different accelerators for Greyedout depending on
Am Mittwoch, dem 07.08.2024 um 07:14 + schrieb Juergen
Spitzmueller:
> commit 1efdc11296b0acf98d1180e18c0daa3e9a79bfec
> Author: Juergen Spitzmueller
> Date: Wed Aug 7 09:11:35 2024 +0200
>
> lyx_pot.py: Fix regex for \Format
>
> Each token could be delimited by quotation marks
Am Mittwoch, dem 07.08.2024 um 11:36 -0400 schrieb Richard Kimberly
Heck:
> There's only three things on that sub-menu.
Yep, sorry. I was mixing it up with the other use of Greyedout (in the
context menu).
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/
Am Mittwoch, dem 07.08.2024 um 12:28 -0400 schrieb Richard Kimberly
Heck:
> You did change the context menu shortcut at c92d14e8c97. But I'm not
> seeing the (potential) conflict now.
No time to investigate now, but it has been there, and it was quite a
challenge to come to a situation where no m
Am Samstag, dem 10.08.2024 um 08:36 + schrieb Roland Schmitz:
> great to se "my oldest Ticket" getting closed 😁
Good to see you're still around.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Since some time (unfortunately not documented when), nomencl uses the
rather odd % escape character (instead of " due to its activation by
babel etc.), but we haven't adapted it fully yet.
The attached patch does that.
Master uses the right escape char with its new approach.
OK?
--
Jürgen
diff
Am Mittwoch, dem 14.08.2024 um 14:29 + schrieb Juergen
Spitzmueller:
> commit c993485782a1f47c6eafc9335c8905b3def7e083
> Author: Juergen Spitzmueller
> Date: Wed Aug 14 16:28:15 2024 +0200
>
> Disable valign widget in tabularx tables
>
> See https://marc.info/?l=lyx-users&m=172
Am Mittwoch, dem 14.08.2024 um 18:40 -0400 schrieb Scott Kostyshak:
> Below are tests that are failing due to recent commits. I'm on
> vacation so I'd rather not dig into these myself. If necessary, I can
> provide more information but not sure when.
I've resolved some and will run the tests mysel
Am Donnerstag, dem 15.08.2024 um 09:35 +0100 schrieb José Matos:
> This will only fail for cases where there are multiple opening and
> closing quotes.
> Is that our case?
My case was escaped quote as last content of the quoted string (e.g.,
"\"" which returned \ rather than \")
> BTW I usually p
Am Donnerstag, dem 15.08.2024 um 13:03 +0100 schrieb José Matos:
> Honestly here the code, in this context, makes more sense like this:
>
> if val.startswith('"') and val.endswith('"'):
> val = val[1:-1]
>
> So it only makes sense to remove both at once.
Yes, I agree.
> Again on practice
Am Freitag, dem 16.08.2024 um 10:00 +0100 schrieb José Matos:
> Thank you for implementing these changes in the code. :-)
I have to thank for the instruction!
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Donnerstag, dem 15.08.2024 um 09:28 +0200 schrieb Jürgen
Spitzmüller:
> I've resolved some and will run the tests myself to see what's left.
I think I've caught all. I still get test failures, but this seems due
to other issues or missing prereqs.
BTW the tests fail with
Am Samstag, dem 17.08.2024 um 19:00 +0200 schrieb Kornel Benko:
> From inside the build-dir call
> # ./prefTest.pl test
>
> This should do the trick. It modifies some converters in local
> Testing/.lyx/preferences.
Thanks, it does. This should probably documented in Development.lyx
(where I
Am Samstag, dem 17.08.2024 um 19:40 -0400 schrieb Richard Kimberly
Heck:
> No, not yet, but soon. Pleases let me know if there are any commits
> you'd like to get into 2.4.x that might change strings before we do
> freeze.
This is important enough for 2.4.2, and it all works well for me. Just
wai
Am Sonntag, dem 18.08.2024 um 09:22 +0200 schrieb Jürgen Spitzmüller:
> This is important enough for 2.4.2, and it all works well for me.
> Just
> waiting for Thibaut's and your feedback:
>
> https://www.lyx.org/trac/ticket/12372
And of course the patch with the string ch
Am Samstag, dem 17.08.2024 um 17:55 -0400 schrieb Scott Kostyshak:
> DEFAULTOUTPUT_export/export/latex/lyxbugs-resolved/11584-iconv-error-
> nomenclature_pdf2 (Failed)
This one's fixed. Strangely, it isn't listed among my failed tests, but
I could reproduce manually.
--
Jürgen
signature.asc
De
Am Samstag, dem 17.08.2024 um 17:55 -0400 schrieb Scott Kostyshak:
> export/doc/Customization_docbook5 (Failed)
This one I cannot reproduce. What's the failure?
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http:
Am Sonntag, dem 18.08.2024 um 11:42 -0400 schrieb Richard Kimberly
Heck:
> If Thibaut approves, so do I. He knows more about this now than I do.
OK, I'll put it to master.
Tell me if you're fine with backporting.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/
Am Sonntag, dem 18.08.2024 um 11:55 -0400 schrieb Richard Kimberly
Heck:
> Yes.
Thanks, all done.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Montag, dem 19.08.2024 um 02:57 -0400 schrieb Scott Kostyshak:
> -- _err = 1, jingout = /home/scott/lyxbuilds/master-
> master/CMakeBuild/autotests/out-
> home/AbC_ax5fq9/doc/Customization.xml:2133:20: error: element "code"
> not allowed here;
Thibaut should have a look at this. I don't know en
Am Dienstag, dem 20.08.2024 um 12:21 +0200 schrieb Kornel Benko:
> The offending line 2127:43 contains
> ...
> [0, 1] If this is
> set to
> 1, a copy of the co-text (either selected text or the
> word preceding the
> cursor) is inserted as content on inset creation.
> ...
> with error
> error: ele
Am Donnerstag, dem 22.08.2024 um 12:08 -0400 schrieb Scott Kostyshak:
> Jürgen does this look OK? Maybe after 0ca600b9 it is expected?
Yes, thanks. I wanted to run the update but then I forgot. Sorry.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel ma
Am Samstag, dem 24.08.2024 um 09:35 +0800 schrieb Jiaxu Zi:
> Updated Simplified Chinese Translations.
Alas, the patch doesn't apply cleanly to stable.
Could you send the whole po file?
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Kornel Benko schrieb am 28.08.2024 12:44 (GMT +02:00):
> Am Tue, 27 Aug 2024 22:21:35 +0200
> schrieb Scott Kostyshak :
>
>> The following tests are failing for me on current master. Note that I haven't
>> updated
>> my TeX Live distribution for a couple of months. And I saw a couple of notes
>> m
Am Mittwoch, dem 04.09.2024 um 15:45 +1200 schrieb Igor:
> Not sure if it's a bug or a new feature, but the whitespaces in my
> labels are now turned into =20
feature.
[...]
> Why?
Because refstyle does not support spaces in references.
> How to disable/enable this?
You can't without ch
Am Samstag, dem 07.09.2024 um 13:22 +0200 schrieb Jean-Marc Lasgouttes:
> I have been resisting to making these changes because someone may
> change the code and use the variable afterwards. But I may be wrong
> after all.
I am not sure at all. I did some research how useful this sort of
advise is
Am Sonntag, dem 08.09.2024 um 02:26 +1200 schrieb Igor:
> Seems like a refstyle's bug. The workaround is to enclose the label
> name within additional {} when referencing and leave the original
> label as the user intended.
>
> For example. Firstly, we'd need to use something like \secref to
> act
Am Samstag, dem 07.09.2024 um 23:34 +0200 schrieb Scott Kostyshak:
> git bisect leads to:
>
> commit b625138be66ec5f76c3b9418a6a33c26bb313902
> Author: Juergen Spitzmueller
> Date: Sun Aug 25 13:22:07 2024 +0200
>
> Add support for the following languages
Sure, but the bug (which is not
Am Sonntag, dem 08.09.2024 um 11:16 +0200 schrieb Jürgen Spitzmüller:
> Sure, but the bug (which is not in LyX) is just exposed by that.
(the reason being that we didn't use polyglossia for Japanese and
Chinese before that commit with non-TeX fonts, but babel)
--
Jürgen
signa
Am Sonntag, dem 08.09.2024 um 22:09 +1200 schrieb Igor:
> I guess I've never run into this whitespace refstyle bug, because I
> redefined all my formatted references, for example
> \renewcommand*{\thmref}[1]{\hyperref[thm:#1]{#1}}. I'm not sure if I
> even need refstyle ... but it's loaded automati
Am Sonntag, dem 08.09.2024 um 02:26 +1200 schrieb Igor:
> \secref{{A B}} -- works!
Actually, considering all eventualities, this might be the best
solution, as the problem only concerns refstyle's formatted ref
commands. All other solutions that I could think of add unnecessary
complication.
Like
Am Sonntag, dem 08.09.2024 um 15:45 +0200 schrieb Jürgen Spitzmüller:
> Am Sonntag, dem 08.09.2024 um 02:26 +1200 schrieb Igor:
> > \secref{{A B}} -- works!
>
> Actually, considering all eventualities, this might be the best
> solution, as the problem only concerns refsty
Am Sonntag, dem 08.09.2024 um 12:18 -0400 schrieb Richard Kimberly
Heck:
> That was my thought, as well. Simple and effective.
Good, I committed to master. Note that if you cherry-pick, you both
need both bfd855747ab (the indentation fix) and 0beb790a6a1945 (the
actual bug fix), as the latter won'
Am Sonntag, dem 08.09.2024 um 19:18 +0200 schrieb Jean-Marc Lasgouttes:
> Does tex2lyx need some adaptation to avoid labels on
> roundtrips?
Yes, you're right.
Done at f725abea051b5
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-de
Am Montag, dem 09.09.2024 um 21:20 +1200 schrieb Igor:
> -- refstyle gets loaded automatically when I choose Formatted
> reference through LyX GUI. Ironically I redefine most of the
> refstyle's formatted commands underneath :) I'm going to test to see
> how I can implement this with "Use refstyle"
Am Montag, dem 09.09.2024 um 16:31 +0200 schrieb Scott Kostyshak:
> Just out of curiosity (no I don't want to receive the scan results
> ;)),
> are most of these from Coverity adding new features that detect new
> things? Or were they there before, and you are whittling down the
> list little by li
Am Sonntag, dem 08.09.2024 um 12:08 +0200 schrieb Scott Kostyshak:
> > (the reason being that we didn't use polyglossia for Japanese and
> > Chinese before that commit with non-TeX fonts, but babel)
>
> Sounds good! Thanks for confirming.
You might want to rerun the test with an up-to date polygl
Am Montag, dem 09.09.2024 um 17:55 +0200 schrieb Jean-Marc Lasgouttes:
> The good thing is that we caught a few real bugs. It is not always
> coverity being annoying.
No, it is actually really helpful.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/lis
Am Montag, dem 09.09.2024 um 17:54 +0200 schrieb Jean-Marc Lasgouttes:
> I am even tempted to use std::move() here to
> point out that this is the standard library method and not just a
> function of our own.
Thankfully, Scott has done that for my commit at 0a7585403832c
--
Jürgen
--
lyx-dev
Am Montag, dem 09.09.2024 um 18:43 +0200 schrieb Kornel Benko:
> LaTeX.cpp (867): Log line:
> LaTeX.cpp (867): Log line: ! LaTeX Error: The key
> 'polyglossia/gloss/english/__current_options_tl' is
> LaTeX.cpp (1156): line: 3954
> Desc: LaTeX Error: The key
> 'polyglossia/gloss/english/__current_op
Am Montag, dem 09.09.2024 um 18:37 +0200 schrieb Jürgen Spitzmüller:
> Am Montag, dem 09.09.2024 um 18:43 +0200 schrieb Kornel Benko:
> > LaTeX.cpp (867): Log line:
> > LaTeX.cpp (867): Log line: ! LaTeX Error: The key
> > 'polyglossia/gloss/english/__current_options_
Am Dienstag, dem 10.09.2024 um 15:21 +0200 schrieb Jean-Marc
Lasgouttes:
> I agree with that. However, I have not found the toggle that tells
> Coverity to skip this proposal. This is most of our reports.
In any case, I will revert the respective commit.
--
Jürgen
--
lyx-devel mailing list
lyx
Am Mittwoch, dem 11.09.2024 um 18:46 +0300 schrieb Udicoudco:
> > export/doc/es/Tutorial_dvi3_systemF
> > export/doc/es/Tutorial_pdf4_systemF
> > export/doc/es/Tutorial_pdf5_systemF
>
> These ones are compiling fine for me after
> a fix from Jürgen at 498135ef383a6e75.
> Are you testing with the m
Am Mittwoch, dem 11.09.2024 um 18:33 +0200 schrieb Kornel Benko:
> > Oh, the Spanish docs are not using
> > polyglossia... Is there a sane error
> > message?
> >
>
> ?? They pass now here. This is without the polyglossia in git, but
> with updated TL24.
Maybe also due to my babel options fix.
-
Am Freitag, dem 13.09.2024 um 11:14 +0200 schrieb Jean-Marc Lasgouttes:
> Jürgen, could you double-check this?
Makes sense to me.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Freitag, dem 13.09.2024 um 17:54 +0200 schrieb Jean-Marc Lasgouttes:
> Jürgen, could you please have a look and tell me why we should not do
> that? It is too simple, I fear I am missing something.
I do not understand if and why that works, but if you say so, I believe
you.
--
Jürgen
--
lyx-
Am Mittwoch, dem 11.09.2024 um 17:15 +0200 schrieb Kornel Benko:
> > UNRELIABLE.WRONG_OUTPUT_export/export/latex/CJK/zh_CN-
> > toc_pdf4_systemF
> > UNRELIABLE.WRONG_OUTPUT_export/export/latex/CJK/zh_CN-
> > toc_pdf5_systemF
Should be fixed. Basically appropriate non-TeX fonts needed to be set
(as
Am Samstag, dem 14.09.2024 um 13:27 +0200 schrieb Jürgen Spitzmüller:
> These, for instance. Here, we need to agree on an appropriate
> typewriter font that supports CJK.
Source Han Code seems to work well:
https://github.com/adobe-fonts/source-han-code-jp
--
Jürgen
signature.asc
Descr
Am Samstag, dem 14.09.2024 um 19:34 +0200 schrieb Scott Kostyshak:
> After cloning the repository, it is 262M. Probably I just need a few
> files from there? If so, can you tell me which files?
Just this:
https://github.com/adobe-fonts/source-han-code-jp/releases/download/2.012R/SourceHanCodeJP.tt
Am Sonntag, dem 15.09.2024 um 10:30 +0200 schrieb Scott Kostyshak:
> Thanks, that's easy enough. And where do I put that file?
I just opened it with KFontView and hit the install button. That
installed it to ~/.fonts/s/SourceHanCodeJP.ttc
It seems that XeTeX does have problems with this sort of f
Am Samstag, dem 14.09.2024 um 23:59 +0200 schrieb Scott Kostyshak:
> UNRELIABLE.WRONG_OUTPUT_export/export/latex/CJK/zh_CN-
> toc_pdf4_systemF (Failed)
> UNRELIABLE.WRONG_OUTPUT_export/export/latex/CJK/zh_CN-
> toc_pdf5_systemF (Failed)
> export/export/latex/languages/ja-listings-uncodable-
> error
Am Sonntag, dem 15.09.2024 um 14:01 +0200 schrieb Jürgen Spitzmüller:
> > DEFAULTOUTPUT_export/export/latex/languages/supported-
> > languages_polyglossia-XeTeX_pdf4_systemF (Failed)
>
> Have to look into this ...
Fixed.
--
Jürgen
signature.asc
Description: This is a digita
Am Sonntag, dem 15.09.2024 um 15:46 +0200 schrieb Kornel Benko:
> At least these tests compiles fine if using
> Serif: Noto Serif CJK HK
> Sans: Noto Sans CJK HK
> Mono: Noto Sans CJK HK
Not quite the correct fonts. I have added the Noto fonts for Simplified
Chinese (i.e., SC) instead. And Mono
Am Sonntag, dem 15.09.2024 um 17:08 +0200 schrieb Kornel Benko:
> That's better. Attached the remaining tests here.
You don't have the Source Han Code JP font installed, right?
https://github.com/adobe-fonts/source-han-code-jp/releases/download/2.012R/SourceHanCodeJP.ttc
--
Jürgen
signature.a
Am Sonntag, dem 15.09.2024 um 17:15 +0200 schrieb Jürgen Spitzmüller:
> Am Sonntag, dem 15.09.2024 um 17:08 +0200 schrieb Kornel Benko:
> > That's better. Attached the remaining tests here.
>
> You don't have the Source Han Code JP font installed, right?
>
> https:
Am Samstag, dem 14.09.2024 um 20:07 +0200 schrieb Jean-Marc Lasgouttes:
> Back in history, the structure was not a map but a
> vecor. It is used to track things like "is there a line below
> this cell?". I am not sure why Juergen changed it to a map
To track whether the lines are trimmed (in boo
Am Sonntag, dem 15.09.2024 um 17:58 +0200 schrieb Kornel Benko:
> With the latest (649c5e9b) change there are only these 10 tests
> failing here.
> The following tests FAILED:
> 490 - DEFAULTOUTPUT_export/export/latex/languages/supported-
> languages_polyglossia-XeTeX_pdf4_systemF (Failed)
>
Am Sonntag, dem 15.09.2024 um 19:05 +0200 schrieb Scott Kostyshak:
> The following tests FAILED:
I need concrete error messages, as these tests pass for me.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://li
Am Sonntag, dem 15.09.2024 um 19:21 +0200 schrieb Kornel Benko:
> I have
> Font : IPAMincho Regular [IPA]
> Font : IPAPMincho Regular [IPA]
> Font : IPAX0208Mincho Regular [IPA]
> Font : IPAX0208PMincho Regular [IPA]
> Font : IPAex Mincho Regular [IPA]
> Font : IPAmj Mincho Regular [IPA]
>
> but n
Am Montag, dem 16.09.2024 um 11:53 +0200 schrieb Kornel Benko:
> I tried, but still failing.
Running out of ideas. The warnings are more or less harmless. Don't
know what your issue is.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-
Am Montag, dem 16.09.2024 um 12:50 +0200 schrieb Kornel Benko:
> Maybe the error output on terminal when using lyx can help. Looks
> like dvipdfm chokes.
Yes, I also have these invalid font errors sometimes. I solved some of
them by installing another version or format of the font. I think
"virtua
Am Sonntag, dem 15.09.2024 um 19:37 +0200 schrieb Scott Kostyshak:
> It is strange (to me) that this export succeeds (i.e., the inverted
> test fails), but the corresponding XeTeX export fails. The LuaTeX
> output looks fine to my eyes though.
The Japanese fonts do not cover some quotation marks.
Am Montag, dem 16.09.2024 um 12:20 +0200 schrieb Scott Kostyshak:
> Regarding this test,
>
> export/examples/es/Curricula_Vitae/Modern_CV_lyx23
>
> I reproduce manually with:
>
> lyx -e lyx23x Modern_CV.lyx && lyx -e lyx23x Modern_CV.23.lyx &&
> lyx -e default Modern_CV.23.23.lyx
>
> I get
Am Montag, dem 16.09.2024 um 16:42 +0200 schrieb Scott Kostyshak:
> Great! These tests are failing now though:
>
> export/doc/ja/Additional_lyx22 (Failed)
> export/doc/ja/Additional_lyx23 (Failed)
> export/doc/ja/Additional_dvi (Failed)
> UNRELIABLE.NONSTANDARD_export/doc/ja/Additional_pdf
Am Montag, dem 16.09.2024 um 18:04 +0200 schrieb Scott Kostyshak:
> To make sure I understand, now the following test fails for you
> (i.e., the export succeeds)?
>
> ctest -R 'INVERTED.TODO_export/doc/ja/UserGuide_pdf4_systemF'
This looks like a problem in the polyglossia XeTeX code of Chinese
Am Dienstag, dem 17.09.2024 um 08:01 +0200 schrieb Jürgen Spitzmüller:
> Am Montag, dem 16.09.2024 um 18:04 +0200 schrieb Scott Kostyshak:
> > To make sure I understand, now the following test fails for you
> > (i.e., the export succeeds)?
> >
> > ctest -R &
Am Dienstag, dem 17.09.2024 um 15:15 +0200 schrieb Kornel Benko:
> I see the following differences between the created between *.23.lyx
> and *.23.23.lyx
> files
> > % Added by lyx2lyx
> > %% This document must be processed with xelatex or
> lualatex!
> > \AtBeginDocument{%
>
Am Dienstag, dem 17.09.2024 um 14:14 + schrieb Juergen
Spitzmueller:
> commit 2e408d2fdccffddebcd05eb2c6ccf6e9607def61
> Author: Juergen Spitzmueller
> Date: Tue Sep 17 15:53:18 2024 +0200
>
> Do not output empty statement in lyx2lyx reversion
Candidate for stable
--
Jürgen
--
lyx-d
Am Dienstag, dem 17.09.2024 um 15:03 +0200 schrieb Pavel Sanda:
> - open some structured text (eg any manual)
> - set tree depth to some higher level (eg 2) by the slider in toc
> dialog
> - go inside any section, highlight the text and remove/replace it
> - the outliner tree depth gets reset to 0
Am Montag, dem 16.09.2024 um 14:33 +0200 schrieb Jürgen Spitzmüller:
> I have also fixed most of Math, but there is a
> remaining issue -- a NULL character (0x) somewhere which cannot
> be displayed by the Japanese system font, I cannot figure out where.
The construct that brea
hort (general) summary.
Index: src/frontends/qt4/GuiAlert.cpp
===
--- src/frontends/qt4/GuiAlert.cpp (Revision 29907)
+++ src/frontends/qt4/GuiAlert.cpp (Arbeitskopie)
@@ -4,6 +4,7 @@
* Licence details can be found in the file COPYING.
*
* \author John Levon
+ * \author Jürgen Spitzmüller
*
Enrico Forestieri wrote:
> When you launch SumatraPDF through the following script:
BTW could we include the respective scripts for win32, cygwin and unix to the
distribution? I take it that there is already a script for Mac.
Jürgen
José Matos wrote:
> > It drove me nuts a long time ago, so please!
> >
> > rh
>
> +\infty
OK. It's in.
Jürgen
Vincent van Ravesteijn wrote:
> There are only a few with a comma.
Exactly 3, if my query was correct. Zero now.
Jürgen
Jean-Marc Lasgouttes wrote:
> Next question: do we have a list of keywords somewhere?
We used to have one on bugzilla, but I guess it is lost.
> Currently I have
> keywords = crash,regression,patch,easyfix,fixedinbranch,fixedintrunk
ui, qtbug, fileformat, assertion, testcase, cosmetic, RFE (?),
Jürgen Spitzmüller wrote:
> > Dear lyx developers,
> > Attached is a "diff -u" patch fixing a small display bug in the AMS
> > article layout, where starred Section, Subsections, etc are not
> > displayed correctly. I fixed it by repeatin
Jean-Marc Lasgouttes wrote:
>Here is my new list. I killed copier and RFE.
>keywords = crash, regression, dataloss, patch, easyfix, fixedinbranch,
> fixedintrunk, ui, qtbug, fileformat, assertion, testcase, cosmetic,
> release_notes, perf, os=linux, os=windows, os=macosx
Nice work!
I found furthe
Jean-Marc Lasgouttes wrote:
> What is this good for? It looks to be related to import problems, but do
> we want to keep it? (we can keep it in old bugs as long as we do not
> edit them IMO)
The old description (which I found now on the server in bugzilla/) says:
'compat','Correct import of previ
Jean-Marc Lasgouttes wrote:
> > The old description (which I found now on the server in bugzilla/)
> > says:
>
> Where exactly?
/home/bugzilla/Bugzilla.sql
> > 'compat','Correct import of previous versions of LyX documents'
>
> OK, I will not add it then.
>
> > * 'leak','(Suspected) memory leak.'
Jean-Marc Lasgouttes wrote:
> On aussie, right?
ftp.devel.lyx.org. Is this aussie (I always forget that)?
> A more recent version seems to be:
>
> ./data/versioncache:@::legal_keywords =
> ('assertion','compat','cosmetic','crash','dataloss','easyfix','fileformat',
>'fixedinbranch','fixedintrunk',
Enrico Forestieri wrote:
>The attached shell script should work for any system except win32
>(I cannot test it on MacOSX, but I think that it should work).
>However, it would not be usable on win32 because the lyxpipe is
>not working there. So, there's no point in translating it to python.
I think
Jean-Marc Lasgouttes wrote:
> > I used that in the past to mark bugs that must be fixed before a release
> > (since "blocker" on bugzilla had a different meaning).
>
> So, do you want it? It is up to you.
Yes, please add it.
BTW. do you know how to add a new version (i.e., 1.6.3) to the version c
Russ Woodroofe wrote:
> I'm pretty sure that the comment "Chapter is not prepended" should
> be "Section is not prepended". That makes a lot more sense, as
> Section isn't prepended, and especially as it comes just before the
> definition of the Section environment.
>
> There was als
Enrico Forestieri wrote:
> > Shall I update the docs?
>
> Yes, please.
done (in branch).
> > BTW2 we should also mention synctex in the docs, since it is about to
> > supersede pdfsync (I don't know if any of the viewers already supports
> > ths, though).
>
> SumatraPDF has support for it. Howeve
Jürgen Spitzmüller wrote:
> > > Shall I update the docs?
> >
> > Yes, please.
>
> done (in branch).
I've done some further revisions, because I found the current description
rather technical and slightly unstructured. The revision is the attempt to
struc
Russ Woodroofe wrote:
> In any case, it looks closer to the output.
I committed it.
Jürgen
Jean-Marc Lasgouttes wrote:
> I added it.
Thanks (I also asked Lars in the meantime)
> Do you want to be trac_admin? There is no way to grant
> specifically
> the right to add versions.
Yes, why not.
Jürgen
Enrico Forestieri wrote:
> You did an excellent job, but there are some formatting glitches to
> be corrected. If you like, I could try to correct them.
Yes.
> BTW, you seem to have forgotten to accept the changes before
> committing.
This was intended, so others can more easily see what I've ch
Enrico Forestieri wrote:
> Fine, but until LyX cannot take advantage of the extended precision granted
> by synctex, using it or pdfsync is a matter of personal taste, IMHO.
> Unless you incur in the above problems, of course :)
Granted, but that's why we should document both and outline the pros
Georg Baum wrote:
> > So let's wait. If we put the patch in early in the 1.6.4 cycle, we have
> > at least the chance to test it.
>
> I put it in now.
OK, thanks. So external-boost people, please give it a try.
Jürgen
Enrico Forestieri wrote:
> Hmm... there's a risk of shipping the document in that state if you
> forgot to accept the changes. I find that ldiff does a good job in
> showing differences between two versions of the same document, if
> you are interested in what was changed.
I got the impression tha
Pavel Sanda wrote:
>thats the convetion for the manuals Uwe maintains. but it doesn't cover
>customization and additional features manual. for the rest it is kind of
> chaos now.
I thought Uwe is the principal documentation maintainer?
> secondly it does inform that trunk has not been updated (wh
Pavel Sanda wrote:
> > I thought Uwe is the principal documentation maintainer?
>
> http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg144789.html
Well, I completely missed that. Do we have maintainers for the other docs?
I really think we need a clear, coherent policy. I also think our trans
501 - 600 of 9259 matches
Mail list logo
