Re: typesetting an algorithm
As far as I know the LyX algorithm is not related to algorithm.sty; it is more like an environment which, like verbatim, obeys user typed spaces, but, unlike verbatim, also allows math, boldface, etc... One thing that bites many users: when exporting to Latex, LyX inserts empty lines between two lines in the algorithm environment. If I recall correctly this can be avoided by using ctrl-enter to go to a new line inside the algorithm environment. I normally use an external package (e.g. listings.sty if you want to typeset code) and insert everything with ert. Stefaan. Raphael Clifford wrote: I am writing a paper in article (AMS) and need to typeset some algorithms. I see that there is an algorithm environmnent defined. I am sorry if I have missed them but are there any docs for using this environment in lyx? It is not clear to me what the correct way to do the indentation etc is. Cheers, Raphael
Re: costumization of italics
On Sat, Apr 24, 2004 at 10:26:04AM -0300, Beny wrote:
Dear all
I posted a few weeks ago a message asking for a way to make autocorrection of
words in lyx. Jean-Pierre kindly suggested to add ERTs with predefined
constructs using the command \newcommand{\bshs}{some string}. Though this
would solve my problem, it is more laborious than to press the keys Shift or
c^E to italize words. Since I have to write a lot of gene names in the text
and they have to be italized, I wonder if there is another way to customize
italization of words, so I would not have to press c^E before and after a
gene name is added.
If pressing two keys is too expensive (and I agree there are situations
like that), maybe you should just write your document without any such
markup and rather add it add the end using a simple script.
Andre'
Re: Two pictures side by side
Hi,
after reading, testing, ... here's my solution, in a ERT:
\begin{figure}[H]
\parbox{.48\linewidth}
{
\centering\includegraphics*{pic1.ps}
\caption{Picture 1}
}
\hfill
\parbox{.48\linewidth}
{
\centering\includegraphics*{pic2.ps}
\caption{Picture 2}
}
\end{figure}
Here both pictures a placed side-by-side, each with a separate caption, an
each with a separate entry in the list of figures.
--
Mit freundlichem GrussYours sincerely
Roland Schmitz
Re: Two pictures side by side --Update
Hi,
while working with my solution, i found somethimg strange. If i use the Enter
key for linebreak in the ERT my pictures are not set side-by-side, ther're
one over the other. If i use Ctrl+Enter for linebreak, it's ok. Can someone
explain the difference to me?
--
Mit freundlichem GrussYours sincerely
Roland Schmitz
Am Sonntag, 25. April 2004 16:10 schrieb Roland Schmitz:
Hi,
after reading, testing, ... here's my solution, in a ERT:
\begin{figure}[H]
\parbox{.48\linewidth}
{
\centering\includegraphics*{pic1.ps}
\caption{Picture 1}
}
\hfill
\parbox{.48\linewidth}
{
\centering\includegraphics*{pic2.ps}
\caption{Picture 2}
}
\end{figure}
Here both pictures a placed side-by-side, each with a separate caption, an
each with a separate entry in the list of figures.
--
Mit freundlichem GrussYours sincerely
Roland Schmitz
Graphics missing in PDF/PS, SGML export??
I'm a relatively unsophisticated but enthusiastic LyX user; I've been following its development for years. I'm using LyX 1.3.1 on RedHat 9 (installed from lyx-1.3.1-1rh9-qt.i386.rpm) with generally good results, creating structured docts for multiple target formats, esp. PDF, also PS, HTML, and text, using Linuxdoc SGML export from a LyX master created with a Linuxdoc template. I have done this successfully before with previous versions of LyX. Today I'm puzzled by absence of graphics in any of the generated products, including PDF generated by either (buffer-export pdf) or pdflatex export. My memory is that this worked fine in earlier versions. I can't imagine that this is really broken, but there does not seem to be any configuration at either the document level or the individual figure to control this. Any ideas? Thanks in advance. Alex Brown [EMAIL PROTECTED]
ASCII considered obscure
When importing text into an OpenOffice document, I suggested to a naïve user that she export the LyX document as text. She had two problems, both of which merit attention to LyX's menus, I think. First, in most programs, Text is a file type listed on the save dialog, not under Export, which tends to be reserved for non-editable formats such as PDF. This is certainly the case in most word processors. Hence, she was confused because there was no option in Save as to change the file type to text. Secondly, and much easier to fix, she then said but there's no option to export as text. She didn't know that ASCII means plain text. I suggest the menu entry be changed to say Plain text or similar, again, in line with most wordprocessors. -- http://rrt.sc3d.org/ | sad, a. the efforts of musical debutantes (Bierce)
Re: ASCII considered obscure
On Sun, Apr 25, 2004 at 10:25:26PM +0200, Reuben Thomas wrote: First, in most programs, Text is a file type listed on the save dialog, not under Export, which tends to be reserved for non-editable formats such as PDF. This is certainly the case in most word processors. Hence, she was confused because there was no option in Save as to change the file type to text. I've wanted this for a while. Secondly, and much easier to fix, she then said but there's no option to export as text. She didn't know that ASCII means plain text. I suggest the menu entry be changed to say Plain text or similar, again, in line with most wordprocessors. Plain Text is a good idea. File a bug. john
Re: ASCII considered obscure
John Levon wrote: On Sun, Apr 25, 2004 at 10:25:26PM +0200, Reuben Thomas wrote: First, in most programs, Text is a file type listed on the save dialog, not under Export, which tends to be reserved for non-editable formats such as PDF. This is certainly the case in most word processors. Hence, she was confused because there was no option in Save as to change the file type to text. I've wanted this for a while. Secondly, and much easier to fix, she then said but there's no option to export as text. She didn't know that ASCII means plain text. I suggest the menu entry be changed to say Plain text or similar, again, in line with most wordprocessors. Plain Text is a good idea. File a bug. Reluctantly, I agree. These days knowing what ASCII means is equivalent to knowing what a bulletin board is, or having worn flared trousers in the 1970s. Robin -- If the lion could speak, we would not understand it. - Wittgenstein Robin Turner IDMYO Bilkent Universitesi Ankara 06533 Turkey www.bilkent.edu.tr/~robin
Re: ASCII considered obscure
We call them there flared trousers as either flared jeans or bell-bottoms. -Marc On Sunday 25 April 2004 16:20, robin wrote: John Levon wrote: On Sun, Apr 25, 2004 at 10:25:26PM +0200, Reuben Thomas wrote: First, in most programs, Text is a file type listed on the save dialog, not under Export, which tends to be reserved for non-editable formats such as PDF. This is certainly the case in most word processors. Hence, she was confused because there was no option in Save as to change the file type to text. I've wanted this for a while. Secondly, and much easier to fix, she then said but there's no option to export as text. She didn't know that ASCII means plain text. I suggest the menu entry be changed to say Plain text or similar, again, in line with most wordprocessors. Plain Text is a good idea. File a bug. Reluctantly, I agree. These days knowing what ASCII means is equivalent to knowing what a bulletin board is, or having worn flared trousers in the 1970s. Robin
Re: typesetting an algorithm
As far as I know the LyX algorithm is not related to algorithm.sty; it is more like an environment which, like verbatim, obeys user typed spaces, but, unlike verbatim, also allows math, boldface, etc... One thing that bites many users: when exporting to Latex, LyX inserts empty lines between two lines in the algorithm environment. If I recall correctly this can be avoided by using ctrl-enter to go to a new line inside the algorithm environment. I normally use an external package (e.g. listings.sty if you want to typeset code) and insert everything with ert. Stefaan. Raphael Clifford wrote: I am writing a paper in article (AMS) and need to typeset some algorithms. I see that there is an algorithm environmnent defined. I am sorry if I have missed them but are there any docs for using this environment in lyx? It is not clear to me what the correct way to do the indentation etc is. Cheers, Raphael
Re: costumization of italics
On Sat, Apr 24, 2004 at 10:26:04AM -0300, Beny wrote:
Dear all
I posted a few weeks ago a message asking for a way to make autocorrection of
words in lyx. Jean-Pierre kindly suggested to add ERTs with predefined
constructs using the command \newcommand{\bshs}{some string}. Though this
would solve my problem, it is more laborious than to press the keys Shift or
c^E to italize words. Since I have to write a lot of gene names in the text
and they have to be italized, I wonder if there is another way to customize
italization of words, so I would not have to press c^E before and after a
gene name is added.
If pressing two keys is too expensive (and I agree there are situations
like that), maybe you should just write your document without any such
markup and rather add it add the end using a simple script.
Andre'
Re: Two pictures side by side
Hi,
after reading, testing, ... here's my solution, in a ERT:
\begin{figure}[H]
\parbox{.48\linewidth}
{
\centering\includegraphics*{pic1.ps}
\caption{Picture 1}
}
\hfill
\parbox{.48\linewidth}
{
\centering\includegraphics*{pic2.ps}
\caption{Picture 2}
}
\end{figure}
Here both pictures a placed side-by-side, each with a separate caption, an
each with a separate entry in the list of figures.
--
Mit freundlichem GrussYours sincerely
Roland Schmitz
Re: Two pictures side by side --Update
Hi,
while working with my solution, i found somethimg strange. If i use the Enter
key for linebreak in the ERT my pictures are not set side-by-side, ther're
one over the other. If i use Ctrl+Enter for linebreak, it's ok. Can someone
explain the difference to me?
--
Mit freundlichem GrussYours sincerely
Roland Schmitz
Am Sonntag, 25. April 2004 16:10 schrieb Roland Schmitz:
Hi,
after reading, testing, ... here's my solution, in a ERT:
\begin{figure}[H]
\parbox{.48\linewidth}
{
\centering\includegraphics*{pic1.ps}
\caption{Picture 1}
}
\hfill
\parbox{.48\linewidth}
{
\centering\includegraphics*{pic2.ps}
\caption{Picture 2}
}
\end{figure}
Here both pictures a placed side-by-side, each with a separate caption, an
each with a separate entry in the list of figures.
--
Mit freundlichem GrussYours sincerely
Roland Schmitz
Graphics missing in PDF/PS, SGML export??
I'm a relatively unsophisticated but enthusiastic LyX user; I've been following its development for years. I'm using LyX 1.3.1 on RedHat 9 (installed from lyx-1.3.1-1rh9-qt.i386.rpm) with generally good results, creating structured docts for multiple target formats, esp. PDF, also PS, HTML, and text, using Linuxdoc SGML export from a LyX master created with a Linuxdoc template. I have done this successfully before with previous versions of LyX. Today I'm puzzled by absence of graphics in any of the generated products, including PDF generated by either (buffer-export pdf) or pdflatex export. My memory is that this worked fine in earlier versions. I can't imagine that this is really broken, but there does not seem to be any configuration at either the document level or the individual figure to control this. Any ideas? Thanks in advance. Alex Brown [EMAIL PROTECTED]
ASCII considered obscure
When importing text into an OpenOffice document, I suggested to a naïve user that she export the LyX document as text. She had two problems, both of which merit attention to LyX's menus, I think. First, in most programs, Text is a file type listed on the save dialog, not under Export, which tends to be reserved for non-editable formats such as PDF. This is certainly the case in most word processors. Hence, she was confused because there was no option in Save as to change the file type to text. Secondly, and much easier to fix, she then said but there's no option to export as text. She didn't know that ASCII means plain text. I suggest the menu entry be changed to say Plain text or similar, again, in line with most wordprocessors. -- http://rrt.sc3d.org/ | sad, a. the efforts of musical debutantes (Bierce)
Re: ASCII considered obscure
On Sun, Apr 25, 2004 at 10:25:26PM +0200, Reuben Thomas wrote: First, in most programs, Text is a file type listed on the save dialog, not under Export, which tends to be reserved for non-editable formats such as PDF. This is certainly the case in most word processors. Hence, she was confused because there was no option in Save as to change the file type to text. I've wanted this for a while. Secondly, and much easier to fix, she then said but there's no option to export as text. She didn't know that ASCII means plain text. I suggest the menu entry be changed to say Plain text or similar, again, in line with most wordprocessors. Plain Text is a good idea. File a bug. john
Re: ASCII considered obscure
John Levon wrote: On Sun, Apr 25, 2004 at 10:25:26PM +0200, Reuben Thomas wrote: First, in most programs, Text is a file type listed on the save dialog, not under Export, which tends to be reserved for non-editable formats such as PDF. This is certainly the case in most word processors. Hence, she was confused because there was no option in Save as to change the file type to text. I've wanted this for a while. Secondly, and much easier to fix, she then said but there's no option to export as text. She didn't know that ASCII means plain text. I suggest the menu entry be changed to say Plain text or similar, again, in line with most wordprocessors. Plain Text is a good idea. File a bug. Reluctantly, I agree. These days knowing what ASCII means is equivalent to knowing what a bulletin board is, or having worn flared trousers in the 1970s. Robin -- If the lion could speak, we would not understand it. - Wittgenstein Robin Turner IDMYO Bilkent Universitesi Ankara 06533 Turkey www.bilkent.edu.tr/~robin
Re: ASCII considered obscure
We call them there flared trousers as either flared jeans or bell-bottoms. -Marc On Sunday 25 April 2004 16:20, robin wrote: John Levon wrote: On Sun, Apr 25, 2004 at 10:25:26PM +0200, Reuben Thomas wrote: First, in most programs, Text is a file type listed on the save dialog, not under Export, which tends to be reserved for non-editable formats such as PDF. This is certainly the case in most word processors. Hence, she was confused because there was no option in Save as to change the file type to text. I've wanted this for a while. Secondly, and much easier to fix, she then said but there's no option to export as text. She didn't know that ASCII means plain text. I suggest the menu entry be changed to say Plain text or similar, again, in line with most wordprocessors. Plain Text is a good idea. File a bug. Reluctantly, I agree. These days knowing what ASCII means is equivalent to knowing what a bulletin board is, or having worn flared trousers in the 1970s. Robin
Re: typesetting an algorithm
As far as I know the LyX algorithm is not related to algorithm.sty; it is more like an environment which, like verbatim, obeys user typed spaces, but, unlike verbatim, also allows math, boldface, etc... One thing that bites many users: when exporting to Latex, LyX inserts empty lines between two lines in the algorithm environment. If I recall correctly this can be avoided by using ctrl-enter to go to a new line inside the algorithm environment. I normally use an external package (e.g. listings.sty if you want to typeset code) and insert everything with ert. Stefaan. Raphael Clifford wrote: I am writing a paper in article (AMS) and need to typeset some algorithms. I see that there is an algorithm environmnent defined. I am sorry if I have missed them but are there any docs for using this environment in lyx? It is not clear to me what the correct way to do the indentation etc is. Cheers, Raphael
Re: costumization of italics
On Sat, Apr 24, 2004 at 10:26:04AM -0300, Beny wrote:
> Dear all
> I posted a few weeks ago a message asking for a way to make autocorrection of
> words in lyx. Jean-Pierre kindly suggested to add ERTs with predefined
> constructs using the command \newcommand{\bshs}{some string}. Though this
> would solve my problem, it is more laborious than to press the keys Shift or
> c^E to italize words. Since I have to write a lot of gene names in the text
> and they have to be italized, I wonder if there is another way to customize
> italization of words, so I would not have to press c^E before and after a
> gene name is added.
If pressing two keys is too expensive (and I agree there are situations
like that), maybe you should just write your document without any such
markup and rather add it add the end using a simple script.
Andre'
Re: Two pictures side by side
Hi,
after reading, testing, ... here's my solution, in a ERT:
\begin{figure}[H]
\parbox{.48\linewidth}
{
\centering\includegraphics*{pic1.ps}
\caption{Picture 1}
}
\hfill
\parbox{.48\linewidth}
{
\centering\includegraphics*{pic2.ps}
\caption{Picture 2}
}
\end{figure}
Here both pictures a placed side-by-side, each with a separate caption, an
each with a separate entry in the list of figures.
--
Mit freundlichem GrussYours sincerely
Roland Schmitz
Re: Two pictures side by side --Update
Hi,
while working with my solution, i found somethimg strange. If i use the Enter
key for linebreak in the ERT my pictures are not set side-by-side, ther're
one over the other. If i use Ctrl+Enter for linebreak, it's ok. Can someone
explain the difference to me?
--
Mit freundlichem GrussYours sincerely
Roland Schmitz
Am Sonntag, 25. April 2004 16:10 schrieb Roland Schmitz:
> Hi,
>
> after reading, testing, ... here's my solution, in a ERT:
>
> \begin{figure}[H]
> \parbox{.48\linewidth}
> {
> \centering\includegraphics*{pic1.ps}
> \caption{Picture 1}
> }
> \hfill
> \parbox{.48\linewidth}
> {
> \centering\includegraphics*{pic2.ps}
> \caption{Picture 2}
> }
> \end{figure}
>
> Here both pictures a placed side-by-side, each with a separate caption, an
> each with a separate entry in the list of figures.
>
> --
> Mit freundlichem GrussYours sincerely
>
> Roland Schmitz
Graphics missing in PDF/PS, SGML export??
I'm a relatively unsophisticated but enthusiastic LyX user; I've been following its development for years. I'm using LyX 1.3.1 on RedHat 9 (installed from lyx-1.3.1-1rh9-qt.i386.rpm) with generally good results, creating structured docts for multiple target formats, esp. PDF, also PS, HTML, and text, using Linuxdoc SGML export from a LyX master created with a Linuxdoc template. I have done this successfully before with previous versions of LyX. Today I'm puzzled by absence of graphics in any of the generated products, including PDF generated by either (buffer-export pdf) or pdflatex export. My memory is that this worked fine in earlier versions. I can't imagine that this is really broken, but there does not seem to be any configuration at either the document level or the individual figure to control this. Any ideas? Thanks in advance. Alex Brown <[EMAIL PROTECTED]>
"ASCII" considered obscure
When importing text into an OpenOffice document, I suggested to a naïve user that she export the LyX document as text. She had two problems, both of which merit attention to LyX's menus, I think. First, in most programs, "Text" is a file type listed on the save dialog, not under "Export", which tends to be reserved for non-editable formats such as PDF. This is certainly the case in most word processors. Hence, she was confused because there was no option in "Save as" to change the file type to text. Secondly, and much easier to fix, she then said "but there's no option to export as text". She didn't know that ASCII means plain text. I suggest the menu entry be changed to say "Plain text" or similar, again, in line with most wordprocessors. -- http://rrt.sc3d.org/ | sad, a. the efforts of musical debutantes (Bierce)
Re: "ASCII" considered obscure
On Sun, Apr 25, 2004 at 10:25:26PM +0200, Reuben Thomas wrote: > First, in most programs, "Text" is a file type listed on the save dialog, > not under "Export", which tends to be reserved for non-editable formats > such as PDF. This is certainly the case in most word processors. Hence, > she was confused because there was no option in "Save as" to change the > file type to text. I've wanted this for a while. > Secondly, and much easier to fix, she then said "but there's no option to > export as text". She didn't know that ASCII means plain text. I suggest > the menu entry be changed to say "Plain text" or similar, again, in line > with most wordprocessors. "Plain Text" is a good idea. File a bug. john
Re: "ASCII" considered obscure
John Levon wrote: On Sun, Apr 25, 2004 at 10:25:26PM +0200, Reuben Thomas wrote: First, in most programs, "Text" is a file type listed on the save dialog, not under "Export", which tends to be reserved for non-editable formats such as PDF. This is certainly the case in most word processors. Hence, she was confused because there was no option in "Save as" to change the file type to text. I've wanted this for a while. Secondly, and much easier to fix, she then said "but there's no option to export as text". She didn't know that ASCII means plain text. I suggest the menu entry be changed to say "Plain text" or similar, again, in line with most wordprocessors. "Plain Text" is a good idea. File a bug. Reluctantly, I agree. These days knowing what ASCII means is equivalent to knowing what a bulletin board is, or having worn flared trousers in the 1970s. Robin -- "If the lion could speak, we would not understand it." - Wittgenstein Robin Turner IDMYO Bilkent Universitesi Ankara 06533 Turkey www.bilkent.edu.tr/~robin
Re: "ASCII" considered obscure
We call them there flared trousers as either flared jeans or "bell-bottoms." -Marc On Sunday 25 April 2004 16:20, robin wrote: > John Levon wrote: > > On Sun, Apr 25, 2004 at 10:25:26PM +0200, Reuben Thomas wrote: > >>First, in most programs, "Text" is a file type listed on the save dialog, > >>not under "Export", which tends to be reserved for non-editable formats > >>such as PDF. This is certainly the case in most word processors. Hence, > >>she was confused because there was no option in "Save as" to change the > >>file type to text. > > > > I've wanted this for a while. > > > >>Secondly, and much easier to fix, she then said "but there's no option to > >>export as text". She didn't know that ASCII means plain text. I suggest > >>the menu entry be changed to say "Plain text" or similar, again, in line > >>with most wordprocessors. > > > > "Plain Text" is a good idea. File a bug. > > Reluctantly, I agree. These days knowing what ASCII means is equivalent > to knowing what a bulletin board is, or having worn flared trousers in > the 1970s. > > Robin
