Re: Trouble with track changes appearing in pdflatex views

[Julien Rioux]

On 28/11/2012 9:19 AM, Richard Heck wrote:

On 11/27/2012 03:01 PM, Allen Wilkinson wrote:

My problem is that if I want to show tracked changes in PDF view or
output I get these errors:

Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the
document is small enough, then PDF output with tracked changes works.

This is true whether I use Lyx PDF viewing, or run OS' pdflatex
compiler on exported .tex file.

If I disable 'show changes in output', then PDF output occurs without
errors.

Can anyone help me resolve this problem?


Odd that the undefined color is in all caps. Is LyX exporting this wrong?

I think we can only answer this with a test file that causes the problem.

rh




The headers from that document class must be all caps. A similar error 
happened with changes in section titles with the revtex document class, 
which use all caps section titles. For some reason latex thinks that it 
should also capitalize the color names. A workaround is to also define 
the colors with capitalized names! c.f. http://www.lyx.org/trac/ticket/4625


Regards,
Julien

Re: Trouble with track changes appearing in pdflatex views

[Julien Rioux]

On 28/11/2012 9:19 AM, Richard Heck wrote:

On 11/27/2012 03:01 PM, Allen Wilkinson wrote:

My problem is that if I want to show tracked changes in PDF view or
output I get these errors:

Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the
document is small enough, then PDF output with tracked changes works.

This is true whether I use Lyx PDF viewing, or run OS' pdflatex
compiler on exported .tex file.

If I disable 'show changes in output', then PDF output occurs without
errors.

Can anyone help me resolve this problem?


Odd that the undefined color is in all caps. Is LyX exporting this wrong?

I think we can only answer this with a test file that causes the problem.

rh




The headers from that document class must be all caps. A similar error 
happened with changes in section titles with the revtex document class, 
which use all caps section titles. For some reason latex thinks that it 
should also capitalize the color names. A workaround is to also define 
the colors with capitalized names! c.f. http://www.lyx.org/trac/ticket/4625


Regards,
Julien

Re: Trouble with track changes appearing in pdflatex views

[Julien Rioux]

On 28/11/2012 9:19 AM, Richard Heck wrote:

On 11/27/2012 03:01 PM, Allen Wilkinson wrote:

My problem is that if I want to show tracked changes in PDF view or
output I get these errors:

Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the
document is small enough, then PDF output with tracked changes works.

This is true whether I use Lyx PDF viewing, or run OS' pdflatex
compiler on exported .tex file.

If I disable 'show changes in output', then PDF output occurs without
errors.

Can anyone help me resolve this problem?


Odd that the "undefined color" is in all caps. Is LyX exporting this wrong?

I think we can only answer this with a test file that causes the problem.

rh




The headers from that document class must be all caps. A similar error 
happened with changes in section titles with the revtex document class, 
which use all caps section titles. For some reason latex thinks that it 
should also capitalize the color names. A workaround is to also define 
the colors with capitalized names! c.f. http://www.lyx.org/trac/ticket/4625


Regards,
Julien

Re: Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

Richard,

where would I file bug report? web page?

Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

On Thu, 29 Nov 2012, Richard Heck wrote:


On 11/28/2012 04:12 PM, Allen Wilkinson wrote:

Richard,

That helped, thanks.

I went back and tested my troubled file. I commented out the nagauth 
\runningheads line (as a tracked change) and all changes were displayed in 
the PDF.


Must be \runningheads definition tramples on something that track changes 
needs.


The change tracking stuff loads soul and xcolor, I think, and there could be 
some kind of incompatibility there. Hard to know.


If you care to debug this for proper nagauth styles, I'll send you the 
nagauth.cls file. I'm not sure I know latex well enough to do it myself.


If you could file a bug report and attach the problematic file and either 
attach or link to ngauth.cls, that'd be great.


rh

Re: Trouble with track changes appearing in pdflatex views

[Scott Kostyshak]

On Thu, Nov 29, 2012 at 7:50 AM, Allen Wilkinson a...@chaff.biz wrote:
 Richard,

 where would I file bug report? web page?

http://www.lyx.org/trac

Thanks,

Scott



 Allen
 
 Address:

 Allen Wilkinson   (cell)  (216) 548-2349
 1286 Yellowstone Road
 Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
 +++

 On Thu, 29 Nov 2012, Richard Heck wrote:

 On 11/28/2012 04:12 PM, Allen Wilkinson wrote:

 Richard,

 That helped, thanks.

 I went back and tested my troubled file. I commented out the nagauth
 \runningheads line (as a tracked change) and all changes were displayed in
 the PDF.

 Must be \runningheads definition tramples on something that track changes
 needs.

 The change tracking stuff loads soul and xcolor, I think, and there could
 be some kind of incompatibility there. Hard to know.

 If you care to debug this for proper nagauth styles, I'll send you the
 nagauth.cls file. I'm not sure I know latex well enough to do it myself.

 If you could file a bug report and attach the problematic file and either
 attach or link to ngauth.cls, that'd be great.

 rh

Re: Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

Richard,

where would I file bug report? web page?

Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

On Thu, 29 Nov 2012, Richard Heck wrote:


On 11/28/2012 04:12 PM, Allen Wilkinson wrote:

Richard,

That helped, thanks.

I went back and tested my troubled file. I commented out the nagauth 
\runningheads line (as a tracked change) and all changes were displayed in 
the PDF.


Must be \runningheads definition tramples on something that track changes 
needs.


The change tracking stuff loads soul and xcolor, I think, and there could be 
some kind of incompatibility there. Hard to know.


If you care to debug this for proper nagauth styles, I'll send you the 
nagauth.cls file. I'm not sure I know latex well enough to do it myself.


If you could file a bug report and attach the problematic file and either 
attach or link to ngauth.cls, that'd be great.


rh

Re: Trouble with track changes appearing in pdflatex views

[Scott Kostyshak]

On Thu, Nov 29, 2012 at 7:50 AM, Allen Wilkinson a...@chaff.biz wrote:
 Richard,

 where would I file bug report? web page?

http://www.lyx.org/trac

Thanks,

Scott



 Allen
 
 Address:

 Allen Wilkinson   (cell)  (216) 548-2349
 1286 Yellowstone Road
 Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
 +++

 On Thu, 29 Nov 2012, Richard Heck wrote:

 On 11/28/2012 04:12 PM, Allen Wilkinson wrote:

 Richard,

 That helped, thanks.

 I went back and tested my troubled file. I commented out the nagauth
 \runningheads line (as a tracked change) and all changes were displayed in
 the PDF.

 Must be \runningheads definition tramples on something that track changes
 needs.

 The change tracking stuff loads soul and xcolor, I think, and there could
 be some kind of incompatibility there. Hard to know.

 If you care to debug this for proper nagauth styles, I'll send you the
 nagauth.cls file. I'm not sure I know latex well enough to do it myself.

 If you could file a bug report and attach the problematic file and either
 attach or link to ngauth.cls, that'd be great.

 rh

Re: Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

Richard,

where would I file bug report? web page?

Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

On Thu, 29 Nov 2012, Richard Heck wrote:


On 11/28/2012 04:12 PM, Allen Wilkinson wrote:

Richard,

That helped, thanks.

I went back and tested my troubled file. I commented out the nagauth 
\runningheads line (as a tracked change) and all changes were displayed in 
the PDF.


Must be \runningheads definition tramples on something that track changes 
needs.


The change tracking stuff loads soul and xcolor, I think, and there could be 
some kind of incompatibility there. Hard to know.


If you care to debug this for proper nagauth styles, I'll send you the 
nagauth.cls file. I'm not sure I know latex well enough to do it myself.


If you could file a bug report and attach the problematic file and either 
attach or link to ngauth.cls, that'd be great.


rh

Re: Trouble with track changes appearing in pdflatex views

[Scott Kostyshak]

On Thu, Nov 29, 2012 at 7:50 AM, Allen Wilkinson  wrote:
> Richard,
>
> where would I file bug report? web page?

http://www.lyx.org/trac

Thanks,

Scott

>
>
> Allen
> 
> Address:
>
> Allen Wilkinson   (cell)  (216) 548-2349
> 1286 Yellowstone Road
> Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
> +++
>
> On Thu, 29 Nov 2012, Richard Heck wrote:
>
>> On 11/28/2012 04:12 PM, Allen Wilkinson wrote:
>>>
>>> Richard,
>>>
>>> That helped, thanks.
>>>
>>> I went back and tested my troubled file. I commented out the nagauth
>>> \runningheads line (as a tracked change) and all changes were displayed in
>>> the PDF.
>>>
>>> Must be \runningheads definition tramples on something that track changes
>>> needs.
>>>
>> The change tracking stuff loads soul and xcolor, I think, and there could
>> be some kind of incompatibility there. Hard to know.
>>
>>> If you care to debug this for proper nagauth styles, I'll send you the
>>> nagauth.cls file. I'm not sure I know latex well enough to do it myself.
>>>
>> If you could file a bug report and attach the problematic file and either
>> attach or link to ngauth.cls, that'd be great.
>>
>> rh
>>
>>
>

Re: Trouble with track changes appearing in pdflatex views

[Richard Heck]

On 11/27/2012 03:01 PM, Allen Wilkinson wrote:
My problem is that if I want to show tracked changes in PDF view or 
output I get these errors:


Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the 
document is small enough, then PDF output with tracked changes works.


This is true whether I use Lyx PDF viewing, or run OS' pdflatex 
compiler on exported .tex file.


If I disable 'show changes in output', then PDF output occurs without 
errors.


Can anyone help me resolve this problem?


Odd that the undefined color is in all caps. Is LyX exporting this wrong?

I think we can only answer this with a test file that causes the problem.

rh

Re: Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

Richard,

Attached is the file I used for testing that shows failure as attached.

If I deleted the text in the Introduction section, then tracked changes 
view okay in the PDF.


At the end of the file I have 3 test lines to see if additional changes 
still displayed when the Introduction was deleted, and they did display.


I did not incrementally delete parts of the Intro to see when the problem 
switches on.


The attached exported .tex file does not show lyxadded and lyxdeleted in 
all caps anywhere.


Hope this provides what you seek.

Thanks, Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

On Wed, 28 No   
v 2012, Richard Heck wrote:


On 11/27/2012 03:01 PM, Allen Wilkinson wrote:
My problem is that if I want to show tracked changes in PDF view or output 
I get these errors:


Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the 
document is small enough, then PDF output with tracked changes works.


This is true whether I use Lyx PDF viewing, or run OS' pdflatex compiler on 
exported .tex file.


If I disable 'show changes in output', then PDF output occurs without 
errors.


Can anyone help me resolve this problem?


Odd that the undefined color is in all caps. Is LyX exporting this wrong?

I think we can only answer this with a test file that causes the problem.

rh



cpt.tst.lyx
Description: lyx test file
%% LyX 2.0.5 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[times]{nagauth}
\usepackage[T1]{fontenc}
\usepackage{xcolor}
\usepackage{pdfcolmk}
\usepackage{amstext}
\PassOptionsToPackage{normalem}{ulem}
\usepackage{ulem}
\usepackage[unicode=true,
 bookmarks=true,bookmarksnumbered=true,bookmarksopen=true,bookmarksopenlevel=1,
 breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
 {hyperref}
\hypersetup{
 colorlinks,bookmarksopen,bookmarksnumbered,citecolor=red,urlcolor=red}

\makeatletter

%% LyX specific LaTeX commands.
\providecolor{lyxadded}{rgb}{0,0,1}
\providecolor{lyxdeleted}{rgb}{1,0,0}
%% Change tracking with ulem
\newcommand{\lyxadded}[3]{{\texorpdfstring{\color{lyxadded}{}}{}#3}}
\newcommand{\lyxdeleted}[3]{{\texorpdfstring{\color{lyxdeleted}\sout{#3}}{}}}

%% User specified LaTeX commands.
% nagdoc.tex V2.0, 13 May 2010

%\documentclass{article}

%\documentclass[times,doublespace]{nagauth}%For paper submission

\usepackage{moreverb}
\usepackage{bm}

% TEMP package to exchange messages


%\usepackage[dvips,colorlinks,bookmarksopen,bookmarksnumbered,%
%citecolor=red,urlcolor=red]{hyperref}



\newcommand{\BibTeX}{{\rmfamily B\kern-.05em \textsc{i\kern-.025em b}%
\kern-.08em T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}

\def\volumeyear{2012}

\makeatother

\begin{document}
\runningheads{Anton Kulchitsky \emph{et~al.}}{\lyxdeleted{Allen Wilkinson}{Sun Nov 25 13:13:12 2012}{Parametrical}\lyxadded{Allen Wilkinson}{Sun Nov 25 13:13:12 2012}{Parametric}
study of cone penetration test\dots}

\title{Parametrical study of cone penetration test in lunar simulant
  using discrete element method}

\author{Anton~Kulchitsky\affil{1}\corrauth, Allen~Wilkinson\affil{2},
Jerome~B.~Johnson\affil{1} and Paul~Duvoy\affil{1}}

%% \address{\affilnum{1}First author's address
%% (in this example it is the same as the third author)\break
%% \affilnum{2}Second author's address}


\address{\affilnum{1}University of Alaska Fairbanks, Institute of
  Northern Engineering, USA\break
  \affilnum{2}NASA Glenn Research Center, USA}

\corraddr{University of Alaska Fairbanks, Institute of Northern
Engineering, PO Box 755910, Fairbanks Alaska~99775-5910, USA. Email:~avkulchits...@alaska.edu}

%\cgs{Contract/grant sponsor name (no number)}
%\cgsn{Contract/grant sponsor name}{number}
\cgsn{NASA Lunar Science Institute project ``Scientific and Exploration
Potential of the Lunar Poles'' through subcontract 957706 to Johns
Hopkins University under NASA contract}{NNA09DB31A}
\begin{abstract}
\textit{To be written by Anton, Allen, and Jerry at the end}

A DEM model parametric study of particle and ensemble physical properties
is performed to identify the most important properties for modeling
cone penetration and triaxial compression tests. Cone penetration
and triaxial compression test data using the silty sand lunar simulant
JSC-1a are used in follow-on simulations to select the best property
values needed to faithfully reproduce the actual tests. The results
of the parametric study and code validation are presented here. 

Re: Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

Richard,

That helped, thanks.

I went back and tested my troubled file. I commented out the nagauth 
\runningheads line (as a tracked change) and all changes were 
displayed in the PDF.


Must be \runningheads definition tramples on something that track 
changes needs.


If you care to debug this for proper nagauth styles, I'll send you the 
nagauth.cls file. I'm not sure I know latex well enough to do it myself.


In any case I can manage with this work around.

Best, Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

On Wed, 28 Nov 2012, Richard Heck wrote:


On 11/28/2012 11:09 AM, Allen Wilkinson wrote:

Richard,

Attached is the file I used for testing that shows failure as attached.

If I deleted the text in the Introduction section, then tracked changes 
view okay in the PDF.


At the end of the file I have 3 test lines to see if additional changes 
still displayed when the Introduction was deleted, and they did display.


I did not incrementally delete parts of the Intro to see when the problem 
switches on.


The attached exported .tex file does not show lyxadded and lyxdeleted in 
all caps anywhere.


Hope this provides what you seek.

I don't have the ngauth class file so had to switch to article. Once I did 
that, I had to delete a lot of the stuff before the abstract, as that was 
ngauth specific. Having done that, however, I had no problem viewing the file 
with changes. I append both the LyX file and the PDF.


Can you correctly view this file?

rh

Re: Trouble with track changes appearing in pdflatex views

[Richard Heck]

On 11/28/2012 04:12 PM, Allen Wilkinson wrote:

Richard,

That helped, thanks.

I went back and tested my troubled file. I commented out the nagauth 
\runningheads line (as a tracked change) and all changes were 
displayed in the PDF.


Must be \runningheads definition tramples on something that track 
changes needs.


The change tracking stuff loads soul and xcolor, I think, and there 
could be some kind of incompatibility there. Hard to know.


If you care to debug this for proper nagauth styles, I'll send you the 
nagauth.cls file. I'm not sure I know latex well enough to do it myself.


If you could file a bug report and attach the problematic file and 
either attach or link to ngauth.cls, that'd be great.


rh

Re: Trouble with track changes appearing in pdflatex views

[Richard Heck]

On 11/27/2012 03:01 PM, Allen Wilkinson wrote:
My problem is that if I want to show tracked changes in PDF view or 
output I get these errors:


Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the 
document is small enough, then PDF output with tracked changes works.


This is true whether I use Lyx PDF viewing, or run OS' pdflatex 
compiler on exported .tex file.


If I disable 'show changes in output', then PDF output occurs without 
errors.


Can anyone help me resolve this problem?


Odd that the undefined color is in all caps. Is LyX exporting this wrong?

I think we can only answer this with a test file that causes the problem.

rh

Re: Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

Richard,

Attached is the file I used for testing that shows failure as attached.

If I deleted the text in the Introduction section, then tracked changes 
view okay in the PDF.


At the end of the file I have 3 test lines to see if additional changes 
still displayed when the Introduction was deleted, and they did display.


I did not incrementally delete parts of the Intro to see when the problem 
switches on.


The attached exported .tex file does not show lyxadded and lyxdeleted in 
all caps anywhere.


Hope this provides what you seek.

Thanks, Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

On Wed, 28 No   
v 2012, Richard Heck wrote:


On 11/27/2012 03:01 PM, Allen Wilkinson wrote:
My problem is that if I want to show tracked changes in PDF view or output 
I get these errors:


Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the 
document is small enough, then PDF output with tracked changes works.


This is true whether I use Lyx PDF viewing, or run OS' pdflatex compiler on 
exported .tex file.


If I disable 'show changes in output', then PDF output occurs without 
errors.


Can anyone help me resolve this problem?


Odd that the undefined color is in all caps. Is LyX exporting this wrong?

I think we can only answer this with a test file that causes the problem.

rh



cpt.tst.lyx
Description: lyx test file
%% LyX 2.0.5 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[times]{nagauth}
\usepackage[T1]{fontenc}
\usepackage{xcolor}
\usepackage{pdfcolmk}
\usepackage{amstext}
\PassOptionsToPackage{normalem}{ulem}
\usepackage{ulem}
\usepackage[unicode=true,
 bookmarks=true,bookmarksnumbered=true,bookmarksopen=true,bookmarksopenlevel=1,
 breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
 {hyperref}
\hypersetup{
 colorlinks,bookmarksopen,bookmarksnumbered,citecolor=red,urlcolor=red}

\makeatletter

%% LyX specific LaTeX commands.
\providecolor{lyxadded}{rgb}{0,0,1}
\providecolor{lyxdeleted}{rgb}{1,0,0}
%% Change tracking with ulem
\newcommand{\lyxadded}[3]{{\texorpdfstring{\color{lyxadded}{}}{}#3}}
\newcommand{\lyxdeleted}[3]{{\texorpdfstring{\color{lyxdeleted}\sout{#3}}{}}}

%% User specified LaTeX commands.
% nagdoc.tex V2.0, 13 May 2010

%\documentclass{article}

%\documentclass[times,doublespace]{nagauth}%For paper submission

\usepackage{moreverb}
\usepackage{bm}

% TEMP package to exchange messages


%\usepackage[dvips,colorlinks,bookmarksopen,bookmarksnumbered,%
%citecolor=red,urlcolor=red]{hyperref}



\newcommand{\BibTeX}{{\rmfamily B\kern-.05em \textsc{i\kern-.025em b}%
\kern-.08em T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}

\def\volumeyear{2012}

\makeatother

\begin{document}
\runningheads{Anton Kulchitsky \emph{et~al.}}{\lyxdeleted{Allen Wilkinson}{Sun Nov 25 13:13:12 2012}{Parametrical}\lyxadded{Allen Wilkinson}{Sun Nov 25 13:13:12 2012}{Parametric}
study of cone penetration test\dots}

\title{Parametrical study of cone penetration test in lunar simulant
  using discrete element method}

\author{Anton~Kulchitsky\affil{1}\corrauth, Allen~Wilkinson\affil{2},
Jerome~B.~Johnson\affil{1} and Paul~Duvoy\affil{1}}

%% \address{\affilnum{1}First author's address
%% (in this example it is the same as the third author)\break
%% \affilnum{2}Second author's address}


\address{\affilnum{1}University of Alaska Fairbanks, Institute of
  Northern Engineering, USA\break
  \affilnum{2}NASA Glenn Research Center, USA}

\corraddr{University of Alaska Fairbanks, Institute of Northern
Engineering, PO Box 755910, Fairbanks Alaska~99775-5910, USA. Email:~avkulchits...@alaska.edu}

%\cgs{Contract/grant sponsor name (no number)}
%\cgsn{Contract/grant sponsor name}{number}
\cgsn{NASA Lunar Science Institute project ``Scientific and Exploration
Potential of the Lunar Poles'' through subcontract 957706 to Johns
Hopkins University under NASA contract}{NNA09DB31A}
\begin{abstract}
\textit{To be written by Anton, Allen, and Jerry at the end}

A DEM model parametric study of particle and ensemble physical properties
is performed to identify the most important properties for modeling
cone penetration and triaxial compression tests. Cone penetration
and triaxial compression test data using the silty sand lunar simulant
JSC-1a are used in follow-on simulations to select the best property
values needed to faithfully reproduce the actual tests. The results
of the parametric study and code validation are presented here. 

Re: Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

Richard,

That helped, thanks.

I went back and tested my troubled file. I commented out the nagauth 
\runningheads line (as a tracked change) and all changes were 
displayed in the PDF.


Must be \runningheads definition tramples on something that track 
changes needs.


If you care to debug this for proper nagauth styles, I'll send you the 
nagauth.cls file. I'm not sure I know latex well enough to do it myself.


In any case I can manage with this work around.

Best, Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

On Wed, 28 Nov 2012, Richard Heck wrote:


On 11/28/2012 11:09 AM, Allen Wilkinson wrote:

Richard,

Attached is the file I used for testing that shows failure as attached.

If I deleted the text in the Introduction section, then tracked changes 
view okay in the PDF.


At the end of the file I have 3 test lines to see if additional changes 
still displayed when the Introduction was deleted, and they did display.


I did not incrementally delete parts of the Intro to see when the problem 
switches on.


The attached exported .tex file does not show lyxadded and lyxdeleted in 
all caps anywhere.


Hope this provides what you seek.

I don't have the ngauth class file so had to switch to article. Once I did 
that, I had to delete a lot of the stuff before the abstract, as that was 
ngauth specific. Having done that, however, I had no problem viewing the file 
with changes. I append both the LyX file and the PDF.


Can you correctly view this file?

rh

Re: Trouble with track changes appearing in pdflatex views

[Richard Heck]

On 11/28/2012 04:12 PM, Allen Wilkinson wrote:

Richard,

That helped, thanks.

I went back and tested my troubled file. I commented out the nagauth 
\runningheads line (as a tracked change) and all changes were 
displayed in the PDF.


Must be \runningheads definition tramples on something that track 
changes needs.


The change tracking stuff loads soul and xcolor, I think, and there 
could be some kind of incompatibility there. Hard to know.


If you care to debug this for proper nagauth styles, I'll send you the 
nagauth.cls file. I'm not sure I know latex well enough to do it myself.


If you could file a bug report and attach the problematic file and 
either attach or link to ngauth.cls, that'd be great.


rh

Re: Trouble with track changes appearing in pdflatex views

[Richard Heck]

On 11/27/2012 03:01 PM, Allen Wilkinson wrote:
My problem is that if I want to show tracked changes in PDF view or 
output I get these errors:


Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the 
document is small enough, then PDF output with tracked changes works.


This is true whether I use Lyx PDF viewing, or run OS' pdflatex 
compiler on exported .tex file.


If I disable 'show changes in output', then PDF output occurs without 
errors.


Can anyone help me resolve this problem?


Odd that the "undefined color" is in all caps. Is LyX exporting this wrong?

I think we can only answer this with a test file that causes the problem.

rh

Re: Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

Richard,

Attached is the file I used for testing that shows failure as attached.

If I deleted the text in the Introduction section, then tracked changes 
view okay in the PDF.


At the end of the file I have 3 test lines to see if additional changes 
still displayed when the Introduction was deleted, and they did display.


I did not incrementally delete parts of the Intro to see when the problem 
switches on.


The attached exported .tex file does not show lyxadded and lyxdeleted in 
all caps anywhere.


Hope this provides what you seek.

Thanks, Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

On Wed, 28 No   
v 2012, Richard Heck wrote:


On 11/27/2012 03:01 PM, Allen Wilkinson wrote:
My problem is that if I want to show tracked changes in PDF view or output 
I get these errors:


Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the 
document is small enough, then PDF output with tracked changes works.


This is true whether I use Lyx PDF viewing, or run OS' pdflatex compiler on 
exported .tex file.


If I disable 'show changes in output', then PDF output occurs without 
errors.


Can anyone help me resolve this problem?


Odd that the "undefined color" is in all caps. Is LyX exporting this wrong?

I think we can only answer this with a test file that causes the problem.

rh



cpt.tst.lyx
Description: lyx test file
%% LyX 2.0.5 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[times]{nagauth}
\usepackage[T1]{fontenc}
\usepackage{xcolor}
\usepackage{pdfcolmk}
\usepackage{amstext}
\PassOptionsToPackage{normalem}{ulem}
\usepackage{ulem}
\usepackage[unicode=true,
 bookmarks=true,bookmarksnumbered=true,bookmarksopen=true,bookmarksopenlevel=1,
 breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
 {hyperref}
\hypersetup{
 colorlinks,bookmarksopen,bookmarksnumbered,citecolor=red,urlcolor=red}

\makeatletter

%% LyX specific LaTeX commands.
\providecolor{lyxadded}{rgb}{0,0,1}
\providecolor{lyxdeleted}{rgb}{1,0,0}
%% Change tracking with ulem
\newcommand{\lyxadded}[3]{{\texorpdfstring{\color{lyxadded}{}}{}#3}}
\newcommand{\lyxdeleted}[3]{{\texorpdfstring{\color{lyxdeleted}\sout{#3}}{}}}

%% User specified LaTeX commands.
% nagdoc.tex V2.0, 13 May 2010

%\documentclass{article}

%\documentclass[times,doublespace]{nagauth}%For paper submission

\usepackage{moreverb}
\usepackage{bm}

% TEMP package to exchange messages


%\usepackage[dvips,colorlinks,bookmarksopen,bookmarksnumbered,%
%citecolor=red,urlcolor=red]{hyperref}



\newcommand{\BibTeX}{{\rmfamily B\kern-.05em \textsc{i\kern-.025em b}%
\kern-.08em T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}

\def\volumeyear{2012}

\makeatother

\begin{document}
\runningheads{Anton Kulchitsky \emph{et~al.}}{\lyxdeleted{Allen Wilkinson}{Sun Nov 25 13:13:12 2012}{Parametrical}\lyxadded{Allen Wilkinson}{Sun Nov 25 13:13:12 2012}{Parametric}
study of cone penetration test\dots}

\title{Parametrical study of cone penetration test in lunar simulant
  using discrete element method}

\author{Anton~Kulchitsky\affil{1}\corrauth, Allen~Wilkinson\affil{2},
Jerome~B.~Johnson\affil{1} and Paul~Duvoy\affil{1}}

%% \address{<\affilnum{1}First author's address
%% (in this example it is the same as the third author)\break
%% \affilnum{2}Second author's address>}


\address{\affilnum{1}University of Alaska Fairbanks, Institute of
  Northern Engineering, USA\break
  \affilnum{2}NASA Glenn Research Center, USA}

\corraddr{University of Alaska Fairbanks, Institute of Northern
Engineering, PO Box 755910, Fairbanks Alaska~99775-5910, USA. Email:~avkulchits...@alaska.edu}

%\cgs{}
%\cgsn{}{}
\cgsn{NASA Lunar Science Institute project ``Scientific and Exploration
Potential of the Lunar Poles'' through subcontract 957706 to Johns
Hopkins University under NASA contract}{NNA09DB31A}
\begin{abstract}
\textit{To be written by Anton, Allen, and Jerry at the end}

A DEM model parametric study of particle and ensemble physical properties
is performed to identify the most important properties for modeling
cone penetration and triaxial compression tests. Cone penetration
and triaxial compression test data using the silty sand lunar simulant
JSC-1a are used in follow-on simulations to select the best property
values needed to faithfully reproduce the actual tests. The results
of the parametric study and code validation are presented here. 
\end{abstract}

\keywords{discrete element method, cone penetration 

Re: Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

Richard,

That helped, thanks.

I went back and tested my troubled file. I commented out the nagauth 
\runningheads line (as a tracked change) and all changes were 
displayed in the PDF.


Must be \runningheads definition tramples on something that track 
changes needs.


If you care to debug this for proper nagauth styles, I'll send you the 
nagauth.cls file. I'm not sure I know latex well enough to do it myself.


In any case I can manage with this work around.

Best, Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

On Wed, 28 Nov 2012, Richard Heck wrote:


On 11/28/2012 11:09 AM, Allen Wilkinson wrote:

Richard,

Attached is the file I used for testing that shows failure as attached.

If I deleted the text in the Introduction section, then tracked changes 
view okay in the PDF.


At the end of the file I have 3 test lines to see if additional changes 
still displayed when the Introduction was deleted, and they did display.


I did not incrementally delete parts of the Intro to see when the problem 
switches on.


The attached exported .tex file does not show lyxadded and lyxdeleted in 
all caps anywhere.


Hope this provides what you seek.

I don't have the ngauth class file so had to switch to article. Once I did 
that, I had to delete a lot of the stuff before the abstract, as that was 
ngauth specific. Having done that, however, I had no problem viewing the file 
with changes. I append both the LyX file and the PDF.


Can you correctly view this file?

rh

Re: Trouble with track changes appearing in pdflatex views

[Richard Heck]

On 11/28/2012 04:12 PM, Allen Wilkinson wrote:

Richard,

That helped, thanks.

I went back and tested my troubled file. I commented out the nagauth 
\runningheads line (as a tracked change) and all changes were 
displayed in the PDF.


Must be \runningheads definition tramples on something that track 
changes needs.


The change tracking stuff loads soul and xcolor, I think, and there 
could be some kind of incompatibility there. Hard to know.


If you care to debug this for proper nagauth styles, I'll send you the 
nagauth.cls file. I'm not sure I know latex well enough to do it myself.


If you could file a bug report and attach the problematic file and 
either attach or link to ngauth.cls, that'd be great.


rh

Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

My problem is that if I want to show tracked changes in PDF view or output 
I get these errors:


Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the 
document is small enough, then PDF output with tracked changes works.


This is true whether I use Lyx PDF viewing, or run OS' pdflatex compiler 
on exported .tex file.


If I disable 'show changes in output', then PDF output occurs without 
errors.


Can anyone help me resolve this problem?

I did some general Google and LyX wiki searching, but nothing popped up.

-
MY SET UP CONTEXT:

I have Lyx 2.0.5 on a Suse 11.1 box. and:

pdflatex -v
pdfTeX using libpoppler 3.141592-1.40.3-2.2 (Web2C 7.5.6)
kpathsea version 3.5.6

Header of .log file:
This is pdfTeX, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=latex 
2009.1.23)  27 NOV 2012 12:44

entering extended mode


Header of .tex file:
%% LyX 2.0.5 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[times]{nagauth}
\usepackage[T1]{fontenc}
\usepackage{xcolor}
\usepackage{pdfcolmk}
\usepackage{bm}
\usepackage{amstext}
\usepackage{graphicx}
\PassOptionsToPackage{normalem}{ulem}
\usepackage{ulem}
\usepackage[unicode=true,

bookmarks=true,bookmarksnumbered=true,bookmarksopen=true,bookmarksopenlevel=1,
 breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
 {hyperref}
\hypersetup{
 colorlinks,bookmarksopen,bookmarksnumbered,citecolor=red,urlcolor=red}

\makeatletter

%% LyX specific LaTeX commands.
\providecolor{lyxadded}{rgb}{0,0,1}
\providecolor{lyxdeleted}{rgb}{1,0,0}
%% Change tracking with ulem
\newcommand{\lyxadded}[3]{{\texorpdfstring{\color{lyxadded}{}}{}#3}}
\newcommand{\lyxdeleted}[3]{{\texorpdfstring{\color{lyxdeleted}\sout{#3}}{}}}

%% User specified LaTeX commands.
% nagdoc.tex V2.0, 13 May 2010

%\documentclass[times,doublespace]{nagauth}%For paper submission

\usepackage{moreverb}
\usepackage{bm}


\newcommand{\BibTeX}{{\rmfamily B\kern-.05em \textsc{i\kern-.025em b}%
\kern-.08em T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}

\def\volumeyear{2012}


Thanks for any help, Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

My problem is that if I want to show tracked changes in PDF view or output 
I get these errors:


Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the 
document is small enough, then PDF output with tracked changes works.


This is true whether I use Lyx PDF viewing, or run OS' pdflatex compiler 
on exported .tex file.


If I disable 'show changes in output', then PDF output occurs without 
errors.


Can anyone help me resolve this problem?

I did some general Google and LyX wiki searching, but nothing popped up.

-
MY SET UP CONTEXT:

I have Lyx 2.0.5 on a Suse 11.1 box. and:

pdflatex -v
pdfTeX using libpoppler 3.141592-1.40.3-2.2 (Web2C 7.5.6)
kpathsea version 3.5.6

Header of .log file:
This is pdfTeX, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=latex 
2009.1.23)  27 NOV 2012 12:44

entering extended mode


Header of .tex file:
%% LyX 2.0.5 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[times]{nagauth}
\usepackage[T1]{fontenc}
\usepackage{xcolor}
\usepackage{pdfcolmk}
\usepackage{bm}
\usepackage{amstext}
\usepackage{graphicx}
\PassOptionsToPackage{normalem}{ulem}
\usepackage{ulem}
\usepackage[unicode=true,

bookmarks=true,bookmarksnumbered=true,bookmarksopen=true,bookmarksopenlevel=1,
 breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
 {hyperref}
\hypersetup{
 colorlinks,bookmarksopen,bookmarksnumbered,citecolor=red,urlcolor=red}

\makeatletter

%% LyX specific LaTeX commands.
\providecolor{lyxadded}{rgb}{0,0,1}
\providecolor{lyxdeleted}{rgb}{1,0,0}
%% Change tracking with ulem
\newcommand{\lyxadded}[3]{{\texorpdfstring{\color{lyxadded}{}}{}#3}}
\newcommand{\lyxdeleted}[3]{{\texorpdfstring{\color{lyxdeleted}\sout{#3}}{}}}

%% User specified LaTeX commands.
% nagdoc.tex V2.0, 13 May 2010

%\documentclass[times,doublespace]{nagauth}%For paper submission

\usepackage{moreverb}
\usepackage{bm}


\newcommand{\BibTeX}{{\rmfamily B\kern-.05em \textsc{i\kern-.025em b}%
\kern-.08em T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}

\def\volumeyear{2012}


Thanks for any help, Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++

Trouble with track changes appearing in pdflatex views

[Allen Wilkinson]

My problem is that if I want to show tracked changes in PDF view or output 
I get these errors:


Package xcolor Error: Undefined color `LYXDELETED'.
Package xcolor Error: Undefined color `LYXADDED'.
...
+++
after a modest finite extent of the document is processed.

If I delete changed and unchanged text from the document such that the 
document is small enough, then PDF output with tracked changes works.


This is true whether I use Lyx PDF viewing, or run OS' pdflatex compiler 
on exported .tex file.


If I disable 'show changes in output', then PDF output occurs without 
errors.


Can anyone help me resolve this problem?

I did some general Google and LyX wiki searching, but nothing popped up.

-
MY SET UP CONTEXT:

I have Lyx 2.0.5 on a Suse 11.1 box. and:

pdflatex -v
pdfTeX using libpoppler 3.141592-1.40.3-2.2 (Web2C 7.5.6)
kpathsea version 3.5.6

Header of .log file:
This is pdfTeX, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=latex 
2009.1.23)  27 NOV 2012 12:44

entering extended mode


Header of .tex file:
%% LyX 2.0.5 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[times]{nagauth}
\usepackage[T1]{fontenc}
\usepackage{xcolor}
\usepackage{pdfcolmk}
\usepackage{bm}
\usepackage{amstext}
\usepackage{graphicx}
\PassOptionsToPackage{normalem}{ulem}
\usepackage{ulem}
\usepackage[unicode=true,

bookmarks=true,bookmarksnumbered=true,bookmarksopen=true,bookmarksopenlevel=1,
 breaklinks=false,pdfborder={0 0 1},backref=false,colorlinks=false]
 {hyperref}
\hypersetup{
 colorlinks,bookmarksopen,bookmarksnumbered,citecolor=red,urlcolor=red}

\makeatletter

%% LyX specific LaTeX commands.
\providecolor{lyxadded}{rgb}{0,0,1}
\providecolor{lyxdeleted}{rgb}{1,0,0}
%% Change tracking with ulem
\newcommand{\lyxadded}[3]{{\texorpdfstring{\color{lyxadded}{}}{}#3}}
\newcommand{\lyxdeleted}[3]{{\texorpdfstring{\color{lyxdeleted}\sout{#3}}{}}}

%% User specified LaTeX commands.
% nagdoc.tex V2.0, 13 May 2010

%\documentclass[times,doublespace]{nagauth}%For paper submission

\usepackage{moreverb}
\usepackage{bm}


\newcommand{\BibTeX}{{\rmfamily B\kern-.05em \textsc{i\kern-.025em b}%
\kern-.08em T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}

\def\volumeyear{2012}


Thanks for any help, Allen

Address:

Allen Wilkinson   (cell)  (216) 548-2349
1286 Yellowstone Road
Cleveland Heights, OH 44121  USA  (INTERNET) aw(at)chaff(dot)biz
+++