From MacOSX-TeX@email.esm.psu.edu Sat Jun 11 19:54:52 2005
Received: from engremail.engr.psu.edu ([130.203.201.4]) by ENGRMAIL1.engr.psu.edu with Microsoft SMTPSVC(5.0.2195.6713);
	 Sat, 11 Jun 2005 19:54:52 -0400
Received: from email.esm.psu.edu ([130.203.247.204]) by engremail.engr.psu.edu with Microsoft SMTPSVC(5.0.2195.6713);
	 Sat, 11 Jun 2005 19:54:52 -0400
Date: Sat, 11 Jun 2005 20:00:13 -0400
Message-ID: <64813.71363@email.esm.psu.edu>
Subject: MacOSX-TeX Digest #1400 - 06/11/05
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: List
List-Software: LetterRip Pro 4.05 (0531) by LetterRip Software, LLC.
List-Subscribe: 
List-Digest: 
List-Unsubscribe: 
X-LR-SENT-TO: mail.engr.psu.edu
Return-Path: MacOSX-TeX@email.esm.psu.edu
X-OriginalArrivalTime: 11 Jun 2005 23:54:52.0252 (UTC) FILETIME=[F59F61C0:01C56EE0]

MacOSX-TeX Digest #1400 - Saturday, June 11, 2005

  TeXShop "holding" files
          by "Ronald Bruck" 

  Re: [OS X TeX] Beta ConTeXt?
          by "Herbert Schulz" 

  Re: [OS X TeX] TeXShop "holding" files
          by "Claus Gerhardt" 

  BibTeX problem with apa.cls and apacite.bst
          by "Olli Hardt" 

  Re: [OS X TeX] Threads on MacIntel
          by "Gerben Wierda" 

  Re: [OS X TeX] Threads on MacIntel
          by "Gerben Wierda" 

  Re: [OS X TeX] Threads on MacIntel
          by "Gerben Wierda" 

  Re: [OS X TeX] Beta ConTeXt?
          by "Gerben Wierda" 

  Re: [OS X TeX] Beta ConTeXt?
          by "Bob Kerstetter" 

  Re: [OS X TeX] Beta ConTeXt?
          by "Herbert Schulz" 

  I Tried It...
          by "Herbert Schulz" 


----------------------------------------------------------------------

Subject: TeXShop "holding" files
From: "Ronald Bruck" 
Date: Fri, 10 Jun 2005 18:11:13 -0700

One of the main complaints of users of Mac OS is the tendency of  
programs to "hold" files open, even after their window has been  
closed and the file has (presumably) been written to disk.  (Yet, the  
file isn't locked; other programs can open it.)  Unfortunately,  
TeXShop shares this behavior.

Can someone elucidate the technical reasons for this?  Clearly the  
file has been locked, but not completely; HOW?, and WHY?  It's  
extremely annoying, after editing a file on a removable disk, to have  
to QUIT TeXShop before ejecting the drive.

And when you have a dozen applications open, it isn't always the  
obvious one which has the hold in place.  On occasion I have had to  
go through the applications one-by-one and quit them all.  Sometimes  
even THAT doesn't release the file, and I have to reboot.  (Logging  
out and back in doesn't work.)

Surely Richard Koch can be persuaded to modify TeXShop not to do this.

This is one of (Apple employee #66) Bruce Tognazinni's infamous bugs  
that he lists on his web page,

       

(They're all interesting, and all are right on.  Example:  you're  
typing away in TeXShop, and Microsoft Word [name almost any other  
app] FINALLY comes up, and seizes focus:  suddenly you're typing in  
Word's dialogue box.)

--Ron Bruck


----------------------------------------------------------------------

Subject: Re: [OS X TeX] Beta ConTeXt?
From: "Herbert Schulz" 
Date: Fri, 10 Jun 2005 22:44:07 -0500


On Jun 10, 2005, at 11:21 AM, Bob Kerstetter wrote:

> Hi Everyone, but Especially Herb and other ConTeXt users.
>
> Some time in recent history, Herb wrote:
>
>
>> I also installed the latest ConTeXt beta...
>>
>
> I am using ConTeXt some, but have never run the i-package for the  
> regular updates.
>
> What goes on in ConTeXt development that makes such frequent  
> updates so attractive?
>
> Thanks.
>
> Bob Kerstetter
> http://homepage.mac.com/bkerstetter/
>

Howdy,

I'm not much of a ConTeXt user but its integration with XML is of  
future interest to me. Why did I download the ConTeXt Updater? I  
guess I figured I'd want the newest things going on but it is proving  
to be quite a bit more unstable than any of GW's ``betas''. Why did I  
do this a second time? Hmmm... another senior moment---my wife call  
it halfheimers. At least I finally remembered how I got out of the  
problem the last time.

Good Luck,

Herb Schulz
(herbs@wideopenwest.com)



----------------------------------------------------------------------

Subject: Re: [OS X TeX] TeXShop "holding" files
From: "Claus Gerhardt" 
Date: Sat, 11 Jun 2005 13:10:33 +0200

There is an easy solution for this problem by always saving an  
external file to an internal hard drive before editing it. This  
procedure also has other advantages like speed ...

Claus

On Jun 11, 2005, at 3:11, Ronald Bruck wrote:

> One of the main complaints of users of Mac OS is the tendency of  
> programs to "hold" files open, even after their window has been  
> closed and the file has (presumably) been written to disk.  (Yet,  
> the file isn't locked; other programs can open it.)  Unfortunately,  
> TeXShop shares this behavior.
>
> Can someone elucidate the technical reasons for this?  Clearly the  
> file has been locked, but not completely; HOW?, and WHY?  It's  
> extremely annoying, after editing a file on a removable disk, to  
> have to QUIT TeXShop before ejecting the drive.
>
> And when you have a dozen applications open, it isn't always the  
> obvious one which has the hold in place.  On occasion I have had to  
> go through the applications one-by-one and quit them all.   
> Sometimes even THAT doesn't release the file, and I have to  
> reboot.  (Logging out and back in doesn't work.)
>
> Surely Richard Koch can be persuaded to modify TeXShop not to do this.
>
> This is one of (Apple employee #66) Bruce Tognazinni's infamous  
> bugs that he lists on his web page,
>
>       
>
> (They're all interesting, and all are right on.  Example:  you're  
> typing away in TeXShop, and Microsoft Word [name almost any other  
> app] FINALLY comes up, and seizes focus:  suddenly you're typing in  
> Word's dialogue box.)
>
> --Ron Bruck
>
> --------------------- Info ---------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>           & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Post: 
>
>
>


----------------------------------------------------------------------

Subject: BibTeX problem with apa.cls and apacite.bst
From: "Olli Hardt" 
Date: Sat, 11 Jun 2005 07:30:11 -0400

hello:  when i typeset a file that uses \documentclass[...]{apa} and =
\usepackage{apacite} in the following sequence (TeXShop -- LaTeX run, =
BiBTeX run, LaTeX run, LaTeX run), i get an error after during the last =
run.  This error looks like as if the codes the BiBTeX generates to put =
the citations in the text have some problems.  the reference list is =
correctly typset.  what is the problem, and how can i prevent this error?  =
thanks for your help.  olli.

----------------------------------------------------------------------

Subject: Re: [OS X TeX] Threads on MacIntel
From: "Gerben Wierda" 
Date: Sat, 11 Jun 2005 13:33:55 +0200

On Jun 10, 2005, at 15:59, Fernando Pereira wrote:

>
> On Jun 10, 2005, at 8:14 AM, Bruno Voisin wrote:
>
>> "Our initial analysis and prediction of a smooth transition still 
>> appears to be accurate, even after a few days of review and 
>> analysis," Siegel said in an e-mail interview. "There are some 
>> adjustments to be made, but nothing particularly daunting."
>
> Swinging this back to TeX on OS X... The issues are different for TeX 
> (and its command-line support programs) and for front-ends like 
> TexShop. We know that TeX and its companions work fine on x86. The 
> problem will not be with the code itself, but rather with the 
> availability of development tools and systems to create fat binaries 
> for these applications. In particular, it's not clear yet whether fat 
> binaries can be built in a standard command-line *nix way, which is 
> what the build processes for those programs require.

There is no problem here. The C-compiler recognizes (always has 
recognized) the -arch flag. Hence

	gcc -arch i386 -arch -ppc

will get you a fat binary. And I do plan to have a multiple-binary 
distribution of TeX ready as soo as I can.

G


----------------------------------------------------------------------

Subject: Re: [OS X TeX] Threads on MacIntel
From: "Gerben Wierda" 
Date: Sat, 11 Jun 2005 13:39:31 +0200

On Jun 10, 2005, at 17:06, Jonathan Kew wrote:

> On 10 Jun 2005, at 6:59 am, Fernando Pereira wrote:
>
>>
>> On Jun 10, 2005, at 8:14 AM, Bruno Voisin wrote:
>>
>>
>>> "Our initial analysis and prediction of a smooth transition still 
>>> appears to be accurate, even after a few days of review and 
>>> analysis," Siegel said in an e-mail interview. "There are some 
>>> adjustments to be made, but nothing particularly daunting."
>>>
>>
>> Swinging this back to TeX on OS X... The issues are different for TeX 
>> (and its command-line support programs) and for front-ends like 
>> TexShop. We know that TeX and its companions work fine on x86. The 
>> problem will not be with the code itself, but rather with the 
>> availability of development tools and systems to create fat binaries 
>> for these applications. In particular, it's not clear yet whether fat 
>> binaries can be built in a standard command-line *nix way, which is 
>> what the build processes for those programs require.
>
> Yes, they can.
>
> However, this isn't really necessary (depending on the overall setup). 
> Consider the output of
>
>     $ which tex
>
> which, on my machine, responds
>
>     /usr/local/teTeX/bin/powerpc-apple-darwin-current/tex
>
> Note the path. If I were on an Intel Mac, the "powerpc" part would be 
> replaced by "i686" or something. So the binaries would be separate 
> anyway. The two architectures can co-exist in a single filesystem even 
> without universal binaries, by appropriate PATH configuration, etc.

This raises an interesting point. The path 
/usr/local/teTeX/bin/powerpc-apple-darwin6.8 tells you on what system 
the binaries were *created*, not what they contain.

So, when I make my distribution, most likely the path will be something 
like /usr/local/teTeX/bin/powerpc-apple-darwin8.x but the binaries 
inside will be fat:

hedwig:~ gerben$ file 
/usr/local/teTeX/bin/powerpc-apple-darwin-current/tex
/usr/local/teTeX/bin/powerpc-apple-darwin-current/tex: Mach-O fat file 
with 2 architectures
/usr/local/teTeX/bin/powerpc-apple-darwin-current/tex (for architecture 
ppc):      Mach-O executable ppc
/usr/local/teTeX/bin/powerpc-apple-darwin-current/tex (for architecture 
i386):     Mach-O executable i386

G


----------------------------------------------------------------------

Subject: Re: [OS X TeX] Threads on MacIntel
From: "Gerben Wierda" 
Date: Sat, 11 Jun 2005 13:43:16 +0200

On Jun 10, 2005, at 17:37, Bruno Voisin wrote:

> As far as I understood, the powerpc here in the path (and more 
> generally the imbrication of directories) was Gerben's decision, not 
> something imposed by TeX or OS X in itself. Or did I misunderstand?

It is something that is part of the build environment of TeX 
Live/teTeX. See other post.

> So what you're saying is that i-Installer (or whichever installer is 
> used for gwTeX at the time MacTel Macs are released) should detect, at 
> install time, the processor and determine the binaries to be installed 
> (ie chooses then between two directories 
> bin/i686-apple-darwin-current/ and bin/powerpc-apple-darwin-current/, 
> both included inside the i-Package). Would'nt it be simpler to have 
> universal binaries?

I can do two things:

1. Have an i-Package with fat binaries and offer to strip the 
architecture you are not using from the binaries after install. Note 
that means that the binary part will be twice as large to download.
2. Have an i-Package with a choice of architectures to install for. 
That would limit the download to what you really need but would be more 
work for me.

I haven't made up my mind yet.

G


----------------------------------------------------------------------

Subject: Re: [OS X TeX] Beta ConTeXt?
From: "Gerben Wierda" 
Date: Sat, 11 Jun 2005 13:47:10 +0200

On Jun 10, 2005, at 18:21, Bob Kerstetter wrote:

> Hi Everyone, but Especially Herb and other ConTeXt users.
>
> Some time in recent history, Herb wrote:
>
>> I also installed the latest ConTeXt beta...
>
> I am using ConTeXt some, but have never run the i-package for the 
> regular updates.
>
> What goes on in ConTeXt development that makes such frequent updates 
> so attractive?

Bug fixes, currently. For  a while during the last weeks there was no 
beta, but the stable version was updated a couple of times. At this 
moment, there is a beta again.

My ConTeXt update package build script checks the availability of new 
ConTeXt distributions each morning at 6AM CET DST and if there has been 
a change, automatically updates the i-Package.

G


----------------------------------------------------------------------

Subject: Re: [OS X TeX] Beta ConTeXt?
From: "Bob Kerstetter" 
Date: Sat, 11 Jun 2005 07:46:34 -0500

> On Jun 10, 2005, at 18:21, Bob Kerstetter wrote:
>
>
>> Hi Everyone, but Especially Herb and other ConTeXt users.
>>
>> Some time in recent history, Herb wrote:
>>
>>
>>> I also installed the latest ConTeXt beta...
>>>
>>
>> I am using ConTeXt some, but have never run the i-package for the  
>> regular updates.
>>
>> What goes on in ConTeXt development that makes such frequent  
>> updates so attractive?


On Jun 10, 2005, at 10:44 PM, Herbert Schulz wrote:

> I'm not much of a ConTeXt user but its integration with XML is of  
> future interest to me. Why did I download the ConTeXt Updater? I  
> guess I figured I'd want the newest things going on but it is  
> proving to be quite a bit more unstable than any of GW's ``betas''.  
> Why did I do this a second time? Hmmm... another senior moment---my  
> wife call it halfheimers. At least I finally remembered how I got  
> out of the problem the last time.

Ah. How this I can understand. Sometimes.


On Jun 11, 2005, at 6:47 AM, Gerben Wierda wrote:

> Bug fixes, currently.

Okay. Thanks.

> For  a while during the last weeks there was no beta, but the  
> stable version was updated a couple of times. At this moment, there  
> is a beta again.
>
> My ConTeXt update package build script checks the availability of  
> new ConTeXt distributions each morning at 6AM CET DST and if there  
> has been a change, automatically updates the i-Package.

That is pretty cool. I may as well try it. Herb can tell me how it  
fix it, if updating breaks my ConTeXt installation. ;)

Bob Kerstetter
http://homepage.mac.com/bkerstetter/


----------------------------------------------------------------------

Subject: Re: [OS X TeX] Beta ConTeXt?
From: "Herbert Schulz" 
Date: Sat, 11 Jun 2005 08:02:30 -0500


On Jun 11, 2005, at 7:46 AM, Bob Kerstetter wrote:

> That is pretty cool. I may as well try it. Herb can tell me how it  
> fix it, if updating breaks my ConTeXt installation. ;)
>
> Bob Kerstetter
> http://homepage.mac.com/bkerstetter/
>

Howdy,

Note: there is a drop down tab to choose the Plain or Beta update if  
they differ. I chose the Beta and ran into the problem. If you choose  
the Plain things may be fine. If so, please let me know.

P.S. the solution is to Uninstall that package and run the TeX i- 
package Configure script again. That is probably overkill but hurts  
my head the least.

Good Luck,

Herb Schulz
(herbs@wideopenwest.com)



----------------------------------------------------------------------

Subject: I Tried It...
From: "Herbert Schulz" 
Date: Sat, 11 Jun 2005 08:59:45 -0500

Howdy,

Well, idiot that I am, I figured I'd be the goat and did another  
ConTeXt-Update i-package install but used the `ConTeXt stable' option  
this time. Unfortunately I ran into the same thing; pdf(la)tex (and  
probably dvips, but I didn't check the ghostscript+dvips route) can't  
find the fonts and starts to build bitmapped fonts.

I use the Unintall (what a terrible name---should be destall or  
unstall but none of the three are accepted as real words by my spell  
checker) in the ConTeXt-Update i-package and then ran the Configure  
script in TeX i-package and all is well again. I'm getting good at this.

Good Luck,

Herb Schulz
(herbs@wideopenwest.com)



----------------------------------------------------------------------
End of MacOSX-TeX Digest

--------------------- Info ---------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
           & FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Post: