[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#355084: marked as done (lmodern: does not work anymore)

Your message dated Mon, 06 Mar 2006 18:21:17 +0100
with message-id <87lkvnjxpu.fsf@florent.maison>
and subject line Bug#355084: lmodern: does not work anymore
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: lmodern
Version: 0.99.3-2
Severity: important

Hi there.

I'm using etch in my own computer and, as I was going to update the
documentation of the algorithms package for a new CTAN upload, I
discovered that something very, very wrong has been happening here with
lmodern.

As I use etch, I'm currently using teTeX 3 and I'm usually working
without any problems with my system. Unfortunately, in one of the
updates, it seems that lmodern got hosed and I even tried to grab the
lmodern version from unstable to see if things worked better, but,
apparently, they didn't.

Here is the output that I get with a simple document:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
rbrito@dumont:~/doc/math$ xdvi short
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 ec-lmr12
mktexpk: don't know how to create bitmap font for ec-lmr12.
kpathsea: Appending font creation commands to missfont.log.
xdvi: Can't find pixel font ec-lmr12; using cmr10 instead at 600 dpi.
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 ec-lmr17
mktexpk: don't know how to create bitmap font for ec-lmr17.
xdvi: Can't find pixel font ec-lmr17; using cmr10 instead at 600 dpi.
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 ec-lmr10
mktexpk: don't know how to create bitmap font for ec-lmr10.
xdvi: Can't find pixel font ec-lmr10; using cmr10 instead at 600 dpi.
xdvi.bin: Warning: Character 233 not defined in font cmr10
xdvi.bin: Warning: Character 233 not defined in font cmr10
xdvi.bin: Warning: Character 243 not defined in font cmr10
xdvi.bin: Warning: Character 255 not defined in font cmr10
rbrito@dumont:~/doc/math$ 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I'm attaching the short text that I tried to compile, just to see if you
can reproduce the problem.

I know almost nothing regarding fonts in LaTeX and I would appreciate
any help here.


Thanks, Rogério Brito.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16-rc5-1
Locale: LANG=C, LC_CTYPE=pt_BR (charmap=ISO-8859-1)

Versions of packages lmodern depends on:
ii  defoma                    0.11.8-0.1     Debian Font Manager -- automatic f
ii  tex-common                0.15           Common infrastructure for using an
ii  xutils                    6.9.0.dfsg.1-4 X Window System utility programs

lmodern recommends no packages.

-- no debconf information

-- 
Rogério Brito : rbrito@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat:  http://freshmeat.net/projects/algorithms/

\documentclass{article}

\usepackage[latin1]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{lmodern}

\title{Just a Small Test}
\author{Rogério Brito}

\begin{document}
\maketitle

This is just a test.
Das ist ein Test.
Este é só um teste.

I need accents in my texts and it would be really nice if I also got the
German character ``ß'' in my output (if possible).
\end{document}

Attachment: short.dvi
Description: TeX dvi file


--- End Message ---
--- Begin Message --- 
Rogério Brito <rbrito@ime.usp.br> wrote:

> I guess that we can close the bug now.

Which is what I'm doing right now.

-- 
Florent

--- End Message ---
Reply to: