LISTSERV mailing list manager LISTSERV 16.0

Help for LATEX-L Archives


LATEX-L Archives

LATEX-L Archives


LATEX-L@LISTSERV.UNI-HEIDELBERG.DE


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

LATEX-L Home

LATEX-L Home

LATEX-L  February 2001

LATEX-L February 2001

Subject:

Re: glyph collections viz font encodings

From:

jbezos <[log in to unmask]>

Reply-To:

Mailing list for the LaTeX3 project <[log in to unmask]>

Date:

Mon, 5 Feb 2001 12:41:56 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (111 lines)

Frank, Chris,

I must admit that I'm too critic with my own macros and that
I try to study every possible implication of them, even if
finally they are unimportant.

>  > However, I found several problems. For example:
>  > - if I say \fontencoding{T1,OT1} we will get t1cmr which points to
another
>  >   font (ec) and not to a t1 encoded cmr,
>
> perhaps we should have that as a separate debate, but the ec fonts where
> supposed to be extended cmr at least this is what they started out to be.
I
> know that Joerg in the end did one or the other change but at least the
> original intention was that those fonts should have been indistinguishable
on
> their common subset of glyphs (and this is why in LaTeX they are
considered
> both family cm).
>
> if a lot of people think this is not the case then this opens an important
> discussion about what to do with them, but it doesn't seem to me a
criticism
> or a problem with the general approach taken in my sample code.

Actually, this is not a criticism to this approach, just an issue. While
there are free PostScript ot1cmr fonts, there are only MF t1cmr ones, which
to me is a huge difference. Sometimes I combine Palatino (T1) and cmtt
(OT1),
and \selectfont{T1,OT1} is not enough. The solution I took in my macros was
to allow explicit declarations like:
  \SetFontEnconding{cmtt}{OT1}

>  > - more importantly, we lost the control of the final result, because
>  >   a faked accented letter may be not exactly the same as an actual
composite
>  >   letter. It so happens that no TeX installations are the same and
perhaps
>  >   a different font in selected in another system just because a file
has not
>  >   been installed.
>
> but this is true already, isn't it? as of today a formatting of latex
document
> depends on a number of factors, one of which is the available fonts. so
100%
> output compatibility is only achieved if you
>
>  - have an identical set of fd files
>  - have identical metrics (this was especially with PostScript fonts an
issue
>    in the past)
>  - actually have the fonts installed that the fd files and metrics are
>    pointing to.

But TeX complains, except in the case of locally generated metrics.
One of the solutions I considered was to generate a file recording the
decisions taken in a system when a document is typeset, so that if we
really want to ensure that TeX complains if there is a different
configuration we can distribute that file with the main .tex ones.
And after all if we really really want a certain layout the obvius
solution is to distribute only a pdf file...

> [Chris]-- differences in the metrics (these can cause major differences in
> the typesetting).

Yes, differences in the metrics, which can reshape the whole document.

> if I now write a document and specify \fontencoding{T1} it might not run
at
> all at a site not having T1 fonts (though such a site is in theory not
allowed
> to exist) or it might switch to ec as default fonts, while with a range of
> encodings i would get a result "closer" to the intended output.
>
>
> also please note that my code (after your fix:-) does both: you can still
> specify a single encoding and then only that encoding will get used ie you
get
> the situation as it is now where the user has total control (assuming that
fd
> files are the same).
>
>  > Despite that, I think that is the right way, and I'm studying how to
solve
>  > these issues. Any ideas?
>
> do you have any other issues than the two above? you mentioned them as
"for
> example".

There are in part related to the fact that a language or a script
can provide a set of default encogings. (Note: in the current draft
for Lambda there are files for both languages and scripts).
But I think that:

> also please note that my code (after your fix:-) does both: you can still
> specify a single encoding and then only that encoding will get used ie you
get
> the situation as it is now where the user has total control (assuming that
fd
> files are the same).

is the best solution.

Cheers
Javier

______________________________________________________________________________
Consigue tu cuenta de correo universal y gratuita en http://webmail.wanadoo.es

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2019
July 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
June 2018
May 2018
April 2018
February 2018
January 2018
December 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
July 2016
April 2016
March 2016
February 2016
January 2016
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
September 2012
August 2012
July 2012
June 2012
May 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
September 2007
August 2007
June 2007
May 2007
March 2007
December 2006
November 2006
October 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
November 2005
October 2005
September 2005
August 2005
May 2005
April 2005
March 2005
November 2004
October 2004
August 2004
July 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
October 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
October 2002
September 2002
August 2002
July 2002
June 2002
March 2002
December 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996

ATOM RSS1 RSS2



LISTSERV.UNI-HEIDELBERG.DE

Universität Heidelberg | Impressum | Datenschutzerklärung

CataList Email List Search Powered by the LISTSERV Email List Manager