[tex-live] bug in dvipdfmx wrt diacritics?

[Reinhard Kotucha]

On 2011-09-10 at 23:12:16 +0200, Zdenek Wagner wrote:

 > 2011/9/10 Reinhard Kotucha <reinhard.kotucha at web.de>:
 > > On 2011-09-09 at 22:44:33 +0900, Akira Kakuto wrote:
 > >
 > >  > Hi Norbert,
 > >  >
 > >  > > \documentclass{article}
 > >  > > \usepackage[T1]{fontenc}
 > >  > > \usepackage{charter}
 > >  > > \begin{document}
 > >  > > chass\'e du G\"obe
 > >  > > \end{document}
 > >  >
 > >  > Please try by removing the line
 > >  > \usepackage[T1]{fontenc}
 > >  >
 > >  > Probably the encoding should be the standard encoding for a SEAC,
 > >  > since dvipdfmx uses type 1C.
 > >
 > > AFAIK the actual encoding of the font doesn't matter.  Glyphs within
 > > Type 1 fonts have a name and an encoding vector is just an array of
 > > such names.
 > >
 > > The seac routine, however, takes numbers as arguments.  And these
 > > numbers denote slot numbers in the StandardEncoding array.  It doesn't
 > > mean that the font has to use StandardEncoding itself since every font
 > > renderer must have StandardEncoding built-in.  A font doesn't have to
 > > provide an encoding vector at all.  It's sufficient to provide a line
 > >
 > >  /Encoding StandardEncoding def
 > >
 > > within the font.  A font may provide more glyphs than StandardEncoding
 > > supports.  In order to access them, it has to be re-encoded.  This is
 > > what the fontenc package does.  As far as the seac routine is
 > 
 > No, this is not the job of the fontenc package. This package assigns
 > slots for characters using \DeclareTextSymbol and
 > \DeclareTextComposite. Thus for instance \'a may occupy different
 > slots in different encodings. It also defines slots for accents using
 > \DeclareTextAccent. This is used if a composite is not available in
 > the encoding. Characters are then build using the \accent primitive.
 > You can see in the TeXbook that accents occupy different slots in OT1
 > and T1. The map file then defines the binding between the TeX name and
 > PS name + font file name. If needed, encoding vector is specified.
 > Reencoding is then achieved by making a copy of the font and inserting
 > the encoding vector into it. It is not possible to insert the encoding
 > vector into the original font because the fonts are read only
 > dictionaries.

Thanks for the correction.  Yes, the actual re-encoding is done
somewhere else.  What I meant is that the fontecnc package is used to
select a font encoding.

Regards,
  Reinhard

-- 
----------------------------------------------------------------------------
Reinhard Kotucha                                      Phone: +49-511-3373112
Marschnerstr. 25
D-30167 Hannover                              mailto:reinhard.kotucha at web.de
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------