Problem with \thanks in Author field
Hi.. I'm trying to include the \thanks in the author field but get a
couple of errors related to extra brackets. Attached is a sample lyx
file. Please let me know what the best way to do this would be..
thanks,
nirmal
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass article
\language american
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Title
Test Title
\layout Author
Author1, Author2
\begin_inset ERT
status Collapsed
\layout Standard
%
\layout Standard
\backslash
thanks{Author1 details}%
\layout Standard
\backslash
thanks{Author2 details}
\end_inset
\layout Abstract
abstract..
\layout Section
Section1
\layout Standard
asdasd
\the_end
Re: woe with indexing
William F. Adams wrote: On Thursday, August 12, 2004, at 09:36 AM, stephan beal wrote: But if i delete it or rename it to, e.g., foo i get even MORE errors. As Herbert noted, special characters which have special meanings aren't changed by LyX when entered into an index field --- this probably qualifies as a bug, or at least should be mentioned in the manual. Not at all a bug, but mentioning the index rules in the manual is a very good idea. The reason we need ability to put all sorts of symbols into an index entry (without having lyx mangle it automatically so you get exactly what you typed into the index ) is that we sometimes need or want to put latex commands in the index entries. There are many reasons for that - special formatting of some words in the index is one. Of course the better approach here would be a lyx that auto-mangles index text so that underscores, other special symbols and formatting like emphasizing works for those who just types the stuff in. This is ok _if_ the enhanced index entry also can contain ERT boxes so the advanced users can keep their latex commands. Helge Hafting
Re: proposal for bug fix vis-a-vis index entries
stephan beal wrote: @lyx developers, i'd look at doing this fix myself, but i'm on a dialup line, paying for each minute online, and the lyx tarball is 5M+. For the Qt interface, it seems it would be trivial to fix the Index Item entry dialog to automatically escape any illegal characters, like _. Careful now. _Only_ autoescaping will render impossible all the stuff we do today with _ and | and \ and so on when writing index entries. (All the symbols that gave you grief is usable in indexes - they are very useful when used right! ) Of course autoescaping is ok _if_ some other way is provided for accessing the advandec functionality of makeindex. Note that _ and \ is equally troublesome/useful in the main tex - but it is autoescaped there, and the ERT box is available for those who need it. The ideal solution is an index entry that allow most of the stuff that works in the main text (except for sectioning and floats). In other words: * Escape special symbols the user just types in, as is done for the main text * Allow math editor in an index entry (My book on algorithm complexity have an index entry for $\Omega$, for example. A math paper might index lots of formulas. Chemistry uses _ a lot in formulas too. * Allow formatting like emphasize, bold and character styles inside an index entry, and translate to the mechanism makeindex uses for this. This would save a lot of latex currently used to get bold/emphasized index entries. * Allow ERT boxes inside index entries so experts still can do everything latex can do. * Perhaps let the index entry GUI have special support for some things, like: - the 'see' something else index entry - the mechanism for special formatting of the page number, by providing a separate field with the text pagenumber so the user can use the ordinary editing GUI to create bold/emphasized/colored numbers. - GUI mechanisms for specifying ranges so we get entries like entry:5,7,8-12,76-233,314 - GUI mechansim for dealing with cases when sort order and presentation is very different. This is important in many cases, for example when indexing math. (I put my $\Omega$ index both among symbols (correctly placed in relation to other greek stuff) as well as alphabetically where the word Omega would go. Doing _all_ of this is probably a lot of work. If you implement autoescaping, possibly by reusing autoescape code used for main text, then at least the ERT inside an index entry is necessary. Expert users can then kludge all the rest in ERT, similar to how they now kludge it in todays index entries. The rest can then come with time. The fact that the dialog allows one to enter invalid data has caused me NO END of grief. Adding a single underscore to one index entry causes errors in completely unrelated parts of the doc when exporting, and tracking down the problem is really difficult (as is shown by my frustrated posts on the topic), especially since Idx entries aren't visible until clicked on (maybe an Expand/View Index Entries option, like the one for Footnotes, is feasible?). The current system could use some warnings as well as a reference to litterature on makeindex syntax . . . IMO a dialog box should not allow you to enter data which is itself illegal for the program the dialog is serving, especially when it *silently* does so. Well, a _ is a perfectly legal character in an index entry, when used right. Example index entries that works fine: foo\_bar $C_2H_5OH$-(ethanol) I agree that the current way is not userfriendly, but don't _remove_ existing possibilities just to make your own case easier. Helge Hafting
Re: Changing text height and width?
Stefano Franchi wrote:
Hi all,
I am asked by a publisher to submit a book length manuscript in
camera-ready form and unfortunately they don't provide LaTeX classes.
In fact, they have given me Microsoft Word instructions :-(
Well, at least they let you use whatever you want, and don't re-type it
all in word or
something equally stupid before printing. (Wasted work, and latex
provides much better output too!)
Anything you want can be tweaked to exactly the right size, you may have to
learn _some_ latex in the process though. I wrote a book, with detail specs
on the text block size, paper size, and fonts to be used from the publisher.
I used the koma-script book class and adapted that. The latex documentation
for koma-script details how the page layout is specified with latex commands
in the preamble. Use that to get exactly the text block you want.
There wasn't
a specifier for the total text block size, so I specified one height for
the text part
of the text block which was the total height minus the height of the
running head.
Fortunately, latex lets you enter such arithmetic expressions so no need
to calculate
it to some number of decimals. (mixing points, inches and centimeters
is easy with latex. :-)
Examples from my preamble. I don't claim it is the best way, but it
worked fine:
\setlength{\paperwidth}{170mm}
\setlength{\paperheight}{240mm}
%text block
\areaset{121.5mm}{203mm}
%Margins. Compensate for tex silly 1in origo
\setlength{\oddsidemargin}{16mm-1in}
\setlength{\evensidemargin}{32.5mm-1in}
%Position the top of text
\setlength{\topmargin}{8.5mm-1in}
%publisher says: headsep+headheight+topmargin=22mm
%(I didn't set headheight anywhere, the default worked well)
\setlength{\headsep}{22mm-8.5mm-\headheight}
I think I can use the Book class in LyX to do everything they want,
but I can't find out how to change the height and width of the text
block. The text on the page must be exactly 4.5 x 7.5 from the top
of the running head to the bottom of the last text line (there are no
footers). Can anyone help? I could not find how to do it in the LyX
documentation and I am no LaTeX expert (that much should be clear).
Read the latex documentation about page layout, and set it up
accordingly. If you
go for some special class or add-on package, check if it provides its own
ways of specifying these sizes. Koma-script certainly does.
Helge Hafting
Re: Problem with \thanks in Author field
On Aug 16, 2004, at 12:47 AM, Nirmal Govind wrote:
Hi.. I'm trying to include the \thanks in the author field but get a
couple of errors related to extra brackets. Attached is a sample lyx
file. Please let me know what the best way to do this would be..
The attached file works for me. (Note the changed placement of the
\thanks{...} -- one after each author -- and the \and in ERT
between authors.)
Bennett
Re: Problem with \thanks in Author field
Nirmal == Nirmal Govind [EMAIL PROTECTED] writes: Nirmal Hi.. I'm trying to include the \thanks in the author field but Nirmal get a couple of errors related to extra brackets. Attached is Nirmal a sample lyx file. Please let me know what the best way to do Nirmal this would be.. Just use a footnote, it should do the right thing. JMarc
Re: Problem with \thanks in Author field
Works great! Thanks Bennett.
nirmal
The attached file works for me. (Note the changed placement of the
\thanks{...} -- one after each author -- and the \and in ERT between
authors.)
[Let's try again with the attachment!]
Bennett
Re: proposal for bug fix vis-a-vis index entries
Quoting Helge Hafting [EMAIL PROTECTED]: The ideal solution is an index entry that allow most of the stuff that works in the main text (except for sectioning and floats). In other words: * Escape special symbols the user just types in, as is done for the main text * Allow math editor in an index entry (My book on algorithm complexity have an index entry for $\Omega$, for example. A math paper might index lots of formulas. Chemistry uses _ a lot in formulas too. * Allow formatting like emphasize, bold and character styles inside an index entry, and translate to the mechanism makeindex uses for this. This would save a lot of latex currently used to get bold/emphasized index entries. * Allow ERT boxes inside index entries so experts still can do everything latex can do. In other words: Make the index entry inset a real text inset. Certainly feasible and gives you all the power you need. Andre'
Re: Problem with \thanks in Author field
On Aug 16, 2004, at 10:38 AM, Jean-Marc Lasgouttes wrote:
Nirmal == Nirmal Govind [EMAIL PROTECTED] writes:
Nirmal Hi.. I'm trying to include the \thanks in the author field but
Nirmal get a couple of errors related to extra brackets. Attached is
Nirmal a sample lyx file. Please let me know what the best way to do
Nirmal this would be..
Just use a footnote, it should do the right thing.
Just using a footnote doesn't work with the memoir class -- I've always
had to use \thanks{...} there, which works just fine. (Is this a LyX
bug? -- should I report it?)
Bennett
Problem with \thanks in Author field
Hi.. I'm trying to include the \thanks in the author field but get a
couple of errors related to extra brackets. Attached is a sample lyx
file. Please let me know what the best way to do this would be..
thanks,
nirmal
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass article
\language american
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Title
Test Title
\layout Author
Author1, Author2
\begin_inset ERT
status Collapsed
\layout Standard
%
\layout Standard
\backslash
thanks{Author1 details}%
\layout Standard
\backslash
thanks{Author2 details}
\end_inset
\layout Abstract
abstract..
\layout Section
Section1
\layout Standard
asdasd
\the_end
Re: woe with indexing
William F. Adams wrote: On Thursday, August 12, 2004, at 09:36 AM, stephan beal wrote: But if i delete it or rename it to, e.g., foo i get even MORE errors. As Herbert noted, special characters which have special meanings aren't changed by LyX when entered into an index field --- this probably qualifies as a bug, or at least should be mentioned in the manual. Not at all a bug, but mentioning the index rules in the manual is a very good idea. The reason we need ability to put all sorts of symbols into an index entry (without having lyx mangle it automatically so you get exactly what you typed into the index ) is that we sometimes need or want to put latex commands in the index entries. There are many reasons for that - special formatting of some words in the index is one. Of course the better approach here would be a lyx that auto-mangles index text so that underscores, other special symbols and formatting like emphasizing works for those who just types the stuff in. This is ok _if_ the enhanced index entry also can contain ERT boxes so the advanced users can keep their latex commands. Helge Hafting
Re: proposal for bug fix vis-a-vis index entries
stephan beal wrote: @lyx developers, i'd look at doing this fix myself, but i'm on a dialup line, paying for each minute online, and the lyx tarball is 5M+. For the Qt interface, it seems it would be trivial to fix the Index Item entry dialog to automatically escape any illegal characters, like _. Careful now. _Only_ autoescaping will render impossible all the stuff we do today with _ and | and \ and so on when writing index entries. (All the symbols that gave you grief is usable in indexes - they are very useful when used right! ) Of course autoescaping is ok _if_ some other way is provided for accessing the advandec functionality of makeindex. Note that _ and \ is equally troublesome/useful in the main tex - but it is autoescaped there, and the ERT box is available for those who need it. The ideal solution is an index entry that allow most of the stuff that works in the main text (except for sectioning and floats). In other words: * Escape special symbols the user just types in, as is done for the main text * Allow math editor in an index entry (My book on algorithm complexity have an index entry for $\Omega$, for example. A math paper might index lots of formulas. Chemistry uses _ a lot in formulas too. * Allow formatting like emphasize, bold and character styles inside an index entry, and translate to the mechanism makeindex uses for this. This would save a lot of latex currently used to get bold/emphasized index entries. * Allow ERT boxes inside index entries so experts still can do everything latex can do. * Perhaps let the index entry GUI have special support for some things, like: - the 'see' something else index entry - the mechanism for special formatting of the page number, by providing a separate field with the text pagenumber so the user can use the ordinary editing GUI to create bold/emphasized/colored numbers. - GUI mechanisms for specifying ranges so we get entries like entry:5,7,8-12,76-233,314 - GUI mechansim for dealing with cases when sort order and presentation is very different. This is important in many cases, for example when indexing math. (I put my $\Omega$ index both among symbols (correctly placed in relation to other greek stuff) as well as alphabetically where the word Omega would go. Doing _all_ of this is probably a lot of work. If you implement autoescaping, possibly by reusing autoescape code used for main text, then at least the ERT inside an index entry is necessary. Expert users can then kludge all the rest in ERT, similar to how they now kludge it in todays index entries. The rest can then come with time. The fact that the dialog allows one to enter invalid data has caused me NO END of grief. Adding a single underscore to one index entry causes errors in completely unrelated parts of the doc when exporting, and tracking down the problem is really difficult (as is shown by my frustrated posts on the topic), especially since Idx entries aren't visible until clicked on (maybe an Expand/View Index Entries option, like the one for Footnotes, is feasible?). The current system could use some warnings as well as a reference to litterature on makeindex syntax . . . IMO a dialog box should not allow you to enter data which is itself illegal for the program the dialog is serving, especially when it *silently* does so. Well, a _ is a perfectly legal character in an index entry, when used right. Example index entries that works fine: foo\_bar $C_2H_5OH$-(ethanol) I agree that the current way is not userfriendly, but don't _remove_ existing possibilities just to make your own case easier. Helge Hafting
Re: Changing text height and width?
Stefano Franchi wrote:
Hi all,
I am asked by a publisher to submit a book length manuscript in
camera-ready form and unfortunately they don't provide LaTeX classes.
In fact, they have given me Microsoft Word instructions :-(
Well, at least they let you use whatever you want, and don't re-type it
all in word or
something equally stupid before printing. (Wasted work, and latex
provides much better output too!)
Anything you want can be tweaked to exactly the right size, you may have to
learn _some_ latex in the process though. I wrote a book, with detail specs
on the text block size, paper size, and fonts to be used from the publisher.
I used the koma-script book class and adapted that. The latex documentation
for koma-script details how the page layout is specified with latex commands
in the preamble. Use that to get exactly the text block you want.
There wasn't
a specifier for the total text block size, so I specified one height for
the text part
of the text block which was the total height minus the height of the
running head.
Fortunately, latex lets you enter such arithmetic expressions so no need
to calculate
it to some number of decimals. (mixing points, inches and centimeters
is easy with latex. :-)
Examples from my preamble. I don't claim it is the best way, but it
worked fine:
\setlength{\paperwidth}{170mm}
\setlength{\paperheight}{240mm}
%text block
\areaset{121.5mm}{203mm}
%Margins. Compensate for tex silly 1in origo
\setlength{\oddsidemargin}{16mm-1in}
\setlength{\evensidemargin}{32.5mm-1in}
%Position the top of text
\setlength{\topmargin}{8.5mm-1in}
%publisher says: headsep+headheight+topmargin=22mm
%(I didn't set headheight anywhere, the default worked well)
\setlength{\headsep}{22mm-8.5mm-\headheight}
I think I can use the Book class in LyX to do everything they want,
but I can't find out how to change the height and width of the text
block. The text on the page must be exactly 4.5 x 7.5 from the top
of the running head to the bottom of the last text line (there are no
footers). Can anyone help? I could not find how to do it in the LyX
documentation and I am no LaTeX expert (that much should be clear).
Read the latex documentation about page layout, and set it up
accordingly. If you
go for some special class or add-on package, check if it provides its own
ways of specifying these sizes. Koma-script certainly does.
Helge Hafting
Re: Problem with \thanks in Author field
On Aug 16, 2004, at 12:47 AM, Nirmal Govind wrote:
Hi.. I'm trying to include the \thanks in the author field but get a
couple of errors related to extra brackets. Attached is a sample lyx
file. Please let me know what the best way to do this would be..
The attached file works for me. (Note the changed placement of the
\thanks{...} -- one after each author -- and the \and in ERT
between authors.)
Bennett
Re: Problem with \thanks in Author field
Nirmal == Nirmal Govind [EMAIL PROTECTED] writes: Nirmal Hi.. I'm trying to include the \thanks in the author field but Nirmal get a couple of errors related to extra brackets. Attached is Nirmal a sample lyx file. Please let me know what the best way to do Nirmal this would be.. Just use a footnote, it should do the right thing. JMarc
Re: Problem with \thanks in Author field
Works great! Thanks Bennett.
nirmal
The attached file works for me. (Note the changed placement of the
\thanks{...} -- one after each author -- and the \and in ERT between
authors.)
[Let's try again with the attachment!]
Bennett
Re: proposal for bug fix vis-a-vis index entries
Quoting Helge Hafting [EMAIL PROTECTED]: The ideal solution is an index entry that allow most of the stuff that works in the main text (except for sectioning and floats). In other words: * Escape special symbols the user just types in, as is done for the main text * Allow math editor in an index entry (My book on algorithm complexity have an index entry for $\Omega$, for example. A math paper might index lots of formulas. Chemistry uses _ a lot in formulas too. * Allow formatting like emphasize, bold and character styles inside an index entry, and translate to the mechanism makeindex uses for this. This would save a lot of latex currently used to get bold/emphasized index entries. * Allow ERT boxes inside index entries so experts still can do everything latex can do. In other words: Make the index entry inset a real text inset. Certainly feasible and gives you all the power you need. Andre'
Re: Problem with \thanks in Author field
On Aug 16, 2004, at 10:38 AM, Jean-Marc Lasgouttes wrote:
Nirmal == Nirmal Govind [EMAIL PROTECTED] writes:
Nirmal Hi.. I'm trying to include the \thanks in the author field but
Nirmal get a couple of errors related to extra brackets. Attached is
Nirmal a sample lyx file. Please let me know what the best way to do
Nirmal this would be..
Just use a footnote, it should do the right thing.
Just using a footnote doesn't work with the memoir class -- I've always
had to use \thanks{...} there, which works just fine. (Is this a LyX
bug? -- should I report it?)
Bennett
Problem with \thanks in Author field
Hi.. I'm trying to include the \thanks in the author field but get a
couple of errors related to extra brackets. Attached is a sample lyx
file. Please let me know what the best way to do this would be..
thanks,
nirmal
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass article
\language american
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Title
Test Title
\layout Author
Author1, Author2
\begin_inset ERT
status Collapsed
\layout Standard
%
\layout Standard
\backslash
thanks{Author1 details}%
\layout Standard
\backslash
thanks{Author2 details}
\end_inset
\layout Abstract
abstract..
\layout Section
Section1
\layout Standard
asdasd
\the_end
Re: woe with indexing
William F. Adams wrote: On Thursday, August 12, 2004, at 09:36 AM, stephan beal wrote: But if i delete it or rename it to, e.g., "foo" i get even MORE errors. As Herbert noted, special characters which have special meanings aren't changed by LyX when entered into an index field --- this probably qualifies as a bug, or at least should be mentioned in the manual. Not at all a bug, but mentioning the index rules in the manual is a very good idea. The reason we need ability to put all sorts of symbols into an index entry (without having lyx mangle it automatically so you get exactly what you typed into the index ) is that we sometimes need or want to put latex commands in the index entries. There are many reasons for that - special formatting of some words in the index is one. Of course the better approach here would be a lyx that auto-mangles index text so that underscores, other special symbols and formatting like emphasizing works for those who just types the stuff in. This is ok _if_ the enhanced index entry also can contain ERT boxes so the advanced users can keep their latex commands. Helge Hafting
Re: proposal for bug fix vis-a-vis index entries
stephan beal wrote: @lyx developers, i'd look at doing this fix myself, but i'm on a dialup line, paying for each minute online, and the lyx tarball is 5M+. For the Qt interface, it seems it would be trivial to fix the Index Item entry dialog to automatically escape any illegal characters, like "_". Careful now. _Only_ autoescaping will render impossible all the stuff we do today with _ and | and \ and so on when writing index entries. (All the symbols that gave you grief is usable in indexes - they are very useful when used right! ) Of course autoescaping is ok _if_ some other way is provided for accessing the advandec functionality of makeindex. Note that _ and \ is equally troublesome/useful in the main tex - but it is autoescaped there, and the ERT box is available for those who need it. The ideal solution is an index entry that allow most of the stuff that works in the main text (except for sectioning and floats). In other words: * Escape special symbols the user just types in, as is done for the main text * Allow math editor in an index entry (My book on algorithm complexity have an index entry for $\Omega$, for example. A math paper might index lots of formulas. Chemistry uses _ a lot in formulas too. * Allow formatting like emphasize, bold and "character styles" inside an index entry, and translate to the mechanism makeindex uses for this. This would save a lot of latex currently used to get bold/emphasized index entries. * Allow ERT boxes inside index entries so experts still can do everything latex can do. * Perhaps let the index entry GUI have special support for some things, like: - the "'see' something else" index entry - the mechanism for special formatting of the page number, by providing a separate field with the text "pagenumber" so the user can use the ordinary editing GUI to create bold/emphasized/colored numbers. - GUI mechanisms for specifying ranges so we get entries like entry:5,7,8-12,76-233,314 - GUI mechansim for dealing with cases when sort order and presentation is very different. This is important in many cases, for example when indexing math. (I put my $\Omega$ index both among symbols (correctly placed in relation to other greek stuff) as well as alphabetically where the word "Omega" would go. Doing _all_ of this is probably a lot of work. If you implement autoescaping, possibly by reusing autoescape code used for main text, then at least the ERT inside an index entry is necessary. Expert users can then kludge all the rest in ERT, similar to how they now kludge it in todays index entries. The rest can then come with time. The fact that the dialog allows one to enter invalid data has caused me NO END of grief. Adding a single underscore to one index entry causes errors in completely unrelated parts of the doc when exporting, and tracking down the problem is really difficult (as is shown by my frustrated posts on the topic), especially since Idx entries aren't visible until clicked on (maybe an Expand/View Index Entries option, like the one for Footnotes, is feasible?). The current system could use some warnings as well as a reference to litterature on makeindex syntax . . . IMO a dialog box should not allow you to enter data which is itself illegal for the program the dialog is serving, especially when it *silently* does so. Well, a _ is a perfectly legal character in an index entry, when used right. Example index entries that works fine: foo\_bar $C_2H_5OH$-(ethanol) I agree that the current way is not userfriendly, but don't _remove_ existing possibilities just to make your own case easier. Helge Hafting
Re: Changing text height and width?
Stefano Franchi wrote:
Hi all,
I am asked by a publisher to submit a book length manuscript in
camera-ready form and unfortunately they don't provide LaTeX classes.
In fact, they have given me Microsoft Word instructions :-(
Well, at least they let you use whatever you want, and don't re-type it
all in word or
something equally stupid before printing. (Wasted work, and latex
provides much better output too!)
Anything you want can be tweaked to exactly the right size, you may have to
learn _some_ latex in the process though. I wrote a book, with detail specs
on the text block size, paper size, and fonts to be used from the publisher.
I used the koma-script book class and adapted that. The latex documentation
for koma-script details how the page layout is specified with latex commands
in the preamble. Use that to get exactly the text block you want.
There wasn't
a specifier for the total text block size, so I specified one height for
the "text part"
of the text block which was the total height minus the height of the
running head.
Fortunately, latex lets you enter such arithmetic expressions so no need
to calculate
it to some number of decimals. (mixing points, inches and centimeters
is easy with latex. :-)
Examples from my preamble. I don't claim it is the best way, but it
worked fine:
\setlength{\paperwidth}{170mm}
\setlength{\paperheight}{240mm}
%text block
\areaset{121.5mm}{203mm}
%Margins. Compensate for tex silly 1in origo
\setlength{\oddsidemargin}{16mm-1in}
\setlength{\evensidemargin}{32.5mm-1in}
%Position the top of text
\setlength{\topmargin}{8.5mm-1in}
%publisher says: headsep+headheight+topmargin=22mm
%(I didn't set headheight anywhere, the default worked well)
\setlength{\headsep}{22mm-8.5mm-\headheight}
I think I can use the Book class in LyX to do everything they want,
but I can't find out how to change the height and width of the text
block. The text on the page must be exactly 4.5" x 7.5" from the top
of the running head to the bottom of the last text line (there are no
footers). Can anyone help? I could not find how to do it in the LyX
documentation and I am no LaTeX expert (that much should be clear).
Read the latex documentation about page layout, and set it up
accordingly. If you
go for some special class or add-on package, check if it provides its own
ways of specifying these sizes. Koma-script certainly does.
Helge Hafting
Re: Problem with \thanks in Author field
On Aug 16, 2004, at 12:47 AM, Nirmal Govind wrote:
Hi.. I'm trying to include the \thanks in the author field but get a
couple of errors related to extra brackets. Attached is a sample lyx
file. Please let me know what the best way to do this would be..
The attached file works for me. (Note the changed placement of the
"\thanks{...}" -- one after each author -- and the "\and" in ERT
between authors.)
Bennett
Re: Problem with \thanks in Author field
> "Nirmal" == Nirmal Govind <[EMAIL PROTECTED]> writes: Nirmal> Hi.. I'm trying to include the \thanks in the author field but Nirmal> get a couple of errors related to extra brackets. Attached is Nirmal> a sample lyx file. Please let me know what the best way to do Nirmal> this would be.. Just use a footnote, it should do the right thing. JMarc
Re: Problem with \thanks in Author field
Works great! Thanks Bennett.
nirmal
The attached file works for me. (Note the changed placement of the
"\thanks{...}" -- one after each author -- and the "\and" in ERT between
authors.)
[Let's try again with the attachment!]
Bennett
Re: proposal for bug fix vis-a-vis index entries
Quoting Helge Hafting <[EMAIL PROTECTED]>: > The ideal solution is an index entry that allow most of the stuff that works > in the main text (except for sectioning and floats). > In other words: > * Escape special symbols the user just types in, as is done for the main > text > * Allow math editor in an index entry (My book on algorithm complexity > have an index entry for $\Omega$, for example. A math paper might > index lots of formulas. Chemistry uses _ a lot in formulas too. > * Allow formatting like emphasize, bold and "character styles" inside an > index entry, > and translate to the mechanism makeindex uses for this. This would > save a lot > of latex currently used to get bold/emphasized index entries. > * Allow ERT boxes inside index entries so experts still can do > everything latex > can do. In other words: "Make the index entry inset a real text inset". Certainly feasible and gives you all the power you need. Andre'
Re: Problem with \thanks in Author field
On Aug 16, 2004, at 10:38 AM, Jean-Marc Lasgouttes wrote:
"Nirmal" == Nirmal Govind <[EMAIL PROTECTED]> writes:
Nirmal> Hi.. I'm trying to include the \thanks in the author field but
Nirmal> get a couple of errors related to extra brackets. Attached is
Nirmal> a sample lyx file. Please let me know what the best way to do
Nirmal> this would be..
Just use a footnote, it should do the right thing.
Just using a footnote doesn't work with the memoir class -- I've always
had to use "\thanks{...}" there, which works just fine. (Is this a LyX
bug? -- should I report it?)
Bennett
