COMPGROUPS.NET | Search | Post Question | Groups | Stream | About | Register

### \usepackage{Times}

• Email
• Follow

I need to use this package.  The version I have consists of just:

\renewcommand{\rmdefault}{ptm}
\renewcommand{\sfdefault}{phv}
\renewcommand{\ttdefault}{pcr}

I don't remember where I got it from (it isn't in my standard
distribution, which is quite old).

Using the package makes the text somewhat compacter, but not by much.

For now, it's good enough, but sometime I want to understand everything;
that could be now if it is quick or later if things are more
complicated.

I get the following warnings:

LaTeX Font Warning: Font shape OT1/ptm/m/n' undefined
(Font)              using OT1/cmr/m/n' instead on input line 88.

LaTeX Font Warning: Font shape OT1/ptm/bx/n' undefined
(Font)              using OT1/ptm/m/n' instead on input line 97.

LaTeX Font Warning: Font shape OT1/ptm/m/it' undefined
(Font)              using OT1/ptm/m/n' instead on input line 97.

but no other warnings.  Is there a QUICK fix to get rid of these
warnings?

As I said, I can live with them for now, but would like to get rid of
them as soon as is practical.


 0
Reply helbig (5078) 12/3/2011 5:16:21 PM

See related articles to this posting

helbig@astro.multiCLOTHESvax.de (Phillip Helbig---undress to reply)
writes:

> Is there a QUICK fix to get rid of these warnings?

Switch from OT1 to T1 font encoding by

\usepackage[T1]{fontenc}

BTW: 'times' is obsolete. It has been superseded by 'mathptmx'.

--
Uwe

 0
Reply usenet1161 (95) 12/3/2011 5:30:27 PM

In article <848vmtpnpo.fsf@siart.de>, Uwe Siart <usenet@siart.de> writes:

> Switch from OT1 to T1 font encoding by
>
> \usepackage[T1]{fontenc}
>

I get the same warnings.

> BTW: 'times' is obsolete. It has been superseded by 'mathptmx'.

Apparently some journals still use it.

Looks like there is no quick solution; perhaps I should put it on the
back burner.


 0
Reply helbig (5078) 12/3/2011 5:58:34 PM

Am Sat, 3 Dec 2011 17:16:21 +0000 (UTC) schrieb Phillip

> I need to use this package.  The version I have consists of just:
>
>    \renewcommand{\rmdefault}{ptm}
>    \renewcommand{\sfdefault}{phv}
>    \renewcommand{\ttdefault}{pcr}

> I get the following warnings:
>
>    LaTeX Font Warning: Font shape OT1/ptm/m/n' undefined
>    (Font)              using OT1/cmr/m/n' instead on input line 88.

You don't have the file OT1ptm.fd (or it is corrupted). The file is
part of the psnfss package.

> As I said, I can live with them for now,

Well I couldn't. If I would load in a document the times package to
use the times fonts I would not like it if they were replaced by the
cm-fonts. ;-)

--
Ulrike Fischer

 0
Reply news36084 (710) 12/3/2011 6:23:28 PM

In article <1sebve9nxu5hq.dlg@nililand.de>, Ulrike Fischer
<news3@nililand.de> writes:

> You don't have the file OT1ptm.fd (or it is corrupted). The file is
> part of the psnfss package.

OK.  Big change needed.  No time now.

> > As I said, I can live with them for now,
>
> Well I couldn't. If I would load in a document the times package to
> use the times fonts I would not like it if they were replaced by the
> cm-fonts. ;-)

I'm not the actual end-user.  As long as it gets processed OK at the
other end, that's good enough for now.

Why is the text nevertheless somewhat more compact?


 0
Reply helbig (5078) 12/3/2011 6:33:08 PM

In article <1sebve9nxu5hq.dlg@nililand.de>, Ulrike Fischer
<news3@nililand.de> writes:

> > I need to use this package.  The version I have consists of just:
> >
> >    \renewcommand{\rmdefault}{ptm}
> >    \renewcommand{\sfdefault}{phv}
> >    \renewcommand{\ttdefault}{pcr}
>
> > I get the following warnings:
> >
> >    LaTeX Font Warning: Font shape OT1/ptm/m/n' undefined
> >    (Font)              using OT1/cmr/m/n' instead on input line 88.
>
> You don't have the file OT1ptm.fd (or it is corrupted). The file is
> part of the psnfss package.
>
> > As I said, I can live with them for now,
>
> Well I couldn't. If I would load in a document the times package to
> use the times fonts I would not like it if they were replaced by the
> cm-fonts. ;-)

Maybe I can't.  :-(

I have a LaTeX setup which is about 12 years old.  I recently added some
more modern .cls files and everything works fine, except for the problem
above.

Upgrading is on the list of things to do, but I need a quick solution
now.

How much trouble would it be to get the times package (I know it's
obsolete, but I need to use it now) working properly, avoiding the
warnings above, which presumably means getting psnfss working properly
as well?


 0
Reply helbig (5078) 12/3/2011 8:15:25 PM

In article <jbe00t$fq3$1@online.de>, helbig@astro.multiCLOTHESvax.de
(Phillip Helbig---undress to reply) writes:

> In article <1sebve9nxu5hq.dlg@nililand.de>, Ulrike Fischer
> <news3@nililand.de> writes:

> > You don't have the file OT1ptm.fd (or it is corrupted). The file is
> > part of the psnfss package.
>
> How much trouble would it be to get the times package (I know it's
> obsolete, but I need to use it now) working properly, avoiding the
> warnings above, which presumably means getting psnfss working properly
> as well?

Here are all the relevant warnings:

LaTeX Font Warning: Font shape OT1/ptm/m/n' undefined
(Font)              using OT1/cmr/m/n' instead on input line 103.

LaTeX Font Warning: Font shape OT1/ptm/bx/n' undefined
(Font)              using OT1/ptm/m/n' instead on input line 112.

LaTeX Font Warning: Font shape OT1/ptm/m/it' undefined
(Font)              using OT1/ptm/m/n' instead on input line 112.

LaTeX Font Warning: Font shape OMS/ptm/m/n' undefined
(Font)              using OMS/cmsy/m/n' instead on input line 237.

LaTeX Font Warning: Font shape OT1/pcr/m/n' undefined
(Font)              using OT1/cmr/m/n' instead on input line 351.

Some questions:

Are all the fonts involved (requested and substituted) scalable fonts
(i.e. PS type 1 or Truetype), are some bitmap fonts (type 3), or does
one need more information in order to tell?

If there are no bitmap fonts involved, and since in some cases some
other substitution within ptm is done rather than substituting something
from cm, which presumably means that some (most?) of the ptm stuff is
working, how easy would it be, as a hotfix, to copy some .fd files (and
maybe something else) to the directory where the .tex file is to tide me
over until I can get the entire installation properly upgraded?


 0
Reply helbig (5078) 12/3/2011 8:52:43 PM

On Sat, 3 Dec 2011 20:15:25 +0000 (UTC), Phillip Helbig
> In article <1sebve9nxu5hq.dlg@nililand.de>, Ulrike Fischer
><news3@nililand.de> writes:
>
>> > I need to use this package.  The version I have consists of just:
>> >
>> >    \renewcommand{\rmdefault}{ptm}
>> >    \renewcommand{\sfdefault}{phv}
>> >    \renewcommand{\ttdefault}{pcr}
>>
>> > I get the following warnings:
>> >
>> >    LaTeX Font Warning: Font shape OT1/ptm/m/n' undefined
>> >    (Font)              using OT1/cmr/m/n' instead on input line 88.
>>
>> You don't have the file OT1ptm.fd (or it is corrupted). The file is
>> part of the psnfss package.
>>
> How much trouble would it be to get the times package (I know it's
> obsolete, but I need to use it now) working properly, avoiding the
> warnings above, which presumably means getting psnfss working properly
> as well?

http://mirrors.ctan.org/macros/latex/required/psnfss/lw35nfss.zip

and extract it at the root of a local or personal texmf tree. Then
update the data base of file names, as in

% texhash \$HOME/texmf

Bob T.

 0
Reply BobT (1484) 12/3/2011 10:02:52 PM

Am Sat, 3 Dec 2011 20:15:25 +0000 (UTC) schrieb Phillip

>>> I get the following warnings:

>>>    LaTeX Font Warning: Font shape OT1/ptm/m/n' undefined
>>>    (Font)              using OT1/cmr/m/n' instead on input line 88.

>> You don't have the file OT1ptm.fd (or it is corrupted). The file is
>> part of the psnfss package.

>>> As I said, I can live with them for now,

>> Well I couldn't. If I would load in a document the times package to
>> use the times fonts I would not like it if they were replaced by the
>> cm-fonts. ;-)
>
> Maybe I can't.  :-(
>
> I have a LaTeX setup which is about 12 years old.  I recently added some
> more modern .cls files and everything works fine, except for the problem
> above.
>
> Upgrading is on the list of things to do, but I need a quick solution
> now.

> How much trouble would it be to get the times package (I know it's
> obsolete, but I need to use it now)

times is not obsolete. It is a bit dump as it simply changes the
text fonts to times, helvet and courier (and doesn't try to correct
like mathptmx also the math fonts). And the font mix is a bit
dubious.

> working properly, avoiding the warnings above, which presumably
> means getting psnfss working properly as well?

Well beside lw35nfss.zip mentioned by you need to tell dvips or
pdflatex or whatever you are using about the fonts themselves with a
map-file. You can either use psnfss.map which is in the
psnfss-package. With this map the fonts will *not* be embedded in
the ps or pdf-file you are generating. It is up to the viewer
(ghostscript/pdf-viewer) to find and use the correct fonts.

You can also install the fonts themselves, e.g. the urw-clones which
you can find in urw/base35.zip. I don't know where the accompaigning
map-file is hidden on CTAN. miktex uses a file named ps2pk35.map in
this case.

I have no idea how you can add map-files to your old system. I doubt
that updmap already existed at this time. Probably you will have to
add them manually to the various configuration files of dvips,
pdftex, etc.

--
Ulrike Fischer

 0
Reply news36084 (710) 12/4/2011 11:03:54 AM

On 2011-12-03, Phillip Helbig---undress to reply wrote:
> In article <848vmtpnpo.fsf@siart.de>, Uwe Siart <usenet@siart.de> writes:

>> Switch from OT1 to T1 font encoding by

>> \usepackage[T1]{fontenc}

> I get the same warnings.

The *same* or similar?

* If the warning still tells OT1 fonts not found, the font encoding
switch came too late. (Provide a minimal example)

* If the warning is similar (with T1 in place of OT1), it seems you miss the
actual fonts (or the correct setup).

> Looks like there is no quick solution; perhaps I should put it on the
> back burner.

Günter

 0
Reply milde1 (94) 12/7/2011 1:13:25 PM

9 Replies
31 Views

Similar Articles

12/8/2013 12:59:45 PM
page loaded in 41404 ms. (0)