> "Garst" == Garst R Reese <[EMAIL PROTECTED]> writes:
Garst> I was not aware that using ae implied switching back to cm.
ae is just a set of virtual fonts which allows to emulate T1 encoded
ec fonts (Almost EC) with OT1 encoded cm fonts. This is useful because
there exist free postscript cm
Jean-Marc Lasgouttes wrote:
>
> You mean that you switched from ec fonts to cm+ae? Indeed, the ec
> fonts have been slightly re-desined wrt the original cm fonts, so one
> should not assume they are equivalent.
>
> JMarc
I was not aware that using ae implied switching back to cm.
Garst
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> My original suggestion was not very good. What about having 4
Dekel> choice buttons for choosing roman, sans serif, typewriter and
Dekel> math fonts ?
This is better IMO. We will certainly have a need a toggle to chose
between separa
> "Miyata" == Miyata Shigeru <[EMAIL PROTECTED]> writes:
Miyata> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
>> There is no real differenciation between PS and compouter modern
>> fonts. Where would you put malvern, concrete or cmbright fonts in
>> your dichotomy? All the fonts should be
> "Garst" == Garst R Reese <[EMAIL PROTECTED]> writes:
Garst> Just a cautionary note: When the subject of ae first appeared
Garst> on this list, I tried it out on a book. The font size changed
Garst> slightly, which changed the effect of page breaks, line
Garst> over-runs etc. Garst
You mean
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> There is no real differenciation between PS and compouter modern
> fonts. Where would you put malvern, concrete or cmbright fonts in your
> dichotomy? All the fonts should be mixed, ps or not ps.
Sorry for nitpicking, but Adobe standarized the na
I apologize if my wording did sound (quite intentionary) harsh.
Dekel Tsur <[EMAIL PROTECTED]> wrote:
> >- if a user doesn't read the documentation of TeX/LyX,
> > then s/he won't get a optimal outputs;
>
> This is an important issue. Even though I wrote a comprehensive explanation
>
On Fri, Jan 26, 2001 at 04:21:22PM +0100, Jean-Marc Lasgouttes wrote:
> Dekel> But if other people don't agree with me, I
> Dekel> suggest that the font button should let you chose from 3
> Dekel> options - Computer Modern (default) - Computer Modern (outline)
> Dekel> - Adobe fonts
>
> What is "
Jean-Marc Lasgouttes wrote:
> Concerning the use of ae.sty, this is a matter of encoding. Currently
> we let the encoding be T1 if T1 fonts are installed. We could also use
> T1 with ae if this is available.
>
> JMarc
Just a cautionary note:
When the subject of ae first appeared on this list, I
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> - The current font button should be replaced by the following:
Dekel> First, there is a button that let you choose between using
Dekel> Computer-Modern fonts, and Postscript Fonts. If you choose the
Dekel> later, then two button are e
> "Shigeru" == Shigeru Miyata <[EMAIL PROTECTED]> writes:
Shigeru> I disagree. - LyX should not interfare with the users' TeX
Shigeru> installation;
Shigeru>- LyX must not try to outsmart users' configurations. In
Shigeru> this specific case, if a user set up his/her
Shigeru> dvips/dvip
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> On Fri, Jan 26, 2001 at 02:52:27PM +0900, Shigeru Miyata wrote:
>> I've also read the users-list discussion. Clearly the outcome can
>> be summarized to: - if a user doesn't read the documentation of
>> TeX/LyX, then s/he won't get a
On Fri, Jan 26, 2001 at 10:47:53AM +0100, Lars Gullik Bjønnes wrote:
> Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> I strongly disagree with this.
Can you explain why ?
What about my suggestion about improving the font selection ?
> BUT as we make the support for pdf really integrated with lyx a
On Fri, Jan 26, 2001 at 02:52:27PM +0900, Shigeru Miyata wrote:
> I've also read the users-list discussion. Clearly the outcome
> can be summarized to:
>- if a user doesn't read the documentation of TeX/LyX,
> then s/he won't get a optimal outputs;
This is an important issue. Even th
Dekel Tsur <[EMAIL PROTECTED]> writes:
I strongly disagree with this.
BUT as we make the support for pdf really integrated with lyx and not
just as an export as it is now we can easily accomodate things like
this to get nicer _pdf_ but as some sort of general change.. it is not
going to happen.
Dekel Tsur <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 25, 2001 at 05:26:56PM +0100, Marcus Beyer wrote:
> > AFAIK the support of bitmap fonts has only two important effects:
> > 1. Many new LyX users have do make the "ugly-fonts-experience",
> >at least when they publish their documents to the w
On Thu, Jan 25, 2001 at 05:26:56PM +0100, Marcus Beyer wrote:
> AFAIK the support of bitmap fonts has only two important effects:
> 1. Many new LyX users have do make the "ugly-fonts-experience",
>at least when they publish their documents to the web,
>where most people view them with Acro
Dear developers,
these are the last lines of a long discussion in "lyx-users" caused by
my proposal to remove the support for bitmap fonts in target documents.
I send you this for the case, that you want to continue the discussion.
My arguments:
AFAIK the support of bitmap fonts has only two i
18 matches
Mail list logo
