Re: Building 1.3.2 on Debian Woody
I've ran into the following problem while trying to build Lyx 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 For the record: I've been told to include -ftemplate-depth-25 in CXXFLAGS and this seems to solve the problem. -- Philipp Lehman [EMAIL PROTECTED]
Re: Building 1.3.2 on Debian Woody
I've ran into the following problem while trying to build Lyx 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 For the record: I've been told to include -ftemplate-depth-25 in CXXFLAGS and this seems to solve the problem. -- Philipp Lehman [EMAIL PROTECTED]
Re: Building 1.3.2 on Debian Woody
> I've ran into the following problem while trying to build Lyx 1.3.2 > on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 For the record: I've been told to include -ftemplate-depth-25 in CXXFLAGS and this seems to solve the problem. -- Philipp Lehman <[EMAIL PROTECTED]>
Building 1.3.2 on Debian Woody
I've ran into the following problem while trying to build Lyx 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 (building the QT frontend): insetcommand.h:39: instantiated from here ../../boost/boost/shared_ptr.hpp:203: invalid use of undefined type `struct boost::detail::shared_ptr_traitsboost::signals:: detail::cached_return_valueboost::signals::detail::unusable ' ../../boost/boost/shared_ptr.hpp:52: forward declaration of `struct boost::detail::shared_ptr_traitsboost::signals::detail:: cached_return_valueboost::signals::detail::unusable ' ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptrboost::signals::detail::cached_return_valueboost: : signals::detail::unusable ::operator *(...)' must have an argument of class or enumerated type ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptrboost::signals::detail::cached_return_valueboost: : signals::detail::unusable ::operator *(...)' must take either one or two arguments make[3]: *** [insetbib.lo] Error 1 make[3]: Leaving directory `/tmp/lyx-1.3.2/src/insets' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/lyx-1.3.2/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/lyx-1.3.2/src' make: *** [all-recursive] Error 1 Any ideas? -- Philipp Lehman [EMAIL PROTECTED]
Re: Building 1.3.2 on Debian Woody
Nachricht von Matej Cepl am Freitag, 25. Juli 2003 10:23: On 2003-07-24, 17:38 GMT, Philipp Lehman wrote: I've ran into the following problem while trying to build Lyx 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 (building the QT frontend): deb http://dpt.tuxfamily.org/pub woody main or there is other (probably more active) repository of woody LyX mentioned somewhere in the archive of this list. Thanks for the pointer, Matej. Unfortunately this binary is linked against QT 2 while I'm using 3.1.1-mt, so I'd prefer an optimized built linked against this version. -- Philipp Lehman [EMAIL PROTECTED]
Building 1.3.2 on Debian Woody
I've ran into the following problem while trying to build Lyx 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 (building the QT frontend): insetcommand.h:39: instantiated from here ../../boost/boost/shared_ptr.hpp:203: invalid use of undefined type `struct boost::detail::shared_ptr_traitsboost::signals:: detail::cached_return_valueboost::signals::detail::unusable ' ../../boost/boost/shared_ptr.hpp:52: forward declaration of `struct boost::detail::shared_ptr_traitsboost::signals::detail:: cached_return_valueboost::signals::detail::unusable ' ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptrboost::signals::detail::cached_return_valueboost: : signals::detail::unusable ::operator *(...)' must have an argument of class or enumerated type ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptrboost::signals::detail::cached_return_valueboost: : signals::detail::unusable ::operator *(...)' must take either one or two arguments make[3]: *** [insetbib.lo] Error 1 make[3]: Leaving directory `/tmp/lyx-1.3.2/src/insets' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/lyx-1.3.2/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/lyx-1.3.2/src' make: *** [all-recursive] Error 1 Any ideas? -- Philipp Lehman [EMAIL PROTECTED]
Re: Building 1.3.2 on Debian Woody
Nachricht von Matej Cepl am Freitag, 25. Juli 2003 10:23: On 2003-07-24, 17:38 GMT, Philipp Lehman wrote: I've ran into the following problem while trying to build Lyx 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 (building the QT frontend): deb http://dpt.tuxfamily.org/pub woody main or there is other (probably more active) repository of woody LyX mentioned somewhere in the archive of this list. Thanks for the pointer, Matej. Unfortunately this binary is linked against QT 2 while I'm using 3.1.1-mt, so I'd prefer an optimized built linked against this version. -- Philipp Lehman [EMAIL PROTECTED]
Building 1.3.2 on Debian Woody
I've ran into the following problem while trying to build Lyx 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 (building the QT frontend): insetcommand.h:39: instantiated from here ../../boost/boost/shared_ptr.hpp:203: invalid use of undefined type `struct boost::detail::shared_ptr_traits >' ../../boost/boost/shared_ptr.hpp:52: forward declaration of `struct boost::detail::shared_ptr_traits >' ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptr<boost::signals::detail::cached_return_value >::operator *(...)' must have an argument of class or enumerated type ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptr<boost::signals::detail::cached_return_value >::operator *(...)' must take either one or two arguments make[3]: *** [insetbib.lo] Error 1 make[3]: Leaving directory `/tmp/lyx-1.3.2/src/insets' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/lyx-1.3.2/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/lyx-1.3.2/src' make: *** [all-recursive] Error 1 Any ideas? -- Philipp Lehman <[EMAIL PROTECTED]>
Re: Building 1.3.2 on Debian Woody
Nachricht von Matej Cepl am Freitag, 25. Juli 2003 10:23: > On 2003-07-24, 17:38 GMT, Philipp Lehman wrote: > > I've ran into the following problem while trying to build Lyx > > 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt > > 3.1.1 (building the QT frontend): > > deb http://dpt.tuxfamily.org/pub woody main > > or there is other (probably more active) repository of woody LyX > mentioned somewhere in the archive of this list. Thanks for the pointer, Matej. Unfortunately this binary is linked against QT 2 while I'm using 3.1.1-mt, so I'd prefer an optimized built linked against this version. -- Philipp Lehman <[EMAIL PROTECTED]>
Building 1.3.2 on Debian Woody
I've ran into the following problem while trying to build Lyx 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 (building the QT frontend): insetcommand.h:39: instantiated from here ../../boost/boost/shared_ptr.hpp:203: invalid use of undefined type `struct boost::detail::shared_ptr_traitsboost::signals:: detail::cached_return_valueboost::signals::detail::unusable ' ../../boost/boost/shared_ptr.hpp:52: forward declaration of `struct boost::detail::shared_ptr_traitsboost::signals::detail:: cached_return_valueboost::signals::detail::unusable ' ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptrboost::signals::detail::cached_return_valueboost:: signals::detail::unusable ::operator *(...)' must have an argument of class or enumerated type ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptrboost::signals::detail::cached_return_valueboost:: signals::detail::unusable ::operator *(...)' must take either one or two arguments make[3]: *** [insetbib.lo] Error 1 make[3]: Leaving directory `/tmp/lyx-1.3.2/src/insets' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/lyx-1.3.2/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/lyx-1.3.2/src' make: *** [all-recursive] Error 1 Any ideas? -- Philipp Lehman [EMAIL PROTECTED]
Building 1.3.2 on Debian Woody
I've ran into the following problem while trying to build Lyx 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 (building the QT frontend): insetcommand.h:39: instantiated from here ../../boost/boost/shared_ptr.hpp:203: invalid use of undefined type `struct boost::detail::shared_ptr_traitsboost::signals:: detail::cached_return_valueboost::signals::detail::unusable ' ../../boost/boost/shared_ptr.hpp:52: forward declaration of `struct boost::detail::shared_ptr_traitsboost::signals::detail:: cached_return_valueboost::signals::detail::unusable ' ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptrboost::signals::detail::cached_return_valueboost:: signals::detail::unusable ::operator *(...)' must have an argument of class or enumerated type ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptrboost::signals::detail::cached_return_valueboost:: signals::detail::unusable ::operator *(...)' must take either one or two arguments make[3]: *** [insetbib.lo] Error 1 make[3]: Leaving directory `/tmp/lyx-1.3.2/src/insets' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/lyx-1.3.2/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/lyx-1.3.2/src' make: *** [all-recursive] Error 1 Any ideas? -- Philipp Lehman [EMAIL PROTECTED]
Building 1.3.2 on Debian Woody
I've ran into the following problem while trying to build Lyx 1.3.2 on Debian Woody, using g++ 2.95.4, libstdc++ 2.10, and Qt 3.1.1 (building the QT frontend): insetcommand.h:39: instantiated from here ../../boost/boost/shared_ptr.hpp:203: invalid use of undefined type `struct boost::detail::shared_ptr_traits >' ../../boost/boost/shared_ptr.hpp:52: forward declaration of `struct boost::detail::shared_ptr_traits >' ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptr<boost::signals::detail::cached_return_value >::operator *(...)' must have an argument of class or enumerated type ../../boost/boost/shared_ptr.hpp:203: `boost::shared_ptr<boost::signals::detail::cached_return_value >::operator *(...)' must take either one or two arguments make[3]: *** [insetbib.lo] Error 1 make[3]: Leaving directory `/tmp/lyx-1.3.2/src/insets' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/lyx-1.3.2/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/lyx-1.3.2/src' make: *** [all-recursive] Error 1 Any ideas? -- Philipp Lehman <[EMAIL PROTECTED]>
Re: MS Word, Lyx, and my resume
On Wed, 26 Sep 2001, Sean LeBlanc [EMAIL PROTECTED] wrote: I'm a complete newbie to lyx. I've heard good things about it, and I'm growing increasingly frustrated with MS Word, esp. when trying to manipulate my resume. [...] I was thinking of doing this: 1. Converting from MS Word to Lyx. It looks like there is at least one project (wv toolkit) that will let me do this. Technically, this is possible and wv might be a good choice for the job, but in this case it doesn't make a lot of sense. Converters mostly try to mimick the layout of the Word document using rather basic Latex constructs. The Latex code you end up with this way is a mess. That might be acceptable if you need to convert something quickly, but it's not the way to go for a text you maintain over the years. The first thing I'd do is find a specialized Latex class for CVs that fits your needs and produces a layout that looks the way you want it. Then I'd simply rewrite the resume manually to take advantage of all possibilities of Latex and the class you chose. After all you do that only once. You could use both plain Latex or Lyx, but you need additional Lyx support files for your Latex class. They might be around or you might need to write your own. It's quite simple, actually. 2. Make the changes I want in Lyx, save, and then... 3. Well, I'm not sure what to do here. Most HR staff don't understand what I do as a living, much less understand anything beyond the realm of M$ Office. I've even heard of HR people having trouble opening an HTML resume a friend of mine sent them. I still would like to try exporting to XML/HTML, if possible, but it would still really be great to be able to kick out the ol' Word format for the people who cling to it. Is this at all possible? What about filters for other formats like PDF? Since Lyx is merely a Latex frontend (a very sophisticated one, but still a frontend), everything that can be done in terms of conversion and output formats with a Latex file can be done with a Lyx file. Which one you choose is mostly a question of convenience. As to Latex, the two primary output formats of Latex are DVI and PDF (yes, there is native PDF output using pdflatex). DVI can be further processed to produce Postscript which in turn can be converted to PDF. There are also latex2html and latex2rtf which convert Latex to HTML or RTF respectively. The fundamental problem with HTML is that its ability to represent a given layout is very restricted. That's just not the point of HTML. Therefore HTML files generated from Latex source tend to look somewhat disappointing even if the converter does a good job. If HTML is going to be your primary target format, you'd be better of writing HTML. I hardly ever used latex2rtf, but I guess if you need Word or RTF output most of the time, it will probably be most effecient to use Word or StarOffice. Switching to Latex will be an effort for you, and if you don't really use Latex's genuin advantages it could very well become a frustrating experience. My impression is that HR folks expect something that can be printed on paper and looks good when printed. That's why I'd never send HTML files, even though they would work for everyone nowadays. Maybe I'm not on track at all here. What do most of you people do to maintain your resume? Are you using Lyx? Or is it not a good fit at all? I'm maintaining my CV in Latex and generate PDF output with pdflatex. PDF has the advantage of preserving the layout 100%, so you can be sure the HR folks get what you want them to get. You don't have to worry about fonts which are a problem with Word and RTF formats. My experience is that most people know what to do with a PDF file, but YMMV. -- Philipp Lehman [EMAIL PROTECTED]
Re: Special Characters
On Thu, 27 Sep 2001, Rich Shepard [EMAIL PROTECTED] wrote: I cannot find reference to being able to insert special characters (other than an elipses and a few others). Specifically, I want the copyright (circled c), registered (circled R), trademark and service mark symbols. I'm sure these are readily available, but I need a pointer to which doc (and section) tells me how to add them to a document. Actually they're not that readily available. There a two related approaches to that: 1) Use the Latex commands provided by the textcomp package, this means inserting commands like \textregistered or \copyright and marking them as Latex code under Lyx. Look for l2short.pdf on CTAN, it comes with an appendix that lists all symbols provided by textcomp. 2) Use textcomp in conjunction with inputenc, run a suitable 8-bit locale and configure your keyboard so that you can enter them directly, more or less like any alphabetic character (that's actually not as complicated as it may sound). This won't give you straight access to all symbols, but it would at least cover the most common ones. I'm assuming that you are running Lyx on some UNIX variant here, I don't know how to deal with that under Windows. -- Philipp Lehman [EMAIL PROTECTED]
Re: Special Characters
On Thu, 27 Sep 2001, Ronald Florence [EMAIL PROTECTED] wrote: Philipp Lehman writes: Actually they're not that readily available. Really? The only times I've tried to use PC wordprocessors, special and foreign characters required clicking on menues or copying characters from a clipboard. With LyX, those characters are as simple as typing compose c 0 for © or compose r 0 for ®. [These sequences are automatically configured on Solaris-Sparc keyboards and probably readily available with other Unixes or Linux, depending on the X-server implementation in use.] Well, I was simply referring to the fact that Lyx doesn't offer any menus entries for inserting all availble special characters. You're right that keyboard mapping is very flexible under UNIX, but even if you're running your system in UTF-8 mode, Latex is still 8bit down to the bone, so the glyphs you can enter straight or with compose key bindings are still limited to stuff like ©®¤¢æÆ. I'll admit that I never tried Omega, though. -- Philipp Lehman [EMAIL PROTECTED]
Re: MS Word, Lyx, and my resume
On Wed, 26 Sep 2001, Sean LeBlanc [EMAIL PROTECTED] wrote: I'm a complete newbie to lyx. I've heard good things about it, and I'm growing increasingly frustrated with MS Word, esp. when trying to manipulate my resume. [...] I was thinking of doing this: 1. Converting from MS Word to Lyx. It looks like there is at least one project (wv toolkit) that will let me do this. Technically, this is possible and wv might be a good choice for the job, but in this case it doesn't make a lot of sense. Converters mostly try to mimick the layout of the Word document using rather basic Latex constructs. The Latex code you end up with this way is a mess. That might be acceptable if you need to convert something quickly, but it's not the way to go for a text you maintain over the years. The first thing I'd do is find a specialized Latex class for CVs that fits your needs and produces a layout that looks the way you want it. Then I'd simply rewrite the resume manually to take advantage of all possibilities of Latex and the class you chose. After all you do that only once. You could use both plain Latex or Lyx, but you need additional Lyx support files for your Latex class. They might be around or you might need to write your own. It's quite simple, actually. 2. Make the changes I want in Lyx, save, and then... 3. Well, I'm not sure what to do here. Most HR staff don't understand what I do as a living, much less understand anything beyond the realm of M$ Office. I've even heard of HR people having trouble opening an HTML resume a friend of mine sent them. I still would like to try exporting to XML/HTML, if possible, but it would still really be great to be able to kick out the ol' Word format for the people who cling to it. Is this at all possible? What about filters for other formats like PDF? Since Lyx is merely a Latex frontend (a very sophisticated one, but still a frontend), everything that can be done in terms of conversion and output formats with a Latex file can be done with a Lyx file. Which one you choose is mostly a question of convenience. As to Latex, the two primary output formats of Latex are DVI and PDF (yes, there is native PDF output using pdflatex). DVI can be further processed to produce Postscript which in turn can be converted to PDF. There are also latex2html and latex2rtf which convert Latex to HTML or RTF respectively. The fundamental problem with HTML is that its ability to represent a given layout is very restricted. That's just not the point of HTML. Therefore HTML files generated from Latex source tend to look somewhat disappointing even if the converter does a good job. If HTML is going to be your primary target format, you'd be better of writing HTML. I hardly ever used latex2rtf, but I guess if you need Word or RTF output most of the time, it will probably be most effecient to use Word or StarOffice. Switching to Latex will be an effort for you, and if you don't really use Latex's genuin advantages it could very well become a frustrating experience. My impression is that HR folks expect something that can be printed on paper and looks good when printed. That's why I'd never send HTML files, even though they would work for everyone nowadays. Maybe I'm not on track at all here. What do most of you people do to maintain your resume? Are you using Lyx? Or is it not a good fit at all? I'm maintaining my CV in Latex and generate PDF output with pdflatex. PDF has the advantage of preserving the layout 100%, so you can be sure the HR folks get what you want them to get. You don't have to worry about fonts which are a problem with Word and RTF formats. My experience is that most people know what to do with a PDF file, but YMMV. -- Philipp Lehman [EMAIL PROTECTED]
Re: Special Characters
On Thu, 27 Sep 2001, Rich Shepard [EMAIL PROTECTED] wrote: I cannot find reference to being able to insert special characters (other than an elipses and a few others). Specifically, I want the copyright (circled c), registered (circled R), trademark and service mark symbols. I'm sure these are readily available, but I need a pointer to which doc (and section) tells me how to add them to a document. Actually they're not that readily available. There a two related approaches to that: 1) Use the Latex commands provided by the textcomp package, this means inserting commands like \textregistered or \copyright and marking them as Latex code under Lyx. Look for l2short.pdf on CTAN, it comes with an appendix that lists all symbols provided by textcomp. 2) Use textcomp in conjunction with inputenc, run a suitable 8-bit locale and configure your keyboard so that you can enter them directly, more or less like any alphabetic character (that's actually not as complicated as it may sound). This won't give you straight access to all symbols, but it would at least cover the most common ones. I'm assuming that you are running Lyx on some UNIX variant here, I don't know how to deal with that under Windows. -- Philipp Lehman [EMAIL PROTECTED]
Re: Special Characters
On Thu, 27 Sep 2001, Ronald Florence [EMAIL PROTECTED] wrote: Philipp Lehman writes: Actually they're not that readily available. Really? The only times I've tried to use PC wordprocessors, special and foreign characters required clicking on menues or copying characters from a clipboard. With LyX, those characters are as simple as typing compose c 0 for © or compose r 0 for ®. [These sequences are automatically configured on Solaris-Sparc keyboards and probably readily available with other Unixes or Linux, depending on the X-server implementation in use.] Well, I was simply referring to the fact that Lyx doesn't offer any menus entries for inserting all availble special characters. You're right that keyboard mapping is very flexible under UNIX, but even if you're running your system in UTF-8 mode, Latex is still 8bit down to the bone, so the glyphs you can enter straight or with compose key bindings are still limited to stuff like ©®¤¢æÆ. I'll admit that I never tried Omega, though. -- Philipp Lehman [EMAIL PROTECTED]
Re: MS Word, Lyx, and my resume
On Wed, 26 Sep 2001, Sean LeBlanc <[EMAIL PROTECTED]> wrote: >I'm a complete newbie to lyx. I've heard good things about >it, and I'm growing increasingly frustrated with MS Word, >esp. when trying to manipulate my resume. > [...] > >I was thinking of doing this: > >1. Converting from MS Word to Lyx. It looks like there is >at least one project (wv toolkit) that will let me do this. Technically, this is possible and wv might be a good choice for the job, but in this case it doesn't make a lot of sense. Converters mostly try to mimick the layout of the Word document using rather basic Latex constructs. The Latex code you end up with this way is a mess. That might be acceptable if you need to convert something quickly, but it's not the way to go for a text you maintain over the years. The first thing I'd do is find a specialized Latex class for CVs that fits your needs and produces a layout that looks the way you want it. Then I'd simply rewrite the resume manually to take advantage of all possibilities of Latex and the class you chose. After all you do that only once. You could use both plain Latex or Lyx, but you need additional Lyx support files for your Latex class. They might be around or you might need to write your own. It's quite simple, actually. >2. Make the changes I want in Lyx, save, and then... > >3. Well, I'm not sure what to do here. Most HR staff don't >understand what I do as a living, much less understand >anything beyond the realm of M$ Office. I've even heard of >HR people having trouble opening an HTML resume a friend of >mine sent them. I still would like to try exporting to XML/HTML, >if possible, but it would still really be great to be able >to kick out the ol' Word format for the people who cling to >it. Is this at all possible? What about filters for other >formats like PDF? Since Lyx is merely a Latex frontend (a very sophisticated one, but still a frontend), everything that can be done in terms of conversion and output formats with a Latex file can be done with a Lyx file. Which one you choose is mostly a question of convenience. As to Latex, the two primary output formats of Latex are DVI and PDF (yes, there is native PDF output using pdflatex). DVI can be further processed to produce Postscript which in turn can be converted to PDF. There are also latex2html and latex2rtf which convert Latex to HTML or RTF respectively. The fundamental problem with HTML is that its ability to represent a given layout is very restricted. That's just not the point of HTML. Therefore HTML files generated from Latex source tend to look somewhat disappointing even if the converter does a good job. If HTML is going to be your primary target format, you'd be better of writing HTML. I hardly ever used latex2rtf, but I guess if you need Word or RTF output most of the time, it will probably be most effecient to use Word or StarOffice. Switching to Latex will be an effort for you, and if you don't really use Latex's genuin advantages it could very well become a frustrating experience. My impression is that HR folks expect something that can be printed on paper and looks good when printed. That's why I'd never send HTML files, even though they would work for everyone nowadays. >Maybe I'm not on track at all here. What do most of you >people do to maintain your resume? Are you using Lyx? Or >is it not a good fit at all? I'm maintaining my CV in Latex and generate PDF output with pdflatex. PDF has the advantage of preserving the layout 100%, so you can be sure the HR folks get what you want them to get. You don't have to worry about fonts which are a problem with Word and RTF formats. My experience is that most people know what to do with a PDF file, but YMMV. -- Philipp Lehman <[EMAIL PROTECTED]>
Re: Special Characters
On Thu, 27 Sep 2001, Rich Shepard <[EMAIL PROTECTED]> wrote: > I cannot find reference to being able to insert special characters (other >than an elipses and a few others). Specifically, I want the copyright >(circled c), registered (circled R), trademark and service mark symbols. I'm >sure these are readily available, but I need a pointer to which doc (and >section) tells me how to add them to a document. Actually they're not that readily available. There a two related approaches to that: 1) Use the Latex commands provided by the textcomp package, this means inserting commands like \textregistered or \copyright and marking them as Latex code under Lyx. Look for l2short.pdf on CTAN, it comes with an appendix that lists all symbols provided by textcomp. 2) Use textcomp in conjunction with inputenc, run a suitable 8-bit locale and configure your keyboard so that you can enter them directly, more or less like any alphabetic character (that's actually not as complicated as it may sound). This won't give you straight access to all symbols, but it would at least cover the most common ones. I'm assuming that you are running Lyx on some UNIX variant here, I don't know how to deal with that under Windows. -- Philipp Lehman <[EMAIL PROTECTED]>
Re: Special Characters
On Thu, 27 Sep 2001, Ronald Florence <[EMAIL PROTECTED]> wrote: >Philipp Lehman writes: >>Actually they're not that readily available. > >Really? The only times I've tried to use PC wordprocessors, special >and foreign characters required clicking on menues or copying >characters from a clipboard. With LyX, those characters are as simple >as typing c 0 for © or r 0 for ®. [These >sequences are automatically configured on Solaris-Sparc keyboards and >probably readily available with other Unixes or Linux, depending on >the X-server implementation in use.] Well, I was simply referring to the fact that Lyx doesn't offer any menus entries for inserting all availble special characters. You're right that keyboard mapping is very flexible under UNIX, but even if you're running your system in UTF-8 mode, Latex is still 8bit down to the bone, so the glyphs you can enter straight or with compose key bindings are still limited to stuff like ©®¤¢æÆ. I'll admit that I never tried Omega, though. -- Philipp Lehman <[EMAIL PROTECTED]>
spell checker problems
After switching from Lyx 1.1.5fix2 to 1.1.6fix3 I can't get the ispell to work any more. Lyx displays the error message I'm sorry I can't find any suitable word lists for the language-tag german. The same happens when setting the ispell language to deutsch or using the document language (that latter results in a message about the language-tag de). Of course, ispell works when I run it from the command line. Any ideas? This is Lyx 1.1.6fix3 compiled with pspell support. -- Philipp Lehman [EMAIL PROTECTED]
spell checker problems
After switching from Lyx 1.1.5fix2 to 1.1.6fix3 I can't get the ispell to work any more. Lyx displays the error message I'm sorry I can't find any suitable word lists for the language-tag german. The same happens when setting the ispell language to deutsch or using the document language (that latter results in a message about the language-tag de). Of course, ispell works when I run it from the command line. Any ideas? This is Lyx 1.1.6fix3 compiled with pspell support. -- Philipp Lehman [EMAIL PROTECTED]
spell checker problems
After switching from Lyx 1.1.5fix2 to 1.1.6fix3 I can't get the ispell to work any more. Lyx displays the error message "I'm sorry I can't find any suitable word lists for the language-tag "german". The same happens when setting the ispell language to "deutsch" or using the document language (that latter results in a message about the language-tag "de"). Of course, ispell works when I run it from the command line. Any ideas? This is Lyx 1.1.6fix3 compiled with pspell support. -- Philipp Lehman <[EMAIL PROTECTED]>
Real iso8859-15 input?
I'm in the process of moving my Linux boxes from iso8859-1 to
iso8859-15. Next stop: Lyx. The story so far: I used to work with
'faked' iso8859-15 support under Lyx, e.g. I would map the currency
sign like this
keycode 26 = e E currency
with xmodmap, set Lyx's screen fonts to *-iso8859-15 and add
\usepackage[latin9]{inputenc} to the preamble to get the euro sign on
screen and on paper. A hack, but it worked.
Now I would like to get proper support under X, so I mapped the
key like this:
keycode 26 = e E EuroSign
But alas, this doesn't work for Lyx, neither for 1.1.5fix2 (which I'm
using by default) nor for 1.1.6fix3. I've set the encoding to
iso8859-15, the fonts are available and I see all characters specific
to iso8859-15 in my old Lyx files. Keyboard mapping is turned off;
since I set this on the X level and want Lyx to use the input straight
without any remapping.
With Lyx 1.1.5fix2 keyboard input just doesn't work for those six new
characters in iso8859-15, with 1.1.6fix3 it works only partly, e.g. oe
and OE work while the euro sign does not.
Is this a know issue or am I missing something?
--
Philipp Lehman [EMAIL PROTECTED]
Real iso8859-15 input?
I'm in the process of moving my Linux boxes from iso8859-1 to
iso8859-15. Next stop: Lyx. The story so far: I used to work with
'faked' iso8859-15 support under Lyx, e.g. I would map the currency
sign like this
keycode 26 = e E currency
with xmodmap, set Lyx's screen fonts to *-iso8859-15 and add
\usepackage[latin9]{inputenc} to the preamble to get the euro sign on
screen and on paper. A hack, but it worked.
Now I would like to get proper support under X, so I mapped the
key like this:
keycode 26 = e E EuroSign
But alas, this doesn't work for Lyx, neither for 1.1.5fix2 (which I'm
using by default) nor for 1.1.6fix3. I've set the encoding to
iso8859-15, the fonts are available and I see all characters specific
to iso8859-15 in my old Lyx files. Keyboard mapping is turned off;
since I set this on the X level and want Lyx to use the input straight
without any remapping.
With Lyx 1.1.5fix2 keyboard input just doesn't work for those six new
characters in iso8859-15, with 1.1.6fix3 it works only partly, e.g. oe
and OE work while the euro sign does not.
Is this a know issue or am I missing something?
--
Philipp Lehman [EMAIL PROTECTED]
Real iso8859-15 input?
I'm in the process of moving my Linux boxes from iso8859-1 to
iso8859-15. Next stop: Lyx. The story so far: I used to work with
'faked' iso8859-15 support under Lyx, e.g. I would map the currency
sign like this
keycode 26 = e E currency
with xmodmap, set Lyx's screen fonts to *-iso8859-15 and add
\usepackage[latin9]{inputenc} to the preamble to get the euro sign on
screen and on paper. A hack, but it worked.
Now I would like to get proper support under X, so I mapped the
key like this:
keycode 26 = e E EuroSign
But alas, this doesn't work for Lyx, neither for 1.1.5fix2 (which I'm
using by default) nor for 1.1.6fix3. I've set the encoding to
iso8859-15, the fonts are available and I see all characters specific
to iso8859-15 in my old Lyx files. Keyboard mapping is turned off;
since I set this on the X level and want Lyx to use the input straight
without any remapping.
With Lyx 1.1.5fix2 keyboard input just doesn't work for those six new
characters in iso8859-15, with 1.1.6fix3 it works only partly, e.g. oe
and OE work while the euro sign does not.
Is this a know issue or am I missing something?
--
Philipp Lehman <[EMAIL PROTECTED]>
Re: lyx 1.1.6 and polish chars
On Thu, 5 Jul 2001, Bronek Baraniecki [EMAIL PROTECTED] wrote: To write polish charakters in Lyx, you have to use xmodmap or gkb_xmmap pl (or else setxkbmap pl) in GNOME. In KDE envirement I cannot obtain a plish chars in Lyx. Err... I'm not familiar with writing polish, but if you can get there with xmodmap, it should work regardless of wether you're running GNOME or KDE. If KDE overrides your mapping (I don't know if it does, but it is possible, of course) I'm pretty sure there's a way to deactivate this feature. -- Philipp Lehman [EMAIL PROTECTED]
Re: lyx 1.1.6 and polish chars
On Thu, 5 Jul 2001, Bronek Baraniecki [EMAIL PROTECTED] wrote: To write polish charakters in Lyx, you have to use xmodmap or gkb_xmmap pl (or else setxkbmap pl) in GNOME. In KDE envirement I cannot obtain a plish chars in Lyx. Err... I'm not familiar with writing polish, but if you can get there with xmodmap, it should work regardless of wether you're running GNOME or KDE. If KDE overrides your mapping (I don't know if it does, but it is possible, of course) I'm pretty sure there's a way to deactivate this feature. -- Philipp Lehman [EMAIL PROTECTED]
Re: lyx 1.1.6 and polish chars
On Thu, 5 Jul 2001, Bronek Baraniecki <[EMAIL PROTECTED]> wrote: >To write polish charakters in Lyx, you have to use xmodmap or "gkb_xmmap >pl" (or else "setxkbmap pl") in GNOME. In KDE envirement I cannot obtain >a plish chars in Lyx. Err... I'm not familiar with writing polish, but if you can get there with xmodmap, it should work regardless of wether you're running GNOME or KDE. If KDE overrides your mapping (I don't know if it does, but it is possible, of course) I'm pretty sure there's a way to deactivate this "feature". -- Philipp Lehman <[EMAIL PROTECTED]>
Re: Can I change the command for View dvi?
On Fri, 6 Jul 2001, Michael Blaesse [EMAIL PROTECTED] wrote: sorry if this is a FAQ, but I couldn't find the answer. Can I somehow include scripts or some commands in the process of viewing the dvi output? I just asked a similar question. Quote: Philipp PRE-/POSTPROCESSOR COMMANDS Philipp I'm running ligatex as a preprocessor for fine-tuning Philipp ligatures when using CM or expert PS fonts. With Lyx, I Philipp presently have to export to a Tex file as a final step, Philipp manually run ligatex, and then manually run Latex. A better solution is to use the new converter code to define a .lig format which is ligatured tex and add the converters .tex - .lig: ligatex .lig - .dvi: latex As far as I know, it should be enough to get it working. Philipp It might also be worthwhile to consider supporting a Philipp postprocessor that is launched after (pdf)latex/bibtex but Philipp before any dvi/pdf viewer (one word: thumbpdf). Same answer. -- Philipp Lehman [EMAIL PROTECTED]
RE: Feedback from a Humble End User(TM)
On Fri, 6 Jul 2001, Juergen Vigna [EMAIL PROTECTED] wrote:
MULTILINGUAL SPELLCHECKING
This is planed for the future.
Ahh! ('nuff said)
PRE-/POSTPROCESSOR COMMANDS
Woulndn't it work to make a shell-skript which calls first ligatex and then
latex like:
#!/bin/sh
#
ligatex $#
latex $#
And define this new command as latex command in the configuration files?
Yes of course, this would work. But I'll look into the solution
mentioned by JMarc, sounds like what I'm after is already in 1.1.6.
--
Philipp Lehman [EMAIL PROTECTED]
Re: Can I change the command for View dvi?
On Fri, 6 Jul 2001, Michael Blaesse [EMAIL PROTECTED] wrote: sorry if this is a FAQ, but I couldn't find the answer. Can I somehow include scripts or some commands in the process of viewing the dvi output? I just asked a similar question. Quote: Philipp PRE-/POSTPROCESSOR COMMANDS Philipp I'm running ligatex as a preprocessor for fine-tuning Philipp ligatures when using CM or expert PS fonts. With Lyx, I Philipp presently have to export to a Tex file as a final step, Philipp manually run ligatex, and then manually run Latex. A better solution is to use the new converter code to define a .lig format which is ligatured tex and add the converters .tex - .lig: ligatex .lig - .dvi: latex As far as I know, it should be enough to get it working. Philipp It might also be worthwhile to consider supporting a Philipp postprocessor that is launched after (pdf)latex/bibtex but Philipp before any dvi/pdf viewer (one word: thumbpdf). Same answer. -- Philipp Lehman [EMAIL PROTECTED]
RE: Feedback from a Humble End User(TM)
On Fri, 6 Jul 2001, Juergen Vigna [EMAIL PROTECTED] wrote:
MULTILINGUAL SPELLCHECKING
This is planed for the future.
Ahh! ('nuff said)
PRE-/POSTPROCESSOR COMMANDS
Woulndn't it work to make a shell-skript which calls first ligatex and then
latex like:
#!/bin/sh
#
ligatex $#
latex $#
And define this new command as latex command in the configuration files?
Yes of course, this would work. But I'll look into the solution
mentioned by JMarc, sounds like what I'm after is already in 1.1.6.
--
Philipp Lehman [EMAIL PROTECTED]
Re: Can I change the command for "View dvi"?
On Fri, 6 Jul 2001, Michael Blaesse <[EMAIL PROTECTED]> wrote: >sorry if this is a FAQ, but I couldn't find the answer. > >Can I somehow include scripts or some commands in the process of viewing >the dvi output? I just asked a similar question. Quote: Philipp> PRE-/POSTPROCESSOR COMMANDS Philipp> I'm running ligatex as a preprocessor for fine-tuning Philipp> ligatures when using CM or expert PS fonts. With Lyx, I Philipp> presently have to export to a Tex file as a final step, Philipp> manually run ligatex, and then manually run Latex. A better solution is to use the new converter code to define a .lig format which is ligatured tex and add the converters .tex -> .lig: ligatex .lig -> .dvi: latex As far as I know, it should be enough to get it working. Philipp> It might also be worthwhile to consider supporting a Philipp> postprocessor that is launched after (pdf)latex/bibtex but Philipp> before any dvi/pdf viewer (one word: thumbpdf). Same answer. -- Philipp Lehman <[EMAIL PROTECTED]>
RE: Feedback from a Humble End User(TM)
On Fri, 6 Jul 2001, Juergen Vigna <[EMAIL PROTECTED]> wrote:
>> MULTILINGUAL SPELLCHECKING
>
>This is planed for the future.
Ahh! ('nuff said)
>> PRE-/POSTPROCESSOR COMMANDS
>
>Woulndn't it work to make a shell-skript which calls first ligatex and then
>latex like:
>
>#!/bin/sh
>#
>ligatex $#
>latex $#
>
>And define this new command as latex command in the configuration files?
Yes of course, this would work. But I'll look into the solution
mentioned by JMarc, sounds like what I'm after is already in 1.1.6.
--
Philipp Lehman <[EMAIL PROTECTED]>
Feedback from a Humble End User(TM)
I hope you don't mind seeing user feedback on lyx-devel, but I don't
know to what extend posts on lyx-user are seen by developers. So, here
we go:
After finshing a thesis written with Lyx, I feel the urge to give some
feedback and offer some ideas based on my experiences with using Lyx
for a project like this. I used 1.1.4fix3 but I checked 1.1.6fix2 to
avoid making any obsolete suggestions (I hope I didn't miss anything).
MULTILINGUAL SPELLCHECKING
I'm in the humanities and I often deal with multilingual texts (e.g.
core text in German with quotes in English and French). This basically
makes spell checking under Lyx impossible (you keep hitting ignore
word to skip the quotes until your fingers bleed).
I noticed that 1.1.6 now supports defining the language of a single
paragraph or phrase. Unfortunately, this only adds \selectlanguage
(which of course is a feature) but doesn't seem to deal with the
spellchecker. Restarting ispell/aspell with the appropriate options
whenever there is a language change would be a major usability
improvement.
PRE-/POSTPROCESSOR COMMANDS
I'm running ligatex as a preprocessor for fine-tuning ligatures when
using CM or expert PS fonts. With Lyx, I presently have to export to a
Tex file as a final step, manually run ligatex, and then manually run
Latex.
I'd appreciate it if there was an option telling Lyx to run a generic
preprocessor before running Latex. That would be ligatex in this case,
but considering the dynamic nature of Tex I'm sure there are a lot of
situations in which some kind of preprocessor would come in handy.
It might also be worthwhile to consider supporting a postprocessor
that is launched after (pdf)latex/bibtex but before any dvi/pdf
viewer (one word: thumbpdf).
NATBIB/BIBTEX
Natbib, as you know, supports a variety of \cite commands. I'm not
only talking about stuff like \citep or \citealt but also things like
\citetalias. I have been missing an option allowing me to pick a
specific \cite command for _each_ citation. The idea is to set a
default command on a per-file basis while being able to override this
(with an occasional \citetalias for example) on a per-citation basis.
The list of \cite commands available would be user defineable in some
configuration file using tokens that are replaced by Lyx when writing
the citation to the Tex file. Consider the following bibcmds.map:
# %b = text before
# %a = text after
# %k = bibtex key
#
# Command Requires
#
\citet[%b][%a]{%k} natbib.sty
\citeauthor{%k} natbib.sty
\citepalias{%k} natbib.sty
This way, the feature wouldn't be restricted to a specific package
like natbib. As far as novice users not familiar with Latex are
concerned, you would just provide the commands suitable for a typical
scenario (which are hard-coded otherwise) as defaults in bibcmds.map.
FONT SELECTION
Having _a lot_ of T1/TT fonts which are available to Latex, I would
really like to pick more of them from the document pop-up instead of
using Latex commands in the preamble. What I've been missing for a
long time is a simple map file allowing me to configure which fonts
show up under the fonts drop down box.
Actually, it might be smarter to have three drop-downs in the document
pop-up so you can set the default serif, sans serif, and typewriter
font independently and support something like a texfonts.map file to
define the list of available fonts:
# Visible Name Latex Name Default Family
# Encoding
#
CM Roman OsF (ecofonts) cmorT1 serif
CM Sans Serif (aefonts) aessT1 sans
CM Typewriter (zefonts) zettT1 typewriter
ITC Officina Sans po9 T1 sans
Adobe Times ptm T1 serif
URW Nimbus Roman No. 9utm T1 serif
BT Courier 10 Pitch bcr T1 typewriter
Adobe Garamondpad T1 serif
Adobe Garamond ExppadxT1 serif
Adobe Garamond Exp OsFpadjT1 serif
I hope you find some of these suggenstions interesting or even worth
implementing. Keep up the great work!
BTW: Will the QT2 GUI support anti-aliased fonts in the text area?
This would take my Lyx experience to a new level ;)
--
Philipp Lehman [EMAIL PROTECTED]
Feedback from a Humble End User(TM)
I hope you don't mind seeing user feedback on lyx-devel, but I don't
know to what extend posts on lyx-user are seen by developers. So, here
we go:
After finshing a thesis written with Lyx, I feel the urge to give some
feedback and offer some ideas based on my experiences with using Lyx
for a project like this. I used 1.1.4fix3 but I checked 1.1.6fix2 to
avoid making any obsolete suggestions (I hope I didn't miss anything).
MULTILINGUAL SPELLCHECKING
I'm in the humanities and I often deal with multilingual texts (e.g.
core text in German with quotes in English and French). This basically
makes spell checking under Lyx impossible (you keep hitting ignore
word to skip the quotes until your fingers bleed).
I noticed that 1.1.6 now supports defining the language of a single
paragraph or phrase. Unfortunately, this only adds \selectlanguage
(which of course is a feature) but doesn't seem to deal with the
spellchecker. Restarting ispell/aspell with the appropriate options
whenever there is a language change would be a major usability
improvement.
PRE-/POSTPROCESSOR COMMANDS
I'm running ligatex as a preprocessor for fine-tuning ligatures when
using CM or expert PS fonts. With Lyx, I presently have to export to a
Tex file as a final step, manually run ligatex, and then manually run
Latex.
I'd appreciate it if there was an option telling Lyx to run a generic
preprocessor before running Latex. That would be ligatex in this case,
but considering the dynamic nature of Tex I'm sure there are a lot of
situations in which some kind of preprocessor would come in handy.
It might also be worthwhile to consider supporting a postprocessor
that is launched after (pdf)latex/bibtex but before any dvi/pdf
viewer (one word: thumbpdf).
NATBIB/BIBTEX
Natbib, as you know, supports a variety of \cite commands. I'm not
only talking about stuff like \citep or \citealt but also things like
\citetalias. I have been missing an option allowing me to pick a
specific \cite command for _each_ citation. The idea is to set a
default command on a per-file basis while being able to override this
(with an occasional \citetalias for example) on a per-citation basis.
The list of \cite commands available would be user defineable in some
configuration file using tokens that are replaced by Lyx when writing
the citation to the Tex file. Consider the following bibcmds.map:
# %b = text before
# %a = text after
# %k = bibtex key
#
# Command Requires
#
\citet[%b][%a]{%k} natbib.sty
\citeauthor{%k} natbib.sty
\citepalias{%k} natbib.sty
This way, the feature wouldn't be restricted to a specific package
like natbib. As far as novice users not familiar with Latex are
concerned, you would just provide the commands suitable for a typical
scenario (which are hard-coded otherwise) as defaults in bibcmds.map.
FONT SELECTION
Having _a lot_ of T1/TT fonts which are available to Latex, I would
really like to pick more of them from the document pop-up instead of
using Latex commands in the preamble. What I've been missing for a
long time is a simple map file allowing me to configure which fonts
show up under the fonts drop down box.
Actually, it might be smarter to have three drop-downs in the document
pop-up so you can set the default serif, sans serif, and typewriter
font independently and support something like a texfonts.map file to
define the list of available fonts:
# Visible Name Latex Name Default Family
# Encoding
#
CM Roman OsF (ecofonts) cmorT1 serif
CM Sans Serif (aefonts) aessT1 sans
CM Typewriter (zefonts) zettT1 typewriter
ITC Officina Sans po9 T1 sans
Adobe Times ptm T1 serif
URW Nimbus Roman No. 9utm T1 serif
BT Courier 10 Pitch bcr T1 typewriter
Adobe Garamondpad T1 serif
Adobe Garamond ExppadxT1 serif
Adobe Garamond Exp OsFpadjT1 serif
I hope you find some of these suggenstions interesting or even worth
implementing. Keep up the great work!
BTW: Will the QT2 GUI support anti-aliased fonts in the text area?
This would take my Lyx experience to a new level ;)
--
Philipp Lehman [EMAIL PROTECTED]
Feedback from a Humble End User(TM)
I hope you don't mind seeing user feedback on lyx-devel, but I don't
know to what extend posts on lyx-user are seen by developers. So, here
we go:
After finshing a thesis written with Lyx, I feel the urge to give some
feedback and offer some ideas based on my experiences with using Lyx
for a project like this. I used 1.1.4fix3 but I checked 1.1.6fix2 to
avoid making any obsolete suggestions (I hope I didn't miss anything).
MULTILINGUAL SPELLCHECKING
I'm in the humanities and I often deal with multilingual texts (e.g.
core text in German with quotes in English and French). This basically
makes spell checking under Lyx impossible (you keep hitting "ignore
word" to skip the quotes until your fingers bleed).
I noticed that 1.1.6 now supports defining the language of a single
paragraph or phrase. Unfortunately, this only adds "\selectlanguage"
(which of course is a feature) but doesn't seem to deal with the
spellchecker. Restarting ispell/aspell with the appropriate options
whenever there is a language change would be a major usability
improvement.
PRE-/POSTPROCESSOR COMMANDS
I'm running ligatex as a preprocessor for fine-tuning ligatures when
using CM or expert PS fonts. With Lyx, I presently have to export to a
Tex file as a final step, manually run ligatex, and then manually run
Latex.
I'd appreciate it if there was an option telling Lyx to run a generic
preprocessor before running Latex. That would be ligatex in this case,
but considering the dynamic nature of Tex I'm sure there are a lot of
situations in which some kind of preprocessor would come in handy.
It might also be worthwhile to consider supporting a postprocessor
that is launched after (pdf)latex/bibtex but before any dvi/pdf
viewer (one word: thumbpdf).
NATBIB/BIBTEX
Natbib, as you know, supports a variety of \cite commands. I'm not
only talking about stuff like \citep or \citealt but also things like
\citetalias. I have been missing an option allowing me to pick a
specific \cite command for _each_ citation. The idea is to set a
default command on a per-file basis while being able to override this
(with an occasional \citetalias for example) on a per-citation basis.
The list of \cite commands available would be user defineable in some
configuration file using tokens that are replaced by Lyx when writing
the citation to the Tex file. Consider the following bibcmds.map:
# %b = text before
# %a = text after
# %k = bibtex key
#
# Command Requires
#
\citet[%b][%a]{%k} natbib.sty
\citeauthor{%k} natbib.sty
\citepalias{%k} natbib.sty
This way, the feature wouldn't be restricted to a specific package
like natbib. As far as novice users not familiar with Latex are
concerned, you would just provide the commands suitable for a typical
scenario (which are hard-coded otherwise) as defaults in bibcmds.map.
FONT SELECTION
Having _a lot_ of T1/TT fonts which are available to Latex, I would
really like to pick more of them from the document pop-up instead of
using Latex commands in the preamble. What I've been missing for a
long time is a simple map file allowing me to configure which fonts
show up under the "fonts" drop down box.
Actually, it might be smarter to have three drop-downs in the document
pop-up so you can set the default serif, sans serif, and typewriter
font independently and support something like a texfonts.map file to
define the list of available fonts:
# Visible Name Latex Name Default Family
# Encoding
#
"CM Roman OsF (ecofonts)" cmorT1 serif
"CM Sans Serif (aefonts)" aessT1 sans
"CM Typewriter (zefonts)" zettT1 typewriter
"ITC Officina Sans" po9 T1 sans
"Adobe Times" ptm T1 serif
"URW Nimbus Roman No. 9"utm T1 serif
"BT Courier 10 Pitch" bcr T1 typewriter
"Adobe Garamond"pad T1 serif
"Adobe Garamond Exp"padxT1 serif
"Adobe Garamond Exp OsF"padjT1 serif
I hope you find some of these suggenstions interesting or even worth
implementing. Keep up the great work!
BTW: Will the QT2 GUI support anti-aliased fonts in the text area?
This would take my "Lyx experience" to a new level ;)
--
Philipp Lehman <[EMAIL PROTECTED]>
Re: Overword package
On Wed, 15 Nov 2000, Matej Cepl [EMAIL PROTECTED] wrote: trying to get up camel package, but it needs overword package, which should be but it is not available on CTAN (there is a broken link in CTAN Catalogue). Is this the one? ftp://ftp.dante.de/tex-archive/macros/latex/contrib/supported/calendar/overword.dtx -- Philipp Lehman [EMAIL PROTECTED]
Re: Overword package
On Wed, 15 Nov 2000, Matej Cepl [EMAIL PROTECTED] wrote: trying to get up camel package, but it needs overword package, which should be but it is not available on CTAN (there is a broken link in CTAN Catalogue). Is this the one? ftp://ftp.dante.de/tex-archive/macros/latex/contrib/supported/calendar/overword.dtx -- Philipp Lehman [EMAIL PROTECTED]
Re: Overword package
On Wed, 15 Nov 2000, Matej Cepl <[EMAIL PROTECTED]> wrote: >trying to get up camel package, but it needs overword package, >which should be but it is not available on CTAN (there is a >broken link in CTAN Catalogue). Is this the one? ftp://ftp.dante.de/tex-archive/macros/latex/contrib/supported/calendar/overword.dtx -- Philipp Lehman <[EMAIL PROTECTED]>
Re: Space in indexes between numbers and titles
On Tue, 7 Nov 2000, Emanuele Gissi Alessia Franceschi [EMAIL PROTECTED] wrote:
I have got a little problem: at the end of my document both chapter numbers and
figure numbers have 2 digits, as in chapter 15 figure 37. In the "List of
figures" the figure captions almost overlap their numbers (example 15.37).
You could use the tocloft package to fix this.
I just put \usepackage{tocloft} in the preamble.
Well, you need to do a little bit more than just that. Try
experimenting with something like:
\setlength{\cftfignumwidth}{insert some width here}
I'm writing this from memory so please double check. In any case,
look for the file tocloft.dvi on your harddrive or on any CTAN
mirror. This package is well documented.
No, it does not seem to work in my case or I am
not able to make it working. I use the book (koma-script) class...
As I said, \usepackage{tocloft} just loads the package, but you
still have to tell it what to do. HTH
--
Philipp Lehman [EMAIL PROTECTED]
Re: Space in indexes between numbers and titles
On Tue, 7 Nov 2000, Emanuele Gissi Alessia Franceschi [EMAIL PROTECTED] wrote:
I have got a little problem: at the end of my document both chapter numbers and
figure numbers have 2 digits, as in chapter 15 figure 37. In the "List of
figures" the figure captions almost overlap their numbers (example 15.37).
You could use the tocloft package to fix this.
I just put \usepackage{tocloft} in the preamble.
Well, you need to do a little bit more than just that. Try
experimenting with something like:
\setlength{\cftfignumwidth}{insert some width here}
I'm writing this from memory so please double check. In any case,
look for the file tocloft.dvi on your harddrive or on any CTAN
mirror. This package is well documented.
No, it does not seem to work in my case or I am
not able to make it working. I use the book (koma-script) class...
As I said, \usepackage{tocloft} just loads the package, but you
still have to tell it what to do. HTH
--
Philipp Lehman [EMAIL PROTECTED]
Re: Space in indexes between numbers and titles
On Tue, 7 Nov 2000, Emanuele Gissi & Alessia Franceschi <[EMAIL PROTECTED]> wrote:
>> >I have got a little problem: at the end of my document both chapter numbers and
>> >figure numbers have 2 digits, as in chapter 15 figure 37. In the "List of
>> >figures" the figure captions almost overlap their numbers (example 15.37).
>
>> You could use the tocloft package to fix this.
>
>I just put \usepackage{tocloft} in the preamble.
Well, you need to do a little bit more than just that. Try
experimenting with something like:
\setlength{\cftfignumwidth}{}
I'm writing this from memory so please double check. In any case,
look for the file tocloft.dvi on your harddrive or on any CTAN
mirror. This package is well documented.
>No, it does not seem to work in my case or I am
>not able to make it working. I use the book (koma-script) class...
As I said, \usepackage{tocloft} just loads the package, but you
still have to tell it what to do. HTH
--
Philipp Lehman <[EMAIL PROTECTED]>
Re: Space in indexes between numbers and titles
On Sun, 5 Nov 2000, Emanuele Gissi Alessia Franceschi [EMAIL PROTECTED] wrote: I have got a little problem: at the end of my document both chapter numbers and figure numbers have 2 digits, as in chapter 15 figure 37. In the "List of figures" the figure captions almost overlap their numbers (example 15.37). You could use the tocloft package to fix this. -- Philipp Lehman [EMAIL PROTECTED]
Re: Space in indexes between numbers and titles
On Sun, 5 Nov 2000, Emanuele Gissi Alessia Franceschi [EMAIL PROTECTED] wrote: I have got a little problem: at the end of my document both chapter numbers and figure numbers have 2 digits, as in chapter 15 figure 37. In the "List of figures" the figure captions almost overlap their numbers (example 15.37). You could use the tocloft package to fix this. -- Philipp Lehman [EMAIL PROTECTED]
Re: Space in indexes between numbers and titles
On Sun, 5 Nov 2000, Emanuele Gissi & Alessia Franceschi <[EMAIL PROTECTED]> wrote: >I have got a little problem: at the end of my document both chapter numbers and >figure numbers have 2 digits, as in chapter 15 figure 37. In the "List of >figures" the figure captions almost overlap their numbers (example 15.37). You could use the tocloft package to fix this. -- Philipp Lehman <[EMAIL PROTECTED]>
Re: Foiltex class
On Sun, 5 Nov 2000, Thomas Adamek [EMAIL PROTECTED] wrote: Hello, my name is Thomas and I'm new in this list and also to lyx. I just made my first steps. Now I want to make some foils. I read, that I can use the slides class for it (what I tried with success) or the foiltex class. This class I couldn't find on my "linux/debian/potato"-system. So I tried to download it but I only find an archive foiltex that contains the files foiltex.dtx and foiltex.ins. What have I to do with these files ? Simply feed them both to latex. Running latex on the .dtx file will produce the documentation (as a .dvi), runnning it on the .ins file will extract the actual code. There is a README file with more detailed instructions. -- Philipp Lehman [EMAIL PROTECTED]
OT: TrueType font installer for teTeX
Recently, I had to build a tetex system from scratch on a new machine and wanted to install some truetype fonts too. Since this is a rather laborious thing to do, I threw several little scripts and tools together to create a script that will install truetype fonts in one shot. I've put it up on: http://lehman.virtualave.net/files/ttf2tex.tar.gz It's just a humble bash script so don't expect anything fancy, but it can save you some trouble. It also installs the fonts in a lyx friendly manner. See he documentation for details. Feel free to mail me your questions, comments, improvements. -- Philipp Lehman [EMAIL PROTECTED]
Re: Foiltex class
On Sun, 5 Nov 2000, Thomas Adamek [EMAIL PROTECTED] wrote: Hello, my name is Thomas and I'm new in this list and also to lyx. I just made my first steps. Now I want to make some foils. I read, that I can use the slides class for it (what I tried with success) or the foiltex class. This class I couldn't find on my "linux/debian/potato"-system. So I tried to download it but I only find an archive foiltex that contains the files foiltex.dtx and foiltex.ins. What have I to do with these files ? Simply feed them both to latex. Running latex on the .dtx file will produce the documentation (as a .dvi), runnning it on the .ins file will extract the actual code. There is a README file with more detailed instructions. -- Philipp Lehman [EMAIL PROTECTED]
OT: TrueType font installer for teTeX
Recently, I had to build a tetex system from scratch on a new machine and wanted to install some truetype fonts too. Since this is a rather laborious thing to do, I threw several little scripts and tools together to create a script that will install truetype fonts in one shot. I've put it up on: http://lehman.virtualave.net/files/ttf2tex.tar.gz It's just a humble bash script so don't expect anything fancy, but it can save you some trouble. It also installs the fonts in a lyx friendly manner. See he documentation for details. Feel free to mail me your questions, comments, improvements. -- Philipp Lehman [EMAIL PROTECTED]
Re: Foiltex class
On Sun, 5 Nov 2000, Thomas Adamek <[EMAIL PROTECTED]> wrote: >Hello, > >my name is Thomas and I'm new in this list and also to lyx. > >I just made my first steps. Now I want to make some foils. I read, >that I can use the slides class for it (what I tried with success) or >the foiltex class. This class I couldn't find on my "linux/debian/potato"-system. So >I tried to download it but I only find an archive foiltex that contains the files >foiltex.dtx and foiltex.ins. > >What have I to do with these files ? Simply feed them both to latex. Running latex on the .dtx file will produce the documentation (as a .dvi), runnning it on the .ins file will extract the actual code. There is a README file with more detailed instructions. -- Philipp Lehman <[EMAIL PROTECTED]>
OT: TrueType font installer for teTeX
Recently, I had to build a tetex system from scratch on a new machine and wanted to install some truetype fonts too. Since this is a rather laborious thing to do, I threw several little scripts and tools together to create a script that will install truetype fonts in one shot. I've put it up on: http://lehman.virtualave.net/files/ttf2tex.tar.gz It's just a humble bash script so don't expect anything fancy, but it can save you some trouble. It also installs the fonts in a lyx friendly manner. See he documentation for details. Feel free to mail me your questions, comments, improvements. -- Philipp Lehman <[EMAIL PROTECTED]>
Re: problems with .eps-files
On Thu, 26 Oct 2000, Wolfgang Engelmann [EMAIL PROTECTED]: However, I am having problems with the bounding box. Some of the figures overlay the horizontal line of my (fancy style) header or sometimes even the text in the header. How can I trim the figure to avoid it? IIRC gs adjust the bbox when you convert eps - eps. Try gs -dBATCH -sDEVICE=epswrite -sOutputFile=new.eps old.eps *Problem 2* When I view my book.ps under ghostview, it stops displaying the pages before the end. View it in gs (running from a terminal) and take a look at the output. gs filename.ps -- Philipp Lehman [EMAIL PROTECTED]
Re: problems with .eps-files
On Thu, 26 Oct 2000, Wolfgang Engelmann [EMAIL PROTECTED]: However, I am having problems with the bounding box. Some of the figures overlay the horizontal line of my (fancy style) header or sometimes even the text in the header. How can I trim the figure to avoid it? IIRC gs adjust the bbox when you convert eps - eps. Try gs -dBATCH -sDEVICE=epswrite -sOutputFile=new.eps old.eps *Problem 2* When I view my book.ps under ghostview, it stops displaying the pages before the end. View it in gs (running from a terminal) and take a look at the output. gs filename.ps -- Philipp Lehman [EMAIL PROTECTED]
Re: problems with .eps-files
On Thu, 26 Oct 2000, Wolfgang Engelmann <[EMAIL PROTECTED]: >However, I am having problems with the bounding box. Some of the >figures overlay the horizontal line of my (fancy style) header or >sometimes even the text in the header. How can I trim the figure >to avoid it? IIRC gs adjust the bbox when you convert eps -> eps. Try gs -dBATCH -sDEVICE=epswrite -sOutputFile=new.eps old.eps >*Problem 2* When I view my book.ps under ghostview, it stops >displaying the pages before the end. View it in gs (running from a terminal) and take a look at the output. gs filename.ps -- Philipp Lehman <[EMAIL PROTECTED]>
Re: Contract package for LyX
On Thu, 26 Oct 2000, Matej Cepl [EMAIL PROTECTED] wrote: -- filename of the document (either .lyx one or .ps) Or Latex? Try "\jobname". -- some formatting of date (I would love to have something like 25.10.2000, 22:35 -- which is today; oh, well, it was yesterday :-). There are several packages for time and date formating. Head over to http://www.ctan.org/search/ and try a keyword search. -- Philipp Lehman [EMAIL PROTECTED]
Re: Contract package for LyX
On Thu, 26 Oct 2000, Matej Cepl <[EMAIL PROTECTED]> wrote: >-- filename of the document (either .lyx one or .ps) Or Latex? Try "\jobname". >-- some formatting of date (I would love to have something like > 25.10.2000, 22:35 -- which is today; oh, well, it was > yesterday :-). There are several packages for time and date formating. Head over to http://www.ctan.org/search/ and try a keyword search. -- Philipp Lehman <[EMAIL PROTECTED]>
Re: online fonts look bad on notebook
On Tue, 24 Oct 2000, Torsten Mueller [EMAIL PROTECTED] wrote: I use LyX with Linux (Suse 6.1) on a Toshiba notebook pc with resolution 1024x768. The program itself works well, but the fonts do not look very well on the screen. I have tried to play with options-screenfonts, but I am not able to get a much better result. When I use LyX on our Solaris system, the fonts look much better. Does anybody know, what I could do about that? Are you using the same fonts in both cases? What kind of fonts are you using (Bitmap, Type1, TrueType)? Is the problem LyX specific? -- Philipp Lehman [EMAIL PROTECTED]
Re: online fonts look bad on notebook
On Tue, 24 Oct 2000, Torsten Mueller [EMAIL PROTECTED] wrote: I use LyX with Linux (Suse 6.1) on a Toshiba notebook pc with resolution 1024x768. The program itself works well, but the fonts do not look very well on the screen. I have tried to play with options-screenfonts, but I am not able to get a much better result. When I use LyX on our Solaris system, the fonts look much better. Does anybody know, what I could do about that? Are you using the same fonts in both cases? What kind of fonts are you using (Bitmap, Type1, TrueType)? Is the problem LyX specific? -- Philipp Lehman [EMAIL PROTECTED]
Re: online fonts look bad on notebook
On Tue, 24 Oct 2000, Torsten Mueller <[EMAIL PROTECTED]> wrote: >I use LyX with Linux (Suse 6.1) on a Toshiba notebook pc with >resolution 1024x768. >The program itself works well, but the fonts do not look very >well on the screen. >I have tried to play with options->screenfonts, but I am not able >to get a much better result. > >When I use LyX on our Solaris system, the fonts look much better. >Does anybody know, what I could do about that? Are you using the same fonts in both cases? What kind of fonts are you using (Bitmap, Type1, TrueType)? Is the problem LyX specific? -- Philipp Lehman <[EMAIL PROTECTED]>
Re: bold courier/typewriter troubles
On Mon, 23 Oct 2000, Tuukka Toivonen [EMAIL PROTECTED] wrote: On the other hand, if LaTeX knows about bold typewriter, then it's an obvious bug in LyX. -- Philipp Lehman [EMAIL PROTECTED]
Re: bold courier/typewriter troubles
[Sorry for the previous bogus post, it went off by accident]
On Mon, 23 Oct 2000, Tuukka Toivonen [EMAIL PROTECTED] wrote:
To flood the list, I'll mention a weird thing I noticed even if it's not a
problem for me, at least not right now.
Type a line of text. Set it to Typewriter font.
Type another line of text. Set it to Bold Typewriter font.
On screen they do look different, but on xdvi/ghostview they look same.
Now, if there actually doesn't exist such a font as Bold Typewriter in
LaTeX, LyX shouldn't display two different fonts on the display either.
On the other hand, if LaTeX knows about bold typewriter, then it's an
obvious bug in LyX.
Neither LyX nor LaTeX 'know' about 'bold typewriter' by default.
The first thing LaTeX knows about is a font definition file for a
given font. Let me give you an example:
If you choose "Times" from the LyX font selection box, it will
simply put "\usepackage{times}" in the preamble. On my system,
the times.sty files contains the following lines:
\renewcommand{\rmdefault}{ptm}
\renewcommand{\sfdefault}{phv}
\renewcommand{\ttdefault}{pcr}
This will switch to Adobe Times as default roman font, Adobe
Helvetica as default sans serif and Adobe Courier as default
typewriter font. If you use the typewriter font in your document
and, say, T1 encoding, LaTeX will look for the file t1pcr.fd. The
latter contains lines like:
\DeclareFontFamily{T1}{pcr}{}
\DeclareFontShape{T1}{pcr}{m}{n}{- pcrr8t}{}
\DeclareFontShape{T1}{pcr}{m}{sc}{- pcrrc8t}{}
\DeclareFontShape{T1}{pcr}{m}{sl}{- pcrro8t}{}
\DeclareFontShape{T1}{pcr}{m}{it}{-ssub * pcr/m/sl}{}
\DeclareFontShape{T1}{pcr}{b}{n}{- pcrb8t}{}
\DeclareFontShape{T1}{pcr}{b}{sc}{- pcrbc8t}{}
\DeclareFontShape{T1}{pcr}{b}{sl}{- pcrbo8t}{}
\DeclareFontShape{T1}{pcr}{b}{it}{-ssub * pcr/b/sl}{}
This maps font shapes to TeX font metric files (*.tfm), for
example Adobe Courier medium normal to pcrr8t.tfm and Adobe
Courier bold normal to pcrb8t.tfm. LaTeX will use the metrics
given in those file to do the typesetting. In a wy, this is the
first step in the typesetting process that will create a link
between what you requested in your document and what is actually
available on your system in terms of resources, like fonts for
example. LyX can't know about that in advance. Keep in mind that
it's a front end, not a typesetting engine.
LyX, on the other hand, will simply use the fonts defined in its
config file and query the X server. Since these are usually
different from the fonts used for typesetting, you can't predict
the output by the contents of you LyX window. This is what the
developers like to call WYSIWYM and what a lot of users consider
a feature, because you can choose a font for the printed output
which looks good on paper (or in a PDF file) and have a display
font which you can stare on for eight hours without having your
head explode.
If you're missing a bold version of a given font and need that,
you should either switch to a different, complete font are
consider substitutions on the level of the font definition
file. This is what fontinst, the font installer for Type1 fonts
that ships with LaTeX does by default. In the above example, this
happens here:
\DeclareFontShape{T1}{pcr}{m}{it}{-ssub * pcr/m/sl}{}
This will tell LaTeX to use Courier normal slanted as a
substitute for Courier normal italic (since typewriter fonts
don't ship with italics but oblique versions for emphasis). On
this level, you can substitute anything for anything. If your
typewriter font doesn't provide a bold version, you could
substitute the bold version of an entirely different font if you
feel like.
Hope this clarifies the situation a little bit.
--
Philipp Lehman [EMAIL PROTECTED]
Re: bold courier/typewriter troubles
On Mon, 23 Oct 2000, Tuukka Toivonen [EMAIL PROTECTED] wrote: On the other hand, if LaTeX knows about bold typewriter, then it's an obvious bug in LyX. -- Philipp Lehman [EMAIL PROTECTED]
Re: bold courier/typewriter troubles
[Sorry for the previous bogus post, it went off by accident]
On Mon, 23 Oct 2000, Tuukka Toivonen [EMAIL PROTECTED] wrote:
To flood the list, I'll mention a weird thing I noticed even if it's not a
problem for me, at least not right now.
Type a line of text. Set it to Typewriter font.
Type another line of text. Set it to Bold Typewriter font.
On screen they do look different, but on xdvi/ghostview they look same.
Now, if there actually doesn't exist such a font as Bold Typewriter in
LaTeX, LyX shouldn't display two different fonts on the display either.
On the other hand, if LaTeX knows about bold typewriter, then it's an
obvious bug in LyX.
Neither LyX nor LaTeX 'know' about 'bold typewriter' by default.
The first thing LaTeX knows about is a font definition file for a
given font. Let me give you an example:
If you choose "Times" from the LyX font selection box, it will
simply put "\usepackage{times}" in the preamble. On my system,
the times.sty files contains the following lines:
\renewcommand{\rmdefault}{ptm}
\renewcommand{\sfdefault}{phv}
\renewcommand{\ttdefault}{pcr}
This will switch to Adobe Times as default roman font, Adobe
Helvetica as default sans serif and Adobe Courier as default
typewriter font. If you use the typewriter font in your document
and, say, T1 encoding, LaTeX will look for the file t1pcr.fd. The
latter contains lines like:
\DeclareFontFamily{T1}{pcr}{}
\DeclareFontShape{T1}{pcr}{m}{n}{- pcrr8t}{}
\DeclareFontShape{T1}{pcr}{m}{sc}{- pcrrc8t}{}
\DeclareFontShape{T1}{pcr}{m}{sl}{- pcrro8t}{}
\DeclareFontShape{T1}{pcr}{m}{it}{-ssub * pcr/m/sl}{}
\DeclareFontShape{T1}{pcr}{b}{n}{- pcrb8t}{}
\DeclareFontShape{T1}{pcr}{b}{sc}{- pcrbc8t}{}
\DeclareFontShape{T1}{pcr}{b}{sl}{- pcrbo8t}{}
\DeclareFontShape{T1}{pcr}{b}{it}{-ssub * pcr/b/sl}{}
This maps font shapes to TeX font metric files (*.tfm), for
example Adobe Courier medium normal to pcrr8t.tfm and Adobe
Courier bold normal to pcrb8t.tfm. LaTeX will use the metrics
given in those file to do the typesetting. In a wy, this is the
first step in the typesetting process that will create a link
between what you requested in your document and what is actually
available on your system in terms of resources, like fonts for
example. LyX can't know about that in advance. Keep in mind that
it's a front end, not a typesetting engine.
LyX, on the other hand, will simply use the fonts defined in its
config file and query the X server. Since these are usually
different from the fonts used for typesetting, you can't predict
the output by the contents of you LyX window. This is what the
developers like to call WYSIWYM and what a lot of users consider
a feature, because you can choose a font for the printed output
which looks good on paper (or in a PDF file) and have a display
font which you can stare on for eight hours without having your
head explode.
If you're missing a bold version of a given font and need that,
you should either switch to a different, complete font are
consider substitutions on the level of the font definition
file. This is what fontinst, the font installer for Type1 fonts
that ships with LaTeX does by default. In the above example, this
happens here:
\DeclareFontShape{T1}{pcr}{m}{it}{-ssub * pcr/m/sl}{}
This will tell LaTeX to use Courier normal slanted as a
substitute for Courier normal italic (since typewriter fonts
don't ship with italics but oblique versions for emphasis). On
this level, you can substitute anything for anything. If your
typewriter font doesn't provide a bold version, you could
substitute the bold version of an entirely different font if you
feel like.
Hope this clarifies the situation a little bit.
--
Philipp Lehman [EMAIL PROTECTED]
Re: bold courier/typewriter troubles
On Mon, 23 Oct 2000, Tuukka Toivonen <[EMAIL PROTECTED]> wrote: > >On the other hand, if LaTeX knows about bold typewriter, then it's an >obvious bug in LyX. > > > -- Philipp Lehman <[EMAIL PROTECTED]>
Re: bold courier/typewriter troubles
[Sorry for the previous bogus post, it went off by accident]
On Mon, 23 Oct 2000, Tuukka Toivonen <[EMAIL PROTECTED]> wrote:
>To flood the list, I'll mention a weird thing I noticed even if it's not a
>problem for me, at least not right now.
>
>Type a line of text. Set it to Typewriter font.
>Type another line of text. Set it to Bold Typewriter font.
>
>On screen they do look different, but on xdvi/ghostview they look same.
>Now, if there actually doesn't exist such a font as Bold Typewriter in
>LaTeX, LyX shouldn't display two different fonts on the display either.
>
>On the other hand, if LaTeX knows about bold typewriter, then it's an
>obvious bug in LyX.
Neither LyX nor LaTeX 'know' about 'bold typewriter' by default.
The first thing LaTeX knows about is a font definition file for a
given font. Let me give you an example:
If you choose "Times" from the LyX font selection box, it will
simply put "\usepackage{times}" in the preamble. On my system,
the times.sty files contains the following lines:
\renewcommand{\rmdefault}{ptm}
\renewcommand{\sfdefault}{phv}
\renewcommand{\ttdefault}{pcr}
This will switch to Adobe Times as default roman font, Adobe
Helvetica as default sans serif and Adobe Courier as default
typewriter font. If you use the typewriter font in your document
and, say, T1 encoding, LaTeX will look for the file t1pcr.fd. The
latter contains lines like:
\DeclareFontFamily{T1}{pcr}{}
\DeclareFontShape{T1}{pcr}{m}{n}{<-> pcrr8t}{}
\DeclareFontShape{T1}{pcr}{m}{sc}{<-> pcrrc8t}{}
\DeclareFontShape{T1}{pcr}{m}{sl}{<-> pcrro8t}{}
\DeclareFontShape{T1}{pcr}{m}{it}{<->ssub * pcr/m/sl}{}
\DeclareFontShape{T1}{pcr}{b}{n}{<-> pcrb8t}{}
\DeclareFontShape{T1}{pcr}{b}{sc}{<-> pcrbc8t}{}
\DeclareFontShape{T1}{pcr}{b}{sl}{<-> pcrbo8t}{}
\DeclareFontShape{T1}{pcr}{b}{it}{<->ssub * pcr/b/sl}{}
This maps font shapes to TeX font metric files (*.tfm), for
example Adobe Courier medium normal to pcrr8t.tfm and Adobe
Courier bold normal to pcrb8t.tfm. LaTeX will use the metrics
given in those file to do the typesetting. In a wy, this is the
first step in the typesetting process that will create a link
between what you requested in your document and what is actually
available on your system in terms of resources, like fonts for
example. LyX can't know about that in advance. Keep in mind that
it's a front end, not a typesetting engine.
LyX, on the other hand, will simply use the fonts defined in its
config file and query the X server. Since these are usually
different from the fonts used for typesetting, you can't predict
the output by the contents of you LyX window. This is what the
developers like to call WYSIWYM and what a lot of users consider
a feature, because you can choose a font for the printed output
which looks good on paper (or in a PDF file) and have a display
font which you can stare on for eight hours without having your
head explode.
If you're missing a bold version of a given font and need that,
you should either switch to a different, complete font are
consider substitutions on the level of the font definition
file. This is what fontinst, the font installer for Type1 fonts
that ships with LaTeX does by default. In the above example, this
happens here:
\DeclareFontShape{T1}{pcr}{m}{it}{<->ssub * pcr/m/sl}{}
This will tell LaTeX to use Courier normal slanted as a
substitute for Courier normal italic (since typewriter fonts
don't ship with italics but oblique versions for emphasis). On
this level, you can substitute anything for anything. If your
typewriter font doesn't provide a bold version, you could
substitute the bold version of an entirely different font if you
feel like.
Hope this clarifies the situation a little bit.
--
Philipp Lehman <[EMAIL PROTECTED]>
