date:20140828

I have a fancy hyphenated word, crosstalk-cancelled, where I spell it with (I 
believe) the proper - which is an n-dash. When this is rendered in the vicinity 
of a line wrap, the entire thing gets pushed to the next line, leaving a lot of 
ugly white space in the first line. So I inserted a hyphenation point after the 
-. This shows on the LyX screen as sort of -- which is my original n-dash and a 
shorter blue dash, probably supposed to represent a hyphen. This is all great, 
but when this version is rendered, the line break now appears after 
crosstalk--, that is, both the n-dash _and_ the hyphenation point are rendered 
which looks very wrong. What is the typographer's say on this, and is LyX doing 
the right thing. Also, is this a LyX problem or a TeX problem? My guess the 
typographer would say, let the n-dash stand alone if it occurs at a line break.

Jerry

\usepackage{flushend} on two-column documents causes misplaced footnotes

When I insert 

\usepackage{flushend}

into the preamble and make the setting for two-column output, so that the 
columns on the last page have the same length (flush end), _some_ footnotes 
appear in embarrassingly inappropriate places, meaning, in the middle of a 
column, surrounded above and below by normal text.

Is this a TeX problem? Is there a known cure? Should I go to a LaTeX group and 
ask this?

Jerry

Re: Generating a Tex

On Wed, Aug 27, 2014 at 10:39 PM, William Hanson whan...@umn.edu wrote:

 This looks wonderful.  However I can't get beyond Step 2 where I'm asked
 to create a new folder.  I can't do this because I don't have
 administrative status.


Waluyo's bog post explained how to take care of a different problem:
namely, how to install a particular Springer LaTeX class (svjour3) in Lyx
and how to create a LyX document that uses it.
I don't know which class Springer has told you to use (there other others,
depending on journal/book collections), but it is indeed svjour3 you
should have it  installed on your system already. You can check by going to
DocumentSettings...Document class  and clicking on the pop-up menu on
the right just under Document class. If you have svjour3 installed, you
will see an item taht reads article (Springer svjour3/global)
Select it and you are all set.

I'll reply to the other problem (the bibtex issue) in another post.


Cheers,

S.


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

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

Re: Generating a Tex

On Wed, Aug 27, 2014 at 11:09 PM, William Hanson whan...@umn.edu wrote:

 Sorry, but I do not seem to be able to reply except by top posting.

 I'm using Windows, 64 bit.

 Here's the very end of my .tex file:

 \begin{quotation}

 \bibliographystyle{plain}

 \bibliography{\string//phil-home.ad.umn.edu/phil-home$/whanson/My
 Documents/BibTeX/library\string}

 \end{quotation}

 \end{document}


 I have tried removing the space in ...My Documents ..., but it doesn't
 help.  In fact in the process of removing the spaces I've somehow managed
 to mess up my document so that now when I convert it to a pdf file there
 are no references at the end.  And in the text all the citations say [?].



I suppose removing the space in My Documents won't help---not, that is,
unless you actaully rename the My Documents directory in Windows to
MyDocuments. And that is not a great idea, as My Documents is a Windows
standard directory and renaming it will undoubtedly mess things up badly,
At any rate, since the the address of your bib file is wrapped by a \string
command, it should actually work even if it contains a space---that is what
the \string command should take care of. In theory at least.
We need to know exactly what is the problem that prevents bibtex from
producing a bbl file. I would suggest the following if you'd like more help:

1. Export your file  to Latex(plain) and produce something called
myfile.tex
2. Run pdflatex myfile.tex in a terminal.
3. You will see that pdflatex produces (in addition to myfile.pdf) a file
called myfile.log.
4. Post that file to the list
5. Run bibtex myfile and cut and paste everything bibtex spits to the
terminal into another file. Call it myfile.bib.log.
6. Post that file to the list as well

(there are more elegant ways to collect a program's output than what I just
suggested, but I don't know how to accomplish them in Windows. Perhaps
other users may help. But the above should work)

Cheers,
Stefano



 Bill







 On Wed, Aug 27, 2014 at 2:47 PM, stefano franchi 
 stefano.fran...@gmail.com wrote:




 On Wed, Aug 27, 2014 at 2:26 PM, William Hanson whan...@umn.edu wrote:

 Well, I got as far as your 3, that is I ran bibtex on myfile.tex from
 the command line.  It gave me lots of LateX Errors, like

 LaTeX Warning: Citation `plantinga:1985a' on page 2 undefined on input
 line 103



 That probably means bibtex cannot find your bib file(s).  Look at the
 .tex file in anb editor. At the very end (most likely the next to last
 line), you'll see a line like:
 \bibliography{}

 Inside the braces you will have the complete path to your bibtex file
 (the .bib file, but without the extension). Check that:
 1. That path is indeed correct (is the file really there?).
 2, There are no spaces in the path (fix the problem if otherwise. Easiest
 way is to copy your lyx file and your bib file to a temporary directory in
 your home directory)


 If neither of these suggestions works, please post the complete output of
 the bibtex run (from the terminal)


 But it didn't seem to produce  myfile.bbl; at least I don't see it
 anywhere.  Maybe it didn't generate because of all the errors?
 So I'm stuck at this point.

 Yes, it was not generated because bibtex ran into troubles.



 By the way, I did find a space in the filename, which I closed.  I don't
 know how to tell if there are spaces in the directory structure.



  Which system are you on (Mac, Linux, Win)? I can help with the first
 two, but I am hopeless on Windows.

 Cheers,

 Stefano

 P.S. Also, please do not top post. Answer in line with your replies
 immediately following the relevant point you are responding to. It makes
 for easier and faster reading. Besides, it is the list convention

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

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





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

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

Re: \usepackage{flushend} on two-column documents causes misplaced footnotes


On 08/28/2014 07:11 AM, Jerry wrote:

When I insert

\usepackage{flushend}

into the preamble and make the setting for two-column output, so that the columns on the 
last page have the same length (flush end), _some_ footnotes appear in 
embarrassingly inappropriate places, meaning, in the middle of a column, surrounded above 
and below by normal text.

Is this a TeX problem? Is there a known cure? Should I go to a LaTeX group and 
ask this?


Yes, it's presumably an issue with that package.

rh

Re: Hyphenating a hyphenated word at a line break


On 08/28/2014 07:03 AM, Jerry wrote:

I have a fancy hyphenated word, crosstalk-cancelled, where I spell it with (I 
believe) the proper - which is an n-dash. When this is rendered in the vicinity 
of a line wrap, the entire thing gets pushed to the next line, leaving a lot of 
ugly white space in the first line. So I inserted a hyphenation point after the 
-. This shows on the LyX screen as sort of -- which is my original n-dash and a 
shorter blue dash, probably supposed to represent a hyphen. This is all great, 
but when this version is rendered, the line break now appears after 
crosstalk--, that is, both the n-dash _and_ the hyphenation point are rendered 
which looks very wrong. What is the typographer's say on this, and is LyX doing 
the right thing. Also, is this a LyX problem or a TeX problem? My guess the 
typographer would say, let the n-dash stand alone if it occurs at a line break.


Yes, the n-dash should stand alone, but LaTeX is doing what you are 
asking: You told it that it was OK to hyphenate there, so it has. What 
you want is the \linebreak command instead. LyX does not have native 
support for this, so you have to use ERT. Note that you can use an 
optional argument with \linebreak, as well, from 0 to 4, which mean: you 
can break here; you really must break here. So you could try:

\linebreak[1]
in ERT to start. The advantage of using the optional argument is that, 
if you move some text around, LaTeX still has a chance of getting the 
linebreaking right, whereas if you insist the line be broken there, then 
things could go very ugly.


Richard

Re: Hyphenating a hyphenated word at a line break

On Thu, Aug 28, 2014 at 6:03 AM, Jerry lancebo...@qwest.net wrote:

I have a fancy hyphenated word, crosstalk-cancelled, where I spell it with
(I believe) the proper - which is an n-dash. When this is rendered in the
vicinity of a line wrap, the entire thing gets pushed to the next line,
leaving a lot of ugly white space in the first line. So I inserted a
hyphenation point after the -. This shows on the LyX screen as sort of --
which is my original n-dash and a shorter blue dash, probably supposed to
represent a hyphen. This is all great, but when this version is rendered,
the line break now appears after crosstalk--, that is, both the n-dash
_and_ the hyphenation point are rendered which looks very wrong. What is
the typographer's say on this, and is LyX doing the right thing. Also, is
this a LyX problem or a TeX problem? My guess the typographer would say,
let the n-dash stand alone if it occurs at a line break.

This stackexchange question [1] contains more info than you probably wished
for, but it may still be useful in laying out the various ways to approach
the problem. Richard's suggestion (\newline) is indeed one of those listed.
Of course, all solution refer to LaTeX an not Lyxd, which means you can use
them only if you insert them in ERT boxes (and add the corresponding
packages, when needed, to your Document's preamble)

Cheers,

Stefano

[1]
http://stackoverflow.com/questions/2193307/how-to-get-latex-to-hyphenate-a-word-that-contains-a-dash

--
__
Stefano Franchi

stefano.fran...@gmail.com stef...@tamu.edu
http://stefano.cleinias.org

Re: Hyphenating a hyphenated word at a line break

On 08/28/2014 11:43 AM, stefano franchi wrote:

On Thu, Aug 28, 2014 at 6:03 AM, Jerry lancebo...@qwest.net
mailto:lancebo...@qwest.net wrote:

I have a fancy hyphenated word, crosstalk-cancelled, where I spell
it with (I believe) the proper - which is an n-dash. When this is
rendered in the vicinity of a line wrap, the entire thing gets
pushed to the next line, leaving a lot of ugly white space in the
first line. So I inserted a hyphenation point after the -. This
shows on the LyX screen as sort of -- which is my original n-dash
and a shorter blue dash, probably supposed to represent a hyphen.
This is all great, but when this version is rendered, the line
break now appears after crosstalk--, that is, both the n-dash
_and_ the hyphenation point are rendered which looks very wrong.
What is the typographer's say on this, and is LyX doing the right
thing. Also, is this a LyX problem or a TeX problem? My guess the
typographer would say, let the n-dash stand alone if it occurs at
a line break.

This stackexchange question [1] contains more info than you probably
wished for, but it may still be useful in laying out the various ways
to approach the problem. Richard's suggestion (\newline) is indeed one
of those listed. Of course, all solution refer to LaTeX an not Lyxd,
which means you can use them only if you insert them in ERT boxes (and
add the corresponding packages, when needed, to your Document's preamble)

[1]
http://stackoverflow.com/questions/2193307/how-to-get-latex-to-hyphenate-a-word-that-contains-a-dash

Wow, that is a lot of information! Mostly, that deals with cases where
you use the word a lot. I took this to be more of a one-off sort of
issue. But I'm going to save that link

Richard

Re: Hyphenating a hyphenated word at a line break

On Thu, Aug 28, 2014 at 11:19 AM, Richard Heck rgh...@lyx.org wrote:

On 08/28/2014 11:43 AM, stefano franchi wrote:

On Thu, Aug 28, 2014 at 6:03 AM, Jerry lancebo...@qwest.net wrote:

I have a fancy hyphenated word, crosstalk-cancelled, where I spell it
with (I believe) the proper - which is an n-dash. When this is rendered in
the vicinity of a line wrap, the entire thing gets pushed to the next line,
leaving a lot of ugly white space in the first line. So I inserted a
hyphenation point after the -. This shows on the LyX screen as sort of --
which is my original n-dash and a shorter blue dash, probably supposed to
represent a hyphen. This is all great, but when this version is rendered,
the line break now appears after crosstalk--, that is, both the n-dash
_and_ the hyphenation point are rendered which looks very wrong. What is
the typographer's say on this, and is LyX doing the right thing. Also, is
this a LyX problem or a TeX problem? My guess the typographer would say,
let the n-dash stand alone if it occurs at a line break.

This stackexchange question [1] contains more info than you probably
wished for, but it may still be useful in laying out the various ways to
approach the problem. Richard's suggestion (\newline) is indeed one of
those listed. Of course, all solution refer to LaTeX an not Lyxd, which
means you can use them only if you insert them in ERT boxes (and add the
corresponding packages, when needed, to your Document's preamble)

[1]
http://stackoverflow.com/questions/2193307/how-to-get-latex-to-hyphenate-a-word-that-contains-a-dash

Wow, that is a lot of information! Mostly, that deals with cases where you
use the word a lot. I took this to be more of a one-off sort of issue. But
I'm going to save that link

Well, for more time-wasting typographic fun, you could also read the
following SX question [1]. Look in particular at the answer from Lover of
Structure One of the highest ranked). Best explanation I have ever found
of the difference between hyphen and en-dash in compound words.

Cheers,

[1] http://tex.stackexchange.com/questions/3819/dashes-vs-vs

--
__
Stefano Franchi

stefano.fran...@gmail.com stef...@tamu.edu
http://stefano.cleinias.org

Re: Generating a Tex

The first time I tried to execute your step 1, immediately above, I got an
error saying that it wouldn't work because of spaces.   I tried it again
and I did get myfile.tex.  I then ran pdflatex myfile.tex (your step 2).
But, contrary to your 3, I did not get a file called myfile.log. (It did,
however, produce the following files:  myfile.toc, myfile.aux,
synctex.gz.)

So I'm stuck at this point.

Cheers,

Bill


On Thu, Aug 28, 2014 at 9:03 AM, stefano franchi stefano.fran...@gmail.com
wrote:




 On Wed, Aug 27, 2014 at 11:09 PM, William Hanson whan...@umn.edu wrote:

 Sorry, but I do not seem to be able to reply except by top posting.

 I'm using Windows, 64 bit.

 Here's the very end of my .tex file:

 \begin{quotation}

 \bibliographystyle{plain}

 \bibliography{\string//phil-home.ad.umn.edu/phil-home$/whanson/My
 Documents/BibTeX/library\string}

 \end{quotation}

 \end{document}


 I have tried removing the space in ...My Documents ..., but it doesn't
 help.  In fact in the process of removing the spaces I've somehow managed
 to mess up my document so that now when I convert it to a pdf file there
 are no references at the end.  And in the text all the citations say [?].



 I suppose removing the space in My Documents won't help---not, that is,
 unless you actaully rename the My Documents directory in Windows to
 MyDocuments. And that is not a great idea, as My Documents is a Windows
 standard directory and renaming it will undoubtedly mess things up badly,
 At any rate, since the the address of your bib file is wrapped by a
 \string command, it should actually work even if it contains a space---that
 is what the \string command should take care of. In theory at least.
 We need to know exactly what is the problem that prevents bibtex from
 producing a bbl file. I would suggest the following if you'd like more help:

 1. Export your file  to Latex(plain) and produce something called
 myfile.tex
 2. Run pdflatex myfile.tex in a terminal.
 3. You will see that pdflatex produces (in addition to myfile.pdf) a file
 called myfile.log.
 4. Post that file to the list
 5. Run bibtex myfile and cut and paste everything bibtex spits to the
 terminal into another file. Call it myfile.bib.log.
 6. Post that file to the list as well

 (there are more elegant ways to collect a program's output than what I
 just suggested, but I don't know how to accomplish them in Windows. Perhaps
 other users may help. But the above should work)

 Cheers,
 Stefano



 Bill







 On Wed, Aug 27, 2014 at 2:47 PM, stefano franchi 
 stefano.fran...@gmail.com wrote:




 On Wed, Aug 27, 2014 at 2:26 PM, William Hanson whan...@umn.edu wrote:

 Well, I got as far as your 3, that is I ran bibtex on myfile.tex from
 the command line.  It gave me lots of LateX Errors, like

 LaTeX Warning: Citation `plantinga:1985a' on page 2 undefined on input
 line 103



 That probably means bibtex cannot find your bib file(s).  Look at the
 .tex file in anb editor. At the very end (most likely the next to last
 line), you'll see a line like:
 \bibliography{}

 Inside the braces you will have the complete path to your bibtex file
 (the .bib file, but without the extension). Check that:
 1. That path is indeed correct (is the file really there?).
 2, There are no spaces in the path (fix the problem if otherwise.
 Easiest way is to copy your lyx file and your bib file to a temporary
 directory in your home directory)


 If neither of these suggestions works, please post the complete output
 of the bibtex run (from the terminal)


 But it didn't seem to produce  myfile.bbl; at least I don't see it
 anywhere.  Maybe it didn't generate because of all the errors?
 So I'm stuck at this point.

 Yes, it was not generated because bibtex ran into troubles.



 By the way, I did find a space in the filename, which I closed.  I
 don't know how to tell if there are spaces in the directory structure.



  Which system are you on (Mac, Linux, Win)? I can help with the first
 two, but I am hopeless on Windows.

 Cheers,

 Stefano

 P.S. Also, please do not top post. Answer in line with your replies
 immediately following the relevant point you are responding to. It makes
 for easier and faster reading. Besides, it is the list convention

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

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





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

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

