Re: #8577: Additional features manual

2022-12-02 Thread Scott Kostyshak
On Tue, Nov 29, 2022 at 12:34:48AM +0100, Pavel Sanda wrote:
> On Mon, Nov 28, 2022 at 06:41:08PM +, John Robert Hudson wrote:
> > Can you let me know how I can obtain/create the version of LyX which I will
> > need to work on the additional features manual, please?
> 
> Excelent question. Are on Windows or Mac or Linux?  
> 
> We did not freeze the fileformat for 2.4 yet so unless you can compile 
> the current development version we need to figure out how to deliver it
> for people like you.
> 
> Perhaps Scott will propose soon some guidelines/deadlines when it comes to
> release process so I have better answers when it's a good time to start
> working on the documentation.

Indeed I hope to do so soon (maybe late next week).

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2022-11-29 Thread John Robert Hudson
On Tuesday, 29 November 2022 11:57:37 GMT Cor Blom wrote:
> Op 29-11-2022 om 12:35 schreef Pavel Sanda:
> > On Tue, Nov 29, 2022 at 10:11:42AM +, John Robert Hudson wrote:
> >> On Monday, 28 November 2022 23:34:48 GMT Pavel Sanda wrote:
> >>> Excelent question. Are on Windows or Mac or Linux?
> >>> 
> >>> We did not freeze the fileformat for 2.4 yet so unless you can compile
> >>> the current development version we need to figure out how to deliver it
> >>> for people like you.
> >>> 
> >>> Perhaps Scott will propose soon some guidelines/deadlines when it comes
> >>> to
> >>> release process so I have better answers when it's a good time to start
> >>> working on the documentation.
> >>> 
> >>> Pavel
> >> 
> >> I use openSUSE Linux but I assume that if I prepare the changes in 2.3
> >> and
> >> then open a text editor and copy and paste them into Additional.lyx, save
> >> that and send you a patch, that should work. I am familiar with working
> >> with markup languages and I do not think there will be anything in a 2.3
> >> markup which will be incompatible with 2.4 - at least not in the layout
> >> of Additional.lyx.
> >> 
> >> At least we could try that when I get round to sending my first patch
> >> and, if it works, carry on that way until is is practical to have a
> >> stable version of 2.4.
> > 
> > Sounds possible, but the 2.4 manuals contain + ~5 years of changes so I
> > would think twice.
> > 
> > On the positive side, you are on Linux! Cor Blom who is our SUSE
> > maintainer is pretty active and as far as I can see there is repository
> > with recent 2.4 so I would try that:
> > https://build.opensuse.org/package/show/home%3Acornelisbb%3Alyx-unstable/l
> > yx
> > 
> > (I have no clue whether how to install this on openSUSE though)
> > Pavel
> 
> And if that is not working, please let me know.
> 
> At the moment it replaces the present lyx installation (in my experience
> master is pretty stable). If a package that is co-installable is needed,
> I can change that.
> 
> Cor
I did not install it over my stable 2.3 installation but had created a 
separate user to hold my git repository and downloaded the rpm to that user 
and used the extract option to make it available only to that user.

After I had reconfigured LyX, it loaded Additional.lyx without any problems.

Thank you. It will make things so much easier.

John




-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2022-11-29 Thread Jürgen Spitzmüller
Am Dienstag, dem 29.11.2022 um 10:11 + schrieb John Robert Hudson:
> I use openSUSE Linux but I assume that if I prepare the changes in
> 2.3 and then open a text editor and copy and paste them into
> Additional.lyx, save that and send you a patch, that should work. I
> am familiar with working with markup languages and I do not think
> there will be anything in a 2.3 markup which will be incompatible
> with 2.4 - at least not in the layout of Additional.lyx.

I don't think this will work. We have changes in Additional.lyx of 2.4
which we don't want to loose. This document can't be opened with 2.3.
You can export it to 2.3 format, but then some new features will be
exported to TeX Mode and not reverted back when opened with 2.4.

2.4 is stable enough meanwhile to use it for such kind of work.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2022-11-29 Thread John Robert Hudson
On Tuesday, 29 November 2022 11:35:42 GMT Pavel Sanda wrote:
> On Tue, Nov 29, 2022 at 10:11:42AM +, John Robert Hudson wrote:
> > On Monday, 28 November 2022 23:34:48 GMT Pavel Sanda wrote:
> > > Excelent question. Are on Windows or Mac or Linux?
> > > 
> > > We did not freeze the fileformat for 2.4 yet so unless you can compile
> > > the current development version we need to figure out how to deliver it
> > > for people like you.
> > > 
> > > Perhaps Scott will propose soon some guidelines/deadlines when it comes
> > > to
> > > release process so I have better answers when it's a good time to start
> > > working on the documentation.
> > > 
> > > Pavel
> > 
> > I use openSUSE Linux but I assume that if I prepare the changes in 2.3 and
> > then open a text editor and copy and paste them into Additional.lyx, save
> > that and send you a patch, that should work. I am familiar with working
> > with markup languages and I do not think there will be anything in a 2.3
> > markup which will be incompatible with 2.4 - at least not in the layout
> > of Additional.lyx.
> > 
> > At least we could try that when I get round to sending my first patch and,
> > if it works, carry on that way until is is practical to have a stable
> > version of 2.4.
> 
> Sounds possible, but the 2.4 manuals contain + ~5 years of changes so I
> would think twice.
> 
> On the positive side, you are on Linux! Cor Blom who is our SUSE maintainer
> is pretty active and as far as I can see there is repository with recent
> 2.4 so I would try that:
> https://build.opensuse.org/package/show/home%3Acornelisbb%3Alyx-unstable/lyx
> 
> (I have no clue whether how to install this on openSUSE though)
> Pavel

I downloaded Cor’s rpm and extracted it and it works fine. So it looks as if I 
am all set. Thanks.

John



-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2022-11-29 Thread Cor Blom

Op 29-11-2022 om 12:35 schreef Pavel Sanda:

On Tue, Nov 29, 2022 at 10:11:42AM +, John Robert Hudson wrote:

On Monday, 28 November 2022 23:34:48 GMT Pavel Sanda wrote:

Excelent question. Are on Windows or Mac or Linux?

We did not freeze the fileformat for 2.4 yet so unless you can compile
the current development version we need to figure out how to deliver it
for people like you.

Perhaps Scott will propose soon some guidelines/deadlines when it comes to
release process so I have better answers when it's a good time to start
working on the documentation.

Pavel


I use openSUSE Linux but I assume that if I prepare the changes in 2.3 and
then open a text editor and copy and paste them into Additional.lyx, save that
and send you a patch, that should work. I am familiar with working with markup
languages and I do not think there will be anything in a 2.3 markup which will
be incompatible with 2.4 - at least not in the layout of Additional.lyx.

At least we could try that when I get round to sending my first patch and, if
it works, carry on that way until is is practical to have a stable version of
2.4.


Sounds possible, but the 2.4 manuals contain + ~5 years of changes so I would
think twice.

On the positive side, you are on Linux! Cor Blom who is our SUSE maintainer is
pretty active and as far as I can see there is repository with recent 2.4 so I
would try that:
https://build.opensuse.org/package/show/home%3Acornelisbb%3Alyx-unstable/lyx

(I have no clue whether how to install this on openSUSE though)
Pavel


And if that is not working, please let me know.

At the moment it replaces the present lyx installation (in my experience 
master is pretty stable). If a package that is co-installable is needed, 
I can change that.


Cor

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2022-11-29 Thread Pavel Sanda
On Tue, Nov 29, 2022 at 10:11:42AM +, John Robert Hudson wrote:
> On Monday, 28 November 2022 23:34:48 GMT Pavel Sanda wrote:
> > Excelent question. Are on Windows or Mac or Linux?
> > 
> > We did not freeze the fileformat for 2.4 yet so unless you can compile
> > the current development version we need to figure out how to deliver it
> > for people like you.
> > 
> > Perhaps Scott will propose soon some guidelines/deadlines when it comes to
> > release process so I have better answers when it's a good time to start
> > working on the documentation.
> > 
> > Pavel
> 
> I use openSUSE Linux but I assume that if I prepare the changes in 2.3 and 
> then open a text editor and copy and paste them into Additional.lyx, save 
> that 
> and send you a patch, that should work. I am familiar with working with 
> markup 
> languages and I do not think there will be anything in a 2.3 markup which 
> will 
> be incompatible with 2.4 - at least not in the layout of Additional.lyx.
> 
> At least we could try that when I get round to sending my first patch and, if 
> it works, carry on that way until is is practical to have a stable version of 
> 2.4.

Sounds possible, but the 2.4 manuals contain + ~5 years of changes so I would
think twice.

On the positive side, you are on Linux! Cor Blom who is our SUSE maintainer is
pretty active and as far as I can see there is repository with recent 2.4 so I
would try that:
https://build.opensuse.org/package/show/home%3Acornelisbb%3Alyx-unstable/lyx

(I have no clue whether how to install this on openSUSE though)
Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2022-11-29 Thread John Robert Hudson
On Monday, 28 November 2022 23:34:48 GMT Pavel Sanda wrote:
> Excelent question. Are on Windows or Mac or Linux?
> 
> We did not freeze the fileformat for 2.4 yet so unless you can compile
> the current development version we need to figure out how to deliver it
> for people like you.
> 
> Perhaps Scott will propose soon some guidelines/deadlines when it comes to
> release process so I have better answers when it's a good time to start
> working on the documentation.
> 
> Pavel

I use openSUSE Linux but I assume that if I prepare the changes in 2.3 and 
then open a text editor and copy and paste them into Additional.lyx, save that 
and send you a patch, that should work. I am familiar with working with markup 
languages and I do not think there will be anything in a 2.3 markup which will 
be incompatible with 2.4 - at least not in the layout of Additional.lyx.

At least we could try that when I get round to sending my first patch and, if 
it works, carry on that way until is is practical to have a stable version of 
2.4.

John



-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2022-11-28 Thread Pavel Sanda
On Mon, Nov 28, 2022 at 06:41:08PM +, John Robert Hudson wrote:
> Can you let me know how I can obtain/create the version of LyX which I will
> need to work on the additional features manual, please?

Excelent question. Are on Windows or Mac or Linux?  

We did not freeze the fileformat for 2.4 yet so unless you can compile 
the current development version we need to figure out how to deliver it
for people like you.

Perhaps Scott will propose soon some guidelines/deadlines when it comes to
release process so I have better answers when it's a good time to start
working on the documentation.

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2022-11-28 Thread John Robert Hudson



On 28/11/2022 08:57, LyX Ticket Tracker wrote:

#8577: Additional features manual
---+
  Reporter:  john_hudson|   Owner:  uwestoehr
  Type:  task   |  Status:  new
  Priority:  normal |   Milestone:  2.4.0
Component:  documentation  | Version:  2.1.0svn
  Severity:  normal |  Resolution:
  Keywords: |
---+

Comment (by sanda):

  >I am but I was extremely busy over the pandemic as people stuck at home
  sent me things to and so I have looked at in detail for at least three
  years but I am still an active user and would be happy to pick  this up
  but probably not until the New Year.

  The final 2.4 won't be out sooner than in the spring so there is still
  time to do it! Thanks :)


Can you let me know how I can obtain/create the version of LyX which I 
will need to work on the additional features manual, please?


John




--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2022-11-28 Thread John Robert Hudson
On Monday, 28 November 2022 08:57:13 GMT LyX Ticket Tracker wrote:
> #8577: Additional features manual
> ---+
>  Reporter:  john_hudson|   Owner:  uwestoehr
>  Type:  task   |  Status:  new
>  Priority:  normal |   Milestone:  2.4.0
> Component:  documentation  | Version:  2.1.0svn
>  Severity:  normal |  Resolution:
>  Keywords: |
> ---+
> 
> Comment (by sanda):
>  >I am but I was extremely busy over the pandemic as people stuck at home
> 
>  sent me things to and so I have looked at in detail for at least three
>  years but I am still an active user and would be happy to pick  this up
>  but probably not until the New Year.
> 
>  The final 2.4 won't be out sooner than in the spring so there is still
>  time to do it! Thanks :)

Thank you. That should be no problem.

John


-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2022-11-27 Thread John Robert Hudson
Hi

I am but I was extremely busy over the pandemic as people stuck at home sent 
me things to and so I have looked at in detail for at least three years but I 
am still an active user and would be happy to pick this up but probably not 
until the New Year.

John

On Saturday, 26 November 2022 21:50:56 GMT LyX Ticket Tracker wrote:
> #8577: Additional features manual
> ---+
>  Reporter:  john_hudson|   Owner:  uwestoehr
>  Type:  task   |  Status:  new
>  Priority:  normal |   Milestone:  2.4.0
> Component:  documentation  | Version:  2.1.0svn
>  Severity:  normal |  Resolution:
>  Keywords: |
> ---+
> 
> Comment (by skostysh):
> 
>  Hi John, are you still around and motivated to knock this out by chance?
> 
> --
> Ticket URL: <https://www.lyx.org/trac/ticket/8577#comment:21>
> The LyX Project <https://www.lyx.org/>
> LyX -- The Document Processor




-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel


Re: #8577: Additional features manual

2017-07-05 Thread John Robert Hudson
On Wednesday, 5 July 2017 16:03:36 BST LyX Ticket Tracker wrote:
> #8577: Additional features manual
> ---+
>  Reporter:  john_hudson|   Owner:  uwestoehr
>  Type:  task   |  Status:  new
>  Priority:  normal |   Milestone:  2.3.0
> Component:  documentation  | Version:  2.1.0svn
>  Severity:  normal |  Resolution:
>  Keywords: |
> ---+
> 
> Comment (by JPChretien):
> 
>  I think I saw this mentioned in the lists (the reworked outline raises a
>  bell) but to have a more precise idea I would need a recent version. Is it
>  available or is the 2013 version OK? And is it possible to extract now a
>  diff in 2.3.0?

I produced a revised outline some years ago but it was never merged; I was 
planning to merge it after 2.2 but pressure of work prevented me from doing it 
then. I am hoping that I can do it after 2.3 is released as I am expecting to 
have more time free by then.
John


Re: #8577: Additional features manual

2017-03-27 Thread John Robert Hudson

On 27/03/17 07:56, LyX Ticket Tracker wrote:

#8577: Additional features manual
---+
  Reporter:  john_hudson|   Owner:  uwestoehr
  Type:  task   |  Status:  new
  Priority:  normal |   Milestone:  2.3.0
Component:  documentation  | Version:  2.1.0svn
  Severity:  normal |  Resolution:
  Keywords: |
---+

Comment (by skostysh):

  Replying to [comment:10 rgheck]:
  > John sent me a new copy recently. He's working on it for 2.3.0.

  Great! Thanks for the work, John. Do you have an idea of about how much
  longer it will take to finish?

I am hoping to resume work on it after Easter. Sorry, my time at the 
start of this year got eaten up by various unexpected things.

John



Re: #8577: Additional features manual

2017-01-30 Thread John Robert Hudson



On 30/01/17 10:14, LyX Ticket Tracker wrote:

#8577: Additional features manual
---+
  Reporter:  john_hudson|   Owner:  uwestoehr
  Type:  task   |  Status:  new
  Priority:  normal |   Milestone:  2.3.0
Component:  documentation  | Version:  2.1.0svn
  Severity:  normal |  Resolution:
  Keywords: |
---+

Comment (by spitz):

  Please remember that there have been recent changes in the version in
  master (by Uwe and by myself) that need to be included in John's version.

Apologies for the delay in getting round to this because of pressure of 
work in other areas. I will start from the master and make the changes 
using the most recent master.

John



Re: #8577: Additional features manual

2014-01-26 Thread John R. Hudson
On Sun, 2014-01-26 at 17:23 +, LyX Ticket Tracker wrote:
> #8577: Additional features manual
> ---+
>  Reporter:  john_hudson|   Owner:  uwestoehr
>  Type:  task   |  Status:  new
>  Priority:  normal |   Milestone:  2.1.x
> Component:  documentation  | Version:  2.1.0svn
>  Severity:  normal |  Resolution:
>  Keywords: |
> ---+
> Changes (by lasgouttes):
> 
>  * milestone:  2.1.0 => 2.1.x
> 
> 
> Comment:
> 
>  I this going to happen? This is not blocking anyway.
> 
As I said in an earlier post, if it does not happen I will use it as the
basis for a revision after 2.1.0 is released.

