Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

CTAN package upload: The Comprehensive LaTeX Symbol List

5 views
Skip to first unread message

Jim Hefferon

unread,
Sep 25, 2003, 1:33:22 PM9/25/03
to ctan...@dante.de
A package has been updated on tug.ctan.org and it should spread
to your favorite mirror in a day or two.

Thanks for the material,
Jim Hefferon

==================================================================

The following information was provided by our fellow contributor.

Name of contribution: The Comprehensive LaTeX Symbol List
Author's name: Scott Pakin
Suggested location on CTAN: info/symbols/comprehensive
Summary description: An organized list of thousands of symbols available to LaTeX
License type: lppl

Announcement text given by the contribution's author:
- ----------------------------------------------------------------------
The Comprehensive LaTeX Symbols List is an organized
list of over 2500 symbols commonly available to LaTeX
users. Some of these symbols are guaranteed to be
available in every TeX distribution. Others require
font files that come with some, but not all, TeX
distributions. The rest require font files that must
be downloaded explicitly from CTAN and installed. The
Comprehensive LaTeX Symbols List currently showcases
symbols from 72 separate typefaces.
- ----------------------------------------------------------------------

Bob Tennent

unread,
Sep 27, 2003, 9:29:40 AM9/27/03
to
On 25 Sep 2003 19:33:22 +0200, Jim Hefferon wrote:

> Name of contribution: The Comprehensive LaTeX Symbol List
> Author's name: Scott Pakin
> Suggested location on CTAN: info/symbols/comprehensive
> Summary description: An organized list of thousands of symbols
> available to LaTeX

Has anyone else had trouble printing this? The PDF version (produced
by pdftex) is unprintable because about 20 pages in it both crash
ghostscript (version 7.05) and fail to print on an HP Postscript
printer. The Postscript version is rendered by ghostscript but fails
to print on the Postscript printer. I was finally able to print it by
pre-rendering it using ghostscript and replacing the type 1 fonts by
type 3 fonts. I've emailed Scott Pakin about this but have had no reply.

Bob T.

Harald Harders

unread,
Sep 27, 2003, 11:44:04 AM9/27/03
to

Here, I cannot print the files either. If I compile the list for
myself, I get a file with only 62 pages.

Yours
Harald

--
Harald Harders Langer Kamp 8
Institut für Werkstoffe D-38106 Braunschweig
Technische Universität Braunschweig Germany
E-Mail: h.ha...@tu-bs.de Tel: +49 (5 31) 3 91-3062
WWW : http://www.tu-bs.de/institute/ifw/ Fax: +49 (5 31) 3 91-3058

Maurizio Loreti

unread,
Sep 29, 2003, 4:02:20 AM9/29/03
to
Maurizio Loreti <m...@foobar.it> writes:

> Bob Tennent <Bo...@cs.queensu.ca> writes:
>
> > Has anyone else had trouble printing this?
>

> Yes. The PostScript version, with Ghostscript 8.11.

I mean --- I have printed all without trouble.

--
Maurizio Loreti http://www.pd.infn.it/~loreti/mlo.html
Dept. of Physics, Univ. of Padova, Italy ROT13: ybe...@cq.vasa.vg

Maurizio Loreti

unread,
Sep 29, 2003, 3:49:32 AM9/29/03
to
Bob Tennent <Bo...@cs.queensu.ca> writes:

> Has anyone else had trouble printing this?

Yes. The PostScript version, with Ghostscript 8.11.

--

Harald Harders

unread,
Sep 29, 2003, 5:00:44 AM9/29/03
to
On 29 Sep 2003 10:02:20 +0200, Maurizio Loreti wrote:
> Maurizio Loreti <m...@foobar.it> writes:
>
>> Bob Tennent <Bo...@cs.queensu.ca> writes:
>>
>> > Has anyone else had trouble printing this?
>>
>> Yes. The PostScript version, with Ghostscript 8.11.
>
> I mean --- I have printed all without trouble.

You have printed with gs 8.11 on a non-postscript printer? This is
not surprising for me because the viewing on screen works here, too.
It means, gs understands the postscript. But our postscript printer
does not understand the file.

Maurizio Loreti

unread,
Sep 29, 2003, 6:16:48 AM9/29/03
to
Harald Harders <h.ha...@tu-bs.de> writes:

> You have printed with gs 8.11 on a non-postscript printer?

Viewed with gv, sent by gv with 'lpr ...' on a PostScript printer.
Hewlett-Packard Laserjet 4 100-DTN, FWIW.

Bob Tennent

unread,
Sep 29, 2003, 7:31:28 AM9/29/03
to
On 29 Sep 2003 12:16:48 +0200, Maurizio Loreti wrote:

>> You have printed with gs 8.11 on a non-postscript printer?
>
> Viewed with gv, sent by gv with 'lpr ...' on a PostScript printer.
> Hewlett-Packard Laserjet 4 100-DTN, FWIW.

This might be sending type 3 fonts (pre-rendered by gs from the type 1
fonts embedded in the original document). What happens if you just

% lpr symbols-*.ps

without using gv/gs?

Bob T.

Maurizio Loreti

unread,
Sep 29, 2003, 8:25:23 AM9/29/03
to
Bob Tennent <Bo...@cs.queensu.ca> writes:

It prints 91 pages ...

Bob Tennent

unread,
Sep 29, 2003, 11:45:46 AM9/29/03
to
On 29 Sep 2003 14:25:23 +0200, Maurizio Loreti wrote:
>> What happens if you just
>>
>> % lpr symbols-*.ps
>>
>> without using gv/gs?
>
> It prints 91 pages ...

... of the 98 pages in the document.

Since posting here, I've received a reply from Scott Pakin, which I'll
attach because it may be of more general interest:

I just tried it and you're right; it doesn't print with either
acroread, xpdf, or gv. I was, however, able to print the document from
Windows using the (commercial) Adobe Acrobat Professional.

I upgraded to the latest pdfTeX (1.11a) but that didn't fix the
problem. I had a little more success using latex+dvipdfm instead
of pdflatex but I need to verify that it included all of the fonts
properly. I also had some success printing the original PDF to a
PostScript file using Acrobat Professional and converting it back to
PDF with Distiller, so I suppose I could go that route, too.

It's a tedious problem to track as I don't even know if the problem is
the total number of fonts in the document, the total number of fonts
(or characters within a font) on a given page, or if there's just one
particular font that's poorly implemented and is screwing up the rest
of the document. I haven't yet been able to produce a minimal subset
of the document that fails to print. If I don't solve the problem
soon, I suppose I'll upload a workaround version of the symbol list
manually converted with the commercial Adobe tools.

It sure is puzzling what the problem could be. If you can think of any
build options you'd like me to try, let me know.

Bob T.

Maurizio Loreti

unread,
Sep 30, 2003, 2:08:46 AM9/30/03
to
Bob Tennent <Bo...@cs.queensu.ca> writes:

> On 29 Sep 2003 14:25:23 +0200, Maurizio Loreti wrote:
> >> What happens if you just
> >>
> >> % lpr symbols-*.ps
> >>
> >> without using gv/gs?
> >
> > It prints 91 pages ...
>
> ... of the 98 pages in the document.

I don't understand. The last page, numbered "91", is the last page of
the index; the last line of the last column says that the symbol
\zugzwang may be found at page 54. The document has 91 pages, and not
98. Are you sure you are speaking about the version "18 September
2003"?

Robin Fairbairns

unread,
Sep 30, 2003, 4:40:52 AM9/30/03
to
Maurizio Loreti <m...@foobar.it> writes:
>Bob Tennent <Bo...@cs.queensu.ca> writes:
>> On 29 Sep 2003 14:25:23 +0200, Maurizio Loreti wrote:
>> >> What happens if you just
>> >>
>> >> % lpr symbols-*.ps
>> >>
>> >> without using gv/gs?
>> >
>> > It prints 91 pages ...
>>
>> ... of the 98 pages in the document.
>
>I don't understand. The last page, numbered "91", is the last page of
>the index; the last line of the last column says that the symbol
>\zugzwang may be found at page 54. The document has 91 pages, and not
>98. Are you sure you are speaking about the version "18 September
>2003"?

91pp in the a4 version, 98pp in the american letter-paper version.

fwiw, both versions read ok in my acrobat reader under linux (v5.00,
it says here), so the problems are most likely to do with people
rashly using current reader (;-). (there have been other problems
with it with tex-produced files in the past, iirc.)
--
Robin (the partially spineless) Fairbairns, Cambridge

