Using CM fonts in OS X **independent of TeX**

  • Follow


I prepare PDFs on a MacBook running SnowLeopard, using TeXShop, pdftex, 
and Plain TeX from a vanilla installation of TUG's MacTeX 2010.  My 
understanding is that the Computer Modern fonts which go into those PDF 
files by default come from inside TeXLive's installation, and as they 
stand are not accessible to other apps or to Snow Leopard's Font Book.

Sometimes I want to edit or modify those PDF documents later on using 
Illustrator or other Mac apps.  For this and maybe other reasons, I'd 
like to have a separate installation of the same Computer Modern fonts 
in one of the regular Snow Leopard Font folders, so that they'd be 
accessible through Font Book (and would appear there with all the same 
individual font "crm9" and "cmbx10" type names), and be usable in all or 
most other Mac apps?

Is there a one-stop, one-or-two-step way to download and then 
drag-and-drop those fonts into one of Snow Leopard's Font folders, 
without having to run a bunch of conversion steps or operations?
(Free is good, but I'd pay a modest amount if necessary.)

If there is a way to do this, a step-by-step pointer on how to do so 
would be appreciated -- I find font procedures, and the numerous 
write-ups about them that I've looked at, extraordinarily confusing.
0
Reply AES 1/28/2011 7:10:42 PM

On Jan 28, 2:10=A0pm, AES <sieg...@stanford.edu> wrote:
> I prepare PDFs on a MacBook running SnowLeopard, using TeXShop, pdftex,
> and Plain TeX from a vanilla installation of TUG's MacTeX 2010. =A0My
> understanding is that the Computer Modern fonts which go into those PDF
> files by default come from inside TeXLive's installation, and as they
> stand are not accessible to other apps or to Snow Leopard's Font Book.
>
> Sometimes I want to edit or modify those PDF documents later on using
> Illustrator or other Mac apps. =A0For this and maybe other reasons, I'd
> like to have a separate installation of the same Computer Modern fonts
> in one of the regular Snow Leopard Font folders, so that they'd be
> accessible through Font Book (and would appear there with all the same
> individual font "crm9" and "cmbx10" type names), and be usable in all or
> most other Mac apps?
>
> Is there a one-stop, one-or-two-step way to download and then
> drag-and-drop those fonts into one of Snow Leopard's Font folders,
> without having to run a bunch of conversion steps or operations?
> (Free is good, but I'd pay a modest amount if necessary.)
>
> If there is a way to do this, a step-by-step pointer on how to do so
> would be appreciated -- I find font procedures, and the numerous
> write-ups about them that I've looked at, extraordinarily confusing.

I think you can get otf version of the Computer Modern fonts and put
them in your Fonts folder. These should then be available to Mac OSX
applications. I have not systematically checked to see if these are
"identical" to the ones available through TeX but I would guess they
are meant to be essentially the same.

http://sourceforge.net/projects/cm-unicode/files/

Good luck.

Tariq
0
Reply Tariq 1/28/2011 7:52:27 PM


On Jan 28, 2:52=A0pm, Tariq <tariq.per...@gmail.com> wrote:
> On Jan 28, 2:10=A0pm, AES <sieg...@stanford.edu> wrote:
>
>
>
> > I prepare PDFs on a MacBook running SnowLeopard, using TeXShop, pdftex,
> > and Plain TeX from a vanilla installation of TUG's MacTeX 2010. =A0My
> > understanding is that the Computer Modern fonts which go into those PDF
> > files by default come from inside TeXLive's installation, and as they
> > stand are not accessible to other apps or to Snow Leopard's Font Book.
>
> > Sometimes I want to edit or modify those PDF documents later on using
> > Illustrator or other Mac apps. =A0For this and maybe other reasons, I'd
> > like to have a separate installation of the same Computer Modern fonts
> > in one of the regular Snow Leopard Font folders, so that they'd be
> > accessible through Font Book (and would appear there with all the same
> > individual font "crm9" and "cmbx10" type names), and be usable in all o=
r
> > most other Mac apps?
>
> > Is there a one-stop, one-or-two-step way to download and then
> > drag-and-drop those fonts into one of Snow Leopard's Font folders,
> > without having to run a bunch of conversion steps or operations?
> > (Free is good, but I'd pay a modest amount if necessary.)
>
> > If there is a way to do this, a step-by-step pointer on how to do so
> > would be appreciated -- I find font procedures, and the numerous
> > write-ups about them that I've looked at, extraordinarily confusing.
>
> I think you can get otf version of the Computer Modern fonts and put
> them in your Fonts folder. These should then be available to Mac OSX
> applications. I have not systematically checked to see if these are
> "identical" to the ones available through TeX but I would guess they
> are meant to be essentially the same.
>
> http://sourceforge.net/projects/cm-unicode/files/
>
> Good luck.
>
> Tariq

Type 1 versions of these fonts also exist On TeXLive:
/usr/local/texlive/2010/texmf-dist/fonts/type1/public/amsfonts/cm/
cmr10.pfb
and
/usr/local/texlive/2010/texmf-dist/fonts/afm/public/amsfonts/cm/
cmr10.afm
If you can get down to the command line level you can find these fonts
and then move them to the directory where
they can be found. I don't use OS X so I am just guessing that this
can be done, since OS X is under the covers
BSD, an Unix clone.

John Culleton
0
Reply wexfordpress 1/28/2011 9:23:08 PM

Tariq <tariq.perwez@gmail.com> writes:

> On Jan 28, 2:10 pm, AES <sieg...@stanford.edu> wrote:
>> I prepare PDFs on a MacBook running SnowLeopard, using TeXShop, pdftex,
>> and Plain TeX from a vanilla installation of TUG's MacTeX 2010.  My
>> understanding is that the Computer Modern fonts which go into those PDF
>> files by default come from inside TeXLive's installation, and as they
>> stand are not accessible to other apps or to Snow Leopard's Font Book.
>>
>> Sometimes I want to edit or modify those PDF documents later on using
>> Illustrator or other Mac apps.  For this and maybe other reasons, I'd
>> like to have a separate installation of the same Computer Modern fonts
>> in one of the regular Snow Leopard Font folders, so that they'd be
>> accessible through Font Book (and would appear there with all the same
>> individual font "crm9" and "cmbx10" type names), and be usable in all or
>> most other Mac apps?
>>
>> Is there a one-stop, one-or-two-step way to download and then
>> drag-and-drop those fonts into one of Snow Leopard's Font folders,
>> without having to run a bunch of conversion steps or operations?
>> (Free is good, but I'd pay a modest amount if necessary.)
>>
>> If there is a way to do this, a step-by-step pointer on how to do so
>> would be appreciated -- I find font procedures, and the numerous
>> write-ups about them that I've looked at, extraordinarily confusing.
>
> I think you can get otf version of the Computer Modern fonts and put
> them in your Fonts folder.

TTF versions of Computer Modern Unicode and Latin Modern are already
included in TeX Live.  On OS X, you can activate them as follows:

1. Open the Font Book application
2. Hit Alt + Cmd + N to add a new library
3. Enter a sensible name, e.g., "TeX Live 2010"
4. Hit Cmd + O
5. Navigate to the directory where the TeX Live fonts are located, e.g.,
   /usr/local/texlive/2010/texmf-dist/fonts
6. Click Open
7. All fonts in the selected tree are added and can be used like any
   other font

-- 
Change “LookInSig” to “tcalveu” to answer by mail.
0
Reply Philipp 1/28/2011 9:50:37 PM

On 11-01-28 1:10 PM, AES wrote:

> Is there a one-stop, one-or-two-step way to download [TeX Computer Modern] and then
> drag-and-drop those fonts into one of Snow Leopard's Font folders,
> without having to run a bunch of conversion steps or operations?
> (Free is good, but I'd pay a modest amount if necessary.)

You can fetch Unicode OTF versions of these from here

   http://sourceforge.net/projects/cm-unicode/

Once you extracted the (oddly) compressed tarball, just drag all of the 
..otf files into Font Book.  Then they will be available to Pages, and 
pretty much everything else on the Mac.

I found that the downloaded tarball I got was compressed with something 
called xz, which was new to me.  Stuffit didn't know what to do with it, 
but I had xz installed through Macports already.

Other than that, this took just a few minutes, without requiring that I 
actually understand how fonts work on OS X (I don't).

Cheers,

-j


-- 
Jeffrey Goldberg          http://goldmark.org/jeff/
I rarely read HTML or poorly quoting posts
Reply-To address is valid
0
Reply Jeffrey 1/28/2011 9:56:07 PM

In message <8qgsboFadfU1@mid.individual.net> 
  Jeffrey Goldberg <nobody@goldmark.org> wrote:
> On 11-01-28 1:10 PM, AES wrote:

>> Is there a one-stop, one-or-two-step way to download [TeX Computer Modern] and then
>> drag-and-drop those fonts into one of Snow Leopard's Font folders,
>> without having to run a bunch of conversion steps or operations?
>> (Free is good, but I'd pay a modest amount if necessary.)

> You can fetch Unicode OTF versions of these from here

>    http://sourceforge.net/projects/cm-unicode/

> Once you extracted the (oddly) compressed tarball, just drag all of the 
> .otf files into Font Book.  Then they will be available to Pages, and 
> pretty much everything else on the Mac.

> I found that the downloaded tarball I got was compressed with something 
> called xz, which was new to me.  Stuffit didn't know what to do with it, 
> but I had xz installed through Macports already.

do you mean .gz? gnuzip is a perfectly ordinary zip compression, and is
what most every sourceforge download is compressed it. Also, the OS X
Archive Utility handles gz (and tar) just fine.

Stuffit is a steaming pile of monkey dung.

-- 
Personal isn't the same as important
0
Reply Lewis 1/29/2011 6:59:45 PM

On 11-01-29 12:59 PM, Lewis wrote:
> In message<8qgsboFadfU1@mid.individual.net>
>    Jeffrey Goldberg<nobody@goldmark.org>  wrote:

>> I found that the downloaded tarball I got was compressed with something
>> called xz, which was new to me.  Stuffit didn't know what to do with it,
>> but I had xz installed through Macports already.
>
> do you mean .gz?

Nope, I meant "xz".  I am very familiar with .gz, .bz2 and others. 
file(1) told me "Compressed data".  But I did find that I had 
/opt/local/bin/xz installed.  Here is more about it.

   http://tukaani.org/xz/

> gnuzip is a perfectly ordinary zip compression,

As long as we are being pedantic, .zip and .gz are not the same thing.

> and is what most every sourceforge download is compressed it.

I don't know why sf gave me a .xz.  I've always gotten gnuzipped stuff 
before.  Maybe the recent attacks against Sourceforge means that someone 
is maliciously tampering with users' download preferences.

> Also, the OS X Archive Utility handles gz (and tar) just fine.

But not .xz (I tried).  I also tried tar -zxvf ...

> Stuffit is a steaming pile of monkey dung.

I have to disagree.  I would say "putrid" instead of "steaming".

Cheers,

-j

-- 
Jeffrey Goldberg          http://goldmark.org/jeff/
I rarely read HTML or poorly quoting posts
Reply-To address is valid
0
Reply Jeffrey 1/29/2011 7:34:20 PM

On Sat, 29 Jan 2011 13:34:20 -0600, Jeffrey Goldberg wrote:
 >
 > Nope, I meant "xz".  I am very familiar with .gz, .bz2 and others. 
 > file(1) told me "Compressed data".  But I did find that I had 
 > /opt/local/bin/xz installed.  Here is more about it.
 >
 >    http://tukaani.org/xz/
 >
 >> Also, the OS X Archive Utility handles gz (and tar) just fine.
 >
 > But not .xz (I tried).  I also tried tar -zxvf ...

Try tar -Jxvf ...

man tar

Bob T.
0
Reply Bob 1/29/2011 9:54:49 PM

On 11-01-29 3:54 PM, Bob Tennent wrote:
> On Sat, 29 Jan 2011 13:34:20 -0600, Jeffrey Goldberg wrote:

>> I also tried tar -zxvf ...
>
> Try tar -Jxvf ...
>
> man tar

I had tried man tar, but the man page that came up (BSDtar) had no 
mention of anything other than -z for gzip.

Still, I know that I've used something else successfully for .bz2, so 
this could be one of the very many places where the man pages on OS X 
don't actually reflect the state of things installed.

Cheers,

-j


-- 
Jeffrey Goldberg          http://goldmark.org/jeff/
I rarely read HTML or poorly quoting posts
Reply-To address is valid
0
Reply Jeffrey 1/29/2011 10:03:39 PM

On Jan 29, 7:56=A0am, Jeffrey Goldberg <nob...@goldmark.org> wrote:
> On 11-01-28 1:10 PM, AES wrote:
>
> > Is there a one-stop, one-or-two-step way to download [TeX Computer Mode=
rn] and then
> > drag-and-drop those fonts into one of Snow Leopard's Font folders,
> > without having to run a bunch of conversion steps or operations?
> > (Free is good, but I'd pay a modest amount if necessary.)
>
> You can fetch Unicode OTF versions of these from here
>
> =A0 =A0http://sourceforge.net/projects/cm-unicode/
>
> Once you extracted the (oddly) compressed tarball, just drag all of the
> .otf files into Font Book. =A0Then they will be available to Pages, and
> pretty much everything else on the Mac.
>
> I found that the downloaded tarball I got was compressed with something
> called xz, which was new to me. =A0Stuffit didn't know what to do with it=
,
> but I had xz installed through Macports already.

I use the Unarchiver (http://wakaba.c3.cx/s/apps/unarchiver.html) to
extract things like this in Mac OS X. I can never remember the command
line options required for the various combinations.

xz compression is now used in TeX Live as well -- its advantage over
gz is that the files are smaller but the decompression times are
(slightly) longer. Considering the minor inconvenience of waiting an
extra fraction of a second, the bandwidth saved is worth real money.

Cheers,
Will
0
Reply Will 1/30/2011 2:09:09 AM

In article <8qjh5sFknU1@mid.individual.net>,
 Jeffrey Goldberg <nobody@goldmark.org> wrote:

> I had tried man tar, but the man page that came up (BSDtar) had no 
> mention of anything other than -z for gzip.
> 
> Still, I know that I've used something else successfully for .bz2, so 
> this could be one of the very many places where the man pages on OS X 
> don't actually reflect the state of things installed.

Following the original pointer to SourceForge.net (which I've now 
mislaid, but thanks to whoever posted it), I was able to download the 
desired fonts, which arrived in some form of 'tar-gz-something' format, 
which I've also forgotten, but whatever it was, Snow Leopard instantly 
and automatically opened and decompressed it.
0
Reply AES 1/30/2011 3:58:42 AM

Jeffrey Goldberg <nobody@goldmark.org> writes:

> On 11-01-29 3:54 PM, Bob Tennent wrote:
>> On Sat, 29 Jan 2011 13:34:20 -0600, Jeffrey Goldberg wrote:
>
>>> I also tried tar -zxvf ...
>>
>> Try tar -Jxvf ...
>>
>> man tar
>
> I had tried man tar, but the man page that came up (BSDtar) had no
> mention of anything other than -z for gzip.
>
> Still, I know that I've used something else successfully for .bz2, so
> this could be one of the very many places where the man pages on OS X
> don't actually reflect the state of things installed.

there's tar jxvf which uses .bz2

i hadn't found J, and i don't know of a letter for lzma (predecessor
of xz, what miktex uses).
-- 
Robin Fairbairns, Cambridge
my address is @cl.cam.ac.uk, regardless of the header.  sorry about that.
0
Reply Robin 1/30/2011 10:25:52 AM

AES <siegman@stanford.edu> writes:

>  Jeffrey Goldberg <nobody@goldmark.org> wrote:
>
>> I had tried man tar, but the man page that came up (BSDtar) had no 
>> mention of anything other than -z for gzip.
>> 
>> Still, I know that I've used something else successfully for .bz2, so 
>> this could be one of the very many places where the man pages on OS X 
>> don't actually reflect the state of things installed.
>
> Following the original pointer to SourceForge.net (which I've now 
> mislaid, but thanks to whoever posted it), I was able to download the 
> desired fonts, which arrived in some form of 'tar-gz-something' format, 
> which I've also forgotten, but whatever it was, Snow Leopard instantly 
> and automatically opened and decompressed it.

of course, you could have looked at ctan -- fonts/cm-unicode

but ctan's probably too complicated for your liking...
-- 
Robin Fairbairns, Cambridge
my address is @cl.cam.ac.uk, regardless of the header.  sorry about that.
0
Reply Robin 1/30/2011 10:28:26 AM

On Sun, 30 Jan 2011 10:25:52 +0000, Robin Fairbairns wrote:
 >
 >> On 11-01-29 3:54 PM, Bob Tennent wrote:
 >>>
 >>> Try tar -Jxvf ...
 >
 > there's tar jxvf which uses .bz2
 >
 > i hadn't found J

I don't know when -J was added but tar 1.22 has it (Fedora 13) and
tar 1.15 doesn't (CentOS 5.5).

Bob T.
0
Reply Bob 1/30/2011 3:13:09 PM

Jeffrey Goldberg <nobody@goldmark.org> writes:

> Cheers,
>
> -j

Yes, that (-j) is the option for bzip2 (SCNR), and is documented as such
in the man page.  XZ, however, is too new to be supported.  Some newer
Linux distros already support it, but not OS X.

-- 
Change “LookInSig” to “tcalveu” to answer by mail.
0
Reply Philipp 1/30/2011 5:59:29 PM

Bob Tennent <BobT@cs.queensu.ca> writes:

> On Sun, 30 Jan 2011 10:25:52 +0000, Robin Fairbairns wrote:
>  >
>  >> On 11-01-29 3:54 PM, Bob Tennent wrote:
>  >>>
>  >>> Try tar -Jxvf ...
>  >
>  > there's tar jxvf which uses .bz2
>  >
>  > i hadn't found J
>
> I don't know when -J was added

http://en.wikipedia.org/wiki/Xz
"Version 1.22 of GNU tar supports using this software to handle xz files
transparently"

-- 
Change “LookInSig” to “tcalveu” to answer by mail.
0
Reply Philipp 1/30/2011 6:01:14 PM

In message <8qj8dtF4t9U1@mid.individual.net> 
  Jeffrey Goldberg <nobody@goldmark.org> wrote:
> On 11-01-29 12:59 PM, Lewis wrote:
>> In message<8qgsboFadfU1@mid.individual.net>
>>    Jeffrey Goldberg<nobody@goldmark.org>  wrote:

>>> I found that the downloaded tarball I got was compressed with something
>>> called xz, which was new to me.  Stuffit didn't know what to do with it,
>>> but I had xz installed through Macports already.
>>
>> do you mean .gz?

> Nope, I meant "xz".  I am very familiar with .gz, .bz2 and others. 
> file(1) told me "Compressed data".  But I did find that I had 
> /opt/local/bin/xz installed.  Here is more about it.

Very odd. I downloaded the fonts and they were in a perfectly ordinary
..tar.gz file.

>    http://tukaani.org/xz/

>> gnuzip is a perfectly ordinary zip compression,

> As long as we are being pedantic, .zip and .gz are not the same thing.

Eh. Whatever. I consider all the LZW descendants to be zip in one for or
another.

>> and is what most every sourceforge download is compressed it.

> I don't know why sf gave me a .xz.  I've always gotten gnuzipped stuff 
> before.  Maybe the recent attacks against Sourceforge means that someone 
> is maliciously tampering with users' download preferences.

>> Also, the OS X Archive Utility handles gz (and tar) just fine.

> But not .xz (I tried).  I also tried tar -zxvf ...

>> Stuffit is a steaming pile of monkey dung.

> I have to disagree.  I would say "putrid" instead of "steaming".

Hmmm. you may be right on that.


-- 
Though it's cold and lonely in the deep dark night I can see paradise by
the dashboard light.
0
Reply Lewis 1/31/2011 2:09:51 AM

On 11-01-29 8:09 PM, Will Robertson wrote:

> I use the Unarchiver (http://wakaba.c3.cx/s/apps/unarchiver.html) to
> extract things like this in Mac OS X.

That looks great, thanks!

> xz compression is now used in TeX Live as well -- its advantage over
> gz is that the files are smaller but the decompression times are
> (slightly) longer. Considering the minor inconvenience of waiting an
> extra fraction of a second, the bandwidth saved is worth real money.

That makes very good sense. I just ran TeX Live Utility for the first 
time in a few weeks. Smaller files are definitely a good thing.

Cheers,

-j

-- 
Jeffrey Goldberg          http://goldmark.org/jeff/
I rarely read HTML or poorly quoting posts
Reply-To address is valid
0
Reply Jeffrey 1/31/2011 2:37:23 AM

Lewis <g.kreme@gmail.com.dontsendmecopies> writes:

>   Jeffrey Goldberg <nobody@goldmark.org> wrote:
>>> gnuzip is a perfectly ordinary zip compression,
>
>> As long as we are being pedantic, .zip and .gz are not the same thing.
>
> Eh. Whatever. I consider all the LZW descendants to be zip in one for or
> another.

gz was developed when lzw was still covered by its patent -- it was
designed specifically to replace lzw -- that it compressed better was
an agreeable side-effect.  (in the same movement, png was developed to
replace gif, which uses lzw, and was therefore dodgy from the patent.)

bz2 represents another sidestep.  i don't know where lzma and xz stand
by way of parentage.
-- 
Robin Fairbairns, Cambridge
my address is @cl.cam.ac.uk, regardless of the header.  sorry about that.
0
Reply Robin 1/31/2011 11:50:43 AM

18 Replies
300 Views

(page loaded in 0.19 seconds)

Similiar Articles:









7/23/2012 10:52:49 PM


Reply: