[Bug 925] bogus error message when font metrics not found

http://bugs.hylafax.org/show_bug.cgi?id=925


[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |trivial
            Summary|faxmail cannot find         |bogus error message when
                   |ghostscript fonts           |font metrics not found




------- Comment #2 from [email protected]  2010-01-19 01:36 -------
(In reply to comment #1)
> Does your suggested code change actually work for you?

I did not yet test my code change.
I extracted the relevant function from the source code and ran it with GDB.
When it had found the alias for Courier and tried to check if it's the last
matching line, it produced the error message. 
I stopped debugging at this point because I found some bug.

After looking at the source code and the Fontmap.GS file again I think my
change will only remove the error message but not the problem finding the font
metrics.

I found another Fontmap file on my system. When I add the corresponding fontmap
path the error is gone.

The only remaining problem is that TextFont::decodeFontName() should store an
error message like "font not found in FontMap or FontPath" in this error
situation.

My code change will only remove the bogus error message "line too long".

I changed the summary and severity.

In my case it might be a bug of the Debian package that does not include the
correct FontMap path in hyla.conf. I will report this to the Debian BTS.


-- 
Configure bugmail: http://bugs.hylafax.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


____________________ HylaFAX(tm) Developers Mailing List ____________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe [email protected] < /dev/null