\usepackage[force]{textcomp} side effects for debiandoc-sgml

[Osamu Aoki <osamu@debian.org>]

On Thu, Dec 29, 2005 at 01:21:43PM +0100, Frank Küster wrote:
> reassign 338376 debiandoc-sgml
> tags 338376 patch
> thanks

Uploaded :-)

> Me again,
> 
> Frank Küster <frank@kuesterei.ch> wrote:
> 
> > - The first is to load the textcomp package with the "force" option:
> >
> > \usepackage[force]{textcomp}
> >
> >   But this might have other side effects; you'd have to carefully check
> >   the rest of the document (I must admit that I don't understand the
> >   sparse and not user-oriented documentation of the textcomp package,
> >   which is only available after processing LaTeX's ltoutenc.dtx).
> 
> I have had a closer look at the debiandoc-sgml-doc.en.pdf,
> and it seems as if someone carefully checked which sgml entities (or how
> do you call that) are available in LaTeX, and replaced the others with
> [NAME].  I assume that this person will also have checked whether the
> output is correct, i.e. whether a LaTeX command with a given name gives
> the output they want.  
> 
> Since the force option only restores the behavior we had in teTeX-2.0.2,
> and it has been checked that this gave correct output, we can safely use
> [force]. 

Well, as I actually build debiandoc-sgml-doc, I realized it contained
all ISO character entries.  So some fonts did not have palatino gliphs.
(Not just currency.)

So I added footnote to tell uses this side effect.  Anyway, not only
PS/PDF but plain text had problem handling these fancy gliphs.  

I think it is right decision for teTeX to check font availability but
forcing this way for debiandoc-sgml is practical solution to keep
bug-to-bug compatibility with old debiandoc-sgml.

Thanks.

Osamu