Dear Lyx users and developers,
I am writing a paper with some EPS figures which I have cropped by manually
adjusting the bounding boxes. In Lyx and in PDFs created by pdflatex,
everything looks fine. But using classic LaTeX (via dvi), the figures are
cropped incorrectly.
The values specified
2012/6/9 Matthias Hunstig:
I am writing a paper with some EPS figures which I have cropped by manually
adjusting the bounding boxes. In Lyx and in PDFs created by pdflatex,
everything looks fine. But using classic LaTeX (via dvi), the figures are
cropped incorrectly.
The values specified
Hi,
I'm sorry, but I don't want to paste it here: It's my unfinished diploma
thesis.
The crashes were with advanced search. I searched a \rho^*. One of it was
found and the others weren't. But when I saw the source code I realized
that there was once a \rho{}^* (or something similar) and the
After upgrade to Lyx 2.0.3 the following problem surfaced: if I am editing a
document with SIAM document class, every time I want to start a new paragraph
with [ENTER] a new theorem environment is created instead of Standard. I guess
this has something to do with the environment order as appears
Dima dima.batenkov at gmail.com writes:
After upgrade to Lyx 2.0.3 the following problem surfaced: if I am editing a
document with SIAM document class, every time I want to start a new paragraph
with [ENTER] a new theorem environment is created instead of Standard. I
guess
this has
Hi,
I have a strange problem with inputenc. I've got it accidentally
updating my document in some place which looks to be not related to the
problem (a listing that doesn't have offending character). I'm unable to
write more text before that place to not to get that error:
! Package inputenc
2012/6/9 Marcin Zajączkowski:
I spotted that the problem occurs only when there is a Polish national
character in a document header (e.g. \rhead{\bfseries ę}). I don't know
why this is a problem. I have set UTF8 encoding in a document. Problem
reproducible with Lyx 2.0.3 and a following
On 2012-06-10 00:27, Jürgen Spitzmüller wrote:
2012/6/9 Marcin Zajączkowski:
I spotted that the problem occurs only when there is a Polish national
character in a document header (e.g. \rhead{\bfseries ę}). I don't know
why this is a problem. I have set UTF8 encoding in a document. Problem
Dear Lyx users and developers,
I am writing a paper with some EPS figures which I have cropped by manually
adjusting the bounding boxes. In Lyx and in PDFs created by pdflatex,
everything looks fine. But using classic LaTeX (via dvi), the figures are
cropped incorrectly.
The values specified
2012/6/9 Matthias Hunstig:
I am writing a paper with some EPS figures which I have cropped by manually
adjusting the bounding boxes. In Lyx and in PDFs created by pdflatex,
everything looks fine. But using classic LaTeX (via dvi), the figures are
cropped incorrectly.
The values specified
Hi,
I'm sorry, but I don't want to paste it here: It's my unfinished diploma
thesis.
The crashes were with advanced search. I searched a \rho^*. One of it was
found and the others weren't. But when I saw the source code I realized
that there was once a \rho{}^* (or something similar) and the
After upgrade to Lyx 2.0.3 the following problem surfaced: if I am editing a
document with SIAM document class, every time I want to start a new paragraph
with [ENTER] a new theorem environment is created instead of Standard. I guess
this has something to do with the environment order as appears
Dima dima.batenkov at gmail.com writes:
After upgrade to Lyx 2.0.3 the following problem surfaced: if I am editing a
document with SIAM document class, every time I want to start a new paragraph
with [ENTER] a new theorem environment is created instead of Standard. I
guess
this has
Hi,
I have a strange problem with inputenc. I've got it accidentally
updating my document in some place which looks to be not related to the
problem (a listing that doesn't have offending character). I'm unable to
write more text before that place to not to get that error:
! Package inputenc
2012/6/9 Marcin Zajączkowski:
I spotted that the problem occurs only when there is a Polish national
character in a document header (e.g. \rhead{\bfseries ę}). I don't know
why this is a problem. I have set UTF8 encoding in a document. Problem
reproducible with Lyx 2.0.3 and a following
On 2012-06-10 00:27, Jürgen Spitzmüller wrote:
2012/6/9 Marcin Zajączkowski:
I spotted that the problem occurs only when there is a Polish national
character in a document header (e.g. \rhead{\bfseries ę}). I don't know
why this is a problem. I have set UTF8 encoding in a document. Problem
Dear Lyx users and developers,
I am writing a paper with some EPS figures which I have cropped by manually
adjusting the bounding boxes. In Lyx and in PDFs created by pdflatex,
everything looks fine. But using classic LaTeX (via dvi), the figures are
cropped incorrectly.
The values specified
2012/6/9 Matthias Hunstig:
> I am writing a paper with some EPS figures which I have cropped by manually
> adjusting the bounding boxes. In Lyx and in PDFs created by pdflatex,
> everything looks fine. But using classic LaTeX (via dvi), the figures are
> cropped incorrectly.
>
> The values
Hi,
I'm sorry, but I don't want to paste it here: It's my unfinished diploma
thesis.
The crashes were with advanced search. I searched a \rho^*. One of it was
found and the others weren't. But when I saw the source code I realized
that there was once a \rho{}^* (or something similar) and the
After upgrade to Lyx 2.0.3 the following problem surfaced: if I am editing a
document with SIAM document class, every time I want to start a new paragraph
with [ENTER] a new theorem environment is created instead of "Standard". I guess
this has something to do with the environment order as appears
Dima gmail.com> writes:
>
> After upgrade to Lyx 2.0.3 the following problem surfaced: if I am editing a
> document with SIAM document class, every time I want to start a new paragraph
> with [ENTER] a new theorem environment is created instead of "Standard". I
guess
> this has something to do
Hi,
I have a strange problem with inputenc. I've got it accidentally
updating my document in some place which looks to be not related to the
problem (a listing that doesn't have offending character). I'm unable to
write more text before that place to not to get that error:
! Package inputenc
2012/6/9 Marcin Zajączkowski:
> I spotted that the problem occurs only when there is a Polish national
> character in a document header (e.g. \rhead{\bfseries ę}). I don't know
> why this is a problem. I have set UTF8 encoding in a document. Problem
> reproducible with Lyx 2.0.3 and a following
On 2012-06-10 00:27, Jürgen Spitzmüller wrote:
> 2012/6/9 Marcin Zajączkowski:
>> I spotted that the problem occurs only when there is a Polish national
>> character in a document header (e.g. \rhead{\bfseries ę}). I don't know
>> why this is a problem. I have set UTF8 encoding in a document.
24 matches
Mail list logo