Bob Tennent

unread,
Sep 30, 2003, 7:25:43 AM9/30/03
to
On 30 Sep 2003 08:40:52 GMT, Robin Fairbairns wrote:

> fwiw, both versions read ok in my acrobat reader under linux

Have you tried *printing* the document?

John Collins

unread,
Sep 30, 2003, 10:53:43 AM9/30/03
to
Robin Fairbairns wrote:
>
> fwiw, both versions read ok in my acrobat reader under linux (v5.00,
> it says here), so the problems are most likely to do with people
> rashly using current reader (;-). (there have been other problems
> with it with tex-produced files in the past, iirc.)

However, some of the reported problems are also about the postscript
files.
Here are my results:

1. Send the Postscript file symbols-letter.ps direct to an old LaserJet
4M printer. This is a postscript printer. Absolutely nothing comes
out.
(I sent the file direct to the printer, so no
ghostview/script/acroread/UNIX-printer-queue processing is involved.)
Files I generate from TeX files with dvips and standard fonts uniformly
print with no problems on the same printer.

2. But when I send the same file to a LaserJet 8000DN, I get all 98
pages with no visible problems.

Conclusion: The problems are not caused by acroread, gv, or gs.

John Collins
Penn State

Harald Harders

unread,
Sep 30, 2003, 12:22:42 PM9/30/03
to
On Tue, 30 Sep 2003 10:53:43 -0400, John Collins wrote:

> However, some of the reported problems are also about the postscript
> files.
> Here are my results:
>
> 1. Send the Postscript file symbols-letter.ps direct to an old LaserJet
> 4M printer. This is a postscript printer. Absolutely nothing comes
> out.
> (I sent the file direct to the printer, so no
> ghostview/script/acroread/UNIX-printer-queue processing is involved.)
> Files I generate from TeX files with dvips and standard fonts uniformly
> print with no problems on the same printer.
>
> 2. But when I send the same file to a LaserJet 8000DN, I get all 98
> pages with no visible problems.

This means, the real Adobe Postscript interpreter does not understand
the file while the Hewlett Packard Emulation does. I think, an
Adobe Interpreter should serve as reference if the files are okay.

Scott Pakin

unread,
Sep 30, 2003, 12:51:26 PM9/30/03
to
I believe I may have a workaround for the PDF printing problems with
the symbol list. I found that I can print fine from the commercial
Acrobat Professional 6.0 under Windows. Hence, I tried using that to
print to PDF from PDF. I'm now able to print the symbol list from
Acrobat Reader 5.0.8 under Linux.

I've uploaded new (29SEP2003) versions of the files to CTAN. Try
downloading the list in your favorite paper size, printing it, and
posting the outcome here. I'm eager to hear if others can print the
new document.

-- Scott

P.S. As it looks like the printing problem might lie with pdfTeX, when
I have time I'll see if I can diagnose the cause and give some feedback
to the pdfTeX crowd.

Felix Neubauer

unread,
Sep 30, 2003, 1:30:25 PM9/30/03
to
Harald Harders <h.ha...@tu-bs.de> wrote:
> On Tue, 30 Sep 2003 10:53:43 -0400, John Collins wrote:
>
>> However, some of the reported problems are also about the postscript
>> files.
>> Here are my results:
>>
>> 1. Send the Postscript file symbols-letter.ps direct to an old LaserJet
>> 4M printer. This is a postscript printer. Absolutely nothing comes
>> out.
>> [...]
>> 2. But when I send the same file to a LaserJet 8000DN, I get all 98
>> pages with no visible problems.
>
> This means, the real Adobe Postscript interpreter does not understand
> the file while the Hewlett Packard Emulation does. I think, an
> Adobe Interpreter should serve as reference if the files are okay.

I could print symbols-a4.ps without problems on my Apple LaserWriter.
It has an original Adobe PostScript interpreter. The file was
processed by the spooling system using pstops. Ghostscript choked on
page 52--either table 193 or table 194--while previewing.

With the pdf version the situation was the other way around. Viewing
worked perfectly with Acrobat 4 and 5.07 on Linux. While printing
from Acrobat 5 the printer choked on page 13 containing table 15 to
18 in the A4 version. Printing from Acrobat 4 even failed completely.

Yours
Felix
--
Felix Neubauer, felix.n...@gmx.de

0 new messages