second 2.4.1 version...
@Udi
Just like Pavel I also saw/participated in some work frameworks where
teams discuss the changes to a given document based on the change
tracking output. This has some advantages and drawbacks but it is
something that is used. :-)
> Of course there is no question th
On Wed, Jun 12, 2024 at 07:09:19PM +0300, Udicoudco wrote:
> As I see it, when show changes in output
> is selected, the output is not even remotely close to the final
> manuscript.
Right, but that was not my point. What I mean is that I just had to submit to a
journal reviewers revised version of
>
> 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 cosmet
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 jour
On Wed, Jun 12, 2024 at 10:32 AM Pavel Sanda wrote:
>
> On Mon, Jun 10, 2024 at 12:19:18PM +, Udi Fogiel wrote:
> > commit a5749b9c1f5c5b42e6d6db7cd9f2aab16bc28f5b
> > Author: Udi Fogiel
> > Date: Mon Jun 10 15:19:08 2024 +0300
> >
> > Fix chang
On Mon, Jun 10, 2024 at 12:19:18PM +, Udi Fogiel wrote:
> commit a5749b9c1f5c5b42e6d6db7cd9f2aab16bc28f5b
> Author: Udi Fogiel
> Date: Mon Jun 10 15:19:08 2024 +0300
>
> Fix change tracking colors with RTL languages (#12923)
> ---
> src/LaTeXFeatures.cpp | 4 ++--
On 2023-11-30 17:46, Lorenzo Bertini wrote:
Il giorno gio 30 nov 2023 alle ore 15:47 Jean-Marc Lasgouttes
ha scritto:
Le 30/11/2023 à 03:01, Daniel a écrit :
LyX has the peculiarity of treating the (de)activating of change
tracking as something that is recorded on the undo stack.
Actually
Il giorno gio 30 nov 2023 alle ore 15:47 Jean-Marc Lasgouttes
ha scritto:
>
> Le 30/11/2023 à 03:01, Daniel a écrit :
> > LyX has the peculiarity of treating the (de)activating of change
> > tracking as something that is recorded on the undo stack.
>
> Actually, everythi
Le 30/11/2023 à 03:01, Daniel a écrit :
LyX has the peculiarity of treating the (de)activating of change
tracking as something that is recorded on the undo stack.
Actually, everything that is stored in the file goes to the undo stack.
I do not see how to avoid that.
One of the problems I
LyX has the peculiarity of treating the (de)activating of change
tracking as something that is recorded on the undo stack.
One of the problems I ran into with this is that it unexpectedly killed
the redo function when I activated change tracking, i.e. I undid some
changes and activated the
On Fri, Feb 17, 2023 at 09:34:17AM -0500, Scott Kostyshak wrote:
> On Fri, Feb 17, 2023 at 03:05:34PM +0100, Pavel Sanda wrote:
> > On Wed, Feb 15, 2023 at 04:33:16PM -0500, Scott Kostyshak wrote:
> > > > we added in master new entries to the menu Document -> Chan
On Fri, Feb 17, 2023 at 03:05:34PM +0100, Pavel Sanda wrote:
> On Wed, Feb 15, 2023 at 04:33:16PM -0500, Scott Kostyshak wrote:
> > > we added in master new entries to the menu Document -> Change Tracking,
> > > in particular
> > >
> > > Accept A
ction does
> not have to be executed often.
>
> Or instead
>
> Master/Children/Siblings -> Accept All Changes
> Master/Children/Siblings -> Reject All Changes
I wanted things *easier* :)
> I also noticed that the menu "Change Tracking" menu misses the &qu
On Wed, Feb 15, 2023 at 04:33:16PM -0500, Scott Kostyshak wrote:
> > we added in master new entries to the menu Document -> Change Tracking, in
> > particular
> >
> > Accept All Changes (incl. Master/Children/Siblings)
> > Reject All Changes (incl. Master/Childre
On 2023-02-15 22:33, Scott Kostyshak wrote:
On Wed, Feb 15, 2023 at 09:39:36PM +0100, Pavel Sanda wrote:
Hi,
we added in master new entries to the menu Document -> Change Tracking, in
particular
Accept All Changes (incl. Master/Children/Siblings)
Reject All Changes (incl. Master/Child
On Wed, Feb 15, 2023 at 09:39:36PM +0100, Pavel Sanda wrote:
> Hi,
>
> we added in master new entries to the menu Document -> Change Tracking, in
> particular
>
> Accept All Changes (incl. Master/Children/Siblings)
> Reject All Changes (incl. Master/Children/Siblings)
Hi,
we added in master new entries to the menu Document -> Change Tracking, in
particular
Accept All Changes (incl. Master/Children/Siblings)
Reject All Changes (incl. Master/Children/Siblings)
and it looks in the menu way too wide (in some translations even longer).
I propose that we shor
On 2020-08-07 14:29, Jürgen Spitzmüller wrote:
Am Freitag, den 07.08.2020, 13:48 +0200 schrieb Daniel:
Anyone seeing this regression?
Steps to reproduce:
1. Enable change tracking
2. Copy something
3. Paste it
Actual result:
- Pasted content not marked as added
Expected result:
- It is
Am Freitag, den 07.08.2020, 15:58 +0200 schrieb Thibaut Cuvelier:
> Shouldn't this parameter be set by default?
I agree.
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Fri, 7 Aug 2020 at 14:30, Jürgen Spitzmüller wrote:
> Am Freitag, den 07.08.2020, 13:48 +0200 schrieb Daniel:
> > Anyone seeing this regression?
> >
> > Steps to reproduce:
> > 1. Enable change tracking
> > 2. Copy something
> > 3. Paste it
> >
Am Freitag, den 07.08.2020, 13:48 +0200 schrieb Daniel:
> Anyone seeing this regression?
>
> Steps to reproduce:
> 1. Enable change tracking
> 2. Copy something
> 3. Paste it
>
> Actual result:
> - Pasted content not marked as added
>
> Expected result:
Anyone seeing this regression?
Steps to reproduce:
1. Enable change tracking
2. Copy something
3. Paste it
Actual result:
- Pasted content not marked as added
Expected result:
- It is marked as added.
--
Daniel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman
file with
any text,
and turn on change tracking. Then change fonts on some words
(italics, bold,
san serif, ...). None of the font changes are flagged as changes.
Adding or
deleting characters still register as normal.
You are not hallucinating, and it has always been like that since the
begin
On 7/26/20 5:56 AM, Enrico Forestieri wrote:
On Sat, Jul 25, 2020 at 05:43:59PM -0400, Paul A. Rubin wrote:
Can someone confirm that (a) I'm not hallucinating and (b) this is a new bug
(I couldn't find it in the issue tracker)? Create a test file with any text,
and turn on change trac
On Sat, Jul 25, 2020 at 05:43:59PM -0400, Paul A. Rubin wrote:
> Can someone confirm that (a) I'm not hallucinating and (b) this is a new bug
> (I couldn't find it in the issue tracker)? Create a test file with any text,
> and turn on change tracking. Then change fonts on some w
Can someone confirm that (a) I'm not hallucinating and (b) this is a new
bug (I couldn't find it in the issue tracker)? Create a test file with
any text, and turn on change tracking. Then change fonts on some words
(italics, bold, san serif, ...). None of the font changes are
On Thu, Jul 09, 2020 at 06:49:10PM +0200, Jürgen Spitzmüller wrote:
> Am Donnerstag, den 09.07.2020, 13:51 +0200 schrieb Pavel Sanda:
> > I encountered this problem yesterday in master when importing docbook
> > changes.
> > Load the attached file, hit Next change in chage-tracking icon bar.
> > Th
Am Donnerstag, den 09.07.2020, 13:51 +0200 schrieb Pavel Sanda:
> I encountered this problem yesterday in master when importing docbook
> changes.
> Load the attached file, hit Next change in chage-tracking icon bar.
> The cursor gets stuck
> inside the code inset and other hits of Next change are
Hi,
I encountered this problem yesterday in master when importing docbook changes.
Load the attached file, hit Next change in chage-tracking icon bar. The cursor
gets stuck
inside the code inset and other hits of Next change are without effect.
Pavel
#LyX 2.4 created this file. For more info see
th an activated branch containing text that
has
been edited, and with change tracking turned on. The user wants to
dissolve the branch but retain the content. If the user does this
with
change tracking turned on, the entire branch gets crossed out and
the
full contents gets reproduced, which is
with an activated branch containing text that
> > has
> > been edited, and with change tracking turned on. The user wants to
> > dissolve the branch but retain the content. If the user does this
> > with
> > change tracking turned on, the entire branch gets crossed
On 5/8/20 1:54 PM, Paul A. Rubin wrote:
> Before I file a ticket on this, I'd like to get a sense of whether it
> is in fact a bug v. intended behavior.
>
> Consider a document with an activated branch containing text that has
> been edited, and with change tracking turned o
Am Samstag, den 18.04.2020, 08:30 +0200 schrieb Jürgen Spitzmüller:
> Am Samstag, den 18.04.2020, 07:57 +0200 schrieb Daniel:
> > I can see how it's not worth the effort.
>
> Sure, since it's not your time that is to be invested ;-)
Sorry. I seem to have some negation parsing problems these days.
Am Samstag, den 18.04.2020, 07:57 +0200 schrieb Daniel:
> I can see how it's not worth the effort.
Sure, since it's not your time that is to be invested ;-)
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.
On 2020-04-17 13:43, Jürgen Spitzmüller wrote:
Am Freitag, den 17.04.2020, 12:54 +0200 schrieb Daniel:
Or maybe there is a specific problem with \underline vs the \color
command? Maybe the latter works in cases where the former doesn't?
Underline will not work in many cases where color does. B
Am Freitag, den 17.04.2020, 12:54 +0200 schrieb Daniel:
> Or maybe there is a specific problem with \underline vs the \color
> command? Maybe the latter works in cases where the former doesn't?
Underline will not work in many cases where color does. Basically you
would need to jump through (at le
On 2020-04-12 08:33, Daniel wrote:
I saw that a new preference was added to disable Underline change
tracking additions:
https://wiki.lyx.org/LyX/NewInLyX24#preferences
I just wanted to flag that this might make it harder to sensibly
implement change tracking of some other changes, such as
I saw that a new preference was added to disable Underline change
tracking additions:
https://wiki.lyx.org/LyX/NewInLyX24#preferences
I just wanted to flag that this might make it harder to sensibly
implement change tracking of some other changes, such as text style
changes. For example
Am Mon, 13 Jan 2020 14:27:53 +0100
schrieb Kornel Benko :
> Am Mon, 13 Jan 2020 14:00:35 +0100
> schrieb Jürgen Spitzmüller :
>
> > Am Montag, den 13.01.2020, 13:54 +0100 schrieb Kornel Benko:
> > > ! Package fontspec Error: The font "FreeSerif" cannot be found.
> >
> > Apparently you need
Le 14/01/2020 à 09:30, Jürgen Spitzmüller a écrit :
Am Montag, den 13.01.2020, 16:00 +0100 schrieb Jürgen Spitzmüller:
Also, is there a reason why your change status does not have a
author
and time associated with it?
The author and time should be recorded via the cells.
It is now recorded i
Am Montag, den 13.01.2020, 16:00 +0100 schrieb Jürgen Spitzmüller:
> > Also, is there a reason why your change status does not have a
> > author
> > and time associated with it?
>
> The author and time should be recorded via the cells.
It is now recorded in the row/column metadata itself.
Jürge
Am Montag, den 13.01.2020, 17:45 +0100 schrieb Jürgen Spitzmüller:
> We could color the lines of the
> added/removed columns/rows blue or red.
Coloring now done. Ideally, deleted rows/columns should be struck-out
as we do for deleted tables. But I don't know how to do that.
Jürgen
signature.asc
Am Montag, den 13.01.2020, 17:49 +0100 schrieb Jean-Marc Lasgouttes:
> To put things differently: what does the support for tracking
> row/column
> addition/removal that you added does in terms of functionality?
It is actually tracked. Before (and still in stable) if you added a
row/column in ct
Le 13/01/2020 à 17:45, Jürgen Spitzmüller a écrit :
Am Montag, den 13.01.2020, 16:14 +0100 schrieb Jean-Marc Lasgouttes:
Yes, but you do not know what column was added.
This is how it was before as well. We could color the lines of the
added/removed columns/rows blue or red.
To put things di
Am Montag, den 13.01.2020, 16:14 +0100 schrieb Jean-Marc Lasgouttes:
> Yes, but you do not know what column was added.
This is how it was before as well. We could color the lines of the
added/removed columns/rows blue or red.
> BTW, the changebar in the margin has a height computed as
>
>
Le 13/01/2020 à 16:00, Jürgen Spitzmüller a écrit :
Am Montag, den 13.01.2020, 15:48 +0100 schrieb Jean-Marc Lasgouttes:
If I switch on change tracking before inserting a column in a
tabular,
there is no way to know what column is new.
I see a change bar in the margin.
Yes, but you do not
Am Montag, den 13.01.2020, 15:48 +0100 schrieb Jean-Marc Lasgouttes:
> If I switch on change tracking before inserting a column in a
> tabular,
> there is no way to know what column is new.
I see a change bar in the margin.
> Should the tabular itself be marked as changed in this
guess what cell/column has been
affected...
Currently, all affected columns/rows also get the respective status set
for each cell. So that should be good.
If I switch on change tracking before inserting a column in a tabular,
there is no way to know what column is new.
Should the tabular itself
Am Montag, den 13.01.2020, 15:12 +0100 schrieb Jean-Marc Lasgouttes:
> OK, I guess the code is a bit better now. BTW, I see that you added
> support for tracking insertion/deletion of cells/columns in Tabular
> Inset. However, there is no way to guess what cell/column has been
> affected...
Cur
Le 13/01/2020 à 14:27, Jürgen Spitzmüller a écrit :
Am Montag, den 13.01.2020, 14:05 +0100 schrieb Jean-Marc Lasgouttes:
I am a bit puzzled. parit points to a paragraph, but this paragraph
is
not in an InsetText? Where is it? In a table cell?
InsetTableCell probably.
OK, I guess the code is
Am Mon, 13 Jan 2020 14:00:35 +0100
schrieb Jürgen Spitzmüller :
> Am Montag, den 13.01.2020, 13:54 +0100 schrieb Kornel Benko:
> > ! Package fontspec Error: The font "FreeSerif" cannot be found.
>
> Apparently you need to install this font.
>
> Jürgen
No, I have this font. Both compilations d
Am Montag, den 13.01.2020, 14:05 +0100 schrieb Jean-Marc Lasgouttes:
> I am a bit puzzled. parit points to a paragraph, but this paragraph
> is
> not in an InsetText? Where is it? In a table cell?
InsetTableCell probably.
Jürgen
signature.asc
Description: This is a digitally signed message par
Le 13/01/2020 à 13:04, Jürgen Spitzmüller a écrit :
Am Montag, den 13.01.2020, 12:08 +0100 schrieb Jürgen Spitzmüller:
Am Montag, den 13.01.2020, 11:32 +0100 schrieb Kornel Benko:
For instance for export/tabletemplates/Grid_with_Head_1x2_dvi
lyx: SIGSEGV signal caught!
JMarc, this looks like
Am Montag, den 13.01.2020, 13:54 +0100 schrieb Kornel Benko:
> ! Package fontspec Error: The font "FreeSerif" cannot be found.
Apparently you need to install this font.
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
h
Am Mon, 13 Jan 2020 13:04:55 +0100
schrieb Jürgen Spitzmüller :
> Am Montag, den 13.01.2020, 12:08 +0100 schrieb Jürgen Spitzmüller:
> > Am Montag, den 13.01.2020, 11:32 +0100 schrieb Kornel Benko:
> > > For instance for export/tabletemplates/Grid_with_Head_1x2_dvi
> > >
> > > lyx: SIGSEGV sign
Am Montag, den 13.01.2020, 12:08 +0100 schrieb Jürgen Spitzmüller:
> Am Montag, den 13.01.2020, 11:32 +0100 schrieb Kornel Benko:
> > For instance for export/tabletemplates/Grid_with_Head_1x2_dvi
> >
> > lyx: SIGSEGV signal caught!
>
> JMarc, this looks like yours:
This should be fixed. JMarc, p
Am Mon, 13 Jan 2020 12:37:00 +0100
schrieb Jürgen Spitzmüller :
> Am Montag, den 13.01.2020, 12:34 +0100 schrieb Kornel Benko:
> > No, of course not. As I wrote 'After the last commits'.
>
> Yes but if you quote my commit it looks like you are pointing fingers
> directly at it. At least I am re
Am Montag, den 13.01.2020, 12:34 +0100 schrieb Kornel Benko:
> Looking at the backtrace, I think it has to do with change tracking.
> ...
> #0 0x007ed966 in lyx::InsetText::isChanged(bool) const
As I said, it looks like 4a4ded2297e which introduced
Inset::isChanged(
Am Montag, den 13.01.2020, 12:34 +0100 schrieb Kornel Benko:
> No, of course not. As I wrote 'After the last commits'.
Yes but if you quote my commit it looks like you are pointing fingers
directly at it. At least I am reading it like that.
Jürgen
signature.asc
Description: This is a digitally
ikely would be dvipost removal)
> Jürgen
Looking at the backtrace, I think it has to do with change tracking.
...
#0 0x007ed966 in lyx::InsetText::isChanged(bool) const
(ic=false, this=0x0) at insets/InsetText.h:130
#1 0x007ed966 in lyx::Buffer::updateBuffer(lyx::ParIterator
Am Montag, den 13.01.2020, 11:32 +0100 schrieb Kornel Benko:
> For instance for export/tabletemplates/Grid_with_Head_1x2_dvi
>
> lyx: SIGSEGV signal caught!
JMarc, this looks like yours:
Thread 1 "lyx" received signal SIGSEGV, Segmentation fault.
0x007ed966 in lyx::InsetText::isChanged (
Am Montag, den 13.01.2020, 12:01 +0100 schrieb Jürgen Spitzmüller:
> Are you sure this is related to this commit? This is very unlikely.
(more likely would be dvipost removal)
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.ly
Am Montag, den 13.01.2020, 11:32 +0100 schrieb Kornel Benko:
> After the last commits many of the dvi-tests are failing.
> ctest -R dvi3
> 55% tests passed, 270 tests failed out of 605
>
> ctest -R 'dvi$'
> 55% tests passed, 143 tests failed out of 320
>
> For instance for export/tabletemplates/G
Am Mon, 13 Jan 2020 09:34:31 +0100 (CET)
schrieb Juergen Spitzmueller :
> commit adfd38e4efd1180df164fa2c75cf15210f366e94
> Author: Juergen Spitzmueller
> Date: Mon Jan 13 09:48:56 2020 +0100
>
> Fix backspace deletion of selected items with change tracking
>
&g
00
>>>Copy documentation of new features of Additional.lyx in de, es, fr
>>> and ja documentation files
>>>as change tracking and remove chnage tracking in Additional.lyx
> The 'Missing glyphs' error with system fonts and xelatex was presen
documentation files
as change tracking and remove chnage tracking in Additional.lyx
lib/doc/Additional.lyx| 484 ++--
lib/doc/de/Additional.lyx | 994 ++-
lib/doc/es/Additional.lyx | 995 ++-
lib/doc/fr
wrote:
> > > > commit c9f398d7c516f9e9f3df71e74231a87e639180b9
> > > > Author: jpc
> > > > Date: Wed Jul 12 22:31:30 2017 +0200
> > > >
> > > >Copy documentation of new features of Additional.lyx in de, es,
> > > > fr and ja docum
gt; > Date: Wed Jul 12 22:31:30 2017 +0200
> > >
> > >Copy documentation of new features of Additional.lyx in de, es, fr
> > > and ja documentation files
> > >as change tracking and remove chnage tracking in Additional.lyx
> > &g
documentation of new features of Additional.lyx in de, es, fr
> > and ja documentation files
> >as change tracking and remove chnage tracking in Additional.lyx
> >
> > lib/doc/Additional.lyx| 484 ++--
> > lib/doc/de/Additional.lyx | 994 +++
On Wed, Jul 12, 2017 at 10:34:53PM +0200, jpc wrote:
> commit c9f398d7c516f9e9f3df71e74231a87e639180b9
> Author: jpc
> Date: Wed Jul 12 22:31:30 2017 +0200
>
>Copy documentation of new features of Additional.lyx in de, es, fr and
> ja documentation files
>
Le 24/10/2016 à 01:00, Enrico Forestieri a écrit :
On Sun, Oct 23, 2016 at 11:52:55PM +0200, Guillaume Munch wrote:
The code does look fragile to me. I do not think that asking that
developers care about maintainability is being overzealous. Then, maybe
I am mistaken about the code and you got
On Sun, Oct 23, 2016 at 11:52:55PM +0200, Guillaume Munch wrote:
>
> The code does look fragile to me. I do not think that asking that
> developers care about maintainability is being overzealous. Then, maybe
> I am mistaken about the code and you got to something found maintainable
> enough after
Correctly track ulem commands with change tracking
LyX assumes that everything in \lyxdeleted is struck out by ulem
and increases the corresponding counter. However, deleted display
math material is struck out using tikz. As we also take into
account the deletion of underlined display math
orrectly track ulem commands with change tracking
> >
> > LyX assumes that everything in \lyxdeleted is struck out by ulem
> > and increases the corresponding counter. However, deleted display
> > math material is struck out using tikz. As we also take into
> >
119bc2364a7ac2b
> > > > Author: Enrico Forestieri
> > > > Date: Sun Oct 23 18:23:41 2016 +0200
> > > >
> > > > Correctly track ulem commands with change tracking
> > > >
> > > > LyX assumes that everything in \lyxdelet
with change tracking
LyX assumes that everything in \lyxdeleted is struck out by ulem
and increases the corresponding counter. However, deleted display
math material is struck out using tikz. As we also take into
account the deletion of underlined display math (in order to
On 10/23/2016 01:02 PM, Guillaume Munch wrote:
> Le 23/10/2016 à 18:38, Enrico Forestieri a écrit :
>> commit dea5ba16de1b98d93cf30ab65119bc2364a7ac2b
>> Author: Enrico Forestieri
>> Date: Sun Oct 23 18:23:41 2016 +0200
>>
>> Correctly track ulem commands w
Le 23/10/2016 à 18:38, Enrico Forestieri a écrit :
commit dea5ba16de1b98d93cf30ab65119bc2364a7ac2b
Author: Enrico Forestieri
Date: Sun Oct 23 18:23:41 2016 +0200
Correctly track ulem commands with change tracking
LyX assumes that everything in \lyxdeleted is struck out by ulem
To do that I shall have to install 2.2.2, which I cannot do at the
moment. I shall follow up once I manage to install the latest
version.
Yours,
Ehud Kaplan
On 10/15/2016 06:29 PM, LyX Ticket
Tracker wrote:
#6563: Change tracking and moving
Le 29/09/2016 à 14:03, Kornel Benko a écrit :
Shouldn't be 'List of Slides' also in French?
See attached.
(Slide in 1.1 Liste des transparents)
Sure, this is not translated in fr.po,
I've added
\def\listslidename{Liste des transparents}
in the preamble without success :-(
In fact, slidesec
Am Donnerstag, 29. September 2016 um 13:59:02, schrieb Jean-Pierre Chrétien
> Le 29/09/2016 à 09:54, Guenter Milde a écrit :
> > On 2016-09-28, Guenter Milde wrote:
> >> On 2016-09-28, Jean-Pierre Chrétien wrote:
> >>> Le 26/09/2016 à 09:24, Jean-Pierre Chrétien a écrit :
>
> >>>- the outline
Le 29/09/2016 à 09:54, Guenter Milde a écrit :
On 2016-09-28, Guenter Milde wrote:
On 2016-09-28, Jean-Pierre Chrétien wrote:
Le 26/09/2016 à 09:24, Jean-Pierre Chrétien a écrit :
- the outline and progress slides include an empty line after slide "Warning"
that I could not remove
Actu
On 2016-09-28, Guenter Milde wrote:
> On 2016-09-28, Jean-Pierre Chrétien wrote:
>> Le 26/09/2016 à 09:24, Jean-Pierre Chrétien a écrit :
Dear Jean-Pierre,
>> I've updated the French translation and committed it, so you may abandon the
>> change tracking as there ar
On 2016-09-28, Jean-Pierre Chrétien wrote:
> Le 26/09/2016 à 09:24, Jean-Pierre Chrétien a écrit :
Dear Jean-Pierre,
> I've updated the French translation and committed it, so you may abandon the
> change tracking as there are no other translations of this document.
tha
the original and would volunteer to update it.
Should I use change tracking for an example file update?
Hi Günter,
yes, please use change tracking. We have an active translator for French.
Jean-Pierre is also a good tester. So he will cross-check the document in terms
of compilability, language
I use change tracking for an example file update?
Hi Günter,
yes, please use change tracking. We have an active translator for French.
Jean-Pierre is also a good tester. So he will cross-check the document in terms
of compilability, language specials etc. when he translates.
Sure, I will take
On Fri, Sep 23, 2016 at 07:37:39PM +, Guenter Milde wrote:
the seminar example file lib/examples/seminar.lyx is outdated.
There is a French translation in lib/examples/fr/seminar.lyx
I wrote the original and would volunteer to update it.
Should I use change tracking for an example file
lde wrote:
> > Dear Lyxdevelopers,
> >
> > the seminar example file lib/examples/seminar.lyx is outdated.
> >
> > There is a French translation in lib/examples/fr/seminar.lyx
> >
> > I wrote the original and would volunteer to update it.
> >
&g
> There is a French translation in lib/examples/fr/seminar.lyx
>
> I wrote the original and would volunteer to update it.
>
> Should I use change tracking for an example file update?
The following thread makes me think that the section in Development.lyx also
refers to ex
Dear Lyxdevelopers,
the seminar example file lib/examples/seminar.lyx is outdated.
There is a French translation in lib/examples/fr/seminar.lyx
I wrote the original and would volunteer to update it.
Should I use change tracking for an example file update?
The Development.lyx guide only speaks
Guillaume Munch wrote:
> commit 8e1a869c45b0c1cb1ee1f3e85d51325224ec3eb4
> Author: Guillaume Munch
> Date: Mon May 23 15:44:29 2016 +0100
>
> Change tracking cue: for instant preview
>
> Strike through deleted previews (expect for inline math where it is
&g
Le 03/07/2016 17:51, Guillaume Munch a écrit :
Dear List
Attached is a patch that makes many small decisions regarding how text
insets should be displayed under change tracking. You would probably
have some comment about these choices. It would be too long to explain
and it is hard to
Dear List
Attached is a patch that makes many small decisions regarding how text
insets should be displayed under change tracking. You would probably
have some comment about these choices. It would be too long to explain
and it is hard to understand these choices just by reading the code
Guillaume Munch wrote:
> That would be a nice enhancement and would be a proper way to solve the
> problem of missing \author lines. Independently from this, the latest
> version of my patch solves every critical aspect of the problem (that
> can be blamed on LyX rather than version control), and
Le 13/11/2015 10:56, Vincent van Ravesteijn a écrit :
I believe that 'git' can have custom merge filter/script for certain
file types. Maybe the community would like a special LyX-merger script
that can be used by the vcs to reduce merge errors as much as
possible.
That would be a nice enhance
Le 13/11/2015 03:18, Pavel Sanda a écrit :
Georg Baum wrote:
Unfortunately there is a good
reason for this behaviour: If LyX would not do that, then unused \author
lines could easily accumulate: If I accept all changes of my co-author, and
he never edits the file again, then his \author line wil
author list. Then, changes only refer to the entry in the
author list, which knows nothing of this buffer id. That's why we need a
dummy author.
We could also add a preference "Anonymous change tracking", instead of
using the user's name and e-mail.
I just don't lik
1
From: Guillaume Munch
Date: Wed, 11 Nov 2015 21:31:05 +
Subject: [PATCH 1/2] Fix bug #9854 "Dataloss after git merge with change
tracking"
A plausible scenario is that change tracking is used together with a versioning
system. In this case, parallel modifications might remove an
Le 12/11/2015 18:29, Georg Baum a écrit :
Guillaume Munch wrote:
* Georg, you told us an old story of "FIXME: UNICODE"s being placed in
the source when the developers decided that docstring would be the only
place where we see Unicode. I am happy to fix these as I go through the
code, but I am
in one
place to where can be refered in the rest of the document. Adding a
dummy author isn't very useful then, because it doesn't add info.
Then, if the author line is not present, we just don't show the author
name and email address in the gui.
We could also add a preference "An
1 - 100 of 665 matches
Mail list logo
