[Mac OS X TeX] TeXShop and BibTeX

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] TeXShop and BibTeX

Martin Stokhof


<x-flowed>Hi,

When I run BibTeX from TeXShop I invariably get the error message:
"Sorry--- you've exceeded BibTeX's buffer size 5000.

This occurs with jobs (files, style files, data files) that run without
a glitch under OS 9.1.
I've cut down the number of references in the source file to just a few
(two or three) and used a very small .bib file, but I still get the same
error.

Any hint of help would be much appreciated.
Martin Stokhof

-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------
</x-flowed>


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] TeXShop and BibTeX

Arthur E. Ogus


<x-flowed>I'm having the same trouble.  According to a local expert, the trouble
is the difference between LF (unix) and CR (Mac).  Bibtex expects
ASCII input which is limited to 1052 (?) characters per line.  If you
have a mac file, everything appears on the same line to unix.

I haven't experimented enough to be sure he is right.
--
Arthur Ogus

-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------
</x-flowed>


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] TeXShop and BibTeX

Gary L. Gray


<x-flowed>On 05/08/2001 at 8:27 AM -0700, Arthur Ogus wrote:

>I'm having the same trouble.  According to a local expert, the trouble
>is the difference between LF (unix) and CR (Mac).  Bibtex expects
>ASCII input which is limited to 1052 (?) characters per line.  If
>you have a mac file, everything appears on the same line to unix.
>
>I haven't experimented enough to be sure he is right.

I believe you are correct. If you have BBEdit, you can open the file
in BBEdit and save it as "UNIX" instead of "Macintosh" for line
breaks.
--
    Gary L. Gray
    Associate Professor
    Engineering Science & Mechanics
    Penn State University
    (814) 863-1778
    http://www.esm.psu.edu/Faculty/Gray/

-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------
</x-flowed>


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] TeXShop and BibTeX

William F. Adams
In reply to this post by Arthur E. Ogus


If it's Unix line endings which are the problem, there're lots of solutions.

There's a ``CRLF'' utility one can d/l from most sites for Mac OS

Or, one can just use the shell....

(from comp.linux.powerpc or some such)

Use tr.  Example:Mac line breaks -> UNIX line breaks:
  cat foobar.txt | tr '\r' '\n' > foobar2.txt
UNIX line breaks -> Mac line breaks:
  cat foobar.txt | tr '\n' '\r' > foobar2.txt

William

--
William Adams, publishing specialist
ATLIS Graphics & Design / 717-731-6707 voice / 717-731-6708 fax
Sphinx of black quartz, judge my vow.
http://members.aol.com/willadams

-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] TeXShop and BibTeX

Andreas Monitzer
In reply to this post by Arthur E. Ogus


<x-flowed>On Tuesday, May 8, 2001, at 05:27 , Arthur Ogus wrote:

> I'm having the same trouble.  According to a local expert, the trouble
> is the difference between LF (unix) and CR (Mac).  Bibtex expects
> ASCII input which is limited to 1052 (?) characters per line.  If you
> have a mac file, everything appears on the same line to unix.

To convert the file, use BBEdit or the following command in Terminal:

tr '\r' '\n' < "input file" > "output file"

(those files must not be the same)

andy
--
Discussion forthcoming.

-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------
</x-flowed>


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] TeXShop and BibTeX

Martin Stokhof
In reply to this post by Arthur E. Ogus


<x-flowed>
On Tuesday, May 8, 2001, at 05:27  PM, Arthur Ogus wrote:

> I'm having the same trouble.  According to a local expert, the trouble
> is the difference between LF (unix) and CR (Mac).  Bibtex expects
> ASCII input which is limited to 1052 (?) characters per line.  If you
> have a mac file, everything appears on the same line to unix.
>
> I haven't experimented enough to be sure he is right.
> -- Arthur Ogus
>
Thanks. Yes, he is right. I went back to 9.1 and opened both the .bib
file and the particular .bst file I was using (which wasn't one of the
.bst files in the standard distribution) in BBEdit and saved them with
the option "Unix line breaks". Back to OS X and TeXShop and everything
runs fine.

Which brings me to the following: I seem to remember that there is a
Unix script "mac2unix" that you can run in the command line to fix this
problem of different ways of coding the line breaks. However it seems to
be missing in OS X. Can anyone confirm its existence or even better,
tell me where I can find it?

Thanks again,
Martin Stokhof


-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------
</x-flowed>


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] malicious script sent to the mailing list?

William F. Adams


I just got a .scr file which clobbered our sysadmin's machine when I
sent it to him....

Here's the safe textual part of it...
        Received:  from taz (tnt2-164-196.cac.psu.edu [130.203.164.196])
by mail.atlis.com (8.7.5/8.6.12) with SMTP id LAA01857 for
<[hidden email]>; Tue, 8 May 2001 11:56:01 -0400 (EDT)
     Organization: Atlis Systems, Inc. - (301) 578-4200 - [hidden email]
            Date: Tue, 8 May 2001 11:56:01 -0400 (EDT)
      Message-ID: <[hidden email]>
            From: Hahaha <[hidden email]>
         Subject: Snowhite and the Seven Dwarfs - The REAL story!
    MIME-Version: 1.0
    Content-Type: multipart/mixed; boundary="--VE1EBG9IVWPQVWD2Z8TQR"
  X-Mozilla-Status: 9001
 X-Mozilla-Status2: 00000000
         X-UIDL: c2392d868c75aa35cf91333a1e600ade