John
--
Sorry - for some reason the verification email to enable me answer in
trac has not arrived so far.




Re: #8577: Additional features manual

2013-07-08 Thread Jürgen Spitzmüller
John R. Hudson wrote:
> >  I would not do that. But you could use the forthcoming 2.1 beta and try
> >to finish the stuff until 2.1 final.
> 
> Unfortunately, I have only one machine which is my production machine.
> So I don't want to compromise that by installing a beta version.

Which OS? Most likely, you will be able to install the beta in parallel of the 
stable version.

Jürgen


Re: #8577: Additional features manual

2013-07-08 Thread John R. Hudson
On Mon, 2013-07-08 at 09:15 +, LyX Ticket Tracker wrote:
> #8577: Additional features manual
> ---+
>  Reporter:  john_hudson|   Owner:  uwestoehr
>  Type:  task   |  Status:  new
>  Priority:  normal |   Milestone:  2.1.0
> Component:  documentation  | Version:  2.1.0svn
>  Severity:  normal |  Resolution:
>  Keywords: |
> ---+
> 
> Comment (by spitz):
> 
>  Replying to [comment:4 spitz]:
>  
>  Actually, I think loading the Lilypond module in this document is a bad
>  idea, since it will annoy everybody who hasn't lilypond installed (which I
>  assume are many). Rather than that, I would just refer to Help >
>  Additional Manuals > LilyPond.

Fine
>  
>  The whole section about multiple columns need to be copied from the recent
>  version in trunk.
It was at the time (Scott kindly sent it to me) - but there may have
been revisions since then.
> 
>  > In undertaking the restructuring, I started from the philosophy set out
>  > in Chapter 1 and restructured the manual around the order of topics in
>  > the User's Guide. I have also copied some parts of the User's Guide
>  > directly into the manual on the assumption that, if these changes are
>  > acceptable, those parts of the User's Guide can be deleted and replaced
>  > by a reference to the Additional Features manual.
> 
>  Which parts are that?
Things like BibTeX that are provided by external programs seemed better
all in the Additional features manual.
> 
>  > One option would be to wait until 2.1 comes out; I could then go through
>  > what I have done and add in anything that has been added to the current
>  > version since I did this one.
> 
>  I would not do that. But you could use the forthcoming 2.1 beta and try to
>  finish the stuff until 2.1 final.
Unfortunately, I have only one machine which is my production machine.
So I don't want to compromise that by installing a beta version.
> 
>  One thing I spotted which needs update are the document class names. The
>  old scheme "genre (class)" is no longer used, since we have proper
>  categories now. So, for instance, "article (koma)" is now called "KOMA
>  Article".
> 
I've noticed a lot of things that have changed since I did the original
work in January. As I cannot access 2.1 files, and assuming no-one else
has the time to do it before 2.1 comes out, that was why I was
suggesting waiting until 2.1 and bringing everything up-to-date then.

John
--




Re: #8577: Additional features manual

2013-07-08 Thread John R. Hudson
On Mon, 2013-07-08 at 07:46 +, LyX Ticket Tracker wrote:
> #8577: Additional features manual
> ---+
>  Reporter:  john_hudson|   Owner:  uwestoehr
>  Type:  task   |  Status:  new
>  Priority:  normal |   Milestone:  2.1.0
> Component:  documentation  | Version:  2.1.0svn
>  Severity:  normal |  Resolution:
>  Keywords: |
> ---+
> 
> Comment (by spitz):
> 
>  I think we should do something about this, else John's efforts will end as
>  vapor. Richard?
> 
>  John, I had a quick glance at this. The changes look good in general, but
>  it's really difficult to tell the differences in detail, since you did not
>  use change tracking. But I understand this cannot be repaired at this
>  stage.
> 
>  However, can you describe what has been done? I understand you did some
>  restructuring, some updating (menu description etc.) and some style
>  polishing. Most of it looks good. What I do not like, though, is that you
>  introduce a very deep sectioning hierarchy (up to paragraph level) and
>  shift some subsections to subsubsections. I think in general that
>  sectioning beyond subsections (if chapters are used) is problematic, and
>  is an indicator that the outline should be rethought.
> 
>  Also, do you have a more up-to-date version? In trunk, some content of the
>  Additional manual changed recently, most importantly, the multicol section
>  was completely rewritten (your version does not even compile anymore).
> 
>  You can follow the changes in the document here:
>  http://www.lyx.org/trac/log/lyxgit/lib/doc/Additional.lyx
> 
This is what I wrote when I finished it:
I attach an updated, expanded and restructured Additional Features
manual. Unfortunately, before I was half way through the changes, TeX
told me that I had reached its limits. So I had to turn Track changes
off in order to continue.

A couple of points need attention:

I have added a short Lilypond example as a note in section 4.10 because
my LaTeX skills proved insufficient to write the appropriate if ...
else ... fi constuction to allow this to be included. Perhaps someone
else can.

I wasn't able to view section 5.3 Multiple Columns because the Multiple
Columns module didn't work in 2.0.5. So this just needs to be checked to
ensure that I haven't introduced any undesired effects into it.

In undertaking the restructuring, I started from the philosophy set out
in Chapter 1 and restructured the manual around the order of topics in
the User's Guide. I have also copied some parts of the User's Guide
directly into the manual on the assumption that, if these changes are
acceptable, those parts of the User's Guide can be deleted and replaced
by a reference to the Additional Features manual.

To summarise for the benefit of the Translators:

Chapters 1 and 2 are substantially the same, with only minor changes.

Chapter 3 is half new and half an update of Chapter 6 in the current
manual.

Chapter 4 is all new.

Chapter 5 is an updated Section 3.4 from the current manual and Uwe's
rewrite of Section 8.1 of the current manual.

Chapter 6 is an updated Section 3.5 from the current manual and the
parts of Chapter 3 of the User's Guide which relate to customizing
lists. (So everything to do with customizing lists is in one place.)

Chpater 7 is almost all new but incorporates a small part of Section 6.5
from the User's Guide.

Chapter 8 is an updated Section 3.2 from the current manual.

Chapter 9 is Chapter 7 from the current manual with minor changes.

Chapter 10 is Section 3.3 from the current manual.

Chapter 11 is Chapter 4 from the current manual.

Chapter 12 is Chapter 5 from the current manual.

One option would be to wait until 2.1 comes out; I could then go through
what I have done and add in anything that has been added to the current
version since I did this one.

So far Uwe has gone through my suggestions for the Intro, Tutorial and
User Guide and made them consistent with the style you like. So I would
assume that could be done to this one.

Basically, my idea was to create a framework which would take account of
known changes in 2.1 and be easier to update in future. But I'm not
precious about how this should be used.

John
--




Re: #8577: Additional features manual

2013-03-12 Thread Pavel Sanda
John R. Hudson wrote:
> If there is no way of doing this, then, when I have time, I could go

Ouch, how long did it take to produce the new version of the manual?
One way is to get #6889 fixed, but no one except Vincent knows this
code ATM.

Pavel


Re: #8577: Additional features manual

2013-03-12 Thread John R. Hudson
On Tue, 2013-03-12 at 07:13 +, LyX Ticket Tracker wrote:
>  I was unable to process this file in order to get it into 2.1.
>  - There is no change tracking on to accept changes.
>  - Full scale comparison between 2.1 manual does not work due to bug #6889
>  so one can't reliabble see which section will be deleted in 2.1 in case we
>  just replace 2.1 additional manual by this file.
>  - I'm bombed by messages about missing lilypond class -> anything related
>  to lilypond should be in lilypond manual not here.
> 
>  Do you have version of this manual with CT on?

Sorry no. When I got about a third of the way through the changes I got
a message from TeX saying that I had exceeded the limit for changes. So
I had to turn off changes in order to proceed.

At the time, I did not have a clear idea of where the changes I was
making were leading; so I did not want to submit anything until I had a
clear overall picture of where what I was doing was leading.

Not being fully familiar with git, I was assuming that it would be
possible to backport the changes in git that had been added since I
started and then force git to accept a completely new file to replace
the existing one.

If there is no way of doing this, then, when I have time, I could go
back with the knowledge of where I want to go and submit a series of
incremental changes. But I wouldn't have the time to do that for a few
months.

John
--