Bug#346205: texmacs: errors and warnings during font generation
On 09.12.05 Laurent Bonnaud (bonnaud@lis.inpg.fr) wrote:
Hi all,
http://bugs.debian.org/346205
> when I start texmacs in an account where the ~/.TeXmacs/ directory
> does not exist and read the full user manual, I see
>
> - many warning messages such as:
>
> TeXmacs] Trying to create ecrm10.123pk from 300 dpi
> mktexpk: Mismatched mode ljfour and resolution 300; ignoring mode.
> mktexpk: Running mf-nowin -progname=mf \mode:=cx; mag:=123/300; nonstopmode; input ecrm10
>
> They seem harmless, but texmacs should avoid them if possible.
>
With texmacs 1.0.7.9 and TL 2009 I see the following messages on
screen:
hille@sid:~ $ texmacs
Welcome to TeXmacs 1.0.7.9
------------------------------------------------------------------------------
Since this seems to be the first time you have run this
version of TeXmacs, I will first analyze your system
in order to set up some TeX paths in the correct way.
This may take some seconds; the result can be found in
/home/hille/.TeXmacs/system/settings.scm
------------------------------------------------------------------------------
TeXmacs] kpsepath works with your TeX distribution
TeXmacs] kpsewhich works with your TeX distribution
TeXmacs] mktextfm works with your TeX distribution
TeXmacs] mktexpk works with your TeX distribution
TeXmacs] texhash works with your TeX distribution
!!!
TeXmacs] Trying to create ecrm10.123pk from 300 dpi
TeXmacs] Metafont works with 300 dpi ec-fonts
!!!
------------------------------------------------------------------------------
Installation completed successfully !
I will now start up the editor
------------------------------------------------------------------------------
TeXmacs] With linked TrueType support
TeXmacs] Loading corktounicode
TeXmacs] Loading unicode-cork-oneway
TeXmacs] Loading tmuniversaltounicode
TeXmacs] Loading unicode-symbol-oneway
At least our part of the problem (the warnings above) seems to be
solved. Can we close *this* bug?
Thanks,
Hilmar
--
sigmentation fault
Reply to: