Le 05/06/2024 à 17:09, Dr Paul Verschueren a écrit :
> Thanks to all for making 2.4 a reality.
>
> I’ve just installed on Win11 and have a strange issue: when a document
> is scrolled or moved up or down, a ghost image is left behind (see
> screenshot below).
>
> This
Le 05/06/2024 à 17:09, Dr Paul Verschueren a écrit :
Thanks to all for making 2.4 a reality.
I’ve just installed on Win11 and have a strange issue: when a document
is scrolled or moved up or down, a ghost image is left behind (see
screenshot below).
This disappears on single clicking
John,
Have a look at https://writer2latex.sourceforge.net/index.html
I have used Writer2LaTeX a few years ago and found it very
helpful when using what was then called the "Ultraclean"
Option, which I don't see on this much more current version
on cursory look.
Install both writer2latex.oxt and
I don't think so. What I am looking into is this: Pacer will only accept pdf
files. If those who
export to pdf from within a word document don't have to "flatten" the document
before
uploading to Pacer, while those who use lyx are forced to flatten any document
imported from a
Word doc
Hi el,
If I get a Word doc, it opens in libreoffice, which allows for export to pdf.
If I recall, I generally
either highlight the words involved while in libreoffice and paste directly to
lyx or instead export
to pdf, highlight the relevant portions of the pdf and paste to lyx.
It took me
Ever looked at Pandoc?
el
On 28/12/2023 21:57, Rich Shepard wrote:
[...]
> When I have a .doc/.docx file sent that I want to
> incorporate into a LyX document I'll do either of two
> things:
>
> 1. Highlight the desired text in the Word document then use
> Edit -> Paste Special -> Join Lines
John,
did you ever try to export using PDF5 (LuaLaTeX)?
Recent PSTricks should load
https://github.com/zauguin/luapstricks when using LuaLaTeX. If
that works for the "normal" way try and upload into Pacer and
see what happens. If Pacer accepts that see what happens when
you import a Word
On Thu, 28 Dec 2023, John White wrote:
To file in Pacer, the document must be "flattened." This poses no problem
with files created in lyx. However, whenever I import a Word file and
convert it to lyx, Pacer balks and refuses to accept the document unless I
"flatten" it. If I am at the office,
I use lyx 2.3.6 on my debian (bullseye) system I often file in Pacer, the
database used by the US
federal court system. Normally, I just do regular lyx stuff and once the file
is ready, export with
pst2pdf (to insure that line numbers exist at the left side of each page) and
upload to
Am 10.09.23 um 06:53 schrieb Daniel:
On 2023-09-09 23:02, Richard Kimberly Heck wrote:
On 9/9/23 14:41, Daniel wrote:
Hi!
I noticed that setting "English (UK)" as language under Document
Settings, leads to some strange hyphenation. For example,
"import-ant"
On 2023-09-09 23:02, Richard Kimberly Heck wrote:
On 9/9/23 14:41, Daniel wrote:
Hi!
I noticed that setting "English (UK)" as language under Document
Settings, leads to some strange hyphenation. For example, "import-ant"
and "theor-ethical". Is that a c
On 9/9/23 14:41, Daniel wrote:
Hi!
I noticed that setting "English (UK)" as language under Document
Settings, leads to some strange hyphenation. For example, "import-ant"
and "theor-ethical". Is that a common issue with that language
dictionary or do I hav
Hi!
I noticed that setting "English (UK)" as language under Document
Settings, leads to some strange hyphenation. For example, "import-ant"
and "theor-ethical". Is that a common issue with that language
dictionary or do I have a faulty setup?
Best,
Daniel
On Sat, 28 Aug 2021, Stephan Witt wrote:
Ok, I mentioned it because you said you’ve killed LyX. If you’ve quit LyX
regularly then the temporary files are removed and you cannot find them anymore.
The running process has this open and therefore you can see it. It’s on disk
present until you kill
Am 28.08.2021 um 14:36 schrieb Rich Shepard :
>
> On Sat, 28 Aug 2021, Stephan Witt wrote:
>
>> on quit LyX removes it’s temporary files and directories. This doesn’t
>> happen on sudden death of LyX. The question now is: is /tmp the location
>> for temporary files and directories?
>>
>> On
On Sat, 28 Aug 2021, Stephan Witt wrote:
on quit LyX removes it’s temporary files and directories. This doesn’t
happen on sudden death of LyX. The question now is: is /tmp the location
for temporary files and directories?
On MacOS it’s not /tmp if you don’t set the path explicitly to /tmp.
Am 27.08.2021 um 22:51 schrieb Rich Shepard :
>
> On Fri, 27 Aug 2021, Paul A. Rubin wrote:
>
>> Do you by any chance have instant preview turned on in Tools > Preferences >
>> Look & Feel > Display.
>
> Paul,
>
> Huh! It was turned on, but I've no recollection of ever doing this. And, as
> I
On 8/27/21 4:51 PM, Rich Shepard wrote:
On Fri, 27 Aug 2021, Paul A. Rubin wrote:
Do you by any chance have instant preview turned on in Tools >
Preferences > Look & Feel > Display.
Paul,
Huh! It was turned on, but I've no recollection of ever doing this.
And, as
I wrote, it's never
On Fri, 27 Aug 2021, Paul A. Rubin wrote:
Do you by any chance have instant preview turned on in Tools > Preferences >
Look & Feel > Display.
Paul,
Huh! It was turned on, but I've no recollection of ever doing this. And, as
I wrote, it's never before been an issue. So I turned it off.
The
On 8/26/21 3:27 PM, Rich Shepard wrote:
Here's another new experience for me. When I kill the lyx process there
remains a file, for example lyxpreviewN17596.tex, which shows up in the
process list as 'latex lyxpreviewN17596.tex' and consumes 100% of the
CPUs
most of the time.
Root cannot find
Here's another new experience for me. When I kill the lyx process there
remains a file, for example lyxpreviewN17596.tex, which shows up in the
process list as 'latex lyxpreviewN17596.tex' and consumes 100% of the CPUs
most of the time.
Root cannot find this file anywhere, and it persists after
On 2019-01-23 18:20 +0100, Daniel wrote:
> On 2019-01-23 18:10, Daniel CLEMENT wrote:
> >Hello,
> >
> >I'm still new to LyX 2.3 (from 2.1) so I'm not ashamed of asking a trivial
> >question:
> >
> >As I open my old documents, in various places I'm can see this
> >(non-printing) symbol which I had
On 2019-01-23 18:10, Daniel CLEMENT wrote:
Hello,
I'm still new to LyX 2.3 (from 2.1) so I'm not ashamed of asking a
trivial question:
As I open my old documents, in various places I'm can see this
(non-printing) symbol which I had never met before:
What does it mean? I can't see any
Hello,
I'm still new to LyX 2.3 (from 2.1) so I'm not ashamed of asking a
trivial question:
As I open my old documents, in various places I'm can see this (non-
printing) symbol which I had never met before:
What does it mean? I can't see any difference in preview if I erase it.
TIA - Daniel
Hello again,
Closing all open buffers and reopening a new document has corrected this
issue, but if I can help you to find the source of this bug, I would be
happy to do it.
I use LyX under OSX 10.13.6
Le sam. 27 oct. 2018 à 17:14, Murat Yildizoglu <
murat.yildizo...@u-bordeaux.fr> a écrit :
>
very well.
Thank you very much!
2017-10-02 11:32 GMT+02:00 Murat Yildizoglu <myi...@gmail.com>:
> Dear list members,
>
> I have been using LyX for many years but I currently meet a strange
> problem: I am writing my first article in Turkish and I use turkish as a
> babel mode
Dear list members,
I have been using LyX for many years but I currently meet a strange
problem: I am writing my first article in Turkish and I use turkish as a
babel mode (with english) and I cannot scale or resize any included PDF
figure (I typeset with pdflatex). In the attached example file
On 03/09/17 21:20, Paul A. Rubin wrote:
On 09/03/2017 04:10 PM, Steve Hnizdur wrote:
Hi
Thanks for replying. Ctrl-R does pdflatex. Attached is the tex file
produced by exporting from lyx, and I get the same error by running
pdflatex directly on it. I'm running Ubuntu 16.04 with everything
On 2017-09-03, Steve Hnizdur wrote:
> Attached is a lyx file which when complied with ctrl-R gives the error
> below copied from the error log. It also fails if I try to compile it as
> a native .tex file.
I tried the example you posted later and it runs without problems here
(Debian/stable
On 09/03/2017 04:10 PM, Steve Hnizdur wrote:
Hi
Thanks for replying. Ctrl-R does pdflatex. Attached is the tex file
produced by exporting from lyx, and I get the same error by running
pdflatex directly on it. I'm running Ubuntu 16.04 with everything upto
date.
By the way the error still
Hi
Thanks for replying. Ctrl-R does pdflatex. Attached is the tex file
produced by exporting from lyx, and I get the same error by running
pdflatex directly on it. I'm running Ubuntu 16.04 with everything upto date.
By the way the error still happens if the superscripts are removed, it
On 09/03/2017 01:06 PM, Steve Hnizdur wrote:
Hi
Attached is a lyx file which when complied with ctrl-R gives the error
below copied from the error log. It also fails if I try to compile it
as a native .tex file.
The error goes away if the \dots is removed and it also goes away if
the
Hi
Attached is a lyx file which when complied with ctrl-R gives the error
below copied from the error log. It also fails if I try to compile it as
a native .tex file.
The error goes away if the \dots is removed and it also goes away if the
"Number Equations by Section" Module is removed.
To me these look like bounce messages which should go to the list-admin
if that was possible tho they can be removed from the list :-)-O
I am not getting these though :-)-O
I don't have Finnish (can someone who does contact the correct new
address of the two offered perhaps?), but the second one
I am using the lyx-users@lists.lyx.org and each time I am sending a
mail to the list, I am getting the message shown below. I was told, that
this happens to other members of the list too and it would be nice if
the cause of the bouncing could be identified and removed. Thanks for
your
Perhaps you could also send an Email to the address below asking them to
stop it. I will try tomorrow to phone them up. Wolfgang
On 24.01.2017 20:44, gordon cooper wrote:
You are not alone Wolfgang, I have been getting them too.
Gordon.
eildert.groenev...@fli.bund.de
You are not alone Wolfgang, I have been getting them too.
Gordon.
Am Dienstag, den 24.01.2017, 18:18 +0100 schrieb Wolfgang Engelmann:
> When I am sending a mail to the Lyx User group lyx-us...@lists.lyx.or
> g I am getting
> always this message:
> Olen lomalla. Sähköpostia voi lähettää jollekin muulle
> henkilökunnastamme etunimi.sukun...@vskonetarvike.com tai
When I am sending a mail to the Lyx User group lyx-users@lists.lyx.org I
am getting
always this message:
Olen lomalla. Sähköpostia voi lähettää jollekin muulle
henkilökunnastammeetunimi.sukun...@vskonetarvike.com tai
vaihtoehtoisestimyy...@vskonetarvike.com
Although I definetely do not
Rich,
LyX has a versioning system (by default).
It uses RCS, which used to be part of the XCode command line tools on
the Mac (and can still be installed via homebrew) and an Ubuntu
package by itself. There should be some Windoze package too,
somewhere.
There is also SVN support for document
I got Time Machine running and am VERY diligent with Unison :-)-O, but
of course once can always run ... rm -v ...
But,
find ~/ -name '*.lyx' -exec grep -h \\lyxformat {} \; | sort| uniq
shows that I have LyX files from 26 different versions lying around
:-)-O
el
On 2016-08-02 16:31, Steve
Thank you all for clarifications and suggestions! I suspected the files
were connected to the new 2.2 version, It's better to ask before deleting
files and discover doing something stupid too late.
2016-08-02 17:52 GMT+02:00 David L. Johnson :
> On 08/02/2016 10:40 AM,
Am Dienstag, 2. August 2016 um 11:52:31, schrieb David L. Johnson
> On 08/02/2016 10:40 AM, Rich Shepard wrote:
> > On Tue, 2 Aug 2016, David L. Johnson wrote:
> >
> >> These are being created since the files were edited by the new
> >> version of
> >> LyX you
On 08/02/2016 10:40 AM, Rich Shepard wrote:
On Tue, 2 Aug 2016, David L. Johnson wrote:
These are being created since the files were edited by the new
version of
LyX you installed, which uses a newer format. LyX then auto-saves
them in
the old format so that you can edit it, if you need to,
On Tue, 2 Aug 2016, Jürgen Spitzmüller wrote:
Note that if you specify a backup directory in Tools > Preferences >
Paths, these files will end up there instead of the working directory,
which might disturb you less.
Jürgen,
I'm not disturbed, just assumed they were backup files and deleted
Am Dienstag, den 02.08.2016, 06:47 -0700 schrieb Rich Shepard:
> On Tue, 2 Aug 2016, Påvel Nicklasson wrote:
>
> > I work on several projects in LyX. Lately I have noticed that in
> the same
> > folders as my .lyx files there is a second file called -lyxformat-
> 474.lyx.
> > For instance, if the
On Tue, 2 Aug 2016 15:26:42 +0100
Dr Eberhard Lisse wrote:
> find ~/ -name '*-lyxformat-*.lyx' -exec rm {] \;
Danger Will Robinson!
I personally would never run a one-liner that does deletions. My pencil
has an eraser because I make mistakes. A mistake with such a one liner
On Tue, 2 Aug 2016, Richard Heck wrote:
It's a new feature with 2.2. When you load files with a new major release,
it has to be converted to the new format (which encodes various new
features). We had some cases where people tried to load files with 2.1 and
the file was for some reason
On 08/02/2016 10:40 AM, Rich Shepard wrote:
> On Tue, 2 Aug 2016, David L. Johnson wrote:
>
>> These are being created since the files were edited by the new
>> version of
>> LyX you installed, which uses a newer format. LyX then auto-saves
>> them in
>> the old format so that you can edit it, if
On Tue, 2 Aug 2016, David L. Johnson wrote:
These are being created since the files were edited by the new version of
LyX you installed, which uses a newer format. LyX then auto-saves them in
the old format so that you can edit it, if you need to, with an older
version of LyX. This seems to be
find ~/ -name '*-lyxformat-*.lyx' -exec rm {] \;
el
On 2016-08-02 14:58, David L. Johnson wrote:
> On 08/02/2016 09:47 AM, Rich Shepard wrote:
>> On Tue, 2 Aug 2016, Påvel Nicklasson wrote:
>>
>>> I work on several projects in LyX. Lately I have noticed that in the
>>> same
>>> folders as my
On 08/02/2016 09:47 AM, Rich Shepard wrote:
On Tue, 2 Aug 2016, Påvel Nicklasson wrote:
I work on several projects in LyX. Lately I have noticed that in the
same
folders as my .lyx files there is a second file called
-lyxformat-474.lyx.
For instance, if the regular file is called xxx.lyx. The
On Tue, 2 Aug 2016, Påvel Nicklasson wrote:
I work on several projects in LyX. Lately I have noticed that in the same
folders as my .lyx files there is a second file called -lyxformat-474.lyx.
For instance, if the regular file is called xxx.lyx. The second is called
xxx-lyxformat-474.lyx. The
I work on several projects in LyX. Lately I have noticed that in the same
folders as my .lyx files there is a second file called -lyxformat-474.lyx.
For instance, if the regular file is called xxx.lyx. The second is called
xxx-lyxformat-474.lyx. The 474.lyx files seems to be old versions of the
Maybe this is not a LyX problem, I am not sure. But I only observe this
with text pasted from LyX. I use LyX Version 2.1.2.2 for OSX 10.10.1.
I am testing a new text correction (spelling/grammar/usage) software for
French: Le Robert Correcteur (*LRC*). It does not come for a module for LyX
of
Just to complete this, I also get the same problem when I paste the text
copied from LyX in a TextEdit window, so it does not seem to be specific to
Le Robert Correcteur.
2014-12-06 13:04 GMT+01:00 Murat Yildizoglu myi...@gmail.com:
Maybe this is not a LyX problem, I am not sure. But I only
Maybe this is not a LyX problem, I am not sure. But I only observe this
with text pasted from LyX. I use LyX Version 2.1.2.2 for OSX 10.10.1.
I am testing a new text correction (spelling/grammar/usage) software for
French: Le Robert Correcteur (*LRC*). It does not come for a module for LyX
of
Just to complete this, I also get the same problem when I paste the text
copied from LyX in a TextEdit window, so it does not seem to be specific to
Le Robert Correcteur.
2014-12-06 13:04 GMT+01:00 Murat Yildizoglu myi...@gmail.com:
Maybe this is not a LyX problem, I am not sure. But I only
Maybe this is not a LyX problem, I am not sure. But I only observe this
with text pasted from LyX. I use LyX Version 2.1.2.2 for OSX 10.10.1.
I am testing a new text correction (spelling/grammar/usage) software for
French: Le Robert Correcteur (*LRC*). It does not come for a module for LyX
of
Just to complete this, I also get the same problem when I paste the text
copied from LyX in a TextEdit window, so it does not seem to be specific to
Le Robert Correcteur.
2014-12-06 13:04 GMT+01:00 Murat Yildizoglu :
> Maybe this is not a LyX problem, I am not sure. But I only
Hi all,
I was writing the introduction to my PhD thesis and since the references to
some pictures were showing up as ?? I changed the label of one of those
pictures in the hopes that it solved the problem.
Well, it didn't, in fact I can't compile my thesis anymore.
Now it fails with the error
This is normal behavior. Just compile the file twice after compiling the .bib
file. Roughly:
Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex file.tex
Sent from my iPhone
On Jul 11, 2014, at 8:16 PM, Bruno Morgado jb.morg...@gmail.com wrote:
Hi all,
I was writing the
Hi,
but how do I do that from Lyx?
--
Bruno Morgado
Sent with Airmail
On 11 Jul 2014 at 18:43:55, Eisa Ayed (eisalen...@yahoo.com) wrote:
This is normal behavior. Just compile the file twice after compiling the .bib
file. Roughly:
Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex
Hi all,
I was writing the introduction to my PhD thesis and since the references to
some pictures were showing up as ?? I changed the label of one of those
pictures in the hopes that it solved the problem.
Well, it didn't, in fact I can't compile my thesis anymore.
Now it fails with the error
This is normal behavior. Just compile the file twice after compiling the .bib
file. Roughly:
Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex file.tex
Sent from my iPhone
On Jul 11, 2014, at 8:16 PM, Bruno Morgado jb.morg...@gmail.com wrote:
Hi all,
I was writing the
Hi,
but how do I do that from Lyx?
--
Bruno Morgado
Sent with Airmail
On 11 Jul 2014 at 18:43:55, Eisa Ayed (eisalen...@yahoo.com) wrote:
This is normal behavior. Just compile the file twice after compiling the .bib
file. Roughly:
Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex
Hi all,
I was writing the introduction to my PhD thesis and since the references to
some pictures were showing up as ?? I changed the label of one of those
pictures in the hopes that it solved the problem.
Well, it didn't, in fact I can't compile my thesis anymore.
Now it fails with the error
This is normal behavior. Just compile the file twice after compiling the .bib
file. Roughly:
Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex file.tex
Sent from my iPhone
> On Jul 11, 2014, at 8:16 PM, Bruno Morgado wrote:
>
> Hi all,
> I was writing the
Hi,
but how do I do that from Lyx?
--
Bruno Morgado
Sent with Airmail
On 11 Jul 2014 at 18:43:55, Eisa Ayed (eisalen...@yahoo.com) wrote:
This is normal behavior. Just compile the file twice after compiling the .bib
file. Roughly:
Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex
2014-06-04 3:53 GMT+02:00 Richard Heck:
On 06/03/2014 03:48 PM, Neal Becker wrote:
But without microtype it hyphenates correctly
Yes, I understand. But microtype modifies all kinds of things.
Also, the use of TeX font style switches is strongly discouraged in
LaTeX2e. I recommend to read
Jürgen Spitzmüller wrote:
2014-06-04 3:53 GMT+02:00 Richard Heck:
On 06/03/2014 03:48 PM, Neal Becker wrote:
But without microtype it hyphenates correctly
Yes, I understand. But microtype modifies all kinds of things.
Also, the use of TeX font style switches is strongly discouraged
2014-06-04 13:06 GMT+02:00 Neal Becker:
By TeX font style switches, you mean the {\em ...}?
Yes.
This was produced automatically from bibtex. The paragraph that produced
the
problem was from the bibliography, this was the .bbl file
OK, then the bst file is to blame.
Jürgen
Well that would be IEEE.bst then
On Wed, Jun 4, 2014 at 7:42 AM, Jürgen Spitzmüller sp...@lyx.org wrote:
2014-06-04 13:06 GMT+02:00 Neal Becker:
By TeX font style switches, you mean the {\em ...}?
Yes.
This was produced automatically from bibtex. The paragraph that produced
the
2014-06-04 3:53 GMT+02:00 Richard Heck:
On 06/03/2014 03:48 PM, Neal Becker wrote:
But without microtype it hyphenates correctly
Yes, I understand. But microtype modifies all kinds of things.
Also, the use of TeX font style switches is strongly discouraged in
LaTeX2e. I recommend to read
Jürgen Spitzmüller wrote:
2014-06-04 3:53 GMT+02:00 Richard Heck:
On 06/03/2014 03:48 PM, Neal Becker wrote:
But without microtype it hyphenates correctly
Yes, I understand. But microtype modifies all kinds of things.
Also, the use of TeX font style switches is strongly discouraged
2014-06-04 13:06 GMT+02:00 Neal Becker:
By TeX font style switches, you mean the {\em ...}?
Yes.
This was produced automatically from bibtex. The paragraph that produced
the
problem was from the bibliography, this was the .bbl file
OK, then the bst file is to blame.
Jürgen
Well that would be IEEE.bst then
On Wed, Jun 4, 2014 at 7:42 AM, Jürgen Spitzmüller sp...@lyx.org wrote:
2014-06-04 13:06 GMT+02:00 Neal Becker:
By TeX font style switches, you mean the {\em ...}?
Yes.
This was produced automatically from bibtex. The paragraph that produced
the
2014-06-04 3:53 GMT+02:00 Richard Heck:
> On 06/03/2014 03:48 PM, Neal Becker wrote:
>
> But without microtype it hyphenates correctly
>
>
> Yes, I understand. But microtype modifies all kinds of things.
>
Also, the use of TeX font style switches is strongly discouraged in
LaTeX2e. I recommend
Jürgen Spitzmüller wrote:
> 2014-06-04 3:53 GMT+02:00 Richard Heck:
>
>> On 06/03/2014 03:48 PM, Neal Becker wrote:
>>
>> But without microtype it hyphenates correctly
>>
>>
>> Yes, I understand. But microtype modifies all kinds of things.
>>
>
> Also, the use of TeX font style switches is
2014-06-04 13:06 GMT+02:00 Neal Becker:
> By TeX font style switches, you mean the {\em ...}?
>
Yes.
> This was produced automatically from bibtex. The paragraph that produced
> the
> problem was from the bibliography, this was the .bbl file
>
OK, then the bst file is to blame.
Jürgen
Well that would be IEEE.bst then
On Wed, Jun 4, 2014 at 7:42 AM, Jürgen Spitzmüller wrote:
> 2014-06-04 13:06 GMT+02:00 Neal Becker:
>
>> By TeX font style switches, you mean the {\em ...}?
>>
>
> Yes.
>
>
>> This was produced automatically from bibtex. The paragraph that
I am finalizing my IEEE conf paper. I added
\usepackage{microtype}
When I do that, one of the references is typeset with an extremely overfull
hbox. But the log says nothing about any overfull hbox!
Without microtype it's fine.
The offending item comes from this:
\bibitem{dvbs2-acm}
On 06/03/2014 01:15 PM, Neal Becker wrote:
I am finalizing my IEEE conf paper. I added
\usepackage{microtype}
When I do that, one of the references is typeset with an extremely overfull
hbox. But the log says nothing about any overfull hbox!
Without microtype it's fine.
The offending item
But without microtype it hyphenates correctly
On Jun 3, 2014 3:46 PM, Richard Heck rgh...@lyx.org wrote:
On 06/03/2014 01:15 PM, Neal Becker wrote:
I am finalizing my IEEE conf paper. I added
\usepackage{microtype}
When I do that, one of the references is typeset with an extremely
On 06/03/2014 03:48 PM, Neal Becker wrote:
But without microtype it hyphenates correctly
Yes, I understand. But microtype modifies all kinds of things.
rh
On Jun 3, 2014 3:46 PM, Richard Heck rgh...@lyx.org
mailto:rgh...@lyx.org wrote:
On 06/03/2014 01:15 PM, Neal Becker wrote:
I am finalizing my IEEE conf paper. I added
\usepackage{microtype}
When I do that, one of the references is typeset with an extremely overfull
hbox. But the log says nothing about any overfull hbox!
Without microtype it's fine.
The offending item comes from this:
\bibitem{dvbs2-acm}
On 06/03/2014 01:15 PM, Neal Becker wrote:
I am finalizing my IEEE conf paper. I added
\usepackage{microtype}
When I do that, one of the references is typeset with an extremely overfull
hbox. But the log says nothing about any overfull hbox!
Without microtype it's fine.
The offending item
But without microtype it hyphenates correctly
On Jun 3, 2014 3:46 PM, Richard Heck rgh...@lyx.org wrote:
On 06/03/2014 01:15 PM, Neal Becker wrote:
I am finalizing my IEEE conf paper. I added
\usepackage{microtype}
When I do that, one of the references is typeset with an extremely
On 06/03/2014 03:48 PM, Neal Becker wrote:
But without microtype it hyphenates correctly
Yes, I understand. But microtype modifies all kinds of things.
rh
On Jun 3, 2014 3:46 PM, Richard Heck rgh...@lyx.org
mailto:rgh...@lyx.org wrote:
On 06/03/2014 01:15 PM, Neal Becker wrote:
I am finalizing my IEEE conf paper. I added
\usepackage{microtype}
When I do that, one of the references is typeset with an extremely overfull
hbox. But the log says nothing about any overfull hbox!
Without microtype it's fine.
The offending item comes from this:
\bibitem{dvbs2-acm}
On 06/03/2014 01:15 PM, Neal Becker wrote:
I am finalizing my IEEE conf paper. I added
\usepackage{microtype}
When I do that, one of the references is typeset with an extremely overfull
hbox. But the log says nothing about any overfull hbox!
Without microtype it's fine.
The offending item
But without microtype it hyphenates correctly
On Jun 3, 2014 3:46 PM, "Richard Heck" wrote:
> On 06/03/2014 01:15 PM, Neal Becker wrote:
>
>> I am finalizing my IEEE conf paper. I added
>> \usepackage{microtype}
>>
>> When I do that, one of the references is typeset with an
On 06/03/2014 03:48 PM, Neal Becker wrote:
But without microtype it hyphenates correctly
Yes, I understand. But microtype modifies all kinds of things.
rh
On Jun 3, 2014 3:46 PM, "Richard Heck" > wrote:
On 06/03/2014 01:15 PM, Neal Becker
Dear all,
I'm seeing this strange behavior when centering a paragraph within a
table float. I see this in both 2.0.6 and 2.1beta1.
In the attached document, each table float contains an ERT inset (for
subsequent use with Sweave) within a centered paragraph. If the ERT
inset is above the caption
Liviu Andronic landronim...@gmail.com írta:
Dear all,
I'm seeing this strange behavior when centering a paragraph within a
table float. I see this in both 2.0.6 and 2.1beta1.
In the attached document, each table float contains an ERT inset (for
subsequent use with Sweave) within a centered
Am Freitag 11 Oktober 2013, 14:56:19 schrieb Csikos Bela:
What is begin{centering}?
I know of \centering command and center environment as
\begin{center}, \end{center}.
Can you give a definition of centering environment or a link
where it is described?
The centering environment
Jürgen Spitzmüller juer...@spitzmueller.org írta:
Am Freitag 11 Oktober 2013, 14:56:19 schrieb Csikos Bela:
What is begin{centering}?
I know of \centering command and center environment as
\begin{center}, \end{center}.
Can you give a definition of centering environment or a link
where it
Csikos Bela wrote:
What do you mean by empty \endcentering ?
empty \endcentering.
It means that \end{centering} calls \endcentering only if this command exists.
This is due to the way LaTeX environments are defined (the environment end
does not call \endcentering directly, but \csname
Dear all,
I'm seeing this strange behavior when centering a paragraph within a
table float. I see this in both 2.0.6 and 2.1beta1.
In the attached document, each table float contains an ERT inset (for
subsequent use with Sweave) within a centered paragraph. If the ERT
inset is above the caption
Liviu Andronic landronim...@gmail.com írta:
Dear all,
I'm seeing this strange behavior when centering a paragraph within a
table float. I see this in both 2.0.6 and 2.1beta1.
In the attached document, each table float contains an ERT inset (for
subsequent use with Sweave) within a centered
1 - 100 of 1286 matches
Mail list logo