Today, Snowhite was turning 18. The 7 Dwarfs always where very educated and
polite with Snowhite. When they go out work at mornign, they promissed a
*huge* surprise. Snowhite was anxious. Suddlently, the door open, and
the Seven
Dwarfs enter...

So if you're running Windows, if you can, delete it.

William
--
William Adams, publishing specialist
ATLIS Graphics & Design / 717-731-6707 voice / 717-731-6708 fax
Sphinx of black quartz, judge my vow.
http://members.aol.com/willadams

-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] TeXShop and BibTeX

Martin Stokhof
In reply to this post by Martin Stokhof


<x-flowed>Thanks everybody: you guys are so quick that you even answered my second
question before I posted it.
I installed fixm (I'm sure the other suggestions work too) and can now
use all my old files without problems.

Martin Stokhof

-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------
</x-flowed>


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] TeXShop and BibTeX

Arthur E. Ogus


<x-flowed>Where do you get fixm?
--
Arthur Ogus

-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------
</x-flowed>


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] \cite question

Oliver Hardt


<x-flowed>i'd like to cite all articles in the .bib of one author: "... Smith and
colleagues demonstrated (Smith, 1980; Smith, 1981; Smith & John,
1990) ...".  In my .bib, the keys are constructed of the first authors
name and year of publication (e.g. Smith:1980).  How can i use \cite to
list all Smith* entries (\cite{Smith*} doesn't work).  Thanks.  Olli.

-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------
</x-flowed>


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] TeXShop and BibTeX

Martin Stokhof
In reply to this post by Arthur E. Ogus
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 131 bytes
Desc: not available
Url : http://email.esm.psu.edu/pipermail/macosx-tex/attachments/20010508/71a02174/attachment.bin
Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] TeXShop and BibTeX

Thomas Kiffe
In reply to this post by Martin Stokhof


I haven't looked at other scripts but here are two simple shell scripts I use for converting between Mac and Unix linebreaks.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
#
# mac2unix.sh
# convert Mac linebreaks to Unix linebreaks
foreach f ($argv[*])
        mv $f $f.mac
        cat $f.mac | tr "\r" "\n" > $f
end
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
If you run

mac2unix.sh foo.tex

the script will save foo.tex as foo.tex.mac and then convert linebreaks.
When you are finished fo.tex will have Unix file breaks. If you type

mac2unix.sh *

the script will convert all the files in the current directory.

For the reverse we have
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
#
# unix2mac.sh
# convert Unix linebreaks to Mac linebreaks
foreach f ($argv[*])
        mv $f $f.unix
        cat $f.unix | tr "\n" "\r" > $f
end
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Save each of these snippets in a separate file (with Unix linebreaks,
a Catch22 situation). In the Terminal type

chmod 744 unix2mac.sh
chmod 744 mac2unix.sh

to make them executable and move them to your local bin. Type "rehash" and you can use them from the Terminal anywhere on your system.

Apple, in its infinite wisdom, decided a long time ago to make \r the
linebreak character on a Mac. Unix uses \n and Windows uses both. Since we
now have a hybrid system of Mac and Unix this is going to present numerous
little problems. Some of the TeX programs were designed to read both Mac
and Unix linebreaks. Bibtex and dvips, as generally distributed, do not.
Fortunately ghostscript does. If you begin to see unexpected behavior when
running a Unix program, linebreaks is one of the first things you should check.

I have been very careful with CMacTeX to make sure that it will handle both
Mac and Unix linebreaks. If anyone encounters this problem with one of my
programs, let me know so I can correct it.


>On Tuesday, May 8, 2001, at 05:27  PM, Arthur Ogus wrote:
>
>> I'm having the same trouble.  According to a local expert, the trouble
>> is the difference between LF (unix) and CR (Mac).  Bibtex expects
>> ASCII input which is limited to 1052 (?) characters per line.  If you have a mac file, everything appears on the same line to unix.
>>
>> I haven't experimented enough to be sure he is right.
>> -- Arthur Ogus
>>
>Thanks. Yes, he is right. I went back to 9.1 and opened both the .bib file and the particular .bst file I was using (which wasn't one of the .bst files in the standard distribution) in BBEdit and saved them with the option "Unix line breaks". Back to OS X and TeXShop and everything runs fine.
>
>Which brings me to the following: I seem to remember that there is a Unix script "mac2unix" that you can run in the command line to fix this problem of different ways of coding the line breaks. However it seems to be missing in OS X. Can anyone confirm its existence or even better, tell me where I can find it?
>


-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------


Reply | Threaded
Open this post in threaded view
|

[Mac OS X TeX] Updated CMacTeX

Thomas Kiffe
In reply to this post by Martin Stokhof


I posted an updated cmactex_osx.sit this noon. All that changed is setup.
It now allows you to have three default texmf trees. The first one searched
is called texmflocal and it must contain the files specific to CMacTeX. The
second is tetexlocal, your local teTeX texmf tree. The last is texmf itself.
All three of these can be symlinks but they must reside in the same folder
as the binaries folder. You can override this default behavior by recording
your search paths in a file and having setup read this file to set search
paths. Read the default_osx.paths file carefully to see just how to do this.
CMacTeX does not read texmf.cnf to get search paths.

If you downloaded cmactex_osx.sit before this noon (U.S. Central Daylight Time)
you only have to download setup.sit. The url is
http://www.kiffe.com/tex/programs/setup.sit.bin.

Tom Kiffe

-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <[hidden email]> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <[hidden email]> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------