Howdy,
Lyx-1.1.4 seems to be incapable of producing an article with the
two-side option. If I select 'one side', it just produces
\documentclass{article}
but if I select 'two side' I get
\documentclass[oneside]{article}
Has anyone else seen this behavior?
--
Matthew Lovell
HP Technica
I think you have to edit your *.bst files and change the and for the
french equivalnet
[]s
rlopes.
--
R.E. de Lima-Lopes
[EMAIL PROTECTED]
Yann Collete wrote:
>
> Hello
>
> I would like to know how to translate in french the "AND" word used
> in a bibtex bibliography. Here's an example:
> [1] Author1 AND Author2, TITLE, REFERENCES
i think you must use the french version of your bst file, in fact for
most of them there is a frenc
Hello
I would like to know how to translate in french the "AND" word used
in a bibtex bibliography. Here's an example:
[1] Author1 AND Author2, TITLE, REFERENCES
I set the document language to Francais in the Layout->Document menu.
YC
Yann COLLETTE ([EMAIL PROTECTED])
> Hi there,
> I've successfully used latex2html, by using the html.sty in LyX
> that comes with latex2html. This provides 'htmladdnormallink'
> latex command, which work well with both ps and tex->html
> output. Also, the latex2html output can be configured in various
> ways.
After some additio
Hi there,
I've successfully used latex2html, by using the html.sty in LyX
that comes with latex2html. This provides 'htmladdnormallink'
latex command, which work well with both ps and tex->html
output. Also, the latex2html output can be configured in various
ways.
I have not tried tth yet.
Che
/software/lyx-1/bin/lyx
Failed to share colors. Using private colormap
LyXTextClassList::Read: unable to find textclass file
`~/'. Exiting.
LyXSetStyle: an error occured during parsing.
here is the configure options when compiling:
./configure --prefix /software/lyx-1 \
--datadir=/software
Florian-Daniel Otel wrote:
>
> Hello everybody,
>
> I have the following problem: I'm using Lyx 1.1.2 and latex2html to
> export to html. My problems:
I thought lyx was made to use tth for exporting latex to html? is that
true?
> 1) When writing the TeX output LyX redefines the \url command t
Hello everybody,
I have the following problem: I'm using Lyx 1.1.2 and latex2html to
export to html. My problems:
1) When writing the TeX output LyX redefines the \url command to make
the URL printed verbatim:
..
\IfFileExists{url.sty}{\usepackage{url}}
{\newcommand{\url
I have a solution.
USE lyx-1.1.2. with that release everything works just nice!!!
If your want to use lyx-1.1.4 - try to include the entire path to the
bibfile.
I encounter exactly the same problem as you have.
Best,
Staffan
Andreas Jaeger wrote:
> I just tried 1.1.4 (upgrading from 1.0.1
I just tried 1.1.4 (upgrading from 1.0.1) and found the following
entry for 1.0.2 in NEWS:
- LyX is now able to parse your BibTex files and show a list of
entries.
Is this supposed to work in 1.1.4?
I couldn't get it to work. I started a new document, inserted "BiBTeX
Reference" and then
Andre Poenitz wrote:
>
> > Is there any reason to even put them in /tmp to begin with? They belong
> > to the user, they should go somewhere under the user's home directory.
> > Putting them in /tmp is just asking for a security problem.
>
> No, /tmp is the place to put temporary files. Believe
> Is there any reason to even put them in /tmp to begin with? They belong
> to the user, they should go somewhere under the user's home directory.
> Putting them in /tmp is just asking for a security problem.
No, /tmp is the place to put temporary files. Believe it or not, there
are people with
On 04-Feb-2000 Andre Poenitz wrote:
>> should be masked with '077' but it's probably not worth to start a huge
>> discussion about this here. I understand what's going on and I have
>> configured an appropriate solution for my systems.
>
> Well, is there any reason not to restrict tempfile acces
Andre Poenitz wrote:
>
> > should be masked with '077' but it's probably not worth to start a huge
> > discussion about this here. I understand what's going on and I have
> > configured an appropriate solution for my systems.
>
> Well, is there any reason not to restrict tempfile access to the u
> should be masked with '077' but it's probably not worth to start a huge
> discussion about this here. I understand what's going on and I have
> configured an appropriate solution for my systems.
Well, is there any reason not to restrict tempfile access to the user?
We should be as restrictive a
16 matches
Mail list logo