Re: Generating a Tex

On Thu, Aug 28, 2014 at 11:47 AM, William Hanson whan...@umn.edu wrote:

 The first time I tried to execute your step 1, immediately above, I got an
 error saying that it wouldn't work because of spaces.   I tried it again
 and I did get myfile.tex.  I then ran pdflatex myfile.tex (your step 2).
 But, contrary to your 3, I did not get a file called myfile.log. (It did,
 however, produce the following files:  myfile.toc, myfile.aux,
 synctex.gz.)



This is strange, pdflatex always produces a log file unless instructed
otherwise. Are you calling pdflatex from the command line or are you using
a latex editor (such as texmaker or winedit, for instance). That would
explain the lack of a log file, as these editors may be configured to erase
log files and/or move them to other directories.

Do you also have a myfile.pdf file? That would indicate that the pdflatex
run was at least partially successful.

And what did you see on the console when you ran pdflatex (assuming you are
using a terminal-like interface and not a LaTeX editor)?


S.



-- 
__
Stefano Franchi

stefano.fran...@gmail.com stef...@tamu.edu
http://stefano.cleinias.org

Re: Generating a Tex

I am calling pdflatex from the command line of TeXworks.

It did also produce a myfile.pdf file.

What I see on my screen after running pdflatex is a window labeled
myfile.tex - TeXworks.  It contains what apparently is myfile.tex, which I
assume is the TeX version of my paper,




On Thu, Aug 28, 2014 at 11:58 AM, stefano franchi stefano.fran...@gmail.com
 wrote:




 On Thu, Aug 28, 2014 at 11:47 AM, William Hanson whan...@umn.edu wrote:

 The first time I tried to execute your step 1, immediately above, I got
 an error saying that it wouldn't work because of spaces.   I tried it again
 and I did get myfile.tex.  I then ran pdflatex myfile.tex (your step 2).
 But, contrary to your 3, I did not get a file called myfile.log. (It did,
 however, produce the following files:  myfile.toc, myfile.aux,
 synctex.gz.)



 This is strange, pdflatex always produces a log file unless instructed
 otherwise. Are you calling pdflatex from the command line or are you using
 a latex editor (such as texmaker or winedit, for instance). That would
 explain the lack of a log file, as these editors may be configured to erase
 log files and/or move them to other directories.

 Do you also have a myfile.pdf file? That would indicate that the pdflatex
 run was at least partially successful.

 And what did you see on the console when you ran pdflatex (assuming you
 are using a terminal-like interface and not a LaTeX editor)?


 S.



 --
 __
 Stefano Franchi

 stefano.fran...@gmail.com stef...@tamu.edu
 http://stefano.cleinias.org

Re: Generating a Tex

Breaking News!  I just ran LaTeX(plain) on myfile.lyx and it produced
mytext.bbl.  I've never gotten a bbl file before.  This is good, isn't it?
Is there an easy way forward from here?


On Thu, Aug 28, 2014 at 12:59 PM, stefano franchi stefano.fran...@gmail.com
 wrote:




 On Thu, Aug 28, 2014 at 12:55 PM, stefano franchi 
 stefano.fran...@gmail.com wrote:




 On Thu, Aug 28, 2014 at 12:26 PM, William Hanson whan...@umn.edu wrote:

 I am calling pdflatex from the command line of TeXworks.

 It did also produce a myfile.pdf file.

 What I see on my screen after running pdflatex is a window labeled
 myfile.tex - TeXworks.  It contains what apparently is myfile.tex, which I
 assume is the TeX version of my paper,



 If you use texworks, you should just be able to select pdflatex from the
 Typeset menu, and it will compile your file to myfile.pdf and also produce
 a myfile.log. For instance, this is what I see in TeXWorks console, when I
 try to compile a test.tex file:

 This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded
 format=pdflatex)

 restricted \write18 enabled.

 entering extended mode

 (./test.tex

 LaTeX2e 2014/05/01

 Babel 3.9k and hyphenation patterns for 79 languages loaded.

 (/usr/local/texlive/2014/texmf-dist/tex/latex/base/article.cls

 Document Class: article 2007/10/19 v1.4h Standard LaTeX document class

 (/usr/local/texlive/2014/texmf-dist/tex/latex/base/size11.clo))

 (/usr/local/texlive/2014/texmf-dist/tex/latex/base/fontenc.sty

 (/usr/local/texlive/2014/texmf-dist/tex/latex/base/t1enc.def))

 (/usr/local/texlive/2014/texmf-dist/tex/generic/babel/babel.sty

 (/usr/local/texlive/2014/texmf-dist/tex/generic/babel-english/english.ldf

 (/usr/local/texlive/2014/texmf-dist/tex/generic/babel/babel.def)))


 LaTeX Warning: Unused global option(s):

 [article].


 (./test.aux)
 [1{/usr/local/texlive/2014/texmf-var/fonts/map/pdftex/updmap/pdfte

 x.map}] (./test.aux)
 ){/usr/local/texlive/2014/texmf-dist/fonts/enc/dvips/cm-su


 per/cm-super-t1.enc}/usr/local/texlive/2014/texmf-dist/fonts/type1/public/cm-s

 uper/sfrm1095.pfb

 Output written on test.pdf (1 page, 13144 bytes).

 SyncTeX written on test.synctex.gz.

 Transcript written on test.log.


 Notice how on the last line it informs me that it has produced a log file.


 At any rate, try recompiling your file, and if you cannot find the log
 file, juct cut and paste everything you see in TeXWorks's console output
 window into an email message and send it to the list.

 Do the same for a compilation with bibtex (just select bibtex from the
 Typeset menu and hit ctrl-T). Cut and paste the console output into an
 email message and send it to the list.


 That should give us enough info to understand what's going wrong.




 The alternative is to use a good old-fashioned terminal---I believe it is
 called Command prompt in Windows, or at least it used to be. See here [1]
 on how to do it in Windows 7 (with apologies if it is obvious to you).


 [1]
 http://smallbusiness.chron.com/open-terminal-session-windows-7-56627.html




 S.


 --
 __
 Stefano Franchi

 stefano.fran...@gmail.com stef...@tamu.edu
 http://stefano.cleinias.org

Re: Generating a Tex

On Thu, Aug 28, 2014 at 1:54 PM, William Hanson whan...@umn.edu wrote:

 Breaking News!  I just ran LaTeX(plain) on myfile.lyx and it produced
 mytext.bbl.  I've never gotten a bbl file before.  This is good, isn't it?
 Is there an easy way forward from here?



Assuming your bbl file is correct, you're almost there. You just:

1. open the myfile.bbl file in TeXWorks (be sure to select all files
ffrom the open dialog or it won't show up)
2. Select and copy everything in the bbl file
3, go to your myfile,.tex file in TeXWorks, delete the two lines (at the
end), that begin with, respectively, \bibliographystyle and \bibliography
and replace them with the content you just copied from the bbl file.
4. Compile the file again with pdflatex to be sure everything works
correctly and the pdf is how it should be (with all the refs, etcetera).
5. Send to Springer!

Cheers,

Stefano

-- 
__
Stefano Franchi

stefano.fran...@gmail.com stef...@tamu.edu
http://stefano.cleinias.org

Re: Generating a Tex

So close, but my bbl file does not show up om TeXWorks.  I don't see any
all files ffrom the open dialog.


On Thu, Aug 28, 2014 at 2:12 PM, stefano franchi stefano.fran...@gmail.com
wrote:




 On Thu, Aug 28, 2014 at 1:54 PM, William Hanson whan...@umn.edu wrote:

 Breaking News!  I just ran LaTeX(plain) on myfile.lyx and it produced
 mytext.bbl.  I've never gotten a bbl file before.  This is good, isn't it?
 Is there an easy way forward from here?



 Assuming your bbl file is correct, you're almost there. You just:

 1. open the myfile.bbl file in TeXWorks (be sure to select all files
 ffrom the open dialog or it won't show up)
 2. Select and copy everything in the bbl file
 3, go to your myfile,.tex file in TeXWorks, delete the two lines (at the
 end), that begin with, respectively, \bibliographystyle and \bibliography
 and replace them with the content you just copied from the bbl file.
 4. Compile the file again with pdflatex to be sure everything works
 correctly and the pdf is how it should be (with all the refs, etcetera).
 5. Send to Springer!

 Cheers,

 Stefano

 --
 __
 Stefano Franchi

 stefano.fran...@gmail.com stef...@tamu.edu
 http://stefano.cleinias.org

Re: Generating a Tex

Foiled again, I'm afraid.  All that's in the bbl file is

\begin{thebibliography}{}

\end{thebibliography}


Cheers nonetheless.



On Thu, Aug 28, 2014 at 3:02 PM, stefano franchi stefano.fran...@gmail.com
wrote:




 On Thu, Aug 28, 2014 at 2:46 PM, William Hanson whan...@umn.edu wrote:

 So close, but my bbl file does not show up om TeXWorks.  I don't see any
   all files ffrom the open dialog.



 Look at the last line in the open file dialog screen (see attached
 screenshot, where it says Filter). It is a pop up menu, you need to click
 on it and select the last item all files


 S.

 --
 __
 Stefano Franchi

 stefano.fran...@gmail.com stef...@tamu.edu
 http://stefano.cleinias.org

Re: Generating a Tex

On Thu, Aug 28, 2014 at 3:22 PM, William Hanson whan...@umn.edu wrote:

 Foiled again, I'm afraid.  All that's in the bbl file is

 \begin{thebibliography}{}

 \end{thebibliography}


 Cheers nonetheless.


That means that the bibtex run failed. Run bibtex again from within
TeXworks, and cut and paste the console output into an email message to the
list.
It is hard to help without knowing what is wrong.
Cheers,

S.

-- 
__
Stefano Franchi

stefano.fran...@gmail.com stef...@tamu.edu
http://stefano.cleinias.org

KOMA-book: Appendices

2014-08-28 Thread Rich Shepard


  With Lyx-2.1.1 and the KOMA book class I want to add appendices in
addition to the Bibliography. The Document menu has an item, 'Start Appendix
Here,' and the KOMA book document tells me that appendices include the
bibliography, index, and other backmatter.

  Does it make any difference if I start apendices before or after the
bibliography? If I want them numbered (upper case letters according to the
KOMA-script book document) do I set each in the Chapter environment,
Chapter* environment, or something else? The bibliograpy is not now numbered
which leads me to think the other appendices should start after it.

  But, ... I'm open to suggestions and guidelines.

Rich

Re: \usepackage{flushend} on two-column documents causes misplaced footnotes

2014-08-28 Thread Marcelo Acuña

I have not problem with flushend and two columns.
Maybe the problem is caused elsewhere in the document or preamble.


Regards
Marcelo


El Jueves, 28 de agosto, 2014 12:24:03, Richard Heck rgh...@lyx.org escribió:
 


On 08/28/2014 07:11 AM, Jerry wrote:

 When I insert

 \usepackage{flushend}

 into the preamble and make the setting for two-column output, so that the 
 columns on the last page have the same length (flush end), _some_ footnotes 
 appear in embarrassingly inappropriate places, meaning, in the middle of a 
 column, surrounded above and below by normal text.

 Is this a TeX problem? Is there a known cure? Should I go to a LaTeX group 
 and ask this?

Yes, it's presumably an issue with that package.

rh

Re: FRAGE: Zeilenabstand

2014-08-28 Thread Jürgen Spitzmüller

Hello

This is an English list, so I reply in English. Please let me know if this is 
a problem.

Try this:

* Select the TOC and LOT insets (the grey buttons for the Table of Contents 
and List of figures, respectively) with the cursor

* Open Edit  Paragraph Settings (Bearbeiten  Absatzeinstellungen)

* Set Paragraph Spacing to Normal (Einfach)

* Hit OK.

HTH
Jürgen

Am Montag 25 August 2014, 20:02:39 schrieb Peter Pattis:
 Sehr geehrtes LyX-Team
 
 Ich habe eine Frage zum Zeilenabstand.
 
 Ich habe für das ganze Dokument den Zeilenabstand 1.5 angegeben. Nun
 erstellt LyX aber auch das Inhaltsverzeichnis und das Abbildungsverzeichnis
 mit 1.5 Zeilenabstand.
 
 Ist es möglich, dass ich den Zeilenabstand für diese Bereiche auf den
 normalen Zeilenabstand stelle? Kann ich das mit TeX-Code irgendwie einbauen.
 
 Herzlichen Dank für die Information.
 
 Beste Grüsse
 Peter Pattis

Hyphenating a hyphenated word at a line break

I have a fancy hyphenated word, crosstalk-cancelled, where I spell it with (I 
believe) the proper - which is an n-dash. When this is rendered in the vicinity 
of a line wrap, the entire thing gets pushed to the next line, leaving a lot of 
ugly white space in the first line. So I inserted a hyphenation point after the 
-. This shows on the LyX screen as sort of -- which is my original n-dash and a 
shorter blue dash, probably supposed to represent a hyphen. This is all great, 
but when this version is rendered, the line break now appears after 
crosstalk--, that is, both the n-dash _and_ the hyphenation point are rendered 
which looks very wrong. What is the typographer's say on this, and is LyX doing 
the right thing. Also, is this a LyX problem or a TeX problem? My guess the 
typographer would say, let the n-dash stand alone if it occurs at a line break.

Jerry

\usepackage{flushend} on two-column documents causes misplaced footnotes

When I insert 

\usepackage{flushend}

into the preamble and make the setting for two-column output, so that the 
columns on the last page have the same length (flush end), _some_ footnotes 
appear in embarrassingly inappropriate places, meaning, in the middle of a 
column, surrounded above and below by normal text.

Is this a TeX problem? Is there a known cure? Should I go to a LaTeX group and 
ask this?

Jerry

Re: Generating a Tex

On Wed, Aug 27, 2014 at 10:39 PM, William Hanson whan...@umn.edu wrote:

 This looks wonderful.  However I can't get beyond Step 2 where I'm asked
 to create a new folder.  I can't do this because I don't have
 administrative status.


Waluyo's bog post explained how to take care of a different problem:
namely, how to install a particular Springer LaTeX class (svjour3) in Lyx
and how to create a LyX document that uses it.
I don't know which class Springer has told you to use (there other others,
depending on journal/book collections), but it is indeed svjour3 you
should have it  installed on your system already. You can check by going to
DocumentSettings...Document class  and clicking on the pop-up menu on
the right just under Document class. If you have svjour3 installed, you
will see an item taht reads article (Springer svjour3/global)
Select it and you are all set.

I'll reply to the other problem (the bibtex issue) in another post.


Cheers,

S.


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

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

Re: Generating a Tex

On Wed, Aug 27, 2014 at 11:09 PM, William Hanson whan...@umn.edu wrote:

 Sorry, but I do not seem to be able to reply except by top posting.

 I'm using Windows, 64 bit.

 Here's the very end of my .tex file:

 \begin{quotation}

 \bibliographystyle{plain}

 \bibliography{\string//phil-home.ad.umn.edu/phil-home$/whanson/My
 Documents/BibTeX/library\string}

 \end{quotation}

 \end{document}


 I have tried removing the space in ...My Documents ..., but it doesn't
 help.  In fact in the process of removing the spaces I've somehow managed
 to mess up my document so that now when I convert it to a pdf file there
 are no references at the end.  And in the text all the citations say [?].



I suppose removing the space in My Documents won't help---not, that is,
unless you actaully rename the My Documents directory in Windows to
MyDocuments. And that is not a great idea, as My Documents is a Windows
standard directory and renaming it will undoubtedly mess things up badly,
At any rate, since the the address of your bib file is wrapped by a \string
command, it should actually work even if it contains a space---that is what
the \string command should take care of. In theory at least.
We need to know exactly what is the problem that prevents bibtex from
producing a bbl file. I would suggest the following if you'd like more help:

1. Export your file  to Latex(plain) and produce something called
myfile.tex
2. Run pdflatex myfile.tex in a terminal.
3. You will see that pdflatex produces (in addition to myfile.pdf) a file
called myfile.log.
4. Post that file to the list
5. Run bibtex myfile and cut and paste everything bibtex spits to the
terminal into another file. Call it myfile.bib.log.
6. Post that file to the list as well

(there are more elegant ways to collect a program's output than what I just
suggested, but I don't know how to accomplish them in Windows. Perhaps
other users may help. But the above should work)

Cheers,
Stefano



 Bill







 On Wed, Aug 27, 2014 at 2:47 PM, stefano franchi 
 stefano.fran...@gmail.com wrote:




 On Wed, Aug 27, 2014 at 2:26 PM, William Hanson whan...@umn.edu wrote:

 Well, I got as far as your 3, that is I ran bibtex on myfile.tex from
 the command line.  It gave me lots of LateX Errors, like

 LaTeX Warning: Citation `plantinga:1985a' on page 2 undefined on input
 line 103



 That probably means bibtex cannot find your bib file(s).  Look at the
 .tex file in anb editor. At the very end (most likely the next to last
 line), you'll see a line like:
 \bibliography{}

 Inside the braces you will have the complete path to your bibtex file
 (the .bib file, but without the extension). Check that:
 1. That path is indeed correct (is the file really there?).
 2, There are no spaces in the path (fix the problem if otherwise. Easiest
 way is to copy your lyx file and your bib file to a temporary directory in
 your home directory)


 If neither of these suggestions works, please post the complete output of
 the bibtex run (from the terminal)


 But it didn't seem to produce  myfile.bbl; at least I don't see it
 anywhere.  Maybe it didn't generate because of all the errors?
 So I'm stuck at this point.

 Yes, it was not generated because bibtex ran into troubles.



 By the way, I did find a space in the filename, which I closed.  I don't
 know how to tell if there are spaces in the directory structure.



  Which system are you on (Mac, Linux, Win)? I can help with the first
 two, but I am hopeless on Windows.

 Cheers,

 Stefano

 P.S. Also, please do not top post. Answer in line with your replies
 immediately following the relevant point you are responding to. It makes
 for easier and faster reading. Besides, it is the list convention

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

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





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

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

Re: \usepackage{flushend} on two-column documents causes misplaced footnotes


On 08/28/2014 07:11 AM, Jerry wrote:

When I insert

\usepackage{flushend}

into the preamble and make the setting for two-column output, so that the columns on the 
last page have the same length (flush end), _some_ footnotes appear in 
embarrassingly inappropriate places, meaning, in the middle of a column, surrounded above 
and below by normal text.

Is this a TeX problem? Is there a known cure? Should I go to a LaTeX group and 
ask this?


Yes, it's presumably an issue with that package.

rh

Re: Hyphenating a hyphenated word at a line break


On 08/28/2014 07:03 AM, Jerry wrote:

I have a fancy hyphenated word, crosstalk-cancelled, where I spell it with (I 
believe) the proper - which is an n-dash. When this is rendered in the vicinity 
of a line wrap, the entire thing gets pushed to the next line, leaving a lot of 
ugly white space in the first line. So I inserted a hyphenation point after the 
-. This shows on the LyX screen as sort of -- which is my original n-dash and a 
shorter blue dash, probably supposed to represent a hyphen. This is all great, 
but when this version is rendered, the line break now appears after 
crosstalk--, that is, both the n-dash _and_ the hyphenation point are rendered 
which looks very wrong. What is the typographer's say on this, and is LyX doing 
the right thing. Also, is this a LyX problem or a TeX problem? My guess the 
typographer would say, let the n-dash stand alone if it occurs at a line break.


Yes, the n-dash should stand alone, but LaTeX is doing what you are 
asking: You told it that it was OK to hyphenate there, so it has. What 
you want is the \linebreak command instead. LyX does not have native 
support for this, so you have to use ERT. Note that you can use an 
optional argument with \linebreak, as well, from 0 to 4, which mean: you 
can break here; you really must break here. So you could try:

\linebreak[1]
in ERT to start. The advantage of using the optional argument is that, 
if you move some text around, LaTeX still has a chance of getting the 
linebreaking right, whereas if you insist the line be broken there, then 
things could go very ugly.


Richard

Re: Hyphenating a hyphenated word at a line break

On Thu, Aug 28, 2014 at 6:03 AM, Jerry lancebo...@qwest.net wrote:

Cheers,

Stefano

[1]
http://stackoverflow.com/questions/2193307/how-to-get-latex-to-hyphenate-a-word-that-contains-a-dash

--
__
Stefano Franchi

stefano.fran...@gmail.com stef...@tamu.edu
http://stefano.cleinias.org

Re: Hyphenating a hyphenated word at a line break

On 08/28/2014 11:43 AM, stefano franchi wrote:

On Thu, Aug 28, 2014 at 6:03 AM, Jerry lancebo...@qwest.net
mailto:lancebo...@qwest.net wrote:

I have a fancy hyphenated word, crosstalk-cancelled, where I spell
it with (I believe) the proper - which is an n-dash. When this is
rendered in the vicinity of a line wrap, the entire thing gets
pushed to the next line, leaving a lot of ugly white space in the
first line. So I inserted a hyphenation point after the -. This
shows on the LyX screen as sort of -- which is my original n-dash
and a shorter blue dash, probably supposed to represent a hyphen.
This is all great, but when this version is rendered, the line
break now appears after crosstalk--, that is, both the n-dash
_and_ the hyphenation point are rendered which looks very wrong.
What is the typographer's say on this, and is LyX doing the right
thing. Also, is this a LyX problem or a TeX problem? My guess the
typographer would say, let the n-dash stand alone if it occurs at
a line break.

This stackexchange question [1] contains more info than you probably
wished for, but it may still be useful in laying out the various ways
to approach the problem. Richard's suggestion (\newline) is indeed one
of those listed. Of course, all solution refer to LaTeX an not Lyxd,
which means you can use them only if you insert them in ERT boxes (and
add the corresponding packages, when needed, to your Document's preamble)

[1]
http://stackoverflow.com/questions/2193307/how-to-get-latex-to-hyphenate-a-word-that-contains-a-dash

Wow, that is a lot of information! Mostly, that deals with cases where
you use the word a lot. I took this to be more of a one-off sort of
issue. But I'm going to save that link

Richard

Re: Hyphenating a hyphenated word at a line break

On Thu, Aug 28, 2014 at 11:19 AM, Richard Heck rgh...@lyx.org wrote:

On 08/28/2014 11:43 AM, stefano franchi wrote:

On Thu, Aug 28, 2014 at 6:03 AM, Jerry lancebo...@qwest.net wrote:

I have a fancy hyphenated word, crosstalk-cancelled, where I spell it
with (I believe) the proper - which is an n-dash. When this is rendered in
the vicinity of a line wrap, the entire thing gets pushed to the next line,
leaving a lot of ugly white space in the first line. So I inserted a
hyphenation point after the -. This shows on the LyX screen as sort of --
which is my original n-dash and a shorter blue dash, probably supposed to
represent a hyphen. This is all great, but when this version is rendered,
the line break now appears after crosstalk--, that is, both the n-dash
_and_ the hyphenation point are rendered which looks very wrong. What is
the typographer's say on this, and is LyX doing the right thing. Also, is
this a LyX problem or a TeX problem? My guess the typographer would say,
let the n-dash stand alone if it occurs at a line break.

This stackexchange question [1] contains more info than you probably
wished for, but it may still be useful in laying out the various ways to
approach the problem. Richard's suggestion (\newline) is indeed one of
those listed. Of course, all solution refer to LaTeX an not Lyxd, which
means you can use them only if you insert them in ERT boxes (and add the
corresponding packages, when needed, to your Document's preamble)

[1]
http://stackoverflow.com/questions/2193307/how-to-get-latex-to-hyphenate-a-word-that-contains-a-dash

Wow, that is a lot of information! Mostly, that deals with cases where you
use the word a lot. I took this to be more of a one-off sort of issue. But
I'm going to save that link

Cheers,

[1] http://tex.stackexchange.com/questions/3819/dashes-vs-vs

--
__
Stefano Franchi

stefano.fran...@gmail.com stef...@tamu.edu
http://stefano.cleinias.org

Re: Generating a Tex

The first time I tried to execute your step 1, immediately above, I got an
error saying that it wouldn't work because of spaces.   I tried it again
and I did get myfile.tex.  I then ran pdflatex myfile.tex (your step 2).
But, contrary to your 3, I did not get a file called myfile.log. (It did,
however, produce the following files:  myfile.toc, myfile.aux,
synctex.gz.)

So I'm stuck at this point.

Cheers,

Bill


On Thu, Aug 28, 2014 at 9:03 AM, stefano franchi stefano.fran...@gmail.com
wrote:




 On Wed, Aug 27, 2014 at 11:09 PM, William Hanson whan...@umn.edu wrote:

 Sorry, but I do not seem to be able to reply except by top posting.

 I'm using Windows, 64 bit.

 Here's the very end of my .tex file:

 \begin{quotation}

 \bibliographystyle{plain}

 \bibliography{\string//phil-home.ad.umn.edu/phil-home$/whanson/My
 Documents/BibTeX/library\string}

 \end{quotation}

 \end{document}


 I have tried removing the space in ...My Documents ..., but it doesn't
 help.  In fact in the process of removing the spaces I've somehow managed
 to mess up my document so that now when I convert it to a pdf file there
 are no references at the end.  And in the text all the citations say [?].



 I suppose removing the space in My Documents won't help---not, that is,
 unless you actaully rename the My Documents directory in Windows to
 MyDocuments. And that is not a great idea, as My Documents is a Windows
 standard directory and renaming it will undoubtedly mess things up badly,
 At any rate, since the the address of your bib file is wrapped by a
 \string command, it should actually work even if it contains a space---that
 is what the \string command should take care of. In theory at least.
 We need to know exactly what is the problem that prevents bibtex from
 producing a bbl file. I would suggest the following if you'd like more help:

 1. Export your file  to Latex(plain) and produce something called
 myfile.tex
 2. Run pdflatex myfile.tex in a terminal.
 3. You will see that pdflatex produces (in addition to myfile.pdf) a file
 called myfile.log.
 4. Post that file to the list
 5. Run bibtex myfile and cut and paste everything bibtex spits to the
 terminal into another file. Call it myfile.bib.log.
 6. Post that file to the list as well

 (there are more elegant ways to collect a program's output than what I
 just suggested, but I don't know how to accomplish them in Windows. Perhaps
 other users may help. But the above should work)

 Cheers,
 Stefano



 Bill







 On Wed, Aug 27, 2014 at 2:47 PM, stefano franchi 
 stefano.fran...@gmail.com wrote:




 On Wed, Aug 27, 2014 at 2:26 PM, William Hanson whan...@umn.edu wrote:

 Well, I got as far as your 3, that is I ran bibtex on myfile.tex from
 the command line.  It gave me lots of LateX Errors, like

 LaTeX Warning: Citation `plantinga:1985a' on page 2 undefined on input
 line 103



 That probably means bibtex cannot find your bib file(s).  Look at the
 .tex file in anb editor. At the very end (most likely the next to last
 line), you'll see a line like:
 \bibliography{}

 Inside the braces you will have the complete path to your bibtex file
 (the .bib file, but without the extension). Check that:
 1. That path is indeed correct (is the file really there?).
 2, There are no spaces in the path (fix the problem if otherwise.
 Easiest way is to copy your lyx file and your bib file to a temporary
 directory in your home directory)


 If neither of these suggestions works, please post the complete output
 of the bibtex run (from the terminal)


 But it didn't seem to produce  myfile.bbl; at least I don't see it
 anywhere.  Maybe it didn't generate because of all the errors?
 So I'm stuck at this point.

 Yes, it was not generated because bibtex ran into troubles.



 By the way, I did find a space in the filename, which I closed.  I
 don't know how to tell if there are spaces in the directory structure.



  Which system are you on (Mac, Linux, Win)? I can help with the first
 two, but I am hopeless on Windows.

 Cheers,

 Stefano

 P.S. Also, please do not top post. Answer in line with your replies
 immediately following the relevant point you are responding to. It makes
 for easier and faster reading. Besides, it is the list convention

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

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





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

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

Re: Generating a Tex

On Thu, Aug 28, 2014 at 11:47 AM, William Hanson whan...@umn.edu wrote:

 The first time I tried to execute your step 1, immediately above, I got an
 error saying that it wouldn't work because of spaces.   I tried it again
 and I did get myfile.tex.  I then ran pdflatex myfile.tex (your step 2).
 But, contrary to your 3, I did not get a file called myfile.log. (It did,
 however, produce the following files:  myfile.toc, myfile.aux,
 synctex.gz.)



This is strange, pdflatex always produces a log file unless instructed
otherwise. Are you calling pdflatex from the command line or are you using
a latex editor (such as texmaker or winedit, for instance). That would
explain the lack of a log file, as these editors may be configured to erase
log files and/or move them to other directories.

Do you also have a myfile.pdf file? That would indicate that the pdflatex
run was at least partially successful.

And what did you see on the console when you ran pdflatex (assuming you are
using a terminal-like interface and not a LaTeX editor)?


S.



-- 
__
Stefano Franchi

stefano.fran...@gmail.com stef...@tamu.edu
http://stefano.cleinias.org

Re: Generating a Tex

I am calling pdflatex from the command line of TeXworks.

It did also produce a myfile.pdf file.

What I see on my screen after running pdflatex is a window labeled
myfile.tex - TeXworks.  It contains what apparently is myfile.tex, which I
assume is the TeX version of my paper,




On Thu, Aug 28, 2014 at 11:58 AM, stefano franchi stefano.fran...@gmail.com
 wrote:




 On Thu, Aug 28, 2014 at 11:47 AM, William Hanson whan...@umn.edu wrote:

 The first time I tried to execute your step 1, immediately above, I got
 an error saying that it wouldn't work because of spaces.   I tried it again
 and I did get myfile.tex.  I then ran pdflatex myfile.tex (your step 2).
 But, contrary to your 3, I did not get a file called myfile.log. (It did,
 however, produce the following files:  myfile.toc, myfile.aux,
 synctex.gz.)



 This is strange, pdflatex always produces a log file unless instructed
 otherwise. Are you calling pdflatex from the command line or are you using
 a latex editor (such as texmaker or winedit, for instance). That would
 explain the lack of a log file, as these editors may be configured to erase
 log files and/or move them to other directories.

 Do you also have a myfile.pdf file? That would indicate that the pdflatex
 run was at least partially successful.

 And what did you see on the console when you ran pdflatex (assuming you
 are using a terminal-like interface and not a LaTeX editor)?


 S.



 --
 __
 Stefano Franchi

 stefano.fran...@gmail.com stef...@tamu.edu
 http://stefano.cleinias.org

Re: Generating a Tex

Breaking News!  I just ran LaTeX(plain) on myfile.lyx and it produced
mytext.bbl.  I've never gotten a bbl file before.  This is good, isn't it?
Is there an easy way forward from here?


On Thu, Aug 28, 2014 at 12:59 PM, stefano franchi stefano.fran...@gmail.com
 wrote:




 On Thu, Aug 28, 2014 at 12:55 PM, stefano franchi 
 stefano.fran...@gmail.com wrote:




 On Thu, Aug 28, 2014 at 12:26 PM, William Hanson whan...@umn.edu wrote:

 I am calling pdflatex from the command line of TeXworks.

 It did also produce a myfile.pdf file.

 What I see on my screen after running pdflatex is a window labeled
 myfile.tex - TeXworks.  It contains what apparently is myfile.tex, which I
 assume is the TeX version of my paper,



 If you use texworks, you should just be able to select pdflatex from the
 Typeset menu, and it will compile your file to myfile.pdf and also produce
 a myfile.log. For instance, this is what I see in TeXWorks console, when I
 try to compile a test.tex file:

 This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded
 format=pdflatex)

 restricted \write18 enabled.

 entering extended mode

 (./test.tex

 LaTeX2e 2014/05/01

 Babel 3.9k and hyphenation patterns for 79 languages loaded.

 (/usr/local/texlive/2014/texmf-dist/tex/latex/base/article.cls

 Document Class: article 2007/10/19 v1.4h Standard LaTeX document class

 (/usr/local/texlive/2014/texmf-dist/tex/latex/base/size11.clo))

 (/usr/local/texlive/2014/texmf-dist/tex/latex/base/fontenc.sty

 (/usr/local/texlive/2014/texmf-dist/tex/latex/base/t1enc.def))

 (/usr/local/texlive/2014/texmf-dist/tex/generic/babel/babel.sty

 (/usr/local/texlive/2014/texmf-dist/tex/generic/babel-english/english.ldf

 (/usr/local/texlive/2014/texmf-dist/tex/generic/babel/babel.def)))


 LaTeX Warning: Unused global option(s):

 [article].


 (./test.aux)
 [1{/usr/local/texlive/2014/texmf-var/fonts/map/pdftex/updmap/pdfte

 x.map}] (./test.aux)
 ){/usr/local/texlive/2014/texmf-dist/fonts/enc/dvips/cm-su


 per/cm-super-t1.enc}/usr/local/texlive/2014/texmf-dist/fonts/type1/public/cm-s

 uper/sfrm1095.pfb

 Output written on test.pdf (1 page, 13144 bytes).

 SyncTeX written on test.synctex.gz.

 Transcript written on test.log.


 Notice how on the last line it informs me that it has produced a log file.


 At any rate, try recompiling your file, and if you cannot find the log
 file, juct cut and paste everything you see in TeXWorks's console output
 window into an email message and send it to the list.

 Do the same for a compilation with bibtex (just select bibtex from the
 Typeset menu and hit ctrl-T). Cut and paste the console output into an
 email message and send it to the list.


 That should give us enough info to understand what's going wrong.




 The alternative is to use a good old-fashioned terminal---I believe it is
 called Command prompt in Windows, or at least it used to be. See here [1]
 on how to do it in Windows 7 (with apologies if it is obvious to you).


 [1]
 http://smallbusiness.chron.com/open-terminal-session-windows-7-56627.html




 S.


 --
 __
 Stefano Franchi

 stefano.fran...@gmail.com stef...@tamu.edu
 http://stefano.cleinias.org

Re: Generating a Tex

On Thu, Aug 28, 2014 at 1:54 PM, William Hanson whan...@umn.edu wrote:

 Breaking News!  I just ran LaTeX(plain) on myfile.lyx and it produced
 mytext.bbl.  I've never gotten a bbl file before.  This is good, isn't it?
 Is there an easy way forward from here?



Assuming your bbl file is correct, you're almost there. You just:

1. open the myfile.bbl file in TeXWorks (be sure to select all files
ffrom the open dialog or it won't show up)
2. Select and copy everything in the bbl file
3, go to your myfile,.tex file in TeXWorks, delete the two lines (at the
end), that begin with, respectively, \bibliographystyle and \bibliography
and replace them with the content you just copied from the bbl file.
4. Compile the file again with pdflatex to be sure everything works
correctly and the pdf is how it should be (with all the refs, etcetera).
5. Send to Springer!

Cheers,

Stefano

-- 
__
Stefano Franchi

stefano.fran...@gmail.com stef...@tamu.edu
http://stefano.cleinias.org

Re: Generating a Tex

So close, but my bbl file does not show up om TeXWorks.  I don't see any
all files ffrom the open dialog.


On Thu, Aug 28, 2014 at 2:12 PM, stefano franchi stefano.fran...@gmail.com
wrote:




 On Thu, Aug 28, 2014 at 1:54 PM, William Hanson whan...@umn.edu wrote:

 Breaking News!  I just ran LaTeX(plain) on myfile.lyx and it produced
 mytext.bbl.  I've never gotten a bbl file before.  This is good, isn't it?
 Is there an easy way forward from here?



 Assuming your bbl file is correct, you're almost there. You just:

 1. open the myfile.bbl file in TeXWorks (be sure to select all files
 ffrom the open dialog or it won't show up)
 2. Select and copy everything in the bbl file
 3, go to your myfile,.tex file in TeXWorks, delete the two lines (at the
 end), that begin with, respectively, \bibliographystyle and \bibliography
 and replace them with the content you just copied from the bbl file.
 4. Compile the file again with pdflatex to be sure everything works
 correctly and the pdf is how it should be (with all the refs, etcetera).
 5. Send to Springer!

 Cheers,

 Stefano

 --
 __
 Stefano Franchi

 stefano.fran...@gmail.com stef...@tamu.edu
 http://stefano.cleinias.org

Re: Generating a Tex

Foiled again, I'm afraid.  All that's in the bbl file is

\begin{thebibliography}{}

\end{thebibliography}


Cheers nonetheless.



On Thu, Aug 28, 2014 at 3:02 PM, stefano franchi stefano.fran...@gmail.com
wrote:




 On Thu, Aug 28, 2014 at 2:46 PM, William Hanson whan...@umn.edu wrote:

 So close, but my bbl file does not show up om TeXWorks.  I don't see any
   all files ffrom the open dialog.



 Look at the last line in the open file dialog screen (see attached
 screenshot, where it says Filter). It is a pop up menu, you need to click
 on it and select the last item all files


 S.

 --
 __
 Stefano Franchi

 stefano.fran...@gmail.com stef...@tamu.edu
 http://stefano.cleinias.org

Re: Generating a Tex

On Thu, Aug 28, 2014 at 3:22 PM, William Hanson whan...@umn.edu wrote:

 Foiled again, I'm afraid.  All that's in the bbl file is

 \begin{thebibliography}{}

 \end{thebibliography}


 Cheers nonetheless.


That means that the bibtex run failed. Run bibtex again from within
TeXworks, and cut and paste the console output into an email message to the
list.
It is hard to help without knowing what is wrong.
Cheers,

S.

-- 
__
Stefano Franchi

stefano.fran...@gmail.com stef...@tamu.edu
http://stefano.cleinias.org

KOMA-book: Appendices

2014-08-28 Thread Rich Shepard


  With Lyx-2.1.1 and the KOMA book class I want to add appendices in
addition to the Bibliography. The Document menu has an item, 'Start Appendix
Here,' and the KOMA book document tells me that appendices include the
bibliography, index, and other backmatter.

  Does it make any difference if I start apendices before or after the
bibliography? If I want them numbered (upper case letters according to the
KOMA-script book document) do I set each in the Chapter environment,
Chapter* environment, or something else? The bibliograpy is not now numbered
which leads me to think the other appendices should start after it.

  But, ... I'm open to suggestions and guidelines.

Rich

Re: \usepackage{flushend} on two-column documents causes misplaced footnotes

2014-08-28 Thread Marcelo Acuña

I have not problem with flushend and two columns.
Maybe the problem is caused elsewhere in the document or preamble.


Regards
Marcelo


El Jueves, 28 de agosto, 2014 12:24:03, Richard Heck rgh...@lyx.org escribió:
 


On 08/28/2014 07:11 AM, Jerry wrote:

 When I insert

 \usepackage{flushend}

 into the preamble and make the setting for two-column output, so that the 
 columns on the last page have the same length (flush end), _some_ footnotes 
 appear in embarrassingly inappropriate places, meaning, in the middle of a 
 column, surrounded above and below by normal text.

 Is this a TeX problem? Is there a known cure? Should I go to a LaTeX group 
 and ask this?

Yes, it's presumably an issue with that package.

rh

Re: FRAGE: Zeilenabstand

2014-08-28 Thread Jürgen Spitzmüller

Hello

This is an English list, so I reply in English. Please let me know if this is 
a problem.

Try this:

* Select the TOC and LOT insets (the grey buttons for the Table of Contents 
and List of figures, respectively) with the cursor

* Open Edit > Paragraph Settings (Bearbeiten > Absatzeinstellungen)

* Set "Paragraph Spacing" to "Normal" ("Einfach")

* Hit OK.

HTH
Jürgen

Am Montag 25 August 2014, 20:02:39 schrieb Peter Pattis:
> Sehr geehrtes LyX-Team
> 
> Ich habe eine Frage zum Zeilenabstand.
> 
> Ich habe für das ganze Dokument den Zeilenabstand 1.5 angegeben. Nun
> erstellt LyX aber auch das Inhaltsverzeichnis und das Abbildungsverzeichnis
> mit 1.5 Zeilenabstand.
> 
> Ist es möglich, dass ich den Zeilenabstand für diese Bereiche auf den
> normalen Zeilenabstand stelle? Kann ich das mit TeX-Code irgendwie einbauen.
> 
> Herzlichen Dank für die Information.
> 
> Beste Grüsse
> Peter Pattis

Hyphenating a hyphenated word at a line break

I have a fancy hyphenated word, crosstalk-cancelled, where I spell it with (I 
believe) the proper - which is an n-dash. When this is rendered in the vicinity 
of a line wrap, the entire thing gets pushed to the next line, leaving a lot of 
ugly white space in the first line. So I inserted a hyphenation point after the 
-. This shows on the LyX screen as sort of -- which is my original n-dash and a 
shorter blue dash, probably supposed to represent a hyphen. This is all great, 
but when this version is rendered, the line break now appears after 
crosstalk--, that is, both the n-dash _and_ the hyphenation point are rendered 
which looks very wrong. What is the typographer's say on this, and is LyX doing 
the right thing. Also, is this a LyX problem or a TeX problem? My guess the 
typographer would say, let the n-dash stand alone if it occurs at a line break.

Jerry

\usepackage{flushend} on two-column documents causes misplaced footnotes

When I insert 

\usepackage{flushend}

into the preamble and make the setting for two-column output, so that the 
columns on the last page have the same length ("flush end"), _some_ footnotes 
appear in embarrassingly inappropriate places, meaning, in the middle of a 
column, surrounded above and below by normal text.

Is this a TeX problem? Is there a known cure? Should I go to a LaTeX group and 
ask this?

Jerry

Re: Generating a Tex

On Wed, Aug 27, 2014 at 10:39 PM, William Hanson  wrote:

> This looks wonderful.  However I can't get beyond Step 2 where I'm asked
> to create a new folder.  I can't do this because I don't have
> administrative status.
>
>
Waluyo's bog post explained how to take care of a different problem:
namely, how to install a particular Springer LaTeX class (svjour3) in Lyx
and how to create a LyX document that uses it.
I don't know which class Springer has told you to use (there other others,
depending on journal/book collections), but it is indeed svjour3 you
should have it  installed on your system already. You can check by going to
Document>>Settings...>>Document class  and clicking on the pop-up menu on
the right just under "Document class". If you have svjour3 installed, you
will see an item taht reads "article (Springer svjour3/global)"
Select it and you are all set.

I'll reply to the other problem (the bibtex issue) in another post.


Cheers,

S.


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

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

Re: Generating a Tex

On Wed, Aug 27, 2014 at 11:09 PM, William Hanson  wrote:

> Sorry, but I do not seem to be able to reply except by "top posting".
>
> I'm using Windows, 64 bit.
>
> Here's the very end of my .tex file:
>
> \begin{quotation}
>
> \bibliographystyle{plain}
>
> \bibliography{\string"//phil-home.ad.umn.edu/phil-home$/whanson/My
> Documents/BibTeX/library\string"}
>
> \end{quotation}
>
> \end{document}
>
>
> I have tried removing the space in "...My Documents ...", but it doesn't
> help.  In fact in the process of removing the spaces I've somehow managed
> to mess up my document so that now when I convert it to a pdf file there
> are no references at the end.  And in the text all the citations say [?].
>
>
>
I suppose removing the space in "My Documents" won't help---not, that is,
unless you actaully rename the "My Documents" directory in Windows to
"MyDocuments". And that is not a great idea, as "My Documents" is a Windows
standard directory and renaming it will undoubtedly mess things up badly,
At any rate, since the the address of your bib file is wrapped by a \string
command, it should actually work even if it contains a space---that is what
the \string command should take care of. In theory at least.
We need to know exactly what is the problem that prevents bibtex from
producing a bbl file. I would suggest the following if you'd like more help:

1. Export your file  to Latex(plain) and produce something called
"myfile.tex"
2. Run "pdflatex myfile.tex" in a terminal.
3. You will see that pdflatex produces (in addition to myfile.pdf) a file
called myfile.log.
4. Post that file to the list
5. Run "bibtex myfile" and cut and paste everything bibtex spits to the
terminal into another file. Call it myfile.bib.log.
6. Post that file to the list as well

(there are more elegant ways to collect a program's output than what I just
suggested, but I don't know how to accomplish them in Windows. Perhaps
other users may help. But the above should work)

Cheers,
Stefano



> Bill
>
>
>
>
>
>
>
> On Wed, Aug 27, 2014 at 2:47 PM, stefano franchi <
> stefano.fran...@gmail.com> wrote:
>
>>
>>
>>
>> On Wed, Aug 27, 2014 at 2:26 PM, William Hanson  wrote:
>>
>>> Well, I got as far as your 3, that is I ran bibtex on myfile.tex from
>>> the command line.  It gave me lots of LateX Errors, like
>>>
>>> LaTeX Warning: Citation `plantinga:1985a' on page 2 undefined on input
>>> line 103
>>>
>>
>>
>> That probably means bibtex cannot find your bib file(s).  Look at the
>> .tex file in anb editor. At the very end (most likely the next to last
>> line), you'll see a line like:
>> \bibliography{}
>>
>> Inside the braces you will have the complete path to your bibtex file
>> (the .bib file, but without the extension). Check that:
>> 1. That path is indeed correct (is the file really there?).
>> 2, There are no spaces in the path (fix the problem if otherwise. Easiest
>> way is to copy your lyx file and your bib file to a temporary directory in
>> your home directory)
>>
>>
>> If neither of these suggestions works, please post the complete output of
>> the bibtex run (from the terminal)
>>
>>
>>> But it didn't seem to produce  myfile.bbl; at least I don't see it
>>> anywhere.  Maybe it didn't generate because of all the errors?
>>> So I'm stuck at this point.
>>>
>>> Yes, it was not generated because bibtex ran into troubles.
>>
>>
>>
>>> By the way, I did find a space in the filename, which I closed.  I don't
>>> know how to tell if there are spaces in the directory structure.
>>>
>>>
>>
>>  Which system are you on (Mac, Linux, Win)? I can help with the first
>> two, but I am hopeless on Windows.
>>
>> Cheers,
>>
>> Stefano
>>
>> P.S. Also, please do not "top post." Answer in line with your replies
>> immediately following the relevant point you are responding to. It makes
>> for easier and faster reading. Besides, it is the list convention
>>
>> --
>> __
>> Stefano Franchi
>> Associate Research Professor
>> Department of Hispanic Studies Ph:   +1 (979) 845-2125
>> Texas A University  Fax:  +1 (979) 845-6421
>> College Station, Texas, USA
>>
>> stef...@tamu.edu
>> http://stefano.cleinias.org
>>
>
>


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

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

Re: \usepackage{flushend} on two-column documents causes misplaced footnotes


On 08/28/2014 07:11 AM, Jerry wrote:

When I insert

\usepackage{flushend}

into the preamble and make the setting for two-column output, so that the columns on the 
last page have the same length ("flush end"), _some_ footnotes appear in 
embarrassingly inappropriate places, meaning, in the middle of a column, surrounded above 
and below by normal text.

Is this a TeX problem? Is there a known cure? Should I go to a LaTeX group and 
ask this?


Yes, it's presumably an issue with that package.

rh

Re: Hyphenating a hyphenated word at a line break


On 08/28/2014 07:03 AM, Jerry wrote:

I have a fancy hyphenated word, crosstalk-cancelled, where I spell it with (I 
believe) the proper - which is an n-dash. When this is rendered in the vicinity 
of a line wrap, the entire thing gets pushed to the next line, leaving a lot of 
ugly white space in the first line. So I inserted a hyphenation point after the 
-. This shows on the LyX screen as sort of -- which is my original n-dash and a 
shorter blue dash, probably supposed to represent a hyphen. This is all great, 
but when this version is rendered, the line break now appears after 
crosstalk--, that is, both the n-dash _and_ the hyphenation point are rendered 
which looks very wrong. What is the typographer's say on this, and is LyX doing 
the right thing. Also, is this a LyX problem or a TeX problem? My guess the 
typographer would say, let the n-dash stand alone if it occurs at a line break.


Yes, the n-dash should stand alone, but LaTeX is doing what you are 
asking: You told it that it was OK to hyphenate there, so it has. What 
you want is the \linebreak command instead. LyX does not have native 
support for this, so you have to use ERT. Note that you can use an 
optional argument with \linebreak, as well, from 0 to 4, which mean: you 
can break here; you really must break here. So you could try:

\linebreak[1]
in ERT to start. The advantage of using the optional argument is that, 
if you move some text around, LaTeX still has a chance of getting the 
linebreaking right, whereas if you insist the line be broken there, then 
things could go very ugly.


Richard

Re: Hyphenating a hyphenated word at a line break

On Thu, Aug 28, 2014 at 6:03 AM, Jerry  wrote:

> I have a fancy hyphenated word, crosstalk-cancelled, where I spell it with
> (I believe) the proper - which is an n-dash. When this is rendered in the
> vicinity of a line wrap, the entire thing gets pushed to the next line,
> leaving a lot of ugly white space in the first line. So I inserted a
> hyphenation point after the -. This shows on the LyX screen as sort of --
> which is my original n-dash and a shorter blue dash, probably supposed to
> represent a hyphen. This is all great, but when this version is rendered,
> the line break now appears after crosstalk--, that is, both the n-dash
> _and_ the hyphenation point are rendered which looks very wrong. What is
> the typographer's say on this, and is LyX doing the right thing. Also, is
> this a LyX problem or a TeX problem? My guess the typographer would say,
> let the n-dash stand alone if it occurs at a line break.
>
>

This stackexchange question [1] contains more info than you probably wished
for, but it may still be useful in laying out the various ways to approach
the problem. Richard's suggestion (\newline) is indeed one of those listed.
Of course, all solution refer to LaTeX an not Lyxd, which means you can use
them only if you insert them in ERT boxes (and add the corresponding
packages, when needed, to your Document's preamble)

Cheers,

Stefano

[1]
http://stackoverflow.com/questions/2193307/how-to-get-latex-to-hyphenate-a-word-that-contains-a-dash

-- 
__
Stefano Franchi

stefano.fran...@gmail.com 
http://stefano.cleinias.org

Re: Hyphenating a hyphenated word at a line break

On 08/28/2014 11:43 AM, stefano franchi wrote:

On Thu, Aug 28, 2014 at 6:03 AM, Jerry > wrote:

I have a fancy hyphenated word, crosstalk-cancelled, where I spell
it with (I believe) the proper - which is an n-dash. When this is
rendered in the vicinity of a line wrap, the entire thing gets
pushed to the next line, leaving a lot of ugly white space in the
first line. So I inserted a hyphenation point after the -. This
shows on the LyX screen as sort of -- which is my original n-dash
and a shorter blue dash, probably supposed to represent a hyphen.
This is all great, but when this version is rendered, the line
break now appears after crosstalk--, that is, both the n-dash
_and_ the hyphenation point are rendered which looks very wrong.
What is the typographer's say on this, and is LyX doing the right
thing. Also, is this a LyX problem or a TeX problem? My guess the
typographer would say, let the n-dash stand alone if it occurs at
a line break.

This stackexchange question [1] contains more info than you probably
wished for, but it may still be useful in laying out the various ways
to approach the problem. Richard's suggestion (\newline) is indeed one
of those listed. Of course, all solution refer to LaTeX an not Lyxd,
which means you can use them only if you insert them in ERT boxes (and
add the corresponding packages, when needed, to your Document's preamble)

[1]
http://stackoverflow.com/questions/2193307/how-to-get-latex-to-hyphenate-a-word-that-contains-a-dash

Wow, that is a lot of information! Mostly, that deals with cases where
you use the word a lot. I took this to be more of a one-off sort of
issue. But I'm going to save that link

Richard

Re: Hyphenating a hyphenated word at a line break

On Thu, Aug 28, 2014 at 11:19 AM, Richard Heck  wrote:

>  On 08/28/2014 11:43 AM, stefano franchi wrote:
>
>
>
>
> On Thu, Aug 28, 2014 at 6:03 AM, Jerry  wrote:
>
>> I have a fancy hyphenated word, crosstalk-cancelled, where I spell it
>> with (I believe) the proper - which is an n-dash. When this is rendered in
>> the vicinity of a line wrap, the entire thing gets pushed to the next line,
>> leaving a lot of ugly white space in the first line. So I inserted a
>> hyphenation point after the -. This shows on the LyX screen as sort of --
>> which is my original n-dash and a shorter blue dash, probably supposed to
>> represent a hyphen. This is all great, but when this version is rendered,
>> the line break now appears after crosstalk--, that is, both the n-dash
>> _and_ the hyphenation point are rendered which looks very wrong. What is
>> the typographer's say on this, and is LyX doing the right thing. Also, is
>> this a LyX problem or a TeX problem? My guess the typographer would say,
>> let the n-dash stand alone if it occurs at a line break.
>>
>>
>
>  This stackexchange question [1] contains more info than you probably
> wished for, but it may still be useful in laying out the various ways to
> approach the problem. Richard's suggestion (\newline) is indeed one of
> those listed. Of course, all solution refer to LaTeX an not Lyxd, which
> means you can use them only if you insert them in ERT boxes (and add the
> corresponding packages, when needed, to your Document's preamble)
>
> [1]
> http://stackoverflow.com/questions/2193307/how-to-get-latex-to-hyphenate-a-word-that-contains-a-dash
>
>
> Wow, that is a lot of information! Mostly, that deals with cases where you
> use the word a lot. I took this to be more of a one-off sort of issue. But
> I'm going to save that link
>
>

Well, for more time-wasting typographic fun, you could also read the
following SX question [1]. Look in particular at the answer from "Lover of
Structure" One of the highest ranked). Best explanation I have ever found
of the difference between hyphen and en-dash in compound words.


Cheers,

S.

[1] http://tex.stackexchange.com/questions/3819/dashes-vs-vs




-- 
__
Stefano Franchi

stefano.fran...@gmail.com 
http://stefano.cleinias.org

Re: Generating a Tex

The first time I tried to execute your step 1, immediately above, I got an
error saying that it wouldn't work because of spaces.   I tried it again
and I did get myfile.tex.  I then ran pdflatex myfile.tex (your step 2).
But, contrary to your 3, I did not get a file called myfile.log. (It did,
however, produce the following files:  myfile.toc, myfile.aux,
synctex.gz.)

So I'm stuck at this point.

Cheers,

Bill


On Thu, Aug 28, 2014 at 9:03 AM, stefano franchi 
wrote:

>
>
>
> On Wed, Aug 27, 2014 at 11:09 PM, William Hanson  wrote:
>
>> Sorry, but I do not seem to be able to reply except by "top posting".
>>
>> I'm using Windows, 64 bit.
>>
>> Here's the very end of my .tex file:
>>
>> \begin{quotation}
>>
>> \bibliographystyle{plain}
>>
>> \bibliography{\string"//phil-home.ad.umn.edu/phil-home$/whanson/My
>> Documents/BibTeX/library\string"}
>>
>> \end{quotation}
>>
>> \end{document}
>>
>>
>> I have tried removing the space in "...My Documents ...", but it doesn't
>> help.  In fact in the process of removing the spaces I've somehow managed
>> to mess up my document so that now when I convert it to a pdf file there
>> are no references at the end.  And in the text all the citations say [?].
>>
>>
>>
> I suppose removing the space in "My Documents" won't help---not, that is,
> unless you actaully rename the "My Documents" directory in Windows to
> "MyDocuments". And that is not a great idea, as "My Documents" is a Windows
> standard directory and renaming it will undoubtedly mess things up badly,
> At any rate, since the the address of your bib file is wrapped by a
> \string command, it should actually work even if it contains a space---that
> is what the \string command should take care of. In theory at least.
> We need to know exactly what is the problem that prevents bibtex from
> producing a bbl file. I would suggest the following if you'd like more help:
>
> 1. Export your file  to Latex(plain) and produce something called
> "myfile.tex"
> 2. Run "pdflatex myfile.tex" in a terminal.
> 3. You will see that pdflatex produces (in addition to myfile.pdf) a file
> called myfile.log.
> 4. Post that file to the list
> 5. Run "bibtex myfile" and cut and paste everything bibtex spits to the
> terminal into another file. Call it myfile.bib.log.
> 6. Post that file to the list as well
>
> (there are more elegant ways to collect a program's output than what I
> just suggested, but I don't know how to accomplish them in Windows. Perhaps
> other users may help. But the above should work)
>
> Cheers,
> Stefano
>
>
>
>> Bill
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Aug 27, 2014 at 2:47 PM, stefano franchi <
>> stefano.fran...@gmail.com> wrote:
>>
>>>
>>>
>>>
>>> On Wed, Aug 27, 2014 at 2:26 PM, William Hanson  wrote:
>>>
 Well, I got as far as your 3, that is I ran bibtex on myfile.tex from
 the command line.  It gave me lots of LateX Errors, like

 LaTeX Warning: Citation `plantinga:1985a' on page 2 undefined on input
 line 103

>>>
>>>
>>> That probably means bibtex cannot find your bib file(s).  Look at the
>>> .tex file in anb editor. At the very end (most likely the next to last
>>> line), you'll see a line like:
>>> \bibliography{}
>>>
>>> Inside the braces you will have the complete path to your bibtex file
>>> (the .bib file, but without the extension). Check that:
>>> 1. That path is indeed correct (is the file really there?).
>>> 2, There are no spaces in the path (fix the problem if otherwise.
>>> Easiest way is to copy your lyx file and your bib file to a temporary
>>> directory in your home directory)
>>>
>>>
>>> If neither of these suggestions works, please post the complete output
>>> of the bibtex run (from the terminal)
>>>
>>>
 But it didn't seem to produce  myfile.bbl; at least I don't see it
 anywhere.  Maybe it didn't generate because of all the errors?
 So I'm stuck at this point.

 Yes, it was not generated because bibtex ran into troubles.
>>>
>>>
>>>
 By the way, I did find a space in the filename, which I closed.  I
 don't know how to tell if there are spaces in the directory structure.


>>>
>>>  Which system are you on (Mac, Linux, Win)? I can help with the first
>>> two, but I am hopeless on Windows.
>>>
>>> Cheers,
>>>
>>> Stefano
>>>
>>> P.S. Also, please do not "top post." Answer in line with your replies
>>> immediately following the relevant point you are responding to. It makes
>>> for easier and faster reading. Besides, it is the list convention
>>>
>>> --
>>> __
>>> Stefano Franchi
>>> Associate Research Professor
>>> Department of Hispanic Studies Ph:   +1 (979) 845-2125
>>> Texas A University  Fax:  +1 (979) 845-6421
>>> College Station, Texas, USA
>>>
>>> stef...@tamu.edu
>>> http://stefano.cleinias.org
>>>
>>
>>
>
>
> --
> __
>

Re: Generating a Tex

On Thu, Aug 28, 2014 at 11:47 AM, William Hanson  wrote:

> The first time I tried to execute your step 1, immediately above, I got an
> error saying that it wouldn't work because of spaces.   I tried it again
> and I did get myfile.tex.  I then ran pdflatex myfile.tex (your step 2).
> But, contrary to your 3, I did not get a file called myfile.log. (It did,
> however, produce the following files:  myfile.toc, myfile.aux,
> synctex.gz.)
>

This is strange, pdflatex always produces a log file unless instructed
otherwise. Are you calling pdflatex from the command line or are you using
a latex editor (such as texmaker or winedit, for instance). That would
explain the lack of a log file, as these editors may be configured to erase
log files and/or move them to other directories.

Do you also have a myfile.pdf file? That would indicate that the pdflatex
run was at least partially successful.

And what did you see on the console when you ran pdflatex (assuming you are
using a terminal-like interface and not a LaTeX editor)?

S.

-- 
__
Stefano Franchi

stefano.fran...@gmail.com 
http://stefano.cleinias.org

Re: Generating a Tex

I am calling pdflatex from the command line of TeXworks.

It did also produce a myfile.pdf file.

What I see on my screen after running pdflatex is a window labeled
myfile.tex - TeXworks.  It contains what apparently is myfile.tex, which I
assume is the TeX version of my paper,




On Thu, Aug 28, 2014 at 11:58 AM, stefano franchi  wrote:

>
>
>
> On Thu, Aug 28, 2014 at 11:47 AM, William Hanson  wrote:
>
>> The first time I tried to execute your step 1, immediately above, I got
>> an error saying that it wouldn't work because of spaces.   I tried it again
>> and I did get myfile.tex.  I then ran pdflatex myfile.tex (your step 2).
>> But, contrary to your 3, I did not get a file called myfile.log. (It did,
>> however, produce the following files:  myfile.toc, myfile.aux,
>> synctex.gz.)
>>
>
>
> This is strange, pdflatex always produces a log file unless instructed
> otherwise. Are you calling pdflatex from the command line or are you using
> a latex editor (such as texmaker or winedit, for instance). That would
> explain the lack of a log file, as these editors may be configured to erase
> log files and/or move them to other directories.
>
> Do you also have a myfile.pdf file? That would indicate that the pdflatex
> run was at least partially successful.
>
> And what did you see on the console when you ran pdflatex (assuming you
> are using a terminal-like interface and not a LaTeX editor)?
>
>
> S.
>
>
>
> --
> __
> Stefano Franchi
>
> stefano.fran...@gmail.com 
> http://stefano.cleinias.org
>

Re: Generating a Tex

Breaking News!  I just ran LaTeX(plain) on myfile.lyx and it produced
mytext.bbl.  I've never gotten a bbl file before.  This is good, isn't it?
Is there an easy way forward from here?


On Thu, Aug 28, 2014 at 12:59 PM, stefano franchi  wrote:

>
>
>
> On Thu, Aug 28, 2014 at 12:55 PM, stefano franchi <
> stefano.fran...@gmail.com> wrote:
>
>>
>>
>>
>> On Thu, Aug 28, 2014 at 12:26 PM, William Hanson  wrote:
>>
>>> I am calling pdflatex from the command line of TeXworks.
>>>
>>> It did also produce a myfile.pdf file.
>>>
>>> What I see on my screen after running pdflatex is a window labeled
>>> myfile.tex - TeXworks.  It contains what apparently is myfile.tex, which I
>>> assume is the TeX version of my paper,
>>>
>>>
>>>
>> If you use texworks, you should just be able to select pdflatex from the
>> Typeset menu, and it will compile your file to myfile.pdf and also produce
>> a myfile.log. For instance, this is what I see in TeXWorks console, when I
>> try to compile a test.tex file:
>>
>> This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded
>> format=pdflatex)
>>
>> restricted \write18 enabled.
>>
>> entering extended mode
>>
>> (./test.tex
>>
>> LaTeX2e <2014/05/01>
>>
>> Babel <3.9k> and hyphenation patterns for 79 languages loaded.
>>
>> (/usr/local/texlive/2014/texmf-dist/tex/latex/base/article.cls
>>
>> Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
>>
>> (/usr/local/texlive/2014/texmf-dist/tex/latex/base/size11.clo))
>>
>> (/usr/local/texlive/2014/texmf-dist/tex/latex/base/fontenc.sty
>>
>> (/usr/local/texlive/2014/texmf-dist/tex/latex/base/t1enc.def))
>>
>> (/usr/local/texlive/2014/texmf-dist/tex/generic/babel/babel.sty
>>
>> (/usr/local/texlive/2014/texmf-dist/tex/generic/babel-english/english.ldf
>>
>> (/usr/local/texlive/2014/texmf-dist/tex/generic/babel/babel.def)))
>>
>>
>> LaTeX Warning: Unused global option(s):
>>
>> [article].
>>
>>
>> (./test.aux)
>> [1{/usr/local/texlive/2014/texmf-var/fonts/map/pdftex/updmap/pdfte
>>
>> x.map}] (./test.aux)
>> ){/usr/local/texlive/2014/texmf-dist/fonts/enc/dvips/cm-su
>>
>>
>> per/cm-super-t1.enc}>
>> uper/sfrm1095.pfb>
>>
>> Output written on test.pdf (1 page, 13144 bytes).
>>
>> SyncTeX written on test.synctex.gz.
>>
>> Transcript written on test.log.
>>
>>
>> Notice how on the last line it informs me that it has produced a log file.
>>
>>
>> At any rate, try recompiling your file, and if you cannot find the log
>> file, juct cut and paste everything you see in TeXWorks's console output
>> window into an email message and send it to the list.
>>
>> Do the same for a compilation with bibtex (just select bibtex from the
>> Typeset menu and hit ctrl-T). Cut and paste the console output into an
>> email message and send it to the list.
>>
>>
>> That should give us enough info to understand what's going wrong.
>>
>>
>>
>
> The alternative is to use a good old-fashioned terminal---I believe it is
> called "Command prompt" in Windows, or at least it used to be. See here [1]
> on how to do it in Windows 7 (with apologies if it is obvious to you).
>
>
> [1]
> http://smallbusiness.chron.com/open-terminal-session-windows-7-56627.html
>
>
>
>
> S.
>
>
> --
> __
> Stefano Franchi
>
> stefano.fran...@gmail.com 
> http://stefano.cleinias.org
>

Re: Generating a Tex

On Thu, Aug 28, 2014 at 1:54 PM, William Hanson  wrote:

> Breaking News!  I just ran LaTeX(plain) on myfile.lyx and it produced
> mytext.bbl.  I've never gotten a bbl file before.  This is good, isn't it?
> Is there an easy way forward from here?
>

Assuming your bbl file is correct, you're almost there. You just:

1. open the myfile.bbl file in TeXWorks (be sure to select "all files"
ffrom the open dialog or it won't show up)
2. Select and copy everything in the bbl file
3, go to your myfile,.tex file in TeXWorks, delete the two lines (at the
end), that begin with, respectively, \bibliographystyle and \bibliography
and replace them with the content you just copied from the bbl file.
4. Compile the file again with pdflatex to be sure everything works
correctly and the pdf is how it should be (with all the refs, etcetera).
5. Send to Springer!

Cheers,

Stefano

-- 
__
Stefano Franchi

stefano.fran...@gmail.com 
http://stefano.cleinias.org

Re: Generating a Tex

So close, but my bbl file does not show up om TeXWorks.  I don't see any
""all files" ffrom the open dialog".


On Thu, Aug 28, 2014 at 2:12 PM, stefano franchi 
wrote:

>
>
>
> On Thu, Aug 28, 2014 at 1:54 PM, William Hanson  wrote:
>
>> Breaking News!  I just ran LaTeX(plain) on myfile.lyx and it produced
>> mytext.bbl.  I've never gotten a bbl file before.  This is good, isn't it?
>> Is there an easy way forward from here?
>>
>
>
> Assuming your bbl file is correct, you're almost there. You just:
>
> 1. open the myfile.bbl file in TeXWorks (be sure to select "all files"
> ffrom the open dialog or it won't show up)
> 2. Select and copy everything in the bbl file
> 3, go to your myfile,.tex file in TeXWorks, delete the two lines (at the
> end), that begin with, respectively, \bibliographystyle and \bibliography
> and replace them with the content you just copied from the bbl file.
> 4. Compile the file again with pdflatex to be sure everything works
> correctly and the pdf is how it should be (with all the refs, etcetera).
> 5. Send to Springer!
>
> Cheers,
>
> Stefano
>
> --
> __
> Stefano Franchi
>
> stefano.fran...@gmail.com 
> http://stefano.cleinias.org
>

Re: Generating a Tex

Foiled again, I'm afraid.  All that's in the bbl file is

\begin{thebibliography}{}

\end{thebibliography}


Cheers nonetheless.



On Thu, Aug 28, 2014 at 3:02 PM, stefano franchi 
wrote:

>
>
>
> On Thu, Aug 28, 2014 at 2:46 PM, William Hanson  wrote:
>
>> So close, but my bbl file does not show up om TeXWorks.  I don't see any
>>   ""all files" ffrom the open dialog".
>>
>>
>
> Look at the last line in the open file dialog screen (see attached
> screenshot, where it says "Filter"). It is a pop up menu, you need to click
> on it and select the last item "all files"
>
>
> S.
>
> --
> __
> Stefano Franchi
>
> stefano.fran...@gmail.com 
> http://stefano.cleinias.org
>

Re: Generating a Tex