> If there are some remarks, please let me know.  I've only access to
> a teTeX distribution on Debian GNU/Linux.

Sorry, I'm away from good internet access for the next three weeks.

> I currently need four hlatex2agl.pl commands, one for each .sfd
> file: UKS-HLaTeX.sfd, UKS-HLaTeX-Hangul.sfd,
> UKS-HLaTeX-Hangul_Hanja.sfd and UKS-HLaTeX-Hangul_Symbol.sfd.  So it
> would be nice if hlatex2agl.pl could also have an extra argument to
> choose which .sfd is to be used.

Patch, please :-)

> The u??.pfb files created by hlatex2agl have exactly the same name
> as the original HLaTeX counterparts.  Do I have to overwrite the
> original fonts?

Yes.  They are improved versions with corrected glyph names; nothing
else has changed.

> I have problems with dinaru and pilgia when I run dvips or pdflatex.
> Well, warnings actually.  With dvips I get:
>
>   dvips: Checksum mismatch in udn10
>   [...]

This is not related to the PFB fonts but to TFM (and VF) files.  PFBs
don't contain a checksum at all.  Apparently the DVI file you are
using for testing purposes has been created with a different set of
metric files (probably the old ones, whatever they are; maybe you have
still something from earlier experiments).

> I noticed that hlatex2agl didn't put a comment in the dinaru and
> pilgia .pfb fonts.  I think the reason is that these two fonts were
> the only two not created by Fontographer 4.1 but by FontForge 1.0.
> Perhaps hlatex2agl botches something up?

The FontForge version used to create those PFBs doesn't add a
`Generated' comment line which hlatex2agl uses as an anchor to insert
its additional comment.  Perhaps it would be useful to apply the
following patch.


--- hlatex2agl.pl       2006-04-25 17:11:50.000000000 +0200
+++ hlatex2agl.pl.new   2006-08-09 10:31:35.000000000 +0200
@@ -455,7 +455,7 @@
     print(OUTFILE $_);

     # Add comment.
-    if (/^% Generated/) {
+    if (/^% CreationDate/) {
       print(OUTFILE "% AGL compliant glyph names added "
                     . "by script $prog 2005-Jul-27.\n");
     }


A similar problem occurs with udn00.pfb: The very first line doesn't
contain `001.000', so the script is not able to correctly update the
version number.  You might extend the regular expression to handle
this; I'm too lazy for it.

> I get the following warnings:
>
>   gothic/log:Use of uninitialized value in hash element at
>     hlatex2agl.pl line 359.
>   [...]

Interesting.  Please tell me which fonts are involved.  I suspect this
is due to problems with Koaung-Hi's VF files.

> Currently each font is its own "italics" and its own "typewriter"
> font.  Only the glue would be different.  Would you prefer to have
> for example every \texttt{} use Tada, or should the user himself be
> smart enough to use \CJKfamily{tt} and to reconfigure \texttt and \tt
> if s/he wishes so?  We might have to rethink how the .fd files are
> configured.

*This* you should discuss with Koaung-Hi :-) I have no idea how Korean
fonts are used in the real world.


    Werner

_______________________________________________
Cjk maillist  -  [email protected]
http://lists.ffii.org/mailman/listinfo/cjk

Reply via email to