Linebreak in \bibitem
Hi! Is it possible to insert a line break after the label of each bibliography item? I now get: [Label1] Author1, title1, year [Label2] Author2, title2, year ... What I would like to have is: [Label1] Author1, title1, year [Label2] Author2, title2, year ... I have tried to manipulate my own bst-file (based on plain), but have not yet figured out how to insert a line break in a bibitem command. Thanks in advance, Kimmo
Re: Simulate update dvi behaviour in update pdflatex
Sharma, Vivek schrieb: I uninstalled and reinstalled adobe reader 9.1 and the bug persists I am on a windows vista business 32 bit os I wonder whether my dilemma is unique to me does it have to do with windows api calls whatever that means(!) Yes it has. We specially wrote a program that calls the Acrobat API to close and open the PDF when it is updated. I used Acrobat professional 7.0 and now 7.1. Both work as well as Adobe Reader 8.1. I haven't tested Adobe Reader 9. But doesn't it at least work when you press in Acrobat's toolbar the button with the left arrow? This jumps back to the last viewed position in the PDF so you get when you want. regards Uwe
Re: powerdot class options
Eran Kaplinsky schrieb: I don't know if there's a bug in Powerdot. I've not used Powerdot in quite some time, and I recently found out that older presentations did not compile as expected. I've always followed the manual which said: 10.3 Compiling with LYX But this is the manual of powerdot not the one of LyX. However, I recently found out that the nopsheader option must now be omitted for the document to compile properly. (See also: http://www.mail-archive.com/lyx-users@lists.lyx.org/msg71492.html). I see what you mean and now removed this option in the powerdot LyX example file. This needs to be described in the powerdot manual. Also note that contrary to the manual, once the powerdot class is selected in LyX, the option to select paper size and orientation is no longer available. This is by design because powerdot uses its own option names for this instead of the LaTeX default ones. You need to add the paper orientation as option to the document class in LyX to change the orientation and the paper size. Can you therefore please inform the authors of powerdot to update their manual and CC me? regards Uwe
Re: Vertical spacing of matrices
Yago schrieb: Without new commands, for matrix you can use the command \vspace like in the attachedd file that presents the Delambre Analogies in a matrix. This is indeed also a solution but might need more time when you have many rows and columns. Looking at you file I noticed that you are using terms like cos1/2(A+B) This is incorrect typesetting. The correct one is this: http://mathworld.wolfram.com/GausssFormulas.html (the 1/2 in in the argument of the function) regards Uwe
Re: Vertical spacing of matrices
Without new commands, for matrix you can use the command \vspace like in the attachedd file that presents the Delambre Analogies in a matrix. - Original Message - From: "Uwe Stöhr" To: "Luca Carlon" Cc: Sent: Thursday, September 10, 2009 7:09 PM Subject: Re: Vertical spacing of matrices Luca Carlon schrieb: I noticed it increses the space for tables in floats too. Isn't it possible to do this only for matrices? No because a table is actually an array as well as a matrix is an array. What you can do is to define your own short command that you can use before and after the matrices, see the attached file. You can also define two keyboard shortcuts that inserts these commands. regards Uwe Analogias_Delambre_Matriz.lyx Description: application/lyx
Re: Option Clash with hyperref
Rob schrieb:
I want to use backref, but I'm getting an options clash.
What is the error message?
I read in a past post
that there is some mess when trying to specify the options in hyperref since
they're already set but that a work around is to add a \hyperset argument to the
preamble. In this case, I tried the following without any success:
\hyperset{pagebackref=yes}
You can also set this option in the document settings in the PDF properties.
When this doesn't work, can you please provide a _small_ example LyX file.
regards Uwe
Option Clash with hyperref
Hi,
I want to use backref, but I'm getting an options clash. I read in a past post
that there is some mess when trying to specify the options in hyperref since
they're already set but that a work around is to add a \hyperset argument to the
preamble. In this case, I tried the following without any success:
\hyperset{pagebackref=yes}
In this case, there is no error message, but backref doesn't work.
Any thoughts are much appreciated.
Rob
Re: Re: Will Lyx run on Mac OS X 10.6?
Here some additional information to my previous post: I think the relevant parts of the log of my failed lyx compilation are: ... imac:BRANCH_1_6_X jo$ ./configure --prefix=/Users/jo/Desktop/lyx_snowleopard/LyX.app --with-version-suffix=-1.6 --with-qt4-dir=/Developer/Tools/Qt --with-included-gettext --enable- ... checking for Qt 4 library name... failed checking for moc-qt4... no checking for moc... /usr/bin/moc checking for uic-qt4... no checking for uic... /usr/bin/uic checking for rcc-qt4... no checking for rcc... /usr/bin/rcc ... Configuration Host type:i386-apple-darwin10.0.0 Special build flags: assertions concept-checks stdlib-debug warnings use-pspell use-ispell C Compiler: gcc C Compiler LyX flags: C Compiler flags: -Wextra -Wall-g -Os C++ Compiler: g++ (4.2.1) C++ Compiler LyX flags: C++ Compiler flags: -Wextra -Wall-g -Os Linker flags: Linker user flags:-framework Carbon -framework OpenGL -framework AGL -framework QuickTime -framework Cocoa Qt 4 Frontend: Qt 4 version: Packaging:macosx LyX binary dir: /Users/account/Desktop/lyx_snowleopard/LyX.app/Contents/MacOS LyX files dir: /Users/account/Desktop/lyx_snowleopard/LyX.app/Contents/Resources The following problems have been detected by configure. Please check the messages below before running 'make'. (see the section 'Problems' in the INSTALL file) ** qt 4 library not found ! Well, what is the correct QT path if it is not the one QT tells me? Johannes. Ist Ihr wunschn...@freenet.de noch frei? Jetzt prüfen und kostenlose E-Mail-Adresse sichern! http://email.freenet.de/dienste/emailoffice/produktuebersicht/basic/mail/index.html?pid=6829
Re: Vertical spacing of matrices
Luca Carlon schrieb: I noticed it increses the space for tables in floats too. Isn't it possible to do this only for matrices? No because a table is actually an array as well as a matrix is an array. What you can do is to define your own short command that you can use before and after the matrices, see the attached file. You can also define two keyboard shortcuts that inserts these commands. regards Uwe newfile3.lyx Description: application/lyx
Re: Vertical spacing of matrices
Uwe Stöhr writes: > You can use the commands \arraycolsep and \arraystretch. Have a look at the Math manual, section 4, > that you find in LyX's Help menu. > > regards Uwe Thanks! This is great! Anyway, I noticed it increses the space for tables in floats too. Isn't it possible to do this only for matrices? It's not too comfortable to change i continuously... Thanks again! Luca
Re: beamer handouts: how to delete/suppress frames?
Erez Yerushalmi wrote:
Hi all,
I'm writing a presentation using beamer, lyx 1.63, window...
I would like to have a handout, where some frames will be automatically
deleted (suppress frames).
What I would like to do in TEX, or internally in LyX, is the following:
\begin{frame}
\frametitle{A title bla bla bla}
*Some content. bla bla bla
*\end{frame}
Some times it works, some times it doesn't, and I get the ERROR
file does not exist: c:/document and
settings/.../temp/lyx_tempdir.Hp3316/lyx_tempbuf0/filename.pdf
Can anyone give me a hint ??
The file does not exist error probably means LaTeX blew up trying to
compile the document; check Document > LaTeX log to see if there's an
error message. Assuming you put in ERT at the very
beginning of the frame title, it seems that it should work, barring a
bug in Beamer.
All else failing, you might try putting the frames to be suppressed in a
branch of the LyX doc, then deactivate that branch for handouts
(activate for slide shows). I just ran a quick test, and it worked fine
for me.
/Paul
Re: Vertical spacing of matrices
Luca Carlon schrieb: Hi! I'm writing some matrices where I put inside some quite big terms (dfracs for instance). I noticed that it is frequent that some term is too close, almost overlapping, to the element over it. Is it possible somehow to increase the vertical spacing? You can use the commands \arraycolsep and \arraystretch. Have a look at the Math manual, section 4, that you find in LyX's Help menu. regards Uwe
Re: Rotating tables with URLs
On Wed, 09 Sep 2009 19:25:27 +0200 Uwe Stöhr wrote: > > I have a (rather wide) table with cross-references in it. When I > > rotate the table to fit it on a page, the table rotates fine, but the > > (red) boxes around the references stay unrotated. > > You can turn off the boxes in the document settings in the section of > the PDF properties. Thanks Uwe! I'll do that for now. John
Vertical spacing of matrices
Hi! I'm writing some matrices where I put inside some quite big terms (dfracs for instance). I noticed that it is frequent that some term is too close, almost overlapping, to the element over it. Is it possible somehow to increase the vertical spacing? Thanks!
Re: More indexing bogosity
Steve Litt wrote:
> Let me refine the concept of "bogus". True, the ERT isn't bogus from a data
> consistency point of view, nor is it bogus from a logical point of view.
> But it's very bogus from the point of view of the user's workflow. The
> user must now, twice per index see or seealso entry, press Ctrl+L and type
> in a curly brace. If the user doesn't use T1 output character set, he has
> to do something similar with every regular index entry with a range. This
> significantly slows the user, makes the user think about something other
> than the content, and can cause temporary failure to an unsophisticated
> user.
I'd consider everything behind "|" in an index entry "sophisticated", because
it requires LaTeX knowledge. I'd say that unsophisticated users would rather
expect "{" to be typeset as "{" rather than to be verbatim LaTeX.
In LyX, all verbatim LaTeX has to be embraced by ERT. Why should we make an
exception just for indexes? I'd consider that conceptually bogus.
> The point of computer programming is to make things faster and easier for
> the user. Otherwise, why not just use TeX? This change makes things slower
> and harder while indexing.
It makes some things harder while making others faster. We considered the gain
bigger than the burden.
> > The gain of this change is that you are not forced to write \"ubergro\ss
> > but can simply write übergroß in all encodings. And you can directly
> > emphasize entries, without the need to write \emph{my entry}.
>
> That's definitely a gain. The trouble is, it comes at the cost of a loss
> for ranges and sees and seealsos. It also breaks formerly working
> documents.
It's not supposed to break formerly working documents. In other words: the
braces should be wrapped in ERT by the lyx2lyx converter. I just verified that
this works. If it doesn't for you, please provide a test case.
I know that "|" need to be wrapped as well, and they aren't yet. But you know
that I have already developed a patch to fix this bug.
> I'm sure there are ways to implement the advantages without the
> disadvantages. Here are a few:
>
> * Use a dialog box to define each element of an index entry.
> * Have a single character to escape |, { and }
> * Have an option to evaluate indexes the way 1.5.x did
As already stated, the way would be to support "|see" and the like natively.
Unless we do that, it is treated as any other verbatim LaTeX.
However, you can easily restore the 1.5.x behaviour:
copy the file stdinsets.onc from the System directory to the user directory,
and in the entry of InsetLayout Index, add the line
PassThru true
Then all content of the inset will be treated verbatim (as in ERT). Of course,
you will lose all the 1.6.x index improvements with this change.
> If nothing is done about this, it won't harm me. I write only English so T1
> is fine with me. I find it better to put see and seealso entries in a
> separate file so I won't have to ERT twice per entry. Even if things
> change some more so T1 doesn't work for me, I already have a kludge script
> to correct the LyX produced LaTeX. But these opportunities aren't
> available to a lot of users, and they will be slowed by this new method of
> parsing LyX index entries.
As said, I have proposed a solution for the T1 problem. So no kludge script is
needed.
> StevET
>
> Steve Litt
> Recession Relief Package
> http://www.recession-relief.US
> Twitter: http://www.twitter.com/stevelitt
>
Jürgen
Re: More indexing bogosity
On Thursday 10 September 2009 04:14:44 Jürgen Spitzmüller wrote:
> Steve Litt wrote:
> > This time, when inserting see and seealso records, I'm forced to use ERT
> > for each of the curly braces or else part of the seealso text doesn't
> > show up and an erroneous page number is shown. This is a huge time sink.
>
> The big change in 1.6.x indexing is that indexes now behave as normal text.
> So you have to use ERT whereever you would need ERT in normal text. Since
> |see{} is a LaTeX macro (just using "|" instead of "\"), ERT is not bogus
> at all here.
Let me refine the concept of "bogus". True, the ERT isn't bogus from a data
consistency point of view, nor is it bogus from a logical point of view. But
it's very bogus from the point of view of the user's workflow. The user must
now, twice per index see or seealso entry, press Ctrl+L and type in a curly
brace. If the user doesn't use T1 output character set, he has to do something
similar with every regular index entry with a range. This significantly slows
the user, makes the user think about something other than the content, and can
cause temporary failure to an unsophisticated user.
The point of computer programming is to make things faster and easier for the
user. Otherwise, why not just use TeX? This change makes things slower and
harder while indexing.
>
> The gain of this change is that you are not forced to write \"ubergro\ss
> but can simply write übergroß in all encodings. And you can directly
> emphasize entries, without the need to write \emph{my entry}.
That's definitely a gain. The trouble is, it comes at the cost of a loss for
ranges and sees and seealsos. It also breaks formerly working documents. I'm
sure there are ways to implement the advantages without the disadvantages.
Here are a few:
* Use a dialog box to define each element of an index entry.
* Have a single character to escape |, { and }
* Have an option to evaluate indexes the way 1.5.x did
If nothing is done about this, it won't harm me. I write only English so T1 is
fine with me. I find it better to put see and seealso entries in a separate
file
so I won't have to ERT twice per entry. Even if things change some more so T1
doesn't work for me, I already have a kludge script to correct the LyX
produced LaTeX. But these opportunities aren't available to a lot of users,
and they will be slowed by this new method of parsing LyX index entries.
StevET
Steve Litt
Recession Relief Package
http://www.recession-relief.US
Twitter: http://www.twitter.com/stevelitt
Re: More indexing bogosity
Steve Litt wrote:
> This time, when inserting see and seealso records, I'm forced to use ERT
> for each of the curly braces or else part of the seealso text doesn't
> show up and an erroneous page number is shown. This is a huge time sink.
The big change in 1.6.x indexing is that indexes now behave as normal text. So
you have to use ERT whereever you would need ERT in normal text. Since |see{}
is a LaTeX macro (just using "|" instead of "\"), ERT is not bogus at all
here.
The gain of this change is that you are not forced to write \"ubergro\ss but
can simply write übergroß in all encodings. And you can directly emphasize
entries, without the need to write \emph{my entry}.
Jürgen
