On Wed, Jun 12, 2024 at 6:40 PM Pavel Sanda <sa...@lyx.org> wrote: > > On Wed, Jun 12, 2024 at 01:11:23PM +0300, Udicoudco wrote: > > Does this matter? i.e. do we hold strongly > > backwards compatibility of the output of change track? > > Generally we do in between minor version. Here I am ambivalent. I think users > should feel confident between switching 2.4.x minor versions while their > output > remain the same. At the same time this fixes bug and it's early in the 2.4 > cycle. > > That's why I am asking how bad things can get with this change. > > Pavel > > PS: submitting revised manuscript with change tracking on was part of > revision process in the last journal I interacted with. Obviously > depending whether your last export was in different minor version of > lyx might backfire, esp. if changes are more than cosmetic.
Hmm, from your comments I'm not really sure I understand what people are looking for with this feature. As I see it, when show changes in output is selected, the output is not even remotely close to the final manuscript. In general, line breaks, vertical spaces between paragraphs and equations, page breaks and more will be different. Is there anyway to rely on what you see in the result while change track with "show changes in output" are on? I thought this feature was more for earlier drafts. Can you describe a change that will backfire? This commit could potentially, in some cases, change some vertical spaces, nothing more really. I can always define separate commands for RTL scripts, I just did not think it was needed in this case. Udi > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
