[ xdvi-Bugs-2914532 ] musixtex font problem with t1lib

Bugs item #2914532, was opened at 2009-12-14 18:20
Message generated for change (Comment added) made by vojta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377580&aid=2914532&group_id=23164

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bob Tennent (rdtennent)
Assigned to: Nobody/Anonymous (nobody)
Summary: musixtex font problem with t1lib

Initial Comment:
The long beams in the attached dvi file "overshoot" the last stem in the two  sequences.  This happens only with t1lib. With tilib:off or
if the file is converted to Postscript (dvips) or PDF (ps2pdf), there are no overshoots. The musixtex type 1 fonts are available here:

ftp://sunsite.dk/mirrors/ctan/fonts/musixtex/ps-type1/musixps-unix.tar.gz

----------------------------------------------------------------------

Comment By: Paul Vojta (vojta)
Date: 2010-01-06 23:26

Message:
I've found the problem (actually two bugs).

The first bug is that the size for the Type 1 file was calculated
incorrectly, resulting in a font that was 4% too large.  The second bug,
which also affected the size, was that the font size (in points) was
rounded down to an integer at a certain point.  This counteracted the first
bug at certain resolutions.

I've attached a patch.

Also, for the record, the following plain TeX file exhibits the bug:

\nopagenumbers
\font\foo=musix16
\hbox{\foo \char133\char133}
\hbox{\foo \char132\char132\char132\char132}
\bye

----------------------------------------------------------------------

Comment By: Paul Vojta (vojta)
Date: 2010-01-06 23:25

Message:
I've found the problem (actually two bugs).

The first bug is that the size for the Type 1 file was calculated
incorrectly, resulting in a font that was 4% too large.  The second bug,
which also affected the size, was that the font size (in points) was
rounded down to an integer at a certain point.  This counteracted the first
bug at certain resolutions.

I've attached a patch.

Also, for the record, the following plain TeX file exhibits the bug:

\nopagenumbers
\font\foo=musix16
\hbox{\foo \char133\char133}
\hbox{\foo \char132\char132\char132\char132}
\bye

----------------------------------------------------------------------

Comment By: Bob Tennent (rdtennent)
Date: 2010-01-04 19:29

Message:
The overshoots disappear if I use -mfmode ljfive:600  instead of -mfmode
ljfive:1200.

----------------------------------------------------------------------

Comment By: Bob Tennent (rdtennent)
Date: 2009-12-14 18:27

Message:
xdvik version 22.84.16 (Xaw toolkit)
Libraries: kpathsea version 3.5.7, T1lib version 5.1.2


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377580&aid=2914532&group_id=23164

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev