Re: Sorting tables in LyX

[Andrew Parsloe]

On 28/11/2012 7:59 p.m., Liviu Andronic wrote:

On Wed, Nov 28, 2012 at 3:18 AM, Andrew Parsloe apars...@clear.net.nz wrote:

I've used the same trick (exporting to an alternatively named LyX format,
but retaining the lyx file extension) for a number of other tasks (e.g.
sorting lists, expanding abbreviations)


Quick question: Would it be a good idea to turn Track Changes on
before launching the script and modifying built-in the .lyx file?
This way the user can check that nothing funny happened to her file
(the parts that shouldn't have been modified), and visually check the
changes that happened to the parts that should have been modified.

Liviu

I don't think change tracking works here, since the file is modified 
*externally* (the built-in feel, although pleasing, is pure illusion). 
My solution to this problem has been to write another script which 
overwrites the current buffer with the backup file. This script is 
accessible with a further toolbar button and the buffer-reload button. 
If something goes wrong, recovery is two clicks away.


Since I have a number of scripts exploiting the 'trick', each requiring 
an alternatively named LyX format, I realised at some point that I 
needed a single python master script which would call the relevant 
sub-script to sort a table or sort a list or expand an abbreviation or 
do a calculation ... according to a signal in the document. That way 
only one alternative LyX format was needed. I've used custom insets to 
provide the signal. Doing things this way also means that the same 
toolbar buttons (or shortcuts) can be used in all cases. I'm working on 
a find--replace script (e.g. across paragraph boundaries) at the 
moment, and have documentation to write and no doubt will burden the 
list with this sometime in the weeks ahead.


Andrew

Re: Sorting tables in LyX

[Liviu Andronic]

On Wed, Nov 28, 2012 at 10:42 AM, Andrew Parsloe apars...@clear.net.nz wrote:
 I don't think change tracking works here, since the file is modified
 *externally* (the built-in feel, although pleasing, is pure illusion). My

I see. What about using the CLI: Can LyX compare two documents from
the command line, and then output a third that 'tracks changes'
between the two?

If this were possible, then in theory it would be possible to come up
with a script that takes the original file, saves the processed files
to some temporary name, has LyX compare the two and output a third
file that tracks the changes between the two, and the loads this last
file in the LyX buffer. This way the user can check that all went
fine, and reject changes if not.


 solution to this problem has been to write another script which overwrites
 the current buffer with the backup file. This script is accessible with a
 further toolbar button and the buffer-reload button. If something goes
 wrong, recovery is two clicks away.

 Since I have a number of scripts exploiting the 'trick', each requiring an
 alternatively named LyX format, I realised at some point that I needed a
 single python master script which would call the relevant sub-script to sort
 a table or sort a list or expand an abbreviation or do a calculation ...
 according to a signal in the document. That way only one alternative LyX
 format was needed. I've used custom insets to provide the signal. Doing
 things this way also means that the same toolbar buttons (or shortcuts) can
 be used in all cases. I'm working on a find--replace script (e.g. across
 paragraph boundaries) at the moment, and have documentation to write and no
 doubt will burden the list with this sometime in the weeks ahead.

Looking forward to this.

Liviu

Re: Biber documentation

[stefano franchi]

The biblatex manual should be installed on your system by your Tex
distribution. The command
texdoc biblatex
should bring it up. TexLive installs it in

/usr/local/texlive/2012/texmf-dist/doc/latex/biblatex/biblatex.pdf

If you use Debian's TEx, however, it may be in a different place---Debian's
Tex used to have a different directory structure than TexLive.

Similarly, the biber manual is called biber.pdf and texlive puts it in

/usr/local/texlive/2012/texmf-dist/doc/bibtex/biber/biber.pdf

A search for either file on your system (with, e.g.  locate
biber|biblatex.pdf) should tell you where they are.

You can also google either file and you'll get to them quickly. Here is
biber.pdf on sourceforge:

http://iweb.dl.sourceforge.net/project/biblatex-biber/biblatex-biber/1.4/documentation/biber.pdf

and here is biblatex.pdf on Ctan:

ftp://www.ctan.org/ctan/macros/latex/exptl/biblatex/doc/biblatex.pdf


Cheers,

Stefano

-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic StudiesPh:   +1 (979) 845-2125
Texas AM University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

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: Biber documentation

[Wolfgang Engelmann]

Am Mittwoch, 28. November 2012, 14:20:00 schrieb stefano franchi:
 The biblatex manual should be installed on your system by your Tex
 distribution. The command
 
 texdoc biblatex
 
 should bring it up. 

Thanks, Stefano

Its a long documentation and not easy for the novice to find what one 
needs/wants. Is there somewhere a document with various examples for the 
citation styles and the various reference styles.

E.g. with my 
\usepackage[backend=biber, style=authoryear,natbib=true]{biblatex}
I get e.g.
Jang, Sung-Wuk et al. (2010). “N-acetylserotonin activates TrkB receptor in 
a circadian rhythm.” eng. In: P Natl Acad Sci USA 107, pp. 3876–3881.
while I would like to have 
Jang, S.-W. et al. (2010). N-acetylserotonin activates TrkB receptor in a 
circadian rhythm. In: P Natl Acad Sci USA 107, pp. 3876–3881.

and
Jewett, M. E., D. W. Rimmer, et al. (1997). “Human circadian pacemaker is 
sensitive to light throughout subjective day without evidence of 
transients”. In: Am J Physiol 273, R1800–R1809.
while I want 
Jewett, M. E. et al. (1997). Human circadian pacemaker is sensitive to
light throughout subjective day without evidence of transients. In: Am J 
Physiol 273, R1800–R1809.

Where would I find the option in the handbook to get rid of eng. (first 
citation) and the number of authors cited. Searching for eng. was not 
successfull

Wolfgang

Re: Biber documentation

[stefano franchi]

On Wed, Nov 28, 2012 at 12:38 PM, Wolfgang Engelmann 
engelm...@uni-tuebingen.de wrote:

 Am Mittwoch, 28. November 2012, 14:20:00 schrieb stefano franchi:
 E.g. with my
 \usepackage[backend=biber, style=authoryear,natbib=true]{biblatex}
 I get e.g.
 Jang, Sung-Wuk et al. (2010). “N-acetylserotonin activates TrkB receptor in
 a circadian rhythm.” eng. In: P Natl Acad Sci USA 107, pp. 3876–3881.
 while I would like to have
 Jang, S.-W. et al. (2010). N-acetylserotonin activates TrkB receptor in a
 circadian rhythm. In: P Natl Acad Sci USA 107, pp. 3876–3881.

 and
 Jewett, M. E., D. W. Rimmer, et al. (1997). “Human circadian pacemaker is
 sensitive to light throughout subjective day without evidence of
 transients”. In: Am J Physiol 273, R1800–R1809.
 while I want
 Jewett, M. E. et al. (1997). Human circadian pacemaker is sensitive to
 light throughout subjective day without evidence of transients. In: Am J
 Physiol 273, R1800–R1809.


The eng. is probably coming from your citation--an abbreviation for
english in the Note field perhaps? Check your bib file, and see where it
comes from.
Once you have found the filed, you can simply erase its content. In case of
multiple citations having the same issue, you can exclude the filed from
the output with the command

\DeclareFieldFormat{note}{}

in your preamble (for the note filed, of course, change note to the name
of the field that contains spurious data if otherwise)



For the second problem, you control how many authors are cited with a
biblatex option. Manual, p.52:

maxnames=integer default: 3
A threshold affecting all lists of names (author, editor, etc.). If a list
exceeds this threshold,
i. e., if it holds more than integer names, it is automatically truncated
according to the
setting of the minnames option. maxnames is the master option which sets
both maxbibnames
and maxcitenames.

minnames=integer default: 1
A limit affecting all lists of names (author, editor, etc.). If a list
holds more than
hmaxnamesi names, it is automatically truncated to minnames names. The
minnames
value must be smaller than or equal to maxnames. minnames is the master
option which
sets both minbibnames and mincitenames.


In brief,, setting maxbibnames=1 (in the call to biblatex or, even better,
within a \ExecuteBibliographyOptions command in the preamble, see manual,
p.71), should solve your problem with citation 2.


Let me say, however, that there is no easy way into biblatex. The package
is so flexible and so powerful that, inevitably, the learning curve is a
bit steep. You should definitely read chapter 3 of the manual (User guide)
and check out the numerous examples that come with the package. In Tex Live
they are installed in
usr/local/texlive/2012/texmf-dist/doc/latex/biblatex/examples/
searching for a file such as 50-style-authoryear.pdf (one of the examples)
should lead you to the right directory if otherwise.
More generally, you can ask more complex questions (how to customize
styles, etcetera) on Comp,text.tex, where a lot of biblatex users hang out.

Cheers,

Stefano



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic StudiesPh:   +1 (979) 845-2125
Texas AM University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

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: Sorting tables in LyX

[Andrew Parsloe]

On 28/11/2012 7:59 p.m., Liviu Andronic wrote:

On Wed, Nov 28, 2012 at 3:18 AM, Andrew Parsloe apars...@clear.net.nz wrote:

I've used the same trick (exporting to an alternatively named LyX format,
but retaining the lyx file extension) for a number of other tasks (e.g.
sorting lists, expanding abbreviations)


Quick question: Would it be a good idea to turn Track Changes on
before launching the script and modifying built-in the .lyx file?
This way the user can check that nothing funny happened to her file
(the parts that shouldn't have been modified), and visually check the
changes that happened to the parts that should have been modified.

Liviu

I don't think change tracking works here, since the file is modified 
*externally* (the built-in feel, although pleasing, is pure illusion). 
My solution to this problem has been to write another script which 
overwrites the current buffer with the backup file. This script is 
accessible with a further toolbar button and the buffer-reload button. 
If something goes wrong, recovery is two clicks away.


Since I have a number of scripts exploiting the 'trick', each requiring 
an alternatively named LyX format, I realised at some point that I 
needed a single python master script which would call the relevant 
sub-script to sort a table or sort a list or expand an abbreviation or 
do a calculation ... according to a signal in the document. That way 
only one alternative LyX format was needed. I've used custom insets to 
provide the signal. Doing things this way also means that the same 
toolbar buttons (or shortcuts) can be used in all cases. I'm working on 
a find--replace script (e.g. across paragraph boundaries) at the 
moment, and have documentation to write and no doubt will burden the 
list with this sometime in the weeks ahead.


Andrew

Re: Sorting tables in LyX

[Liviu Andronic]

On Wed, Nov 28, 2012 at 10:42 AM, Andrew Parsloe apars...@clear.net.nz wrote:
 I don't think change tracking works here, since the file is modified
 *externally* (the built-in feel, although pleasing, is pure illusion). My

I see. What about using the CLI: Can LyX compare two documents from
the command line, and then output a third that 'tracks changes'
between the two?

If this were possible, then in theory it would be possible to come up
with a script that takes the original file, saves the processed files
to some temporary name, has LyX compare the two and output a third
file that tracks the changes between the two, and the loads this last
file in the LyX buffer. This way the user can check that all went
fine, and reject changes if not.


 solution to this problem has been to write another script which overwrites
 the current buffer with the backup file. This script is accessible with a
 further toolbar button and the buffer-reload button. If something goes
 wrong, recovery is two clicks away.

 Since I have a number of scripts exploiting the 'trick', each requiring an
 alternatively named LyX format, I realised at some point that I needed a
 single python master script which would call the relevant sub-script to sort
 a table or sort a list or expand an abbreviation or do a calculation ...
 according to a signal in the document. That way only one alternative LyX
 format was needed. I've used custom insets to provide the signal. Doing
 things this way also means that the same toolbar buttons (or shortcuts) can
 be used in all cases. I'm working on a find--replace script (e.g. across
 paragraph boundaries) at the moment, and have documentation to write and no
 doubt will burden the list with this sometime in the weeks ahead.

Looking forward to this.

Liviu

Re: Biber documentation

[stefano franchi]

The biblatex manual should be installed on your system by your Tex
distribution. The command
texdoc biblatex
should bring it up. TexLive installs it in

/usr/local/texlive/2012/texmf-dist/doc/latex/biblatex/biblatex.pdf

If you use Debian's TEx, however, it may be in a different place---Debian's
Tex used to have a different directory structure than TexLive.

Similarly, the biber manual is called biber.pdf and texlive puts it in

/usr/local/texlive/2012/texmf-dist/doc/bibtex/biber/biber.pdf

A search for either file on your system (with, e.g.  locate
biber|biblatex.pdf) should tell you where they are.

You can also google either file and you'll get to them quickly. Here is
biber.pdf on sourceforge:

http://iweb.dl.sourceforge.net/project/biblatex-biber/biblatex-biber/1.4/documentation/biber.pdf

and here is biblatex.pdf on Ctan:

ftp://www.ctan.org/ctan/macros/latex/exptl/biblatex/doc/biblatex.pdf


Cheers,

Stefano

-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic StudiesPh:   +1 (979) 845-2125
Texas AM University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

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: Biber documentation

[Wolfgang Engelmann]

Am Mittwoch, 28. November 2012, 14:20:00 schrieb stefano franchi:
 The biblatex manual should be installed on your system by your Tex
 distribution. The command
 
 texdoc biblatex
 
 should bring it up. 

Thanks, Stefano

Its a long documentation and not easy for the novice to find what one 
needs/wants. Is there somewhere a document with various examples for the 
citation styles and the various reference styles.

E.g. with my 
\usepackage[backend=biber, style=authoryear,natbib=true]{biblatex}
I get e.g.
Jang, Sung-Wuk et al. (2010). “N-acetylserotonin activates TrkB receptor in 
a circadian rhythm.” eng. In: P Natl Acad Sci USA 107, pp. 3876–3881.
while I would like to have 
Jang, S.-W. et al. (2010). N-acetylserotonin activates TrkB receptor in a 
circadian rhythm. In: P Natl Acad Sci USA 107, pp. 3876–3881.

and
Jewett, M. E., D. W. Rimmer, et al. (1997). “Human circadian pacemaker is 
sensitive to light throughout subjective day without evidence of 
transients”. In: Am J Physiol 273, R1800–R1809.
while I want 
Jewett, M. E. et al. (1997). Human circadian pacemaker is sensitive to
light throughout subjective day without evidence of transients. In: Am J 
Physiol 273, R1800–R1809.

Where would I find the option in the handbook to get rid of eng. (first 
citation) and the number of authors cited. Searching for eng. was not 
successfull

Wolfgang

Re: Biber documentation

[stefano franchi]

On Wed, Nov 28, 2012 at 12:38 PM, Wolfgang Engelmann 
engelm...@uni-tuebingen.de wrote:

 Am Mittwoch, 28. November 2012, 14:20:00 schrieb stefano franchi:
 E.g. with my
 \usepackage[backend=biber, style=authoryear,natbib=true]{biblatex}
 I get e.g.
 Jang, Sung-Wuk et al. (2010). “N-acetylserotonin activates TrkB receptor in
 a circadian rhythm.” eng. In: P Natl Acad Sci USA 107, pp. 3876–3881.
 while I would like to have
 Jang, S.-W. et al. (2010). N-acetylserotonin activates TrkB receptor in a
 circadian rhythm. In: P Natl Acad Sci USA 107, pp. 3876–3881.

 and
 Jewett, M. E., D. W. Rimmer, et al. (1997). “Human circadian pacemaker is
 sensitive to light throughout subjective day without evidence of
 transients”. In: Am J Physiol 273, R1800–R1809.
 while I want
 Jewett, M. E. et al. (1997). Human circadian pacemaker is sensitive to
 light throughout subjective day without evidence of transients. In: Am J
 Physiol 273, R1800–R1809.


The eng. is probably coming from your citation--an abbreviation for
english in the Note field perhaps? Check your bib file, and see where it
comes from.
Once you have found the filed, you can simply erase its content. In case of
multiple citations having the same issue, you can exclude the filed from
the output with the command

\DeclareFieldFormat{note}{}

in your preamble (for the note filed, of course, change note to the name
of the field that contains spurious data if otherwise)



For the second problem, you control how many authors are cited with a
biblatex option. Manual, p.52:

maxnames=integer default: 3
A threshold affecting all lists of names (author, editor, etc.). If a list
exceeds this threshold,
i. e., if it holds more than integer names, it is automatically truncated
according to the
setting of the minnames option. maxnames is the master option which sets
both maxbibnames
and maxcitenames.

minnames=integer default: 1
A limit affecting all lists of names (author, editor, etc.). If a list
holds more than
hmaxnamesi names, it is automatically truncated to minnames names. The
minnames
value must be smaller than or equal to maxnames. minnames is the master
option which
sets both minbibnames and mincitenames.


In brief,, setting maxbibnames=1 (in the call to biblatex or, even better,
within a \ExecuteBibliographyOptions command in the preamble, see manual,
p.71), should solve your problem with citation 2.


Let me say, however, that there is no easy way into biblatex. The package
is so flexible and so powerful that, inevitably, the learning curve is a
bit steep. You should definitely read chapter 3 of the manual (User guide)
and check out the numerous examples that come with the package. In Tex Live
they are installed in
usr/local/texlive/2012/texmf-dist/doc/latex/biblatex/examples/
searching for a file such as 50-style-authoryear.pdf (one of the examples)
should lead you to the right directory if otherwise.
More generally, you can ask more complex questions (how to customize
styles, etcetera) on Comp,text.tex, where a lot of biblatex users hang out.

Cheers,

Stefano



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic StudiesPh:   +1 (979) 845-2125
Texas AM University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

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: Sorting tables in LyX

[Andrew Parsloe]

On 28/11/2012 7:59 p.m., Liviu Andronic wrote:

On Wed, Nov 28, 2012 at 3:18 AM, Andrew Parsloe  wrote:

I've used the same trick (exporting to an alternatively named LyX format,
but retaining the lyx file extension) for a number of other tasks (e.g.
sorting lists, expanding abbreviations)


Quick question: Would it be a good idea to turn Track Changes on
before launching the script and modifying "built-in" the .lyx file?
This way the user can check that nothing funny happened to her file
(the parts that shouldn't have been modified), and visually check the
changes that happened to the parts that should have been modified.

Liviu

I don't think change tracking works here, since the file is modified 
*externally* (the built-in feel, although pleasing, is pure illusion). 
My solution to this problem has been to write another script which 
overwrites the current buffer with the backup file. This script is 
accessible with a further toolbar button and the buffer-reload button. 
If something goes wrong, recovery is two clicks away.


Since I have a number of scripts exploiting the 'trick', each requiring 
an alternatively named LyX format, I realised at some point that I 
needed a single python master script which would call the relevant 
sub-script to sort a table or sort a list or expand an abbreviation or 
do a calculation ... according to a signal in the document. That way 
only one alternative LyX format was needed. I've used custom insets to 
provide the signal. Doing things this way also means that the same 
toolbar buttons (or shortcuts) can be used in all cases. I'm working on 
a find-&-replace script (e.g. across paragraph boundaries) at the 
moment, and have documentation to write and no doubt will burden the 
list with this sometime in the weeks ahead.


Andrew

Re: Sorting tables in LyX

[Liviu Andronic]

On Wed, Nov 28, 2012 at 10:42 AM, Andrew Parsloe  wrote:
> I don't think change tracking works here, since the file is modified
> *externally* (the built-in feel, although pleasing, is pure illusion). My
>
I see. What about using the CLI: Can LyX compare two documents from
the command line, and then output a third that 'tracks changes'
between the two?

If this were possible, then in theory it would be possible to come up
with a script that takes the original file, saves the processed files
to some temporary name, has LyX compare the two and output a third
file that tracks the changes between the two, and the loads this last
file in the LyX buffer. This way the user can check that all went
fine, and reject changes if not.


> solution to this problem has been to write another script which overwrites
> the current buffer with the backup file. This script is accessible with a
> further toolbar button and the buffer-reload button. If something goes
> wrong, recovery is two clicks away.
>
> Since I have a number of scripts exploiting the 'trick', each requiring an
> alternatively named LyX format, I realised at some point that I needed a
> single python master script which would call the relevant sub-script to sort
> a table or sort a list or expand an abbreviation or do a calculation ...
> according to a signal in the document. That way only one alternative LyX
> format was needed. I've used custom insets to provide the signal. Doing
> things this way also means that the same toolbar buttons (or shortcuts) can
> be used in all cases. I'm working on a find-&-replace script (e.g. across
> paragraph boundaries) at the moment, and have documentation to write and no
> doubt will burden the list with this sometime in the weeks ahead.
>
Looking forward to this.

Liviu

Re: Biber documentation

[stefano franchi]

The biblatex manual should be installed on your system by your Tex
distribution. The command
>texdoc biblatex
should bring it up. TexLive installs it in

/usr/local/texlive/2012/texmf-dist/doc/latex/biblatex/biblatex.pdf

If you use Debian's TEx, however, it may be in a different place---Debian's
Tex used to have a different directory structure than TexLive.

Similarly, the biber manual is called biber.pdf and texlive puts it in

/usr/local/texlive/2012/texmf-dist/doc/bibtex/biber/biber.pdf

A search for either file on your system (with, e.g.  >locate
biber|biblatex.pdf) should tell you where they are.

You can also google either file and you'll get to them quickly. Here is
biber.pdf on sourceforge:

http://iweb.dl.sourceforge.net/project/biblatex-biber/biblatex-biber/1.4/documentation/biber.pdf

and here is biblatex.pdf on Ctan:

ftp://www.ctan.org/ctan/macros/latex/exptl/biblatex/doc/biblatex.pdf


Cheers,

Stefano

-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic StudiesPh:   +1 (979) 845-2125
Texas A University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

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: Biber documentation

[Wolfgang Engelmann]

Am Mittwoch, 28. November 2012, 14:20:00 schrieb stefano franchi:
> The biblatex manual should be installed on your system by your Tex
> distribution. The command
> 
> >texdoc biblatex
> 
> should bring it up. 

