Documentation Errors I've Found
I've just downloaded, and compiled LyX 2.04 for Ubuntu 12.04. I've found a couple of errors as I've been reading the documentation. * In the user guide that came with the package in section 3.9.5 Lyx's Proper Names, the sentence It's an old tradition in the TeX world to give programs geek version numbers - I think geek should be Greek. * In section 6.14 Spell Checking, 2nd paragraph, 4th sentence begins This work - work should be works.
Documentation Errors I've Found
I've just downloaded, and compiled LyX 2.04 for Ubuntu 12.04. I've found a couple of errors as I've been reading the documentation. * In the user guide that came with the package in section 3.9.5 Lyx's Proper Names, the sentence It's an old tradition in the TeX world to give programs geek version numbers - I think geek should be Greek. * In section 6.14 Spell Checking, 2nd paragraph, 4th sentence begins This work - work should be works.
Fonts guide
Hi everyone, Is there likely to be any action on bug #269, Do something with Robin's fonts document? Robin -- It takes less effort to condemn than to think. - Emma Goldman Robin Turner IDMYO Bilkent Univeritesi Ankara 06533 Turkey www.bilkent.edu.tr/~robin
Fonts guide
Hi everyone, Is there likely to be any action on bug #269, "Do something with Robin's fonts document"? Robin -- "It takes less effort to condemn than to think." - Emma Goldman Robin Turner IDMYO Bilkent Univeritesi Ankara 06533 Turkey www.bilkent.edu.tr/~robin
Re: FAQ
Christian Ridderström wrote: Hi As you (ought to) know, I've more or less arbitrarily been writing down some of the questions and answers I've seen on the user's list here: http://ev-en.org/wiki/moin.cgi/LyxFAQ However, the unsorted questions are getting a bit too many now, so I'd like to do something about that. At first I just copied everything from FAQ.lyx, including the structure with the following categories: * Introduction and General Information * Internet Resources * Compatibility with other word/document processors * Obtaining and Compiling LyX * Questions about Evil Red Text (IMPORTANT!) * Questions Related to Using LyX * Questions Related to Using LyX * Questions Related to LyX on Windows * How to get further assistance * Administrative information and acknowledgments and added the category: * Unsorted questions. where I've been adding questions. After I while I also started adding separate pages for some of the answers (in an unstructured way) since the page was getting a bit long. Here are my questions: * Are there any objections to me moving questions into the priorly defined categories? * Do you have any ideas or opinions on new categories? * Any opinions etc on where the different questions should go? PS. The reason I'm asking about objection to moving new questions into the prior categories is that it will definitely make this FAQ get a life separately from FAQ.lyx, and if FAQ.lyx is (ever) updated, this entire FAQ ought to be checked for questions that should go into FAQ.lyx, instead of just the category: *unsorted questions* DS No objections. I think a section on layout would catch a lot of questions. Robin -- A Perl script is correct if it gets the job done before your boss fires you. - Larry Wall Robin Turner IDMYO Bilkent Univeritesi Ankara 06533 Turkey www.bilkent.edu.tr/~robin
Re: FAQ
Christian Ridderström wrote: Hi As you (ought to) know, I've more or less arbitrarily been writing down some of the questions and answers I've seen on the user's list here: http://ev-en.org/wiki/moin.cgi/LyxFAQ However, the unsorted questions are getting a bit too many now, so I'd like to do something about that. At first I just copied everything from FAQ.lyx, including the structure with the following categories: * Introduction and General Information * Internet Resources * Compatibility with other word/document processors * Obtaining and Compiling LyX * Questions about Evil Red Text (IMPORTANT!) * Questions Related to Using LyX * Questions Related to Using LyX * Questions Related to LyX on Windows * How to get further assistance * Administrative information and acknowledgments and added the category: * Unsorted questions. where I've been adding questions. After I while I also started adding separate pages for some of the answers (in an unstructured way) since the page was getting a bit long. Here are my questions: * Are there any objections to me moving questions into the priorly defined categories? * Do you have any ideas or opinions on new categories? * Any opinions etc on where the different questions should go? PS. The reason I'm asking about objection to moving new questions into the prior categories is that it will definitely make this FAQ get a life separately from FAQ.lyx, and if FAQ.lyx is (ever) updated, this entire FAQ ought to be checked for questions that should go into FAQ.lyx, instead of just the category: *unsorted questions* DS No objections. I think a section on layout would catch a lot of questions. Robin -- "A Perl script is "correct" if it gets the job done before your boss fires you." - Larry Wall Robin Turner IDMYO Bilkent Univeritesi Ankara 06533 Turkey www.bilkent.edu.tr/~robin
Re: Comments on the tutorial
On Monday 27 May 2002 08:53, Mike van Emmerik wrote: On the basis that these things should be idiot proof, as as much as possible, I feel qualified to mention the first two problems that I had: 1) When talking about the Table Of Contents, it suggests pressing the grey button, but doesn't say where it is. Good point - with xforms almost anything could be described as a grey button! Robin -- The reason we come up with new versions is not to fix bugs. It's absolutely not. It's the stupidest reason to buy a new version I ever heard. - Bill Gates Robin Turner IDMYO, Bilkent Universitesi Ankara 06533 Turkey http://www.bilkent.edu.tr/~robin
Re: Comments on the tutorial
On Monday 27 May 2002 08:53, Mike van Emmerik wrote: > On the basis that these things should be idiot proof, as as much > as possible, I feel qualified to mention the first two problems > that I had: > > 1) When talking about the Table Of Contents, it suggests pressing > "the grey button", but doesn't say where it is. Good point - with xforms almost anything could be described as a grey button! Robin -- "The reason we come up with new versions is not to fix bugs. It's absolutely not. It's the stupidest reason to buy a new version I ever heard." - Bill Gates Robin Turner IDMYO, Bilkent Universitesi Ankara 06533 Turkey http://www.bilkent.edu.tr/~robin
Re: I'm still here too + revised docs
Andre Poenitz wrote: On Thu, Sep 13, 2001 at 11:17:03PM -0700, Micheas Herman wrote: (not sure) shouldn't it be The LyX team know not The LyX team knows It is correct as is. The LyX team is one team so the verb is also singular (knows). But there is more than one person in it... I guess that's again American vs British English. It's entirely dependent on the way the speaker/writer views the group in that context:as a mass or as a buch of individuals. I don't think there is much difference between UK and US English here. Massification is not something English handles particularly well. Robin
Re: I'm still here too + revised docs
Andre Poenitz wrote:
>
> On Thu, Sep 13, 2001 at 11:17:03PM -0700, Micheas Herman wrote:
> > > (not sure) shouldn't it be "The LyX team know" not "The LyX team knows"
> > >
> >
> > It is correct as is. "The LyX team" is one team so the verb is also
> > singular ("knows").
>
> But there is more than one person in it... I guess that's again American
> vs British English.
It's entirely dependent on the way the speaker/writer views the group in
that context:as a mass or as a buch of individuals.
I don't think there is much difference between UK and US English here.
Massification is not something English handles particularly well.
Robin
Re: fonts
Here's an updated file, slightly delayed by a bug in 1.2 -- be careful
with cut-and-pasting ERT!
Robin
#LyX 1.2 created this file. For more info see http://www.lyx.org/
\lyxformat 220
\textclass article
\language english
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\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 Subsection
Using different fonts in LyX
\layout Standard
by
\noun on
Robin Turner
\layout Standard
\begin_inset ERT
status Open
\layout Standard
\backslash
newfont{
\backslash
yinit}{yinit}
\backslash
yinit
\end_inset
\layout Standard
L
\begin_inset ERT
status Open
\layout Standard
\backslash
normalfont
\end_inset
yX currently uses a fairly limited selection of fonts.
While it may come as a disappointment to people used to the thousands of
TrueType fonts available to conventional word processors, there are in
fact good reasons for this choice.
LyX actually has no fonts of its own; for the screen it uses whatever fonts
are available to the X-window system, and for output it uses the fonts
of the TeX setup it is operating with.
The selection of default faults correspond to the most useful and commonly-foun
d fonts available in TeX.
The
\begin_inset Quotes eld
\end_inset
L
\begin_inset Quotes erd
\end_inset
at the beginning of this section is a case in point: most TeX distributions
include the
\family typewriter
yinit
\family default
font, so you should see a nice decorated
\begin_inset Quotes eld
\end_inset
L
\begin_inset Quotes erd
\end_inset
at the beginning; some distributions may not, so you won't.
\layout Standard
Another point is that the profusion of fonts which TrueType brought about
has generally had a bad effect on desktop publishing, leading to documents
with inappropriate, badly-scaled or simply too many fonts.
You should therefore think carefully before using a different default font,
or mixing font families in the same document.
\layout Standard
Nevertheless, you can, with a little Evil Red Text, make LyX produce just
about any font you want, and even design your own fonts.
What follows is a
\begin_inset Quotes eld
\end_inset
quick fix
\noun on
\begin_inset Quotes erd
\end_inset
\noun default
guide; it is no substitute for reading a good book on (La)TeX.
\layout Subsubsection
Changing the default font
\layout Standard
The easiest and most reliable way to change the default font is from within
LyX, through
\family sans
Layout\SpecialChar \menuseparator
Document\SpecialChar \menuseparator
Fonts
\family default
.
The next easiest is to use a package contained in your TeX distribution.
For example, the rather pretty Pandora font family can be accessed simply
by putting
\family typewriter
\backslash
usepackage{pandora}
\family default
in your LaTeX preamble (
\family sans
Layout\SpecialChar \menuseparator
LaTeX\SpecialChar ~
preamble
\family default
).
Similarly,
\family typewriter
\backslash
usepackage{oldgerm}
\family default
in the preamble gives you access to Yannis Haralambous' Old German (Gothisch)
fonts via the specially-defined
\family typewriter
\backslash
gothfamily
\family default
,
\family typewriter
\backslash
swabfamily
\family default
, and
\family typewriter
\backslash
frakfamily
\family default
commands, which you insert in your document (as TeX) to obtain the desired
font (note that nothing will change in your screen display, which considering
the difficulty involved in reading some of these fonts is just as well).
Other useful packages are
\family typewriter
concrete
\family default
, which gives access to both the Concrete Roman and the Euler math fonts,
and
\family typewriter
chancery
\family default
, which gives you the Zapf Chancery font
\layout Standard
A less reliable method is the
\family typewriter
\backslash
familydefault
\family default
command.
If you have a font installed and know its family name, you can put something
like
\layout Quote
\family typewriter
\backslash
renewcommand{
\backslash
familydefault}{pzc}
\layout Standard
in the preamble (
\begin_inset Quotes eld
\end_inset
pzc
\begin_inset Quotes erd
\end_inset
is the family name for the Zapf Chancery font).
You should be aware, however, that this method may produce strange results
if the font you have selected does not have the sizes or shapes you want
(e.g.
adding emphasis to text has no effect on Zapf Chancery, and choosing the
sans serif or typewriter series will cause it to revert to the standard
font).
\layout Subsubsection
More than one font family in one document
\layout Standard
As I've said, different font families in the same
Re: fonts
Here's an updated file, slightly delayed by a bug in 1.2 -- be careful
with cut-and-pasting ERT!
Robin
#LyX 1.2 created this file. For more info see http://www.lyx.org/
\lyxformat 220
\textclass article
\language english
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\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 Subsection
Using different fonts in LyX
\layout Standard
by
\noun on
Robin Turner
\layout Standard
\begin_inset ERT
status Open
\layout Standard
\backslash
newfont{
\backslash
yinit}{yinit}
\backslash
yinit
\end_inset
\layout Standard
L
\begin_inset ERT
status Open
\layout Standard
\backslash
normalfont
\end_inset
yX currently uses a fairly limited selection of fonts.
While it may come as a disappointment to people used to the thousands of
TrueType fonts available to conventional word processors, there are in
fact good reasons for this choice.
LyX actually has no fonts of its own; for the screen it uses whatever fonts
are available to the X-window system, and for output it uses the fonts
of the TeX setup it is operating with.
The selection of default faults correspond to the most useful and commonly-foun
d fonts available in TeX.
The
\begin_inset Quotes eld
\end_inset
L
\begin_inset Quotes erd
\end_inset
at the beginning of this section is a case in point: most TeX distributions
include the
\family typewriter
yinit
\family default
font, so you should see a nice decorated
\begin_inset Quotes eld
\end_inset
L
\begin_inset Quotes erd
\end_inset
at the beginning; some distributions may not, so you won't.
\layout Standard
Another point is that the profusion of fonts which TrueType brought about
has generally had a bad effect on desktop publishing, leading to documents
with inappropriate, badly-scaled or simply too many fonts.
You should therefore think carefully before using a different default font,
or mixing font families in the same document.
\layout Standard
Nevertheless, you can, with a little Evil Red Text, make LyX produce just
about any font you want, and even design your own fonts.
What follows is a
\begin_inset Quotes eld
\end_inset
quick fix
\noun on
\begin_inset Quotes erd
\end_inset
\noun default
guide; it is no substitute for reading a good book on (La)TeX.
\layout Subsubsection
Changing the default font
\layout Standard
The easiest and most reliable way to change the default font is from within
LyX, through
\family sans
Layout\SpecialChar \menuseparator
Document\SpecialChar \menuseparator
Fonts
\family default
.
The next easiest is to use a package contained in your TeX distribution.
For example, the rather pretty Pandora font family can be accessed simply
by putting
\family typewriter
\backslash
usepackage{pandora}
\family default
in your LaTeX preamble (
\family sans
Layout\SpecialChar \menuseparator
LaTeX\SpecialChar ~
preamble
\family default
).
Similarly,
\family typewriter
\backslash
usepackage{oldgerm}
\family default
in the preamble gives you access to Yannis Haralambous' Old German (Gothisch)
fonts via the specially-defined
\family typewriter
\backslash
gothfamily
\family default
,
\family typewriter
\backslash
swabfamily
\family default
, and
\family typewriter
\backslash
frakfamily
\family default
commands, which you insert in your document (as TeX) to obtain the desired
font (note that nothing will change in your screen display, which considering
the difficulty involved in reading some of these fonts is just as well).
Other useful packages are
\family typewriter
concrete
\family default
, which gives access to both the Concrete Roman and the Euler math fonts,
and
\family typewriter
chancery
\family default
, which gives you the Zapf Chancery font
\layout Standard
A less reliable method is the
\family typewriter
\backslash
familydefault
\family default
command.
If you have a font installed and know its family name, you can put something
like
\layout Quote
\family typewriter
\backslash
renewcommand{
\backslash
familydefault}{pzc}
\layout Standard
in the preamble (
\begin_inset Quotes eld
\end_inset
pzc
\begin_inset Quotes erd
\end_inset
is the family name for the Zapf Chancery font).
You should be aware, however, that this method may produce strange results
if the font you have selected does not have the sizes or shapes you want
(e.g.
adding emphasis to text has no effect on Zapf Chancery, and choosing the
sans serif or typewriter series will cause it to revert to the standard
font).
\layout Subsubsection
More than one font family in one document
\layout Standard
As I've said, different font families in the same
Re: Fonts
On Tuesday 11 September 2001 02:59, John Levon wrote: On Mon, Sep 10, 2001 at 06:27:41PM +0300, Robin Turner wrote: Would the doc team be interested in a section on using different fonts to go in Extended features? I have a piece which might be suitable, covering changing the default font (to use fonts not available in the popup), using more than one font family in the same document and installing TeX fonts. this sounds like a great idea ! How should I submit it? As an attached .lyx doc? Robin
Re: Fonts
Amir Karger wrote:
On Tue, Sep 11, 2001 at 12:43:05PM +0300, Robin Turner wrote:
On Tuesday 11 September 2001 02:59, John Levon wrote:
this sounds like a great idea !
How should I submit it? As an attached .lyx doc?
Probably easiest if you just submit a Word file, so everyone will be able to
read it.
[repeats the incantation against trolls]
Here it is. The first letter is a bit of frivolity which not all readers
may like.
Robin
#LyX 1.2 created this file. For more info see http://www.lyx.org/
\lyxformat 220
\textclass article
\language english
\inputencoding latin5
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\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 Subsection
Using different fonts in LyX
\layout Standard
by
\noun on
Robin Turner
\layout Standard
\begin_inset ERT
status Open
\layout Standard
\backslash
newfont{
\backslash
yinit}{yinit scaled
\backslash
magstep1}
\backslash
yinit
\end_inset
\layout Standard
L
\begin_inset ERT
status Open
\layout Standard
\backslash
normalfont
\end_inset
yX currently uses a fairly limited selection of fonts.
While it may come as a disappointment to people used to the thousands of
fonts available to conventional word processors, there are in fact good
reasons for this choice.
LyX has no fonts of its own; for the screen it uses whatever fonts are
available to the X-window system, and for output it uses the fonts of the
TeX setup it is operating with.
The selection of default faults correspond to the most useful and commonly
found fonts available in TeX.
For example, the first letter of this section, uses the Initial (yinit)
font.
You have
\emph on
probably
\emph default
got this in your TeX distribution, so it
\emph on
should
\emph default
come out as a big pretty gothic letter, but if you haven't, it won't.
Another factor is that the profusion of fonts which TrueType brought about
has generally had a bad effect on desktop publishing, leading to documents
with inappropriate, badly-scaled or simply too many fonts.
You should therefore think carefully before using a different default font,
or mixing font families in the same document.
\layout Standard
\noun on
Note
\noun default
: When trying out the various methods here, it's a good idea to make up
a test file containing a variety of headings and character styles, so that
you can see the effect different font commands have; for example, many
fonts will refuse to do headings.
\layout Subsubsection
Changing the default font
\layout Standard
The easiest and most reliable way to change the default font is from within
LyX, through
\family sans
Layout\SpecialChar \menuseparator
Document\SpecialChar \menuseparator
Fonts
\family default
.
The next easiest is to use a package contained in your TeX distribution.
For example, the rather pretty Pandora font family can be accessed simply
by putting
\family typewriter
\backslash
usepackage{pandora}
\family default
in your LaTeX preamble (
\family sans
Layout\SpecialChar \menuseparator
LaTeX\SpecialChar ~
preamble
\family default
).
Similarly,
\family typewriter
\backslash
usepackage{oldgerm}
\family default
in the preamble gives you access to Yannis Haralambous' Old German (Gothisch)
fonts via the specially-defined
\family typewriter
\backslash
gothfamily
\family default
,
\family typewriter
\backslash
swabfamily
\family default
, and
\family typewriter
\backslash
frakfamily
\family default
commands, which you insert in your document (as TeX) to obtain the desired
font (note that nothing will change in your screen display, which considering
the difficulty involved in reading some of these fonts is just as well).
Other useful packages are
\family typewriter
concrete
\family default
, which gives access to both the Concrete Roman and the Euler math fonts,
and
\family typewriter
chancery
\family default
, which gives you the Zapf Chancery fonts.
\layout Standard
A less reliable method is the
\family typewriter
\backslash
familydefault
\family default
command.
If you have a font installed and know its family name, you can put something
like
\layout Quote
\family typewriter
\backslash
renewcommand{
\backslash
familydefault}{rpxppl}
\layout Standard
in the preamble (
\begin_inset Quotes eld
\end_inset
rpxppl
\begin_inset Quotes erd
\end_inset
is the family name for the Palladio fonts).
\layout Standard
You should be aware that these methods may produce strange results if the
font you have selected does not have the sizes or shapes you want (e.g.
adding emphasis to text has no effect on Zapf Chancery, and choosing the
sans serif or typewriter
Re: Fonts
On Tuesday 11 September 2001 02:59, John Levon wrote: > On Mon, Sep 10, 2001 at 06:27:41PM +0300, Robin Turner wrote: > > Would the doc team be interested in a section on using different fonts to > > go in "Extended features"? I have a piece which might be suitable, > > covering changing the default font (to use fonts not available in the > > popup), using more than one font family in the same document and > > installing TeX fonts. > > this sounds like a great idea ! How should I submit it? As an attached .lyx doc? Robin
Re: Fonts
Amir Karger wrote:
>
> On Tue, Sep 11, 2001 at 12:43:05PM +0300, Robin Turner wrote:
> > On Tuesday 11 September 2001 02:59, John Levon wrote:
> > >
> > > this sounds like a great idea !
> >
> > How should I submit it? As an attached .lyx doc?
>
> Probably easiest if you just submit a Word file, so everyone will be able to
> read it.
[repeats the incantation against trolls]
Here it is. The first letter is a bit of frivolity which not all readers
may like.
Robin
#LyX 1.2 created this file. For more info see http://www.lyx.org/
\lyxformat 220
\textclass article
\language english
\inputencoding latin5
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\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 Subsection
Using different fonts in LyX
\layout Standard
by
\noun on
Robin Turner
\layout Standard
\begin_inset ERT
status Open
\layout Standard
\backslash
newfont{
\backslash
yinit}{yinit scaled
\backslash
magstep1}
\backslash
yinit
\end_inset
\layout Standard
L
\begin_inset ERT
status Open
\layout Standard
\backslash
normalfont
\end_inset
yX currently uses a fairly limited selection of fonts.
While it may come as a disappointment to people used to the thousands of
fonts available to conventional word processors, there are in fact good
reasons for this choice.
LyX has no fonts of its own; for the screen it uses whatever fonts are
available to the X-window system, and for output it uses the fonts of the
TeX setup it is operating with.
The selection of default faults correspond to the most useful and commonly
found fonts available in TeX.
For example, the first letter of this section, uses the Initial (yinit)
font.
You have
\emph on
probably
\emph default
got this in your TeX distribution, so it
\emph on
should
\emph default
come out as a big pretty gothic letter, but if you haven't, it won't.
Another factor is that the profusion of fonts which TrueType brought about
has generally had a bad effect on desktop publishing, leading to documents
with inappropriate, badly-scaled or simply too many fonts.
You should therefore think carefully before using a different default font,
or mixing font families in the same document.
\layout Standard
\noun on
Note
\noun default
: When trying out the various methods here, it's a good idea to make up
a test file containing a variety of headings and character styles, so that
you can see the effect different font commands have; for example, many
fonts will refuse to do headings.
\layout Subsubsection
Changing the default font
\layout Standard
The easiest and most reliable way to change the default font is from within
LyX, through
\family sans
Layout\SpecialChar \menuseparator
Document\SpecialChar \menuseparator
Fonts
\family default
.
The next easiest is to use a package contained in your TeX distribution.
For example, the rather pretty Pandora font family can be accessed simply
by putting
\family typewriter
\backslash
usepackage{pandora}
\family default
in your LaTeX preamble (
\family sans
Layout\SpecialChar \menuseparator
LaTeX\SpecialChar ~
preamble
\family default
).
Similarly,
\family typewriter
\backslash
usepackage{oldgerm}
\family default
in the preamble gives you access to Yannis Haralambous' Old German (Gothisch)
fonts via the specially-defined
\family typewriter
\backslash
gothfamily
\family default
,
\family typewriter
\backslash
swabfamily
\family default
, and
\family typewriter
\backslash
frakfamily
\family default
commands, which you insert in your document (as TeX) to obtain the desired
font (note that nothing will change in your screen display, which considering
the difficulty involved in reading some of these fonts is just as well).
Other useful packages are
\family typewriter
concrete
\family default
, which gives access to both the Concrete Roman and the Euler math fonts,
and
\family typewriter
chancery
\family default
, which gives you the Zapf Chancery fonts.
\layout Standard
A less reliable method is the
\family typewriter
\backslash
familydefault
\family default
command.
If you have a font installed and know its family name, you can put something
like
\layout Quote
\family typewriter
\backslash
renewcommand{
\backslash
familydefault}{rpxppl}
\layout Standard
in the preamble (
\begin_inset Quotes eld
\end_inset
rpxppl
\begin_inset Quotes erd
\end_inset
is the family name for the Palladio fonts).
\layout Standard
You should be aware that these methods may produce strange results if the
font you have selected does not have the sizes or shapes you want (e.g.
adding emphasis to text has
Fonts
Would the doc team be interested in a section on using different fonts to go in "Extended features"? I have a piece which might be suitable, covering changing the default font (to use fonts not available in the popup), using more than one font family in the same document and installing TeX fonts. Robin
Fonts
Would the doc team be interested in a section on using different fonts to go in "Extended features"? I have a piece which might be suitable, covering changing the default font (to use fonts not available in the popup), using more than one font family in the same document and installing TeX fonts. Robin
Re: Introduction in User Guide
On Friday 04 May 2001 01:23, SoundChaser wrote: Mike, You have a volunteer right here. :) As I have been reading the documentation lately, I've come across a number of things that I wuold like to see revisited / revised. (Mostly things in tone of the documentation...) I'd also be happy to help - in fact I'd considered submitting material before, but I was put off a little by the intimidating tone of the stylesheet, so wrot my own guide instead. I think this is a good time to ask ourselves who (plural) LyX is designed for, and what kind of documentation suits each type of user base. There seem to be three rather distinct groups of (potential) LyX users: 1. LaTeX users who want a convenient graphic front-end because they're fed up with typing out all those LaTeX commands. All they really need in terms of documentation is how LyX does \somelatexcommand. 2. Linux users who stumbled upon LyX in search of a good alternative to Word(Perfect). No knowledge of LaTeX, but pretty computer-savvy. current documentation is well suited to this group. 3. Non-computer-savvy users who just want an easy way to write stuff. This last group is pretty small, I think, but they are where the future lies. I keep trying to tell my workmates that LyX is actually _easier_ to use than MS Word, but they don't believe me. Maybe we should have a LyX animated paperclip -- just kidding! Robin
Re: Introduction in User Guide
On Friday 04 May 2001 01:23, SoundChaser wrote: > Mike, > > You have a volunteer right here. :) As I have been reading the > documentation lately, I've come across a number of things that I wuold > like to see revisited / revised. (Mostly things in tone of the > documentation...) I'd also be happy to help - in fact I'd considered submitting material before, but I was put off a little by the intimidating tone of the stylesheet, so wrot my own guide instead. I think this is a good time to ask ourselves who (plural) LyX is designed for, and what kind of documentation suits each type of user base. There seem to be three rather distinct groups of (potential) LyX users: 1. LaTeX users who want a convenient graphic front-end because they're fed up with typing out all those LaTeX commands. All they really need in terms of documentation is how LyX does \somelatexcommand. 2. Linux users who stumbled upon LyX in search of a good alternative to Word(Perfect). No knowledge of LaTeX, but pretty computer-savvy. current documentation is well suited to this group. 3. Non-computer-savvy users who just want an easy way to write stuff. This last group is pretty small, I think, but they are where the future lies. I keep trying to tell my workmates that LyX is actually _easier_ to use than MS Word, but they don't believe me. Maybe we should have a LyX animated paperclip -- just kidding! Robin
