Date: Fri, 23 Nov 2001 20:00:01 -0500
Subject: MacOSX-TeX Digest #161 - 11/23/01
From: "TeX on Mac OS X Mailing List"
To: "TeX on Mac OS X Mailing List"
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Sender:
Precedence: Bulk
List-Software: LetterRip Pro 3.0.7 by Fog City Software, Inc.
List-Subscribe:
List-Digest:
List-Unsubscribe:
MacOSX-TeX Digest #161 - Friday, November 23, 2001
put files in bundles?
by "J.Huelsmann"
RE: [Mac OS X TeX] put files in bundles?
by "Maarten Sneep"
Re: [Mac OS X TeX] put files in bundles?
by "Bruno Voisin"
Re: [Mac OS X TeX] put files in bundles?
by "Maarten Sneep"
Re: [Mac OS X TeX] put files in bundles?
by "Bruno Voisin"
Mac font encodings for ConTeXt?
by "Harri Hakula"
Re: [Mac OS X TeX] put files in bundles?
by "J.Huelsmann"
Re: MacOSX-TeX Digest #159 - 11/21/01
by "Charles Bouldin"
----------------------------------------------------------------------
Subject: put files in bundles?
From: "J.Huelsmann"
Date: Fri, 23 Nov 2001 11:19:04 +0100
I wonder if it would be a good option (for TeXShop) to save all the
files generated on a typesetting-run into a MacOS X bundle, so one
would see only one single "file" in the Finder with the .tex .pdf
..aux .log etc. files inside.
So moving and renaming of this entire bunch would be very simple and
TeX associated documents would be very nice organized.
What do you think about this?
--Jan--
----------------------------------------------------------------------
Subject: RE: [Mac OS X TeX] put files in bundles?
From: "Maarten Sneep"
Date: Fri, 23 Nov 2001 11:34:43 +0100 (CET)
On 23-Nov-01 J.Huelsmann wrote:
# I wonder if it would be a good option (for TeXShop) to save all the
# files generated on a typesetting-run into a MacOS X bundle, so one
# would see only one single "file" in the Finder with the .tex .pdf
# .aux .log etc. files inside.
# So moving and renaming of this entire bunch would be very simple and
# TeX associated documents would be very nice organized.
Two remarks:
1) although bundles are really direcories, and as such platform =
independent,
when sending such a "file" via e-mail, one would still need to make an
archive (tar for example).
2) How would you handle a tree with several files, the user cannot create
his/her own tree, so that needs to be handled by the program as well. =
But the
user would need to type in the path in the source when including the =
file.
In short, I think this would be very messy.
With a propper interface (an outliner to organize the files/chapters, an
exporter to create an archive for transfering files and a bunch of other =
parts)
it might work, but make it optional.
Makefiles may come in handy here. A few days ago someone on this list =
mentions
he used Makefiles to manage his TeX projects. Would this person be so kind =
and
send me a sample Makefile? I once tried to create one, but failed (on the
dependencies), maybe you had a better idea.
Cheers,
Maarten Sneep
>>>-----------------------------------------------------------------------
Murphy's Law, supplemental:
Celibacy is not hereditory.
>>>-----------------------------------------------------------------------
Maarten Sneep
Atomic- and Laser Physics group
vrije Universiteit, amsterdam
The Netherlands
----------------------------------------------------------------------
Subject: Re: [Mac OS X TeX] put files in bundles?
From: "Bruno Voisin"
Date: Fri, 23 Nov 2001 12:06:11 +0100
> # I wonder if it would be a good option (for TeXShop) to save all the
> # files generated on a typesetting-run into a MacOS X bundle, so one
> # would see only one single "file" in the Finder with the .tex .pdf
> # .aux .log etc. files inside.
> # So moving and renaming of this entire bunch would be very simple and
> # TeX associated documents would be very nice organized.
Yes I think that would be a really nice idea, pretty much like the way
Textures bundled the .dvi file in the resource fork of the .tex source
and did not create a .log file but displayed it in a TeX log window.
Then you don't have to learn about the internal cuisine of TeX and
associated programs (what files are created, and what for), unless you
absolutely need to. Very Mac-like!
On the other hand I suspect teTeX would have difficulties to cope with
this, since TeX and its associated programs (BibTeX, MakeIndex, dvips,
pdfTeX, ...) expect to find and read files with specific extensions. Or
even just LaTeX, which needs an .aux file and may use .toc, .bbl,
..ind, ... files.
> Two remarks:
> 1) although bundles are really direcories, and as such platform
> independent,
> when sending such a "file" via e-mail, one would still need to make
> an
> archive (tar for example).
> 2) How would you handle a tree with several files, the user cannot
> create
> his/her own tree, so that needs to be handled by the program as
> well. But the
> user would need to type in the path in the source when including the
> file.
>
> In short, I think this would be very messy.
Is it really necessary to go to such complexities, isn't it possible to
have only TeX-generated files bundled together, not the whole directory
structure created by the user to typeset a book with figures etc.?
By the way, how does Project Builder deal with projects? Does it create
bundles? (I'm no developer myself, so that's really a candid question.)
By the way, too, since Project Builder is on the Developer Tools CD
which came freely with my Mac OS X packages (10.0 then 10.1), is it
possible to use it as an external editor for TeXShop (probably an
overkill, but...). Is it possible to define TeX-specific features for
it, like a TeX menu? (I'm thinking especially of the first
implementations of OzTeX and DirectTeX, which both suggested MPW Shell
as an external editor of choice.)
Bye,
Bruno Voisin
----------------------------------------------------------------------
Subject: Re: [Mac OS X TeX] put files in bundles?
From: "Maarten Sneep"
Date: Fri, 23 Nov 2001 12:21:13 +0100 (CET)
On 23-Nov-01 Bruno Voisin wrote:
# > # I wonder if it would be a good option (for TeXShop) to save all the
# > # files generated on a typesetting-run into a MacOS X bundle, so one
# > # would see only one single "file" in the Finder with the .tex .pdf
# > # .aux .log etc. files inside.
# > # So moving and renaming of this entire bunch would be very simple =
and
# > # TeX associated documents would be very nice organized.
#
# On the other hand I suspect teTeX would have difficulties to cope with
# this, since TeX and its associated programs (BibTeX, MakeIndex, dvips,
# pdfTeX, ...) expect to find and read files with specific extensions. Or =
# even just LaTeX, which needs an .aux file and may use .toc, .bbl,
# .ind, ... files.
As far as unix tools are concerned: a bundle is just a directory, so there =
are
no technical obstacles.
# > Two remarks:
# > 1) although bundles are really direcories, and as such platform
# > independent, when sending such a "file" via e-mail, one would still =
need to
# > make an archive (tar for example).
# > 2) How would you handle a tree with several files, the user cannot
# > create his/her own tree, so that needs to be handled by the program
# > as well. But the user would need to type in the path in the source
# > when including the file.
# >
# > In short, I think this would be very messy.
#
# Is it really necessary to go to such complexities, isn't it possible to =
# have only TeX-generated files bundled together, not the whole directory =
# structure created by the user to typeset a book with figures etc.?
With which file would you include the other files then? Maybe you can put =
all
tex related files in a bundle (main-tex-file.texnical, anyone) I think it =
is
unwise to create a bundle from one of the .tex files, since no other =
editor
would understand what they meant. Also most users want to have their =
resulting
(pdf) file ready to send through e-mail, so that's no option either.
# By the way, how does Project Builder deal with projects? Does it create =
# bundles? (I'm no developer myself, so that's really a candid question.)
Project builder creates a normal directory for your project, in which you =
can
have a build (normal) directory where the object files are generated along =
with
the final build product. The project files themselves are bundles, with =
several
files describing the options and the included files.
# By the way, too, since Project Builder is on the Developer Tools CD
# which came freely with my Mac OS X packages (10.0 then 10.1), is it
# possible to use it as an external editor for TeXShop (probably an
# overkill, but...).
You'd need to create jam files to tell ProjectBuilder how to handle tex =
files.
I guess it can be done, but it takes a lot of work.
The current version doesn't support plugins (not publicly) so syntax =
colours
are out.
# Is it possible to define TeX-specific features for
# it, like a TeX menu? (I'm thinking especially of the first
# implementations of OzTeX and DirectTeX, which both suggested MPW Shell
# as an external editor of choice.)
CMacTeX does this as well (it has all the tools to work directly in the =
shell).
Project builder should be simpler: it uses command-line tools to do it's =
job,
and a call to pdflatex is about as complicated as calling cc... (actually
pdflatex is simpler, far less options to include)
Maarten Sneep
>>>-----------------------------------------------------------------------
A prune isn't really a vegetable... Cabbage is a vegetable
>>>-----------------------------------------------------------------------
Maarten Sneep
Atomic- and Laser Physics group
vrije Universiteit, amsterdam
The Netherlands
----------------------------------------------------------------------
Subject: Re: [Mac OS X TeX] put files in bundles?
From: "Bruno Voisin"
Date: Fri, 23 Nov 2001 12:38:59 +0100
Le vendredi 23 novembre 2001, =E0 12:21 PM, Maarten Sneep a =E9crit :
> # Is it really necessary to go to such complexities, isn't it =
possible=20
> to
> # have only TeX-generated files bundled together, not the whole=20
> directory
> # structure created by the user to typeset a book with figures etc.?
>
> With which file would you include the other files then? Maybe you can=20=
> put all
> tex related files in a bundle (main-tex-file.texnical, anyone) I think=20=
> it is
> unwise to create a bundle from one of the .tex files, since no other=20=
> editor
> would understand what they meant. Also most users want to have their=20=
> resulting
> (pdf) file ready to send through e-mail, so that's no option either.
I was thinking of bundling tex-related files with the file designated as=20=
the "Project Root". But yes, I perfectly agree with the objection for=20
PDF files, that's what I do myself: sending PDF files by e-mail.
Thanks for all the technical details, which I wasn't aware of. Now I=20
understand better.
Bruno Voisin
----------------------------------------------------------------------
Subject: Mac font encodings for ConTeXt?
From: "Harri Hakula"
Date: Fri, 23 Nov 2001 15:27:38 +0200
ConTeXt does not recognize accented characters such as \"a.
That is, typing \"a in text is fine but the keyboard equivalent is lost.
Using latex I'll just have to say
\usepackage[applemac]{inputenc}
Within the distribution I found a number of files named enco-* but
not the enco-mac.tex I wanted to see...
Any ideas, experience on this?
Harri Hakula
--
Harri Hakula
Institute of Mathematics
Helsinki University of Technology
PL 1100
FIN-02015 HUT
tel. +358-9-451-5862
fax. +358-9-451-3016
----------------------------------------------------------------------
Subject: Re: [Mac OS X TeX] put files in bundles?
From: "J.Huelsmann"
Date: Fri, 23 Nov 2001 14:49:02 +0100
....
>I was thinking of bundling tex-related files with the file
>designated as the "Project Root". But yes, I perfectly agree with
>the objection for PDF files, that's what I do myself: sending PDF
>files by e-mail.
....
you can still access every file inside a bundle via control-klick in
the Finder, (but not in the list view)-:
--Jan--
----------------------------------------------------------------------
Subject: Re: MacOSX-TeX Digest #159 - 11/21/01
From: "Charles Bouldin"
Date: Fri, 23 Nov 2001 10:16:04 -0500
> Your config.ps file is telling dvips to pipe its output to lpr, the
>standard printer on Unix. You should comment out the line
>
>o |lpr
>
>and dvips will send its output to a file. You can avoid having to
>change a config file by editing dvips.script. Change the line
>
>dvips $OPTIONS $1
>
>to
>
>dvips $OPTIONS -o ${argv[1]:r}".ps" $1
>
>This is a simple example of how you can modify the bbedit plug-in
>scripts to have them do exactly what you want.
Thanks, Tom, that fixes it. I like these plugins and it is really a
toss up between TeXShop and the BBEdit/TeX plugins. Nice to have some
choices.
----------------------------------------------------------------------
End of MacOSX-TeX Digest
-----------------------------------------------------------------
To UNSUBSCRIBE, send email to with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------