Just further to the elsart question, the problem with the elsart layout is
that it implements a new environment, frontmatter, into which all the the
things like \title{}, \thanks{} etc. are meant to go.
What I wasn't able to work out was a way of tying these commands to the
frontmatter
in the bibtex file *.bib
...
title = {{E}ltern und {K}inder}
...
Bibtex will leave all capitalizations in {} unchanged.
Er, I may be missing something here, but if you create a .bst file using
makebst, part of the custbib package, you are given the option of using
either a
psfrag, I think
On Tue, 12 Feb 2002, Guenter Milde wrote:
On Mon, 11 Feb 2002 23:33:33 -0600 wrote Paul Johnson [EMAIL PROTECTED]:
I found the tip on importing xfig drawings
http://www.lyx.org/help/xfig/xfig.html as well as Allen Barker's essay
referred to there. That essay is
in the bibtex file *.bib
...
title = {{E}ltern und {K}inder}
...
Bibtex will leave all capitalizations in {} unchanged.
Er, I may be missing something here, but if you create a .bst file using
makebst, part of the custbib package, you are given the option of using
either a
psfrag, I think
On Tue, 12 Feb 2002, Guenter Milde wrote:
On Mon, 11 Feb 2002 23:33:33 -0600 wrote Paul Johnson [EMAIL PROTECTED]:
I found the tip on importing xfig drawings
http://www.lyx.org/help/xfig/xfig.html as well as Allen Barker's essay
referred to there. That essay is
> in the bibtex file *.bib
> ...
>title = {{E}ltern und {K}inder}
> ...
>
> Bibtex will leave all capitalizations in {} unchanged.
Er, I may be missing something here, but if you create a .bst file using
makebst, part of the custbib package, you are given the option of using
either
psfrag, I think
On Tue, 12 Feb 2002, Guenter Milde wrote:
> On Mon, 11 Feb 2002 23:33:33 -0600 wrote Paul Johnson <[EMAIL PROTECTED]>:
>
> > I found the tip on importing xfig drawings
> > http://www.lyx.org/help/xfig/xfig.html as well as Allen Barker's essay
> > referred to there. That
On Tue, 15 Jan 2002, J.S. wrote:
1. For my chapters I selected `Chapter*' so that the word Chapter
doesn't enter my report. Is it because of the `Chapter*' and not `Chapter'
that the TOC won't even appear?
Yes.
2. And what about the TOC's Contents and the Bibliography's
References? My
On Tue, 15 Jan 2002, J.S. wrote:
1. For my chapters I selected `Chapter*' so that the word Chapter
doesn't enter my report. Is it because of the `Chapter*' and not `Chapter'
that the TOC won't even appear?
Yes.
2. And what about the TOC's Contents and the Bibliography's
References? My
On Tue, 15 Jan 2002, J.S. wrote:
> 1. For my chapters I selected `Chapter*' so that the word "Chapter"
> doesn't enter my report. Is it because of the `Chapter*' and not `Chapter'
> that the TOC won't even appear?
Yes.
> 2. And what about the TOC's "Contents" and the Bibliography's
>
I find grace works pretty well for this sort of thing.
Rod
On Sat, 15 Dec 2001, Rich Shepard wrote:
On Sat, 15 Dec 2001, Kent Kostuk wrote:
Instead of me blindly trying out a bunch of packages, I thought I would
see what other LyX users are using. I want to include a series of graphs
I find grace works pretty well for this sort of thing.
Rod
On Sat, 15 Dec 2001, Rich Shepard wrote:
On Sat, 15 Dec 2001, Kent Kostuk wrote:
Instead of me blindly trying out a bunch of packages, I thought I would
see what other LyX users are using. I want to include a series of graphs
I find grace works pretty well for this sort of thing.
Rod
On Sat, 15 Dec 2001, Rich Shepard wrote:
> On Sat, 15 Dec 2001, Kent Kostuk wrote:
>
> > Instead of me blindly trying out a bunch of packages, I thought I would
> > see what other LyX users are using. I want to include a series of
To set helvetica to be the default font, I believe the instruction is
\renewcommand{\familydefault}{\sfdefault}
Put that in the preamble, and it should work.
All a template is is a Lyx file, in the directory
/usr/local/share/lyx/templates
So open one that looks about right, put the above
To set helvetica to be the default font, I believe the instruction is
\renewcommand{\familydefault}{\sfdefault}
Put that in the preamble, and it should work.
All a template is is a Lyx file, in the directory
/usr/local/share/lyx/templates
So open one that looks about right, put the above
To set helvetica to be the default font, I believe the instruction is
\renewcommand{\familydefault}{\sfdefault}
Put that in the preamble, and it should work.
All a template is is a Lyx file, in the directory
/usr/local/share/lyx/templates
So open one that looks about right, put the above
Rod,
On 11-12-01, Rod Pinna wrote:
Mr Masters,
I currently use LyX on a debian potato system, without too many problems.
Have you installed all the debian tetex packages? This includes
tetex-extra, and tetex-nonfree, as well as tetex-base. If that doesn't
help, telling people
.
Rod
On Tue, 11 Dec 2001, Rod Pinna wrote:
I just checked my installation; doing
locate helvet.sty showed the file in
/usr/share/texmf/tex/latex/psnfss
As far as I remember, this should have come from the standard debian tetex
installation. Checking the file helvet.sty, it appears
Final note,
If you are running stable, there is a package called task-tex, which
should give you a working system.
i.e. apt-get install task-tex
This doesn't exist in the unstable branch.
Rod
On Tue, 11 Dec 2001, Rod Pinna wrote:
Actually, looking at the psnfss documentation, helvet.sty
Rod,
On 11-12-01, Rod Pinna wrote:
Mr Masters,
I currently use LyX on a debian potato system, without too many problems.
Have you installed all the debian tetex packages? This includes
tetex-extra, and tetex-nonfree, as well as tetex-base. If that doesn't
help, telling people
.
Rod
On Tue, 11 Dec 2001, Rod Pinna wrote:
I just checked my installation; doing
locate helvet.sty showed the file in
/usr/share/texmf/tex/latex/psnfss
As far as I remember, this should have come from the standard debian tetex
installation. Checking the file helvet.sty, it appears
Final note,
If you are running stable, there is a package called task-tex, which
should give you a working system.
i.e. apt-get install task-tex
This doesn't exist in the unstable branch.
Rod
On Tue, 11 Dec 2001, Rod Pinna wrote:
Actually, looking at the psnfss documentation, helvet.sty
Tue, 11 Dec 2001, cmasters wrote:
> Greetings Rod,
>
> On 11-12-01, Rod Pinna wrote:
> >
> > Mr Masters,
> >
> > I currently use LyX on a debian potato system, without too many problems.
> > Have you installed all the debian tetex packages? This includes
&g
.
Rod
On Tue, 11 Dec 2001, Rod Pinna wrote:
>
> I just checked my installation; doing
>
> locate helvet.sty showed the file in
>
> /usr/share/texmf/tex/latex/psnfss
>
> As far as I remember, this should have come from the standard debian tetex
> installation. C
Final note,
If you are running stable, there is a package called task-tex, which
should give you a working system.
i.e. apt-get install task-tex
This doesn't exist in the unstable branch.
Rod
On Tue, 11 Dec 2001, Rod Pinna wrote:
>
> Actually, looking at the psnfss documen
Mr Masters,
I currently use LyX on a debian potato system, without too many problems.
Have you installed all the debian tetex packages? This includes
tetex-extra, and tetex-nonfree, as well as tetex-base. If that doesn't
help, telling people which packages are coming up as missing might give us
One thing, in twoside mode, the geometry package puts in an extra 20pt
spacing, to allow for binding. Page 9 of the documentation explains it. To
get around it, you need to specify margins that aren't equal, or else
invoke the package in the preamble, rather than through the button.
Rod
On
Mr Masters,
I currently use LyX on a debian potato system, without too many problems.
Have you installed all the debian tetex packages? This includes
tetex-extra, and tetex-nonfree, as well as tetex-base. If that doesn't
help, telling people which packages are coming up as missing might give us
One thing, in twoside mode, the geometry package puts in an extra 20pt
spacing, to allow for binding. Page 9 of the documentation explains it. To
get around it, you need to specify margins that aren't equal, or else
invoke the package in the preamble, rather than through the button.
Rod
On
Mr Masters,
I currently use LyX on a debian potato system, without too many problems.
Have you installed all the debian tetex packages? This includes
tetex-extra, and tetex-nonfree, as well as tetex-base. If that doesn't
help, telling people which packages are coming up as missing might give us
One thing, in twoside mode, the geometry package puts in an extra 20pt
spacing, to allow for binding. Page 9 of the documentation explains it. To
get around it, you need to specify margins that aren't equal, or else
invoke the package in the preamble, rather than through the button.
Rod
On
To get rid of the markers in the text, use the option [nomarkers], and to
remove the figure or table lists, use [nofiglist] and [notablist].
[nolists] gets rid of both lists.
eg.
\usepackage[nolists,nomarkers]{endfloat}
The page with the [figure X should go here] is meant to show the
To get rid of the markers in the text, use the option [nomarkers], and to
remove the figure or table lists, use [nofiglist] and [notablist].
[nolists] gets rid of both lists.
eg.
\usepackage[nolists,nomarkers]{endfloat}
The page with the [figure X should go here] is meant to show the
To get rid of the markers in the text, use the option [nomarkers], and to
remove the figure or table lists, use [nofiglist] and [notablist].
[nolists] gets rid of both lists.
eg.
\usepackage[nolists,nomarkers]{endfloat}
The page with the [figure X should go here] is meant to show the
Just a comment on VMWare. I've used it under Windows NT for awhile now,
just so I can have Linux at work. (I'm not doing it the other way around,
as there was no way I would have been allowed to have Linux as the primary
OS). I've found it offers a very good solution.
The speed has been fine.
Just a comment on VMWare. I've used it under Windows NT for awhile now,
just so I can have Linux at work. (I'm not doing it the other way around,
as there was no way I would have been allowed to have Linux as the primary
OS). I've found it offers a very good solution.
The speed has been fine.
Just a comment on VMWare. I've used it under Windows NT for awhile now,
just so I can have Linux at work. (I'm not doing it the other way around,
as there was no way I would have been allowed to have Linux as the primary
OS). I've found it offers a very good solution.
The speed has been fine.
On Fri, 23 Mar 2001, Andre Poenitz wrote:
I wonder, whether after all these years it is getting time for buying Mac
for me. The question is simple -- is the GUI based on X?
I don't know but I doubt it.
It isn't.
If yes, does it mean, that there is day coming near when M$ Office will
On Fri, 23 Mar 2001, Andre Poenitz wrote:
I wonder, whether after all these years it is getting time for buying Mac
for me. The question is simple -- is the GUI based on X?
I don't know but I doubt it.
It isn't.
If yes, does it mean, that there is day coming near when M$ Office will
On Fri, 23 Mar 2001, Andre Poenitz wrote:
> > I wonder, whether after all these years it is getting time for buying Mac
> > for me. The question is simple -- is the GUI based on X?
>
> I don't know but I doubt it.
It isn't.
> > If yes, does it mean, that there is day coming near when M$
On 19 Jan 2001, Lars Gullik Bjønnes wrote:
Rod Pinna [EMAIL PROTECTED] writes:
| Hello all,
|
| Mea Culpa. Well, sort of. The format of {\a{a}} doesn't work. Oddly, it
| works for {\"{u}} though.
\aa is not an accent it is a character in its own right.
The accented varian
On 19 Jan 2001, Lars Gullik Bjønnes wrote:
Rod Pinna [EMAIL PROTECTED] writes:
| Hello all,
|
| Mea Culpa. Well, sort of. The format of {\a{a}} doesn't work. Oddly, it
| works for {\"{u}} though.
\aa is not an accent it is a character in its own right.
The accented varian
On 19 Jan 2001, Lars Gullik Bjønnes wrote:
> Rod Pinna <[EMAIL PROTECTED]> writes:
>
> | Hello all,
> |
> | Mea Culpa. Well, sort of. The format of {\a{a}} doesn't work. Oddly, it
> | works for {\"{u}} though.
>
> \aa is not an accent it is a character
Hi all,
A latex problem I suspect, but I'm not sure what I'm doing wrong. I want
to use {\a{a}} in an author name in bibtex, however, when I view the
postscript file, I get an error about the character not being available in
the T1 encoding.
It appears that lyx uses the T1 encoding as a
the
same result.
Thanks alot,
Rod
On 18 Jan 2001, Jean-Marc Lasgouttes wrote:
"Rod" == Rod Pinna [EMAIL PROTECTED] writes:
Rod Hi all, A latex problem I suspect, but I'm not sure what I'm
Rod doing wrong. I want to use {\a{a}} in an author name in bibtex,
Rod however, w
Hello all,
Mea Culpa. Well, sort of. The format of {\a{a}} doesn't work. Oddly, it
works for {\"{u}} though. Not sure where I picked it up. Changing it to
{\aa} provided the solution, which now quite happily uses T1 encoding.
Sorry 'bout that,
Rod
On Fri, 19 Jan 2001, Rod Pinna
Hi all,
A latex problem I suspect, but I'm not sure what I'm doing wrong. I want
to use {\a{a}} in an author name in bibtex, however, when I view the
postscript file, I get an error about the character not being available in
the T1 encoding.
It appears that lyx uses the T1 encoding as a
the
same result.
Thanks alot,
Rod
On 18 Jan 2001, Jean-Marc Lasgouttes wrote:
"Rod" == Rod Pinna [EMAIL PROTECTED] writes:
Rod Hi all, A latex problem I suspect, but I'm not sure what I'm
Rod doing wrong. I want to use {\a{a}} in an author name in bibtex,
Rod however, w
Hello all,
Mea Culpa. Well, sort of. The format of {\a{a}} doesn't work. Oddly, it
works for {\"{u}} though. Not sure where I picked it up. Changing it to
{\aa} provided the solution, which now quite happily uses T1 encoding.
Sorry 'bout that,
Rod
On Fri, 19 Jan 2001, Rod Pinna
Hi all,
A latex problem I suspect, but I'm not sure what I'm doing wrong. I want
to use {\a{a}} in an author name in bibtex, however, when I view the
postscript file, I get an error about the character not being available in
the T1 encoding.
It appears that lyx uses the T1 encoding as a
the
same result.
Thanks alot,
Rod
On 18 Jan 2001, Jean-Marc Lasgouttes wrote:
> >>>>> "Rod" == Rod Pinna <[EMAIL PROTECTED]> writes:
>
> Rod> Hi all, A latex problem I suspect, but I'm not sure what I'm
> Rod> doing wrong. I want to use {\a{a}}
Hello all,
Mea Culpa. Well, sort of. The format of {\a{a}} doesn't work. Oddly, it
works for {\"{u}} though. Not sure where I picked it up. Changing it to
{\aa} provided the solution, which now quite happily uses T1 encoding.
Sorry 'bout that,
Rod
On Fri, 19 Jan 2001, Rod Pinna
gs is ghostscript, the postscript processor. For some reason, it
occasionally keeps running, after it should be killed. When that happens,
the easiest way to deal with it is to simply kill it. Run top to get the
process id, and either kill it in top, or exit top and use
kill -9 pid
where pid
gs is ghostscript, the postscript processor. For some reason, it
occasionally keeps running, after it should be killed. When that happens,
the easiest way to deal with it is to simply kill it. Run top to get the
process id, and either kill it in top, or exit top and use
kill -9 pid
where pid
gs is ghostscript, the postscript processor. For some reason, it
occasionally keeps running, after it should be killed. When that happens,
the easiest way to deal with it is to simply kill it. Run top to get the
process id, and either kill it in top, or exit top and use
kill -9 pid
where pid
Hello all,
Just had a quick look at the new release. A small bug seems to have crept
in. I can't access the "look feel" and "language opts" menus. Instead,
clicking on those brings up the "screen fonts" and "language" menus
respectively.
I'm using xforms 0.89, which comes with debian potato.
I suspect in this case though it is
simply the case that convention was a little unexpected.
Rod
On Wed, 29 Nov 2000, Allan Rae wrote:
On Wed, 29 Nov 2000, Rod Pinna wrote:
Hello all,
Just had a quick look at the new release. A small bug seems to have crept
in. I can't access the &
Hello all,
Just had a quick look at the new release. A small bug seems to have crept
in. I can't access the "look feel" and "language opts" menus. Instead,
clicking on those brings up the "screen fonts" and "language" menus
respectively.
I'm using xforms 0.89, which comes with debian potato.
I suspect in this case though it is
simply the case that convention was a little unexpected.
Rod
On Wed, 29 Nov 2000, Allan Rae wrote:
On Wed, 29 Nov 2000, Rod Pinna wrote:
Hello all,
Just had a quick look at the new release. A small bug seems to have crept
in. I can't access the &
Hello all,
Just had a quick look at the new release. A small bug seems to have crept
in. I can't access the "look & feel" and "language opts" menus. Instead,
clicking on those brings up the "screen fonts" and "language" menus
respectively.
I'm using xforms 0.89, which comes with debian potato.
I suspect in this case though it is
simply the case that convention was a little unexpected.
Rod
On Wed, 29 Nov 2000, Allan Rae wrote:
> On Wed, 29 Nov 2000, Rod Pinna wrote:
>
> > Hello all,
> >
> > Just had a quick look at the new release. A small bug seems to have crep
Hello all,
Herbert Voss posted the following to the list a while ago. I've had a look
at the page, but I can't find any links there to debian packages. Anybody
know of a current version?
Thanks,
Rod
On Wed, 20 Sep 2000, Herbert Voss wrote:
thomas schönhoff wrote:
Hello,
I wonder
Hello all,
Herbert Voss posted the following to the list a while ago. I've had a look
at the page, but I can't find any links there to debian packages. Anybody
know of a current version?
Thanks,
Rod
On Wed, 20 Sep 2000, Herbert Voss wrote:
thomas schönhoff wrote:
Hello,
I wonder
Hello all,
Herbert Voss posted the following to the list a while ago. I've had a look
at the page, but I can't find any links there to debian packages. Anybody
know of a current version?
Thanks,
Rod
On Wed, 20 Sep 2000, Herbert Voss wrote:
> thomas schönhoff wrote:
> >
> > Hello,
> >
> > I
For going from jpeg to ps, the best option is a program called jepg2ps.
The embeds the bitmap into a postscript file, along with a small
converter, written in postscript. Usually only adds a few k to the file
size.
Rod
On Wed, 5 Jul 2000, Rachel Greenham wrote:
Fred C wrote:
Didn't find
For going from jpeg to ps, the best option is a program called jepg2ps.
The embeds the bitmap into a postscript file, along with a small
converter, written in postscript. Usually only adds a few k to the file
size.
Rod
On Wed, 5 Jul 2000, Rachel Greenham wrote:
Fred C wrote:
Didn't find
For going from jpeg to ps, the best option is a program called jepg2ps.
The embeds the bitmap into a postscript file, along with a small
converter, written in postscript. Usually only adds a few k to the file
size.
Rod
On Wed, 5 Jul 2000, Rachel Greenham wrote:
> Fred C wrote:
> >
> > Didn't
There is a package called rcsinfo.sty that might help.
Rod
On Mon, 26 Jun 2000, Darryl wrote:
I'm using RCS / CVS with Lyx
and I'm inserting a RCS keyword
$Id$ into a section.
However when i print the document the
expanded Id does not print.
Is there a way to get it to print.
There is a package called rcsinfo.sty that might help.
Rod
On Mon, 26 Jun 2000, Darryl wrote:
> I'm using RCS / CVS with Lyx
> and I'm inserting a RCS keyword
> $Id$ into a section.
>
> However when i print the document the
> expanded Id does not print.
>
> Is there a way to get it to
Olof,
However, I would still like to now if I am the only who has problems
with BibTeX citations in the figure captions in 1.1.5pre3.
It appears to work for me, using 1.1.4fix3.
Regards.
Rod
__
rod | "If morale is low
Olof,
However, I would still like to now if I am the only who has problems
with BibTeX citations in the figure captions in 1.1.5pre3.
It appears to work for me, using 1.1.4fix3.
Regards.
Rod
__
rod | "If morale is low
Olof,
> However, I would still like to now if I am the only who has problems
> with BibTeX citations in the figure captions in 1.1.5pre3.
It appears to work for me, using 1.1.4fix3.
Regards.
Rod
__
rod | "If morale is low
Hello all,
Just while everybody is putting wish list items up...would it be possible
to not have to incude the .eps or .ps extension for included graphics
files? The \includegraphics command is smart enough to be able to pick the
right sort of file, depending on whether latex or pdflatex is
Hello all,
Just while everybody is putting wish list items up...would it be possible
to not have to incude the .eps or .ps extension for included graphics
files? The \includegraphics command is smart enough to be able to pick the
right sort of file, depending on whether latex or pdflatex is
Hello all,
Just while everybody is putting wish list items up...would it be possible
to not have to incude the .eps or .ps extension for included graphics
files? The \includegraphics command is smart enough to be able to pick the
right sort of file, depending on whether latex or pdflatex is
A good place to look for tex packages is
http://www.act.cmis.csiro.au/gjw/tex/catalogue.html
Rod
On Tue, 15 Feb 2000, Andre Poenitz wrote:
I need to number each line of a manuscript (journal requirement). I've been
looking around at the users, customization, and extended manuals, and in
A good place to look for tex packages is
http://www.act.cmis.csiro.au/gjw/tex/catalogue.html
Rod
On Tue, 15 Feb 2000, Andre Poenitz wrote:
I need to number each line of a manuscript (journal requirement). I've been
looking around at the users, customization, and extended manuals, and in
A good place to look for tex packages is
http://www.act.cmis.csiro.au/gjw/tex/catalogue.html
Rod
On Tue, 15 Feb 2000, Andre Poenitz wrote:
> > I need to number each line of a manuscript (journal requirement). I've been
> > looking around at the users, customization, and extended manuals, and
You'll need the package rcsinfo, available from your nearest CTAN outlet.
Then, in your preamble, add a line similar to
\usepackage{}[rcsinfo]
It's explained in the instructions that come with it.
Rod
On Thu, 27 Jan 2000, luc taesch wrote:
how can i include the RCS release number in a lyx
You'll need the package rcsinfo, available from your nearest CTAN outlet.
Then, in your preamble, add a line similar to
\usepackage{}[rcsinfo]
It's explained in the instructions that come with it.
Rod
On Thu, 27 Jan 2000, luc taesch wrote:
how can i include the RCS release number in a lyx
You'll need the package rcsinfo, available from your nearest CTAN outlet.
Then, in your preamble, add a line similar to
\usepackage{}[rcsinfo]
It's explained in the instructions that come with it.
Rod
On Thu, 27 Jan 2000, luc taesch wrote:
> how can i include the RCS release number in a lyx
On Wed, 3 Nov 1999, Christian wrote:
Hi all,
Sorry to do this but no one responded to this question when I posted it
earlier this week and I'm fast running out of time. If anyone has *any*
suggestions on how to do any of these things then please let me know.
:) Sorry again for the
On Wed, 3 Nov 1999, Christian wrote:
Hi all,
Sorry to do this but no one responded to this question when I posted it
earlier this week and I'm fast running out of time. If anyone has *any*
suggestions on how to do any of these things then please let me know.
:) Sorry again for the
On Wed, 3 Nov 1999, Christian wrote:
> Hi all,
>
> Sorry to do this but no one responded to this question when I posted it
> earlier this week and I'm fast running out of time. If anyone has *any*
> suggestions on how to do any of these things then please let me know.
> :) Sorry again for the
On 14 Oct 1999, Jean-Marc Lasgouttes wrote:
Jean-Marc,
Thanks for having a look at the problem. In the end, it turned out the it
was a "stupid user" error. The problem was that the line:
Rod Also, I've got the following in the body of the text
Rod r_\textrm{wave}
should have been
On 14 Oct 1999, Jean-Marc Lasgouttes wrote:
Jean-Marc,
Thanks for having a look at the problem. In the end, it turned out the it
was a "stupid user" error. The problem was that the line:
Rod Also, I've got the following in the body of the text
Rod r_\textrm{wave}
should have been
On 14 Oct 1999, Jean-Marc Lasgouttes wrote:
Jean-Marc,
Thanks for having a look at the problem. In the end, it turned out the it
was a "stupid user" error. The problem was that the line:
> Rod> Also, I've got the following in the body of the text
> Rod> r_\textrm{wave}
should have been
Hello,
On Wed, 6 Oct 1999, Rod Pinna wrote:
Something he can't reproduce again...
Essentially, I was getting a behaviour where Lyx (1.0.4) was inserting
extra spaces between non-roman characters and their sub- and superscripts.
Anyway, the problem turned out to be that in a preceeding
Hello,
On Wed, 6 Oct 1999, Rod Pinna wrote:
Something he can't reproduce again...
Essentially, I was getting a behaviour where Lyx (1.0.4) was inserting
extra spaces between non-roman characters and their sub- and superscripts.
Anyway, the problem turned out to be that in a preceeding
Hello,
On Wed, 6 Oct 1999, Rod Pinna wrote:
Something he can't reproduce again...
Essentially, I was getting a behaviour where Lyx (1.0.4) was inserting
extra spaces between non-roman characters and their sub- and superscripts.
Anyway, the problem turned out to be that in a preceeding
find this sort of thing v. useful.
Regards,
Rod Pinna
__
rod | "If morale is low it's because the employees have character defects.
| There is nothing you can do about that."
|from
find this sort of thing v. useful.
Regards,
Rod Pinna
__
rod | "If morale is low it's because the employees have character defects.
| There is nothing you can do about that."
|from
ll all the rage.
I, for one, would also find this sort of thing v. useful.
Regards,
Rod Pinna
__
rod | "If morale is low it's because the employees have character defects.
| There is nothing you can do about that.&
On Thu, 1 Jul 1999, Sasa Janiska wrote:
Sasa,
You can specifiy the option in Layout-Document ExtraOptions. Simply put
twoside in the box. Whatever goes into that gets passed on as an option to
the document class.
It seems to be a problem with the version of tetex that is common with
Linux
Ingo,
Thanks for the reply. That is a resource I wasn't aware of :)
Rod.
On Sat, 3 Jul 1999, Ingo Kloecker wrote:
Rod Pinna wrote:
Take a look at the following archived threads from this mailing-list (btw the
archive is searchable ;-)
http://www.mail-archive.com/lyx-users
On Thu, 1 Jul 1999, Sasa Janiska wrote:
Sasa,
You can specifiy the option in Layout-Document ExtraOptions. Simply put
twoside in the box. Whatever goes into that gets passed on as an option to
the document class.
It seems to be a problem with the version of tetex that is common with
Linux
Ingo,
Thanks for the reply. That is a resource I wasn't aware of :)
Rod.
On Sat, 3 Jul 1999, Ingo Kloecker wrote:
Rod Pinna wrote:
Take a look at the following archived threads from this mailing-list (btw the
archive is searchable ;-)
http://www.mail-archive.com/lyx-users
On Thu, 1 Jul 1999, Sasa Janiska wrote:
Sasa,
You can specifiy the option in Layout->Document ExtraOptions. Simply put
twoside in the box. Whatever goes into that gets passed on as an option to
the document class.
It seems to be a problem with the version of tetex that is common with
Linux
Ingo,
Thanks for the reply. That is a resource I wasn't aware of :)
Rod.
On Sat, 3 Jul 1999, Ingo Kloecker wrote:
> Rod Pinna wrote:
>
> Take a look at the following archived threads from this mailing-list (btw the
> archive is searchable ;-)
>
> http://www.mail-arc
and the using
both update or view dvi again shows the changes.
Changes have include adding and deleting text, and adding and deleting a
bibtex reference. The latter was done using \citep{blah}, with natbib.
Also, I'm viewing the document using Xdvi.
Regards,
Rod Pinna
201 - 300 of 302 matches
Mail list logo
