> > . I'm not really happy that font is called `dgjhwff'. Its name
> > should be simply `dgjhw'.
>
> The font filename is dgjhw.sfd. Now, when I use the subfonts.pe
> script to extract .pfb and .tfm subfont files [...]
You shouldn't use this script: It's not necessary for a font which
contains less than 256 characters. Just move the half-width katakana
glyphs to the SJIS positions and create a standard Type 1 font
directly (see below).
> > I further suggest to use the SJIS code positions for the PFB
> > encoding vector. This would allow to use the font directly
> > for a C49 encoding (which is explicitly reserved for
> > half-width katakana). Consequently, c49{goth,maru,min}.fd
> > files should be added.
>
> I have to study what to do here, since I am not yet very good at
> tracing errors. I expected Unicode to be the natural way to encode;
> you seem to prefer SJIS with a virtual font reencoding (which I also
> need to study) for Unicode.
Well, the Wadalab fonts are not in Unicode encoding, so it would be
natural to have a font which fits into this framework.
> So what about EUC as well then?
JIS X 0208 doesnt' contain half-width katakana glyphs at all. Hmm. I
haven't yet thought about providing this for EUC-JIS encoding so that
the \CJKhwkatakana option works... However, such a modification would
be quite simple.
> > Additionally, TeXLive has a virtual font `udmj' which maps the
> > Wadalab dmj family to Unicode. It might be a good idea to
> > provide replacements for udmjff.vf and udmjff.tfm which add
> > the half-width katakana appropriately so that you don't need
> > to switch the family just to access the half-width katakana.
>
> That would be very useful. I suppose I can hand-edit the .vf file.
Yep (or probably writing a script to do that).
> But how is the .tfm file created?
vptovf creates a TFM file too.
> I only know how to do that with fontforge using a particular
> encoding. Since I am starting out with a .sfd file in Unicode
> mapping, I cannot directly output a .pfb file but need to use the
> subfonts.pe script to split and output.
This is not correct. In FontForge, just do
Encoding->Reencode->SJIS
and you get the right encoding which I suggest for the Type 1 font.
Afterwards, simply generate a Type_1 font (and ignore the `2-byte
warning') and you are done.
Werner
_______________________________________________
Cjk maillist - [email protected]
https://lists.ffii.org/mailman/listinfo/cjk