Thanks, Stefano

Its a long documentation and not easy for the novice to find what one 
needs/wants. Is there somewhere a document with various examples for the 
citation styles and the various reference styles.

E.g. with my 
\usepackage[backend=biber, style=authoryear,natbib=true]{biblatex}
I get e.g.
Jang, Sung-Wuk et al. (2010). “N-acetylserotonin activates TrkB receptor in 
a circadian rhythm.” eng. In: P Natl Acad Sci USA 107, pp. 3876–3881.
while I would like to have 
Jang, S.-W. et al. (2010). N-acetylserotonin activates TrkB receptor in a 
circadian rhythm. In: P Natl Acad Sci USA 107, pp. 3876–3881.

and
Jewett, M. E., D. W. Rimmer, et al. (1997). “Human circadian pacemaker is 
sensitive to light throughout subjective day without evidence of 
transients”. In: Am J Physiol 273, R1800–R1809.
while I want 
Jewett, M. E. et al. (1997). Human circadian pacemaker is sensitive to
light throughout subjective day without evidence of transients. In: Am J 
Physiol 273, R1800–R1809.

Where would I find the option in the handbook to get rid of eng. (first 
citation) and the number of authors cited. Searching for eng. was not 
successfull

Wolfgang

Re: Biber documentation

[stefano franchi]

On Wed, Nov 28, 2012 at 12:38 PM, Wolfgang Engelmann <
engelm...@uni-tuebingen.de> wrote:

> Am Mittwoch, 28. November 2012, 14:20:00 schrieb stefano franchi:
> E.g. with my
> \usepackage[backend=biber, style=authoryear,natbib=true]{biblatex}
> I get e.g.
> Jang, Sung-Wuk et al. (2010). “N-acetylserotonin activates TrkB receptor in
> a circadian rhythm.” eng. In: P Natl Acad Sci USA 107, pp. 3876–3881.
> while I would like to have
> Jang, S.-W. et al. (2010). N-acetylserotonin activates TrkB receptor in a
> circadian rhythm. In: P Natl Acad Sci USA 107, pp. 3876–3881.
>
> and
> Jewett, M. E., D. W. Rimmer, et al. (1997). “Human circadian pacemaker is
> sensitive to light throughout subjective day without evidence of
> transients”. In: Am J Physiol 273, R1800–R1809.
> while I want
> Jewett, M. E. et al. (1997). Human circadian pacemaker is sensitive to
> light throughout subjective day without evidence of transients. In: Am J
> Physiol 273, R1800–R1809.
>
>
The "eng." is probably coming from your citation--an abbreviation for
"english" in the Note field perhaps? Check your bib file, and see where it
comes from.
Once you have found the filed, you can simply erase its content. In case of
multiple citations having the same issue, you can exclude the filed from
the output with the command

\DeclareFieldFormat{note}{}

in your preamble (for the note filed, of course, change "note" to the name
of the field that contains spurious data if otherwise)



For the second problem, you control how many authors are cited with a
biblatex option. Manual, p.52:

maxnames= default: 3
A threshold affecting all lists of names (author, editor, etc.). If a list
exceeds this threshold,
i. e., if it holds more than  names, it is automatically truncated
according to the
setting of the minnames option. maxnames is the master option which sets
both maxbibnames
and maxcitenames.

minnames= default: 1
A limit affecting all lists of names (author, editor, etc.). If a list
holds more than
hmaxnamesi names, it is automatically truncated to  names. The

value must be smaller than or equal to . minnames is the master
option which
sets both minbibnames and mincitenames.


In brief,, setting maxbibnames=1 (in the call to biblatex or, even better,
within a \ExecuteBibliographyOptions command in the preamble, see manual,
p.71), should solve your problem with citation 2.


Let me say, however, that there is no easy way into biblatex. The package
is so flexible and so powerful that, inevitably, the learning curve is a
bit steep. You should definitely read chapter 3 of the manual (User guide)
and check out the numerous examples that come with the package. In Tex Live
they are installed in
usr/local/texlive/2012/texmf-dist/doc/latex/biblatex/examples/
searching for a file such as 50-style-authoryear.pdf (one of the examples)
should lead you to the right directory if otherwise.
More generally, you can ask more complex questions (how to customize
styles, etcetera) on Comp,text.tex, where a lot of biblatex users hang out.

Cheers,

Stefano



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic StudiesPh:   +1 (979) 845-2125
Texas A University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

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