Re: Change Tracking Colors (Screen vs PDF)
Kornel, thank you. How do I change the colors? el On 08/02/2019 12:16, Kornel Benko wrote: [...] > The screen and paper are different output devices. Therefore they deserve > different > configuration parameters. (Imagine screen background having the color of > printed 'added/deleted text') > > Kornel > signature.asc Description: OpenPGP digital signature
Re: Change Tracking Colors (Screen vs PDF)
Am Freitag, 8. Februar 2019 10:17:28 CET schrieb Jean-Marc Lasgouttes
:
> Le 08/02/2019 à 10:05, Dr Eberhard Lisse a écrit :
> > Hi,
> >
> > I have been modifying the change colors for a tracked document, using
> > Preferences -> Look&Feel -> Screen Colors, I wanted the switch "changed
> > text 1st author" to be in red and the 3rd author in blue.
> >
> > That works on the screen, but the output has still first author in blue,
> > which I see in the LaTeX document preamble as
> >
> > \providecolor{lyxadded}{rgb}{0,0,1}
> > \providecolor{lyxdeleted}{rgb}{1,0,0}
> >
> > Reason being that if I use Compare Documents an insert of a (single)
> > character is better visible in red than in blue. In the Tracking proper
> > it's ok because it shows the whole word delete and a new word added.
>
> The colors you see here are "added text" and "deleted text". These
> colors are only used for the latex output.
>
> I am not sure why the colors are so different between screen and print.
>
> HTH,
> JMarc
>
The screen and paper are different output devices. Therefore they deserve
different
configuration parameters. (Imagine screen background having the color of
printed 'added/deleted text')
Kornel
signature.asc
Description: This is a digitally signed message part.
Re: Change Tracking Colors (Screen vs PDF)
Le 08/02/2019 à 10:05, Dr Eberhard Lisse a écrit :
Hi,
I have been modifying the change colors for a tracked document, using
Preferences -> Look&Feel -> Screen Colors, I wanted the switch "changed
text 1st author" to be in red and the 3rd author in blue.
That works on the screen, but the output has still first author in blue,
which I see in the LaTeX document preamble as
\providecolor{lyxadded}{rgb}{0,0,1}
\providecolor{lyxdeleted}{rgb}{1,0,0}
Reason being that if I use Compare Documents an insert of a (single)
character is better visible in red than in blue. In the Tracking proper
it's ok because it shows the whole word delete and a new word added.
The colors you see here are "added text" and "deleted text". These
colors are only used for the latex output.
I am not sure why the colors are so different between screen and print.
HTH,
JMarc
RE: Change tracking + fancy headers + changed section = error
>From: Scott Kostyshak [skost...@lyx.org] >Sent: Thursday, February 04, 2016 12:40 PM >To: lyx-users@lists.lyx.org >Subject: Re: Change tracking + fancy headers + changed section = error > >On Thu, Feb 04, 2016 at 05:32:17PM +, Denniston, Todd A CIV >NAVSURFWARCENDIV Crane >wrote: >> Scott, >> looks like one more reason to pull up to RHEL 7 as soon as possible, epel 7 >> has lyx 2.1.3, and RHEL 7 includes texlive-2012. >> Thanks again for the feedback. > >Sounds like a good plan, Todd. In case you want to confirm my claim that >the fix is due to LyX and not TeX Live (and thus there should be no >concern of differences due to the fact that I'm on TL 2015 and you will >be on TL 2012), I've attached the .tex file that LyX 2.1.3 produces. If >you can compile this and the result is as expected, then you're set. > >Scott Thanks for the test file, it does indeed produce the expected output when ran through pdflatex on my system. Apparently the DeclareRobustCommand** is considerably more robust. :) ** the old version of LyX exported \newcommand the new one exports \DeclareRobustCommand Even when this disclaimer is not here: I am not a contracting officer. I do not have authority to make or modify the terms of any contract.
Re: Change tracking + fancy headers + changed section = error
On Thu, Feb 04, 2016 at 05:32:17PM +, Denniston, Todd A CIV NAVSURFWARCENDIV Crane wrote: > Scott, > looks like one more reason to pull up to RHEL 7 as soon as possible, epel 7 > has lyx 2.1.3, and RHEL 7 includes texlive-2012. > Thanks again for the feedback. Sounds like a good plan, Todd. In case you want to confirm my claim that the fix is due to LyX and not TeX Live (and thus there should be no concern of differences due to the fact that I'm on TL 2015 and you will be on TL 2012), I've attached the .tex file that LyX 2.1.3 produces. If you can compile this and the result is as expected, then you're set. Scott TC_sections.tex Description: TeX document signature.asc Description: PGP signature
RE: Change tracking + fancy headers + changed section = error
Scott, looks like one more reason to pull up to RHEL 7 as soon as possible, epel 7 has lyx 2.1.3, and RHEL 7 includes texlive-2012. Thanks again for the feedback. Even when this disclaimer is not here: I am not a contracting officer. I do not have authority to make or modify the terms of any contract. From: Scott Kostyshak [skost...@lyx.org] Sent: Thursday, February 04, 2016 12:20 PM To: lyx-users@lists.lyx.org Subject: Re: Change tracking + fancy headers + changed section = error Hi Todd, Your example file works for me with LyX 2.1.3 as well as the development version of 2.2.0. I am using TeX Live 2015 on Ubuntu but I expect this depends more on the LyX version than the TeX Live version. Attached is the PDF that is created for me. Scott On Thu, Feb 04, 2016 at 04:28:54PM +, Denniston, Todd A CIV NAVSURFWARCENDIV Crane wrote: > It appears that if you are generating PDFs with fancy headers on, and change > tracking, that changing the last section of a page (the one that ends up in > the fancy header) is not allowed. > See attached minimal example file, poking the 'View PDF (pdflatex)' button > should generate the error. > > The error is "Package xcolor Error: Undefined color 'LYXADDED'." > > 1. Can someone verify that this is still a problem in the newest version of > LyX? (my distro is still using lyx 1.6.10 & texlive-2007-60) > 1a. if it seems to be working, please state lyx and *tex version, so I know > when I should see relief from this error. [I have worked around it by just > 'accepting' the changed section, but it is always confusing when I hit it.] > 2. If it is still an existing problem, could someone with a > www.lyx.org/trac/wiki/BugTrackerHome login please enter an appropriate ticket? > > > Thanks. > > Even when this disclaimer is not here: > I am not a contracting officer. I do not have authority to make or modify the > terms of any contract.
Re: Change tracking + fancy headers + changed section = error
Hi Todd, Your example file works for me with LyX 2.1.3 as well as the development version of 2.2.0. I am using TeX Live 2015 on Ubuntu but I expect this depends more on the LyX version than the TeX Live version. Attached is the PDF that is created for me. Scott On Thu, Feb 04, 2016 at 04:28:54PM +, Denniston, Todd A CIV NAVSURFWARCENDIV Crane wrote: > It appears that if you are generating PDFs with fancy headers on, and change > tracking, that changing the last section of a page (the one that ends up in > the fancy header) is not allowed. > See attached minimal example file, poking the 'View PDF (pdflatex)' button > should generate the error. > > The error is "Package xcolor Error: Undefined color 'LYXADDED'." > > 1. Can someone verify that this is still a problem in the newest version of > LyX? (my distro is still using lyx 1.6.10 & texlive-2007-60) > 1a. if it seems to be working, please state lyx and *tex version, so I know > when I should see relief from this error. [I have worked around it by just > 'accepting' the changed section, but it is always confusing when I hit it.] > 2. If it is still an existing problem, could someone with a > www.lyx.org/trac/wiki/BugTrackerHome login please enter an appropriate > ticket? > > > Thanks. > > Even when this disclaimer is not here: > I am not a contracting officer. I do not have authority to make or modify the > terms of any contract. TC_sections.pdf Description: Adobe PDF document signature.asc Description: PGP signature
Re: Change tracking: no change bar in PDF output
2015-12-30 16:40 GMT+01:00 Rudi Gaelzer : > There is a possible bug here: > Using change tracking with PDF output (pdflatex), the \lyxdeleted and > \lyxadded > commands work as supposed (respectively: read, strike out and blue). > However, > the change bar is not printed at the margin. > This is not a bug (you can call it a missing feature). LyX is not supposed to print a change bar in the output. You can find a module that implements the feature here: http://wiki.lyx.org/Layouts/Modules This module will be part of LyX 2.2. Jürgen
Re: change tracking
Le 02/02/2015 11:48, Patrick Dupre a écrit : Hello, The tool change tracking is very convenient. However, it seems that it does not work in formula mode. Did I miss something? Unfortunately not. This is not yet implemented. JMarc
Re: Change tracking and the fate of deleted text
EK writes:
> At Julien's advice, this is what I have put in the preamble. It works
> fine outside the captions.
>
> \usepackage{color}
>
> \renewcommand{\lyxdeleted}[3]{{\color{red}*}\marginpar{{\color{red}*#3}
> (removed by #1 on #2)}}
>
> \renewcommand{\lyxadded}[3]{{\color{blue}#3}}
Try to add \protect in front of \color, and then in front of \marginpar.
JMarc
Re: Change tracking and the fate of deleted text
At Julien's advice, this is what I have put in the preamble. It works
fine outside the captions.
\usepackage{color}
\renewcommand{\lyxdeleted}[3]{{\color{red}*}\marginpar{{\color{red}*#3}
(removed by #1 on #2)}}
\renewcommand{\lyxadded}[3]{{\color{blue}#3}}
EK
On 6/2/2010 6:47 AM, Jean-Marc LASGOUTTES wrote:
"ehud.kap...@gmail.com" writes:
Although I applauded the suggested additions to the preamble, which
made Lyx place deleted text in the margin, I have now discovered that
Lyx will fail to compile (pdflatex) /if the change is made to a figure
caption/. Is there a quick fix to this fix?
What is the definition that you use? You may need to use \protect,
because the contents of a caption is a so called ``moving argument''.
JMarc
Re: Change tracking and the fate of deleted text
"ehud.kap...@gmail.com" writes: > Although I applauded the suggested additions to the preamble, which > made Lyx place deleted text in the margin, I have now discovered that > Lyx will fail to compile (pdflatex) /if the change is made to a figure > caption/. Is there a quick fix to this fix? What is the definition that you use? You may need to use \protect, because the contents of a caption is a so called ``moving argument''. JMarc
re: Change tracking and the fate of deleted text
Although I applauded the suggested additions to the preamble, which made Lyx place deleted text in the margin, I have now discovered that Lyx will fail to compile (pdflatex) /if the change is made to a figure caption/. Is there a quick fix to this fix? Thanks, EK --
Re: Change tracking and the fate of deleted text
On 2010-05-31, E. Kaplan wrote: > I am aware that you can disable the Show changes in the output, but that > is not what the user wants-- she wants to see the changed text without > losing deleted text. She could try with version control: only the most recent text is seen (and known to LyX), but earlier versions are not lost but available for recovery. Drawback: there is no provision for "restore this paragraph" but only "restore the document to version X". Günter
Re: Change tracking and the fate of deleted text
I love it! That's just what I had in mind. Ehud Kaplan, Ph.D. Jules and Doris Stein/Research to Prevent Blindness/ Professor *The laboratory of Visual& Computational Neuroscience* Depts. of Neuroscience, Ophthalmology, Chemical& Structural Biology The Mount Sinai School of Medicine One Gustave Levy Place New York, NY, 10029 On 5/31/2010 10:19 AM, Julien Rioux wrote: On 31/05/2010 8:40 AM, E. Kaplan wrote: I realize that this is a BIG request, but it might reflect the wishes of others. In MS WORD, when text is deleted (with /change tracking/ turned on), the deleted text is shown in the margin, and the newly-flowed or inserted text is shown in the body of the document. This makes it easier to detect any missing spaces, judge space compliance etc. In Lyx, the deleted and inserted text are shown together in both Lyx and the pdf output. The WORD method is far superior. I am not going to return to WORD because of it, but since the change tracking feature is one of the main reasons I use Lyx instead of plain Latex, it would be really nice if something like that could be implemented-- perhaps inserting the new text and making the deleted text appear as a comment. Before you tell me how hard it is-- see my first sentence. Hi, It can be done in the LaTeX output by redefining the commands \lyxadded and \lyxdeleted to your liking. But you are right it would be much harder to implement inside the LyX editor. Cheers, Julien
Re: Change tracking and the fate of deleted text
"What is the use of having it in an (unfolded) comment ? Then it still obfuscates the text." IMHO the ideal solution is the one WORD uses-- show the text as it would be after the changes, but do not discard the deleted text-- they keep it in the margins, which might be difficult to implement, so I suggested keeping it as comments. I am aware that you can disable the Show changes in the output, but that is not what the user wants-- she wants to see the changed text without losing deleted text. EK Ehud Kaplan, Ph.D. Jules and Doris Stein/Research to Prevent Blindness/ Professor *The laboratory of Visual& Computational Neuroscience* Depts. of Neuroscience, Ophthalmology, Chemical& Structural Biology The Mount Sinai School of Medicine One Gustave Levy Place New York, NY, 10029 On 5/31/2010 11:35 AM, Vincent van Ravesteijn wrote: What is the use of having it in an (unfolded) comment ? Then it still obfuscates the text.
Re: Change tracking and the fate of deleted text
On 31/05/2010 18:07, RGH wrote: On 05/31/2010 10:19 AM, Julien Rioux wrote: On 31/05/2010 8:40 AM, E. Kaplan wrote: I realize that this is a BIG request, but it might reflect the wishes of others. In MS WORD, when text is deleted (with /change tracking/ turned on), the deleted text is shown in the margin, and the newly-flowed or inserted text is shown in the body of the document. This makes it easier to detect any missing spaces, judge space compliance etc. In Lyx, the deleted and inserted text are shown together in both Lyx and the pdf output. The WORD method is far superior. I am not going to return to WORD because of it, but since the change tracking feature is one of the main reasons I use Lyx instead of plain Latex, it would be really nice if something like that could be implemented-- perhaps inserting the new text and making the deleted text appear as a comment. Before you tell me how hard it is-- see my first sentence. Hi, It can be done in the LaTeX output by redefining the commands \lyxadded and \lyxdeleted to your liking. But you are right it would be much harder to implement inside the LyX editor. I'm not sure how hard this is, actually. But then, I'm not quite sure what this would look like in LyX. The margins aren't large enough as the display currently is. No need to, the "List of Changes" in the outline panel does exactly that. And about hiding optionally the deleted text it's already implemented in trunk IIRC, or at least there's a proposed patch. Abdel.
Re: Change tracking and the fate of deleted text
On 05/31/2010 10:19 AM, Julien Rioux wrote: On 31/05/2010 8:40 AM, E. Kaplan wrote: I realize that this is a BIG request, but it might reflect the wishes of others. In MS WORD, when text is deleted (with /change tracking/ turned on), the deleted text is shown in the margin, and the newly-flowed or inserted text is shown in the body of the document. This makes it easier to detect any missing spaces, judge space compliance etc. In Lyx, the deleted and inserted text are shown together in both Lyx and the pdf output. The WORD method is far superior. I am not going to return to WORD because of it, but since the change tracking feature is one of the main reasons I use Lyx instead of plain Latex, it would be really nice if something like that could be implemented-- perhaps inserting the new text and making the deleted text appear as a comment. Before you tell me how hard it is-- see my first sentence. Hi, It can be done in the LaTeX output by redefining the commands \lyxadded and \lyxdeleted to your liking. But you are right it would be much harder to implement inside the LyX editor. I'm not sure how hard this is, actually. But then, I'm not quite sure what this would look like in LyX. The margins aren't large enough as the display currently is. Richard
Re: Change tracking and the fate of deleted text
On 05/31/2010 11:46 AM, Rudi Gaelzer wrote: Julien, how do I redefine the \lyxadded and \lyxdeleted from inside the LyX editor? Your suggestion seems very useful. Document>Settings>LaTeX Preamble. You can do what you like there. rh
Re: Change tracking and the fate of deleted text
Julien, how do I redefine the \lyxadded and \lyxdeleted from inside the LyX editor? Your suggestion seems very useful. On Monday 31 May 2010 11:19:04 Julien Rioux wrote: > Hi, > It can be done in the LaTeX output by redefining the commands \lyxadded > and \lyxdeleted to your liking. But you are right it would be much > harder to implement inside the LyX editor. -- Rudi Gaelzer Department of Physics Institute of Physics and Mathematics Federal University of Pelotas BRAZIL Registered linux user # 153741
Re: Change tracking and the fate of deleted text
On 31/05/2010 8:40 AM, E. Kaplan wrote: I realize that this is a BIG request, but it might reflect the wishes of others. In MS WORD, when text is deleted (with /change tracking/ turned on), the deleted text is shown in the margin, and the newly-flowed or inserted text is shown in the body of the document. This makes it easier to detect any missing spaces, judge space compliance etc. In Lyx, the deleted and inserted text are shown together in both Lyx and the pdf output. The WORD method is far superior. I am not going to return to WORD because of it, but since the change tracking feature is one of the main reasons I use Lyx instead of plain Latex, it would be really nice if something like that could be implemented-- perhaps inserting the new text and making the deleted text appear as a comment. Before you tell me how hard it is-- see my first sentence. Hi, It can be done in the LaTeX output by redefining the commands \lyxadded and \lyxdeleted to your liking. But you are right it would be much harder to implement inside the LyX editor. Cheers, Julien change-tracking-in-margin.lyx Description: application/lyx
Re: Change tracking
On 01/23/2010 04:59 AM, E. Kaplan wrote: It seems that inserting notes into a Lyx file while tracking changes modifies the color of some parts of the text in the pdf output to blue, misleading the reader to believe that the blue text is new insertions, while it is not. This is true of both 1.6.4 (on Kubuntu 9.10, 64 bit) and 1.6.5 (Windows XP). Is this a bug? It certainly is not a helpful feature! Can you post an example file? What are you seeing in the LaTeX output? rh
Re: Change tracking ... in Lyx
Guenter Milde wrote: On 2009-01-04, Unknown wrote: What's the way to track changes made in a Lyx document? I know there's a patch for earlier versions [...]but is there something now for 1.6.1? Yes, change tracking is supported by default in 1.5.x and 1.6.x. Document>Change Tracking. rh
Re: Change tracking ... in Lyx
On 2009-01-04, Unknown wrote: > What's the way to track changes made in a Lyx document? I know there's > a patch for earlier versions [...]but is there something now for 1.6.1? Yes, change tracking is supported by default in 1.5.x and 1.6.x. Günter
Re: Change tracking in LyX and multiple users
G. Milde wrote: How do you generally track the changes in your documents ? * LyX has in-built support for RCS [etc etc] And it would not be a lot of work to convert it to CVS, SVN, etc. I've been kind of meaning to do this, as have a lot of other people, but other things always intervene, and I have limited time. But if anyone out there would like to get involved in this way, as I said, it wouldn't be too bad, and it would be a great way to start to learn about the LyX code. I'd be happy to guide someone through this. rh
Re: Change tracking in LyX and multiple users
On Nov 9 2007, [EMAIL PROTECTED] wrote: I want to track changes in LyX in the same way that I do with my computer programs in C++, and for that purpose I use CVS. I look at the mail list but did not found relevant information about this. Over the years, I've used the built-in support in LyX for RCS (works very well for individual use only) every now and again but usually use one of the distributed revision control systems. My current favourite is Mercurial but SVN and Darcs have also worked well for me in the past for LyX files. cheers, eric
Re: Change tracking in LyX and multiple users
On 8.11.07, [EMAIL PROTECTED] wrote: > I want to track changes in LyX in the same way that I do with my computer > programs in C++, and for that purpose I use CVS. > How do you generally track the changes in your documents ? * LyX has in-built support for RCS > think is the best system ? Do you recommend CVS or another one ? * If you are familiar and satisfied with CVS, stick to it. * I prefer SVN (e.g. because this allows easier renaming/moving of files) it it stable, very similar in the user interface and widely used. * For personal use, I take SVK, as it doesnot put a CVS/ or .svn/ sub-directory in every dir of the work copy. > By the way, my objective is also to have several users working on the same > LyX document at the same time. What do you think is the best approach ? In this case, using RCS does not help. I'd go for a common CVS or SVN repository. In case of conflicts, you will need to deal with the lyx source, so have a look at a lyx source file in a text-editor before and decide whether all co-workers would be able to make sense of it. Guenter
Re: Change Tracking not visible in output. How to install {xcolor} and {soul}?
Hi, I experience the same problem on my Mac running LyX 1.5.1. When I look at "Tools/TeX Information/LaTeX styles" I see both, "xcolor.sty" and "soul.sty". I tested "xcolor" form the terminal and it worked. "Soul" contains as far as I can tell only the .sty file, so copying it to a location included in the path should do (and it is even recognized by LyX). Doesn't solve the problem however ... Kurt > I'd like to see the change tracking in the pdflatex output. However, I > only get the error that I've to install xcolor and soul or define > \lyxdeleted and \lyxadded. As I'm not a latex professional I couldn't > really figure out how to do that. > > Any Ideas? (You have been great so far :-)!) > > btw: I'm running lyx 1.5.0 on Ubuntu 7.04 > > Cheers > Michael
Re: Change Tracking not visible in output. How to install {xcolor} and {soul}?
On 9/5/07, Michael Beckmann <[EMAIL PROTECTED]> wrote: > Dear Lyx Users! > Any Ideas? (You have been great so far :-)!) > > btw: I'm running lyx 1.5.0 on Ubuntu 7.04 Both are part of the packages provided by ubuntu, so you can use whatever package management tool you prefer to install them. xcolor is provided the latex-xcolor package in universe. soul is part of the tetex-extra package, which is in main. hope that helps -- Neil Muller
Re: change tracking in 1.4.2
Jean-Marc Lasgouttes wrote: > And dvipost.sty is in the tex search path? I.e., what do you get with kpsewhich dvipost.sty Matěj -- GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC http://www.ceplovi.cz/matej/blog/, Jabber: [EMAIL PROTECTED] 23 Marion St. #3, (617) 876-1259, ICQ 132822213 I have never killed a man, but I have read many obituaries with great pleasure. -- Clarence Darrow
Re: change tracking in 1.4.2
> "Martin" == Martin A Hansen <[EMAIL PROTECTED]> writes: Martin> whoops, i mistyped the original message. i have dvipost Martin> installed already, but apparently lyx is not aware. And dvipost.sty is in the tex search path? JMarc
Re: change tracking in 1.4.2
whoops, i mistyped the original message. i have dvipost installed already, but apparently lyx is not aware. martin On 8/25/06, Matej Cepl <[EMAIL PROTECTED]> wrote: Martin A. Hansen wrote: > what can i do? Install dvipost (http://freshmeat.net/projects/dvipost/ or from your distribution) Matěj -- GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC http://www.ceplovi.cz/matej/blog/, Jabber: [EMAIL PROTECTED] 23 Marion St. #3, (617) 876-1259, ICQ 132822213 Home is where ~/.bashrc is. -- from Usenet
Re: change tracking in 1.4.2
Martin A. Hansen wrote: > what can i do? Install dvipost (http://freshmeat.net/projects/dvipost/ or from your distribution) Matěj -- GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC http://www.ceplovi.cz/matej/blog/, Jabber: [EMAIL PROTECTED] 23 Marion St. #3, (617) 876-1259, ICQ 132822213 Home is where ~/.bashrc is. -- from Usenet
Re: Change tracking
Nicolás wrote: > Hello! > > Right now the change tracking feature does only allow to reject or > accept all changes. This is a very restrictive behaviour. Normally one > wants to accept some changes and reject others. Sure you can. Document->Change Tracking->Merge Changes. Jürgen
Re: change tracking
David M Hunter wrote: > Angus, as a windows newbie I have managed to create a new windows Lyx > with the tracking changes. Well now, that's an amazing accomplishment. I'm truly impressed. > Compilation was very lengthy Indeed. > and I used the > MinWG platform and method you outlined in your notes. That's Minimal Gnu for Windows (MinGW) together with Minimal SYStem (MSYS). Together MinGW/MSYS. > Not familiar with making "builds" I have not made a "package" but > created a new Lyx executable based on the stable 1.3.6 source code. Is that BRANCH_1_3_X of the lyx-devel repository? If not, you really should use this. Lots and lots of tiresome little bugs have been squashed. If you're interested in the packaging, read the README, same directory which details the steps I take to go on and package it all up. You'll be especially interested in the package_lyxwin.sh script which, despite its name, doesn't package anything but indulges in a few tricks to create a truly useful (working) system on Windows. It transpires that "paths with spaces" are a real pain in the LaTeX world and we must jump through a few hoops to make things less unpleasant. That's package_lyxwin.sh. > I am stuck on a problem with dvipost. Dvipost is necessary to create a > final printable document. I don't know how to compile it without errors > on the MinGW system and I'm also foggy about where it should reside > should I succeed in compiling it. Compilation problems: see the bottom of this mail. Where to put the resulting executable? MiKTeX's binaries appear to live in C:\MiKTeX\Main\miktex\bin Don't put the thing there because Main is for official MiKTeX stuff. However, there's also a C:\MiKTeX\Local directory tree for your own, unofficial additions. So C:\MiKTeX\Local\miktex\bin I'm not sure if you need to explicitly add this directory to your PATH for MikTeX to find executables therein. FWIW, here's my own personal MSYS .bashrc file (as seen from my linux box) which tunes my MSYS environment. You could also adjust the PATH from the Start menu. $ cat /mnt/windowsJ/MSYS/home/angus/.bashrc #! /bin/sh alias ls="ls --color -F" alias rm="rm -i" PATH=$HOME/bin:/j/emacs-21.3/bin:$PATH; export PATH > A few questions: > Should I try to learn and follow your method for creating a package (is > it the same as the windows installer package?) and in doing so would it > solve all my problems, including the dvipost one? I ask these questions > because things take a long time to compile. Running package_lyxwin.sh will take a few seconds and its well worth doing. Creating the Windows Installer is a useful exercise if you're going to make this stuff available to others. You'll need to install NSIS, compile lyx_configure.C and put the resulting lyx_configure.dll in C:\Program Files\NSIS\Plugins\ Thereafter, building the installer is as simple as C:\Program Files\NSIS\makensis lyx_installer.nsi > Thanks for your time. Again, at the risk of being tiresome, I wish to > point out that I am doing this work to try bring windows users (I am not > a windows user) to Lyx, Linux and opensource software. You don't need to justify yourself ;-) You'll notice I haven't answered the dvipost questions. Mail me privately with more info about your problems. Regards, -- Angus
Re: change tracking
Angus Leeming wrote: David M Hunter wrote: Hi, Yesterday I applied the tracking changes patch to my Lyx on my Linux box and the tracking works ok with a few caveats. However I work with a colleague who uses word to write documents and he might be convinced to use lyx if tracking were implemented. Is it possible to apply the tracking change to the windows lyx version (he uses windows) or will it be necessary to wait for version 1.4? Sure. The source for linux and for Windows is identical, so if the patch can be applied on linux it can also be applied on Windows. Building takes a while but the scripts in development/Win32/packaging should automate the process. See http://article.gmane.org/gmane.editors.lyx.devel/49989 for how I go about packaging LyX 1.3.x on Windows. Angus Angus, as a windows newbie I have managed to create a new windows Lyx with the tracking changes. Compilation was very lengthy and I used the MinWG platform and method you outlined in your notes. Not familiar with making "builds" I have not made a "package" but created a new Lyx executable based on the stable 1.3.6 source code. I am stuck on a problem with dvipost. Dvipost is necessary to create a final printable document. I don't know how to compile it without errors on the MinGW system and I'm also foggy about where it should reside should I succeed in compiling it. A few questions: Should I try to learn and follow your method for creating a package (is it the same as the windows installer package?) and in doing so would it solve all my problems, including the dvipost one? I ask these questions because things take a long time to compile. Thanks for your time. Again, at the risk of being tiresome, I wish to point out that I am doing this work to try bring windows users (I am not a windows user) to Lyx, Linux and opensource software. Sincerely, David Hunter
Re: change tracking
Angus Leeming wrote: David M Hunter wrote: Hi, Yesterday I applied the tracking changes patch to my Lyx on my Linux box and the tracking works ok with a few caveats. However I work with a colleague who uses word to write documents and he might be convinced to use lyx if tracking were implemented. Is it possible to apply the tracking change to the windows lyx version (he uses windows) or will it be necessary to wait for version 1.4? Sure. The source for linux and for Windows is identical, so if the patch can be applied on linux it can also be applied on Windows. Building takes a while but the scripts in development/Win32/packaging should automate the process. Thanks! I'm a windows ignoramus and I wasn't sure how things are done on windows. I'll try it! Thanks very much. David H See http://article.gmane.org/gmane.editors.lyx.devel/49989 for how I go about packaging LyX 1.3.x on Windows. Angus
Re: change tracking
David M Hunter wrote: Hi, Yesterday I applied the tracking changes patch to my Lyx on my Linux box and the tracking works ok with a few caveats. However I work with a colleague who uses word to write documents and he might be convinced to use lyx if tracking were implemented. Is it possible to apply the tracking change to the windows lyx version (he uses windows) or will it be necessary to wait for version 1.4? Sure. The source for linux and for Windows is identical, so if the patch can be applied on linux it can also be applied on Windows. Building takes a while but the scripts in development/Win32/packaging should automate the process. See http://article.gmane.org/gmane.editors.lyx.devel/49989 for how I go about packaging LyX 1.3.x on Windows. Angus
Re: change tracking feature extension request.
On Tue, Apr 20, 2004 at 02:06:07PM -0300, Ralph Boland wrote: > 1) I don't want users to send me a complete file > (say the size of the lyx user's guide) >just to point out a few minor mistakes. >They could instead send me a diff file >of the two verions of the documentations and I could then >reconstruct their verion of the documentation from from >my copy of the original lyx document and the diff file. > > This all sounds quite complicated. >Instead, lyx could have a command > "createLyxDiff" > which creates this diff file (say doc.lyx.diff) or (preferably) > some other file containing the necessary information. > The user then sends me the file doc.lyx.diff. I then run lyx > on my copy of the docuumentation and from lyx run the command >"installDiffFile: doc.lyx.diff" What's wrong with you send foo.lyx to co-author, change-tracking enabled co-author creates copy foo.lyx.orig co-author changes foo.lyx co-author runs diff foo.lyx.orig foo.lyx | mail whatever you run patch < foo.diff you check his changes ? > 2)If the above feature is implemented then there is a problem. > If two users send me change files to > update my documentation then once I update the documentation > based on one of the files, the other file will not match > correctly with the updated version of the document since > it was created based on the older original version of > the documentation. > Thus the "installDiffFile:" command needs > to be able to load multiple (possibly a large number) of > doc.lyx.diff.num files at one time and > the change tracking facility of lyx needs to support processing > them all at one time. LyX will certainly not implement the functionality of diff/diff3 and patch, given that these things exist already. > With this feature when the document is released > it would have embedded in it a date stamp. > Once that date is reached copies of the document would not > allow change tracking to be used (with some kind of > override facility of course). > Also, once that date is reached I would run > lyx on the document and all the doc.lyx.diff.num files I have > received and update the documentation accordingly. > I would then release the new version of the documentation > with a new embedded date stamp. > > Note that this implies documentation releases, > much more often then say the sofware releases. > I believe this mechanism will result in much more rapid > development of user documentation. Why not simply set up a cvs server and be done? Andre'
Re: change tracking feature extension request.
One solution for the fear of large documents being sent for change tracking. Generate a top level document that is nothing more than \include filenames of every piece of the document and offer a reference within the finished document which part of the overall document this section references. myCompleteDocument.lyx As a structure it would appear as a sort of meta document. If we wanted to worry about every little nuance why not just integrate Subversion as an optional Service with LyX and people could commit changes to documents and once verified they could fork that to a release update. -Marc J. Driftmeyer On Tuesday 20 April 2004 10:06, Ralph Boland wrote: > As a lyx user I am forever thankful (and forever expecting more) > for the work of lyx developers. > I read on the internet that lyx 1.4 supports change tracking. > > I will be glad to use this feature once lyx 1.4 is released > but I already want more. > > I am developing a parser generator tool and when I release it the > documentation will be in Lyx. > > I would like for users who find errors in the documentation > to be able to send me files pointing out these errors. > Change tracking will allow a way of doing this. > Users can simply send me a copy of the documentation containing > the proposed changes that they added using the change tracking facility. > > But a number of problems immediately come to mind. > > 1) I don't want users to send me a complete file > (say the size of the lyx user's guide) > just to point out a few minor mistakes. > They could instead send me a diff file > of the two verions of the documentations and I could then > reconstruct their verion of the documentation from from > my copy of the original lyx document and the diff file. > >This all sounds quite complicated. > Instead, lyx could have a command >"createLyxDiff" >which creates this diff file (say doc.lyx.diff) or (preferably) >some other file containing the necessary information. >The user then sends me the file doc.lyx.diff. I then run lyx >on my copy of the docuumentation and from lyx run the command > "installDiffFile: doc.lyx.diff" >which morphs my copy of the documention to > the users version containing his/her comments. > I then run the change tracking facility features to update the > documentation. > I think that this would be nice feature but it has problems of its > own. > > 2)If the above feature is implemented then there is a problem. >If two users send me change files to > update my documentation then once I update the documentation > based on one of the files, the other file will not match > correctly with the updated version of the document since > it was created based on the older original version of > the documentation. > Thus the "installDiffFile:" command needs > to be able to load multiple (possibly a large number) of > doc.lyx.diff.num files at one time and > the change tracking facility of lyx needs to support processing > them all at one time. > > With this feature when the document is released > it would have embedded in it a date stamp. > Once that date is reached copies of the document would not > allow change tracking to be used (with some kind of > override facility of course). > Also, once that date is reached I would run > lyx on the document and all the doc.lyx.diff.num files I have > received and update the documentation accordingly. > I would then release the new version of the documentation > with a new embedded date stamp. > > Note that this implies documentation releases, > much more often then say the sofware releases. > I believe this mechanism will result in much more rapid > development of user documentation. > It should result in documentation that is very clean in terms > of typos (but of course doesn't guaranttee quality documention). > Since the documentation for Lyx is in Lyx, the first > benifitiary of this feature could be Lyx itself. > > Comments welcome. > > Ralph Boland
Re: Change tracking for LyX 1.3.2 (QT)
On August 20, 2003 01:16 am, Nirmal Govind wrote: > > You're right! Unfortunately they don't use LyX, although I just got > > the change tracking working last week, so there's opportunity to bring > > them onside :). > > I guess so.. I'm trying myself to get some converts.. :-) > > > examiner, with a CVS commit in between each set. My motivation for the > > thesis is to make it easier to point my advisor to the changes so he > > can see how I've implemented the various suggestions (follow the > > vertical blue bars). Then I'll merge them myself based on his > > feedback. > > That sounds like a great plan.. I think I'll apply your patch and follow > your style of changing/commiting.. that way I guess I can always revert > to something that was there earlier but was removed somewhere down the > line... now do I have the luxury of choosing which changes I want to > revert and which not when I revert to an older version of the file? Yes, you can go through the changes one-by-one, and either accept or reject them. It's easy to accept or reject one particular change as well, because the merge dialog starts looking for changes at the current cursor position. There is also the option of accepting or rejecting all changes at once. JB -- Johnathan K. Burchill, Ph.D. Department of Physics and Astronomy University of Calgary 2500 University Drive N.W. Calgary, AB T2N 1N4 Canada (403) 217-4286 [EMAIL PROTECTED]
Re: Change tracking for LyX 1.3.2 (QT)
On August 19, 2003 10:36 pm, Nirmal Govind wrote: > Hello Johnathan.. just curious - how exactly did you use the change > tracking stuff.. I mean, was it just you making changes to your thesis > and deciding, based on comments from your advisors I guess, as to > whether to apply them? Or did your advisors also use LyX (my guess is > no! :-)).. You're right! Unfortunately they don't use LyX, although I just got the change tracking working last week, so there's opportunity to bring them onside :). I use the change tracking in combination with CVS. I commited the submitted version, then went through all the suggested changes, examiner by examiner, with a CVS commit in between each set. My motivation for the thesis is to make it easier to point my advisor to the changes so he can see how I've implemented the various suggestions (follow the vertical blue bars). Then I'll merge them myself based on his feedback. JB > thanks, > nirmal -- Johnathan K. Burchill, Ph.D. Department of Physics and Astronomy University of Calgary 2500 University Drive N.W. Calgary, AB T2N 1N4 Canada (403) 217-4286 [EMAIL PROTECTED]
