On Sat, Dec 4, 2010 at 1:46 AM, Jürgen Spitzmüller wrote:
> stefano franchi wrote:
> > Latex 2: This is line of text with a word in small caps:
> > \noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
> > ^^^
> >
> > whereas I would expect:
> >
> >
> > Latex 3: Thi
stefano franchi wrote:
> Latex 2: This is line of text with a word in small caps:
> \noun{small-caps-word}\index{small-caps-w...@\noun{small-caps-word}}
> ^^^
>
> whereas I would expect:
>
>
> Latex 3: This is line of text with a word in small caps:
> \noun{small-caps-word}\index
Dear Lyxers,
can anyone explain to me why the \noun command (small caps) produces this
funny latex code when used within a \idex command? Consider the following:
> This is a line of text with with a word in small caps: small-caps-word
shows up in the LateX source window as :
Latex 1: This is li
1. I certainly chose view/pdflatex when the failure occurred.
2. The pdflatext command is recognized by the failing Windows
machine: I get a pdf file if I do not include pdf graphics in the
Lyx file. It is only the pdf figures that cause it to produce a
"damaged" file.
-
Ehud Kaplan wrote:
This must be simple for the experts, but it puzzles me:
I have a file with some figures. It compiles without any problem on
both a WINDOWS (with Miktex 2.7) machine and on a Kubuntu 8.10 machine,
both running Lyx 16.1. But on another WINDOWS machine (Miktex 2.7, Lyx
1.6.1)
On 2009-02-02, Ehud Kaplan wrote:
> I have a file with some figures. It compiles without any problem on
> both a WINDOWS (with Miktex 2.7) machine and on a Kubuntu 8.10 machine,
> both running Lyx 16.1. But on another WINDOWS machine (Miktex 2.7, Lyx
> 1.6.1) it fails to compile (View-->pdfla
On Mon, 2 Feb 2009, E.Kaplan wrote:
By the way, which libraries were you referring to?
Ehud,
I don't do windows so I've no idea where they'd be in the LaTeX port. The
LyX interface calls the tool or library to do the work. Those who are
familiar with Microsoft products and applications port
Thanks. I did suspect a converter, but the lists of converters under
/tools/preferences/file-handling/converters seem identical. In
addition, both Windows machines are running the same version of Lyx,
installed a couple of days apart. It is unclear why they should differ,
and why there would
On Mon, 2 Feb 2009, Ehud Kaplan wrote:
This must be simple for the experts, but it puzzles me: I have a file with
some figures. It compiles without any problem on both a WINDOWS (with
Miktex 2.7) machine and on a Kubuntu 8.10 machine, both running Lyx 16.1.
But on another WINDOWS machine (Mikt
This must be simple for the experts, but it puzzles me:
I have a file with some figures. It compiles without any problem on
both a WINDOWS (with Miktex 2.7) machine and on a Kubuntu 8.10 machine,
both running Lyx 16.1. But on another WINDOWS machine (Miktex 2.7, Lyx
1.6.1) it fails to compile
10 matches
Mail list logo