From MacOSX-TeX@email.esm.psu.edu Thu Jun  9 19:54:53 2005
Received: from engremail.engr.psu.edu ([130.203.201.4]) by ENGRMAIL1.engr.psu.edu with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 9 Jun 2005 19:54:53 -0400
Received: from email.esm.psu.edu ([130.203.247.204]) by engremail.engr.psu.edu with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 9 Jun 2005 19:54:52 -0400
Date: Thu, 9 Jun 2005 20:00:13 -0400
Message-ID: <92013.3362@email.esm.psu.edu>
Subject: MacOSX-TeX Digest #1398 - 06/09/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: 09 Jun 2005 23:54:52.0919 (UTC) FILETIME=[A131A870:01C56D4E]

MacOSX-TeX Digest #1398 - Thursday, June 9, 2005

  Re: [OS X TeX] PPC to Intel
          by "Jon Breitenbucher" 

  Re: [ANN] BibDesk 1.1
          by "Stephen Anderson" 

  bibdesk 1.1
          by "Michael Gedalin" 

  multi-page preview in Texshop 2.03
          by "Ingo Reich" 

  Re: [OS X TeX] iTeXMac
          by "Riboni Enrico" 

  Re: [OS X TeX] A suggestion for NewPdftricks (or for pdftricks in general
          by "Alain Matthes" 

  Re: [OS X TeX] PPC to Intel
          by "Joseph C. Slater" 

  Re: [OS X TeX] PPC to Intel
          by "Bruno Voisin" 

  OT: [OS X TeX] PPC to Intel
          by "Gerben Wierda" 

  Re: [OS X TeX] iTeXMac (waiting for stable v. 2)
          by "Eric van der Oord" 

  Re: [OS X TeX] A suggestion for NewPdftricks (or for pdftricks in general
          by "Herbert Schulz" 

  Re: [OS X TeX] Font problem?
          by "Fran=E7ois G. Schmitt" 

  Re: [OS X TeX] Font problem?
          by "Aaron Jackson" 

  Re: [OS X TeX] bibdesk 1.1
          by "Norm Gall" 

  Re: [OS X TeX] multi-page preview in Texshop 2.03
          by "Gary L. Gray" 

  Re: [OS X TeX] bibdesk 1.1
          by "Adam R. Maxwell" 

  Re: [OS X TeX] bibdesk 1.1
          by "Adam R. Maxwell" 

  Re: [OS X TeX] Font problem?
          by "Fran=E7ois G. Schmitt" 

  Re: [OS X TeX] bibdesk 1.1
          by "Norm Gall" 

  Macs and Intel
          by "Rene Borgella" 

  Re: [OS X TeX] bibdesk 1.1
          by "Adam R. Maxwell" 

  Re: [OS X TeX] Font problem?
          by "Bruno Voisin" 

  Re: [OS X TeX] Font problem?
          by "Peter Dyballa" 

  Re: [OS X TeX] PPC to Intel
          by "Joseph C. Slater" 

  Re: [OS X TeX] Font problem?
          by "Fran=E7ois G. Schmitt" 

  PPC, x86, Linux performence
          by "Rene Borgella" 

  Yet Another New Adapted pdftricks Package
          by "Herbert Schulz" 

  Threads on MacIntel
          by "Simon Spiegel" 

  Re: [OS X TeX] Threads on MacIntel
          by "Jon Guyer" 

  Re: [OS X TeX] Font problem?
          by "Aaron Jackson" 

  [OS X TeX] Threads on MacIntel
          by "Rene Borgella" 

  Re: [OS X TeX] Font problem?
          by "Herbert Schulz" 

  Re: [OS X TeX] A suggestion for NewPdftricks (or for pdftricks in general
          by "Alain Matthes" 

  Re: [OS X TeX] Font problem?
          by "Fran=E7ois G. Schmitt" 

  Re: [OS X TeX] Threads on MacIntel
          by "Jon Guyer" 

  Re: [OS X TeX] Font problem?
          by "Aaron Jackson" 

  Re: [OS X TeX] Font problem?
          by "Gerben Wierda" 

  Re: [OS X TeX] PPC to Intel
          by "Bruno Voisin" 

  Re: [OS X TeX] PPC to Intel
          by "Gary L. Gray" 

  Re: [OS X TeX] Font problem?
          by "Bruno Voisin" 

  What Happened to My Lucida Bright?
          by "Herbert Schulz" 

  Re: [OS X TeX] Threads on MacIntel
          by "Bob Kerstetter" 

  Re: [OS X TeX] What Happened to My Lucida Bright?
          by "Bruno Voisin" 

  Re: [OS X TeX] Font problem?
          by "Claus Gerhardt" 

  Re: [OS X TeX] What Happened to My Lucida Bright?
          by "Herbert Schulz" 


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

Subject: Re: [OS X TeX] PPC to Intel
From: "Jon Breitenbucher" 
Date: Wed, 8 Jun 2005 19:59:06 -0400


On Jun 8, 2005, at 5:57 PM, mark oilcan wrote:

>
>
> --- Maarten Sneep  wrote:
>
>
>> On 8 Jun 2005, at 12:25, Gerben Wierda wrote:
>>
>>
>>>> ...and so the question, for those who know best, will the
>>>>
>> transition
>>
>>>> from PowerPC to Intel be painless, as far as TeX (and all the
>>>>
>> related
>>
>>>> apps that we so cherish) is concerned?
>>>>
>>>
>>> Regarding the backend most people use on Mac OS X: I have already a
>>>
>>
>>
>>> report
>>> that TeX Live compiles fine on an Intellimac.
>>>
>>
>> I would expect the 'Intellimac' (first time I hear this name) to be
>>
>
> Personally, I would prefer Macintel as I don't particularly see any
> reason to associate the word "intelligent" with a Mac using an Intel
> cpu. Not that it's a big deal or anything....
>
> Mark A

I vote for Xtel, since it is all about the OS.
_______________________________________
When confronted with actual numbers, a mathematician is at a loss.   
(Steffen Hokland)

Jon Breitenbucher, Ph. D.
Adjunct Professor and Instructional Technology Specialist
The College of Wooster
Department of Mathematics and Computer Science
308 E. University
Wooster, Ohio 44691

work:    (330)263-2207
e-mail:    jbreitenbuch@wooster.edu
web:    http://jbreitenbuch.wooster.edu/~jonb
cal:    http://ical.mac.com/kahless/Work


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

Subject: Re: [ANN] BibDesk 1.1
From: "Stephen Anderson" 
Date: Thu, 9 Jun 2005 15:40:53 +1000

On Tue, 7 Jun 2005 22:07:40 -0700,  "Adam R.Maxwell"  
 said:

> The BibDesk development team is pleased to announce that version 1.1
> is available for download at .
> There are some major changes in this version, so it should probably
> be considered a beta release; as usual with beta releases, don't use
> it to overwrite the only copy of your .bib file!
>
> Items using the BibTeX crossref field are now searchable and
> sortable, and inherited fields are displayed in the main pubs list
> and the editor.

Many, many thanks for this enhancement to BibDesk, which seems to  
work well with my bibfiles containing crossrefs.  I'm delighted to be  
able to join the crowd of happy users, and grateful for your  
responsiveness to the request for this feature.  As far as I can see,  
it works just as I hoped.

-- 
Steve Anderson



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

Subject: bibdesk 1.1
From: "Michael Gedalin" 
Date: Thu, 9 Jun 2005 08:55:21 +0300

The following is produced by downloading from the adsabs abstract  
service:

@ARTICLE{2004JGRA..10903106G,
    author =3D {{Gedalin}, M. and {Balikhin}, M.},
     title =3D "{Electric potential in the low-Mach-number quasi- 
perpendicular collisionless shock ramp revisited}",
   journal =3D {Journal of Geophysical Research (Space Physics)},
      year =3D 2004,
     month =3D mar,
    volume =3D 109,
     number =3D A18,
     pages =3D {3106-+},
    adsurl =3D {http://adsabs.harvard.edu/cgi-bin/nph-bib_query? 
bibcode=3D2004JGRA..10903106G&db_key=3DAST},
   adsnote =3D {Provided by the Smithsonian/NASA Astrophysics Data System}
}


After Saving As from Bibdesk 1.1 I get the following:

@article{2004JGRA..10903106G,
     Adsnote =3D {Provided by the Smithsonian/NASA Astrophysics Data  
System},
     Adsurl =3D {http://adsabs.harvard.edu/cgi-bin/nph-bib_query? 
bibcode=3D2004JGRA..10903106G&db_key=3DAST},
     Author =3D {{Gedalin}, M. and {Balikhin}, M.},
     Journal =3D {Journal of Geophysical Research (Space Physics)},
     Month =3D mar,
     Number =3D A18,
     Pages =3D {3106-+},
     Title =3D {{Electric potential in the low-Mach-number quasi- 
perpendicular collisionless shock ramp revisited}},
     Volume =3D 109,
     Year =3D 2004}

and the bib file becomes not portable: the first one is properly  
opened by the corresponding software on a PC (Windows), the latter  
does not show most of the fields.
Is there any reason why Bibdesk changes the order of the fields in  
the bib file ? (It is the order which makes the file not portable.)
Michael



*******************************************************
*Michael Gedalin
*Department of Physics
*Ben-Gurion University
*POB 653
*Beer-Sheva, 84105
*Israel
*Tel: 972-8-6461645
*Fax: 972-8-6472904
*Email: gedalin@bgumail.bgu.ac.il
*http://physics.bgu.ac.il/~gedalin
*******************************************************


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

Subject: multi-page preview in Texshop 2.03
From: "Ingo Reich" 
Date: Thu, 9 Jun 2005 09:02:48 +0200

Hi,

if I select the preview option "multi-page" in the preferences of =20
texshop 2.03, the preview always jumps to the top of the currrent =20
page after typesetting. I remember that this has already been =20
discussed =96 and fixed =96 with respect to the "one page" option, but I =
=20
just cannot find the relevant mails. Is there some easy way to fix this?

Another point: Is there some way to tell texshop to immediately put =20
the preview to the forground after hitting command+t  in the source? =20
(This is what I'm used to from using texshop together with alphaX =96=96 =
=20
I just switched to 'texshop only' because I love the build-in =20
synchronization feature that even works if one takes the dvi-ps-pdf =20
route.)

Best, Ingo=

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

Subject: Re: [OS X TeX] iTeXMac
From: "Riboni Enrico" 
Date: Thu, 9 Jun 2005 09:18:39 +0200

> On Jun 7, 2005, at 02:23, J=E9r=F4me Laurens wrote:
>>
>> Le 6 juin 05, =E0 17:12, Simon Spiegel a =E9crit :
>>>
>>> On 06.06.2005, at 17:01, Riboni Enrico wrote:
>>>
>>>> For information:
>>>>
>>>> I just saw on Macupdate that there is a new iTeXMac beta =20
>>>> releaste, Tiger compatible, for those interested.
>>>
>>> It's actually not Tiger compatible but requires Tiger. Just a =20
>>> warning: The release not clearly state that this a beta and only =20
>>> recommended for the brave ones. I did a little test and imported =20
>>> my PhD project, I wasn't even able to typeset it. Don't know if =20
>>> the problem was on my side or if my project is just too complex =20
>>> to have it easily imported.
>>>
>>> Anyway, good to see that ITM is also progressing, I'm very =20
>>> curious about further developments.
>>>
>>>
>>
>> Actually iTM2 is not a beta not even an alpha, it is a just  a =20
>> public preview
>>
>> However, I do need some feedback!

It is impressive and interesting, and the "project based" approach =20
seems brillant. I do not have sufficient knowledge about software =20
development to give you very specific feedback at this stage, but if =20
there are specific things/ functions/ideas which you would want to =20
have somebody test pls. let me know.

Enrico Riboni
www.ozone.ch/enrico/=

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

Subject: Re: [OS X TeX] A suggestion for NewPdftricks (or for pdftricks in general)
From: "Alain Matthes" 
Date: Thu, 9 Jun 2005 09:57:07 +0200


Le 7 juin 05 =E0 07:10, Franck Pastor a =E9crit :

>
> It works perfectly on all my 12pt-documents document that use =20
> pdftricks :-))
>
> Thanks again !
>
> Franck Pastor
>


Sorry but there is a little problem. \@ptsize is defined
in the class Article  and if you use a personal class (without =20
\@ptsize) ,
  you obtain an error. It is my case !

But with :


\ifpdf
     \usepackage{pdftricks}
     \begin{psinputs}
     \RequirePackage[utf8]{inputenc}
     \RequirePackage[upright,expert]{fourier}
     \input{size10.clo} etc....


I've no problem with the preceding version of pdftricks
`
Thanks

Alain Matthes




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

Subject: Re: [OS X TeX] PPC to Intel
From: "Joseph C. Slater" 
Date: Thu, 09 Jun 2005 07:34:59 -0400


On Jun 8, 2005, at 7:59 PM, Jon Breitenbucher wrote:

>
> On Jun 8, 2005, at 5:57 PM, mark oilcan wrote:
>
>> 
> I vote for Xtel, since it is all about the OS.
>

... with the new G6 processor from Intel...

I wouldn't be surprised if from a consumer standpoint they try to  
sell it as no different than going from a G4 to a G5. After all,  
Apple's goal has always been to try to keep it simple for the  
consumer. Highlighting the potential problems of the transition isn't  
to their advantage.
Joe




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

Subject: Re: [OS X TeX] PPC to Intel
From: "Bruno Voisin" 
Date: Thu, 9 Jun 2005 13:55:03 +0200

Le 9 juin 05 =E0 13:34, Joseph C. Slater a =E9crit :

> I wouldn't be surprised if from a consumer standpoint they try to =20
> sell it as no different than going from a G4 to a G5.

Not really. Did you look at the WWDC keynote's webcast? Steve Jobs =20
presented the transition PPC -> PIV as the 3rd one for the Mac, the =20
first two being: (1) 68k -> PPC; (2) OS 9 -> OS X.

Bruno=

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

Subject: OT: [OS X TeX] PPC to Intel
From: "Gerben Wierda" 
Date: Thu, 9 Jun 2005 14:06:21 +0200 (CEST)

> I don't know, but maybe Intel is pushing the envelope and maybe IBM
> has lost its edge. I used to work for IBM. At the time (1980-89) a
> lot of the staff were star trek-ish futuristic smart---I mean one of
> my colleagues programmed the fuel flow simulator for the Saturn V in
> assembly language and fortran---and it was not unusual to work with
> this caliber of people in both hardware and software. I get the
> impression that is not the case any longer. They appear to be
> becoming sort of a software service company. I really don't know what
> happens at IBM these days when it comes to hardware development, but
> Apple is obviously not impressed.

IBM is doing fine work for instance with the Cell processor. But that
beast has a target which quite differs from PC or Server-like systems
(e.g. it has "lossy behaviour" which is fine for getting pixels to a
screen in a playstation but not so fine for data integrity on PC's or
servers). The PPC is also doing fine as far as being able to build really
powerful computing with it (Big Mac, Blue/Gene), but at a terrible price
in terms of power consumption (and heat). Both processors do very fine
when it comes to support for multi-processor etc. And the G4 from
Freescale (formerly Motorola) is not going anywhere too (Where is the
7448? And if it comes will it even reach 2GHz?)

My personal guess is that next to the power consumption issue Steve
mentioned, the big issue is Office:Mac. With an Intel CPU, running the
Windows version of Office becomes a viable alternative. Microsoft is unde=
r
pressure to cut cost (profits are not increasing anymore). Maybe Steve
knows something we don't?

I think it is a missed opportunity that they have not chosen to do a
dual-architecture strategy. Customer: whatever is inside your Mac: Intel
or PPC, the user experience will be the same. CPU architecture doesn't
matter. That would have prevented an Osborne on coming PPC sales as well
as the option to keep things like XServe's and such G5, something science
likes a lot (Big Mac).

I guess that they have not done this because it might have led to
lackluster efforts by developers to support Intel and confusion for some.
But the dual-CPU-architecture option will remain open to them and given
their road map they will in fact have a period of multiple-architecture,
something they could keep up for a long time (and in the labs they
definitely will). But the Osborne worry remains.

G


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

Subject: Re: [OS X TeX] iTeXMac (waiting for stable v. 2)
From: "Eric van der Oord" 
Date: Thu, 9 Jun 2005 14:52:28 +0200

I hope to be wrong, but I'm afraid no patch for the Tiger-preview  
issue of good ol' iTeXmac 1.3.15 is planned.

In the meanwhile, can one run pdfsync with iTexmac 1.3.15 and  
Texniscope -- is some "howto" available ?

Thanks for any hint

Eric

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

Subject: Re: [OS X TeX] A suggestion for NewPdftricks (or for pdftricks in general)
From: "Herbert Schulz" 
Date: Thu, 9 Jun 2005 07:57:55 -0500


On Jun 9, 2005, at 2:57 AM, Alain Matthes wrote:

>
> Sorry but there is a little problem. \@ptsize is defined
> in the class Article  and if you use a personal class (without  
> \@ptsize) ,
>  you obtain an error. It is my case !
>
> But with :
>
>
> \ifpdf
>     \usepackage{pdftricks}
>     \begin{psinputs}
>     \RequirePackage[utf8]{inputenc}
>     \RequirePackage[upright,expert]{fourier}
>     \input{size10.clo} etc....
>
>
> I've no problem with the preceding version of pdftricks
> `
> Thanks
>
> Alain Matthes
>
>


Howdy,

Hmmm...

I knew that I was going to run into a problem but I didn't expect it  
this fast. I'll have to try to work around it. I can require the  
definition of \@ptsize so if it isn't already defined it will get the  
value defined as an option to the pdftricks package. Note that with  
\providecommand a point size designation as an option to pdftricks  
will NOT override one by the class if it exists; is that the behavior  
one wants? It is easy to make it an override but I worry about other  
packages that follow pdftricks that need the original value. Give me  
a bit of time to think about it.

Good Luck,

Herb Schulz
(herbs@wideopenwest.com)



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

Subject: Re: [OS X TeX] Font problem?
From: "Fran=E7ois G. Schmitt" 
Date: Thu, 9 Jun 2005 15:20:34 +0200

Thanks for the several comments I received. Here are some answers.

> How did you install tex?  You seem to be missing the cmextra fonts,=20
> but I think they are part of the base install.
>
> Aaron

I installed everything listed using the i-Installer.

> Howdy,
>
> How did you re-install ``all the indicated files''? Was it via=20
> i-installer or directly from teTeX/TeXLive? It looks like the system=20=

> is not finding the Computer Modern .pfb files. That could just be that=20=

> you need to run `sudo texhash' in Terminal or maybe worse.
>
> Good Luck,
>
> Herb Schulz

I tried to run `sudo texhash'  but I get 'sudo: texhash: command not=20
found'. is there something to be done before? I am not using Terminal=20
very often.

> This looks very bad! The command `basename=B4 is usually found in=20
> /usr/bin. I think you need to fix your ~/.MacOSX/environment.plist and=20=

> your environment. Could you check ~/.MacOSX/environment.plist and open=20=

> Terminal and invoke there 'env | grep -i path'?
>
> But the actual problem is that TeX thinks you haven't installed the PS=20=

> versions of Computer Modern fonts, so it tries to create the PK fonts=20=

> at the right size.
>
> So solve this: what is 'updmap --listmaps' showing in Terminal?
>
> --
> Greetings
>
>   Pete
>

Where is located the '~/.MacOSX/' folder? If this is in my home=20
directory, I could not find it.
The commands 'env | grep -i path' and  'updmap --listmaps'  receive as=20=

answers 'command not found'.

Do you have other suggestions?
Francois Schmitt=


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

Subject: Re: [OS X TeX] Font problem?
From: "Aaron Jackson" 
Date: Thu, 9 Jun 2005 09:38:43 -0400

On Jun 9, 2005, at 9:20 AM, Fran=E7ois G. Schmitt wrote:

> Thanks for the several comments I received. Here are some answers.
>
>> How did you install tex?  You seem to be missing the cmextra fonts,=20=

>> but I think they are part of the base install.
>>
>> Aaron
>
> I installed everything listed using the i-Installer.
>
>> Howdy,
>>
>> How did you re-install ``all the indicated files''? Was it via=20
>> i-installer or directly from teTeX/TeXLive? It looks like the system=20=

>> is not finding the Computer Modern .pfb files. That could just be=20
>> that you need to run `sudo texhash' in Terminal or maybe worse.
>>
>> Good Luck,
>>
>> Herb Schulz
>
> I tried to run `sudo texhash'  but I get 'sudo: texhash: command not=20=

> found'. is there something to be done before? I am not using Terminal=20=

> very often.

The command texhash is part of the base install and should be there. =20
So, either your path is not set properly, or something is seriously=20
wrong with your tex install.  At this point it is a mystery as to what=20=

is going wrong.  Try the following:

ls -la /usr/local/teTeX/bin/powerpc-apple-darwin6.8/texhash

you should get the following result:

lrwxrwxrwx  1 root  admin  8 30 Mar 18:10=20
/usr/local/teTeX/bin/powerpc-apple-darwin6.8/texhash@ -> mktexlsr

You could always just try to reinstall using the i-installer.  This is=20=

a bit drastic, but sometimes it helps to fix what's broken and saves=20
the time that would otherwise be spent debugging.

Aaron

>
>> This looks very bad! The command `basename=B4 is usually found in=20
>> /usr/bin. I think you need to fix your ~/.MacOSX/environment.plist=20
>> and your environment. Could you check ~/.MacOSX/environment.plist and=20=

>> open Terminal and invoke there 'env | grep -i path'?
>>
>> But the actual problem is that TeX thinks you haven't installed the=20=

>> PS versions of Computer Modern fonts, so it tries to create the PK=20
>> fonts at the right size.
>>
>> So solve this: what is 'updmap --listmaps' showing in Terminal?
>>
>> --
>> Greetings
>>
>>   Pete
>>
>
> Where is located the '~/.MacOSX/' folder? If this is in my home=20
> directory, I could not find it.
> The commands 'env | grep -i path' and  'updmap --listmaps'  receive as=20=

> answers 'command not found'.
>
> Do you have other suggestions?
> Francois Schmitt
> --------------------- 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: Re: [OS X TeX] bibdesk 1.1
From: "Norm Gall" 
Date: Thu, 09 Jun 2005 07:46:19 -0600

Are you sure that it is the order and not the capitalisation of the  
field names?  I've had a feature/bug request in for months about that.

ng

On 8-Jun-05, at 23:55 hrs, Michael Gedalin wrote:

> The following is produced by downloading from the adsabs abstract  
> service:
>
> @ARTICLE{2004JGRA..10903106G,
>    author =3D {{Gedalin}, M. and {Balikhin}, M.},
>     title =3D "{Electric potential in the low-Mach-number quasi- 
> perpendicular collisionless shock ramp revisited}",
>   journal =3D {Journal of Geophysical Research (Space Physics)},
>      year =3D 2004,
>     month =3D mar,
>    volume =3D 109,
>     number =3D A18,
>     pages =3D {3106-+},
>    adsurl =3D {http://adsabs.harvard.edu/cgi-bin/nph-bib_query? 
> bibcode=3D2004JGRA..10903106G&db_key=3DAST},
>   adsnote =3D {Provided by the Smithsonian/NASA Astrophysics Data  
> System}
> }
>
>
> After Saving As from Bibdesk 1.1 I get the following:
>
> @article{2004JGRA..10903106G,
>     Adsnote =3D {Provided by the Smithsonian/NASA Astrophysics Data  
> System},
>     Adsurl =3D {http://adsabs.harvard.edu/cgi-bin/nph-bib_query? 
> bibcode=3D2004JGRA..10903106G&db_key=3DAST},
>     Author =3D {{Gedalin}, M. and {Balikhin}, M.},
>     Journal =3D {Journal of Geophysical Research (Space Physics)},
>     Month =3D mar,
>     Number =3D A18,
>     Pages =3D {3106-+},
>     Title =3D {{Electric potential in the low-Mach-number quasi- 
> perpendicular collisionless shock ramp revisited}},
>     Volume =3D 109,
>     Year =3D 2004}
>
> and the bib file becomes not portable: the first one is properly  
> opened by the corresponding software on a PC (Windows), the latter  
> does not show most of the fields.
> Is there any reason why Bibdesk changes the order of the fields in  
> the bib file ? (It is the order which makes the file not portable.)
> Michael
>
>
>
> *******************************************************
> *Michael Gedalin
> *Department of Physics
> *Ben-Gurion University
> *POB 653
> *Beer-Sheva, 84105
> *Israel
> *Tel: 972-8-6461645
> *Fax: 972-8-6472904
> *Email: gedalin@bgumail.bgu.ac.il
> *http://physics.bgu.ac.il/~gedalin
> *******************************************************
>
> --------------------- 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: 
>
>
>

-- 
There's something the technicians need to learn from the artists.
If it isn't aesthetically pleasing, it's probably wrong.


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

Subject: Re: [OS X TeX] multi-page preview in Texshop 2.03
From: "Gary L. Gray" 
Date: Thu, 9 Jun 2005 09:54:12 -0400


On Jun 9, 2005, at 3:02 AM, Ingo Reich wrote:

> if I select the preview option "multi-page" in the preferences of =20
> texshop 2.03, the preview always jumps to the top of the currrent =20
> page after typesetting. I remember that this has already been =20
> discussed =96 and fixed =96 with respect to the "one page" option, but =
=20
> I just cannot find the relevant mails. Is there some easy way to =20
> fix this?

This needs to be fixed by Dick and I know he is aware of the problem =20
and is working on it. It is really the only thing about TeXShop under =20=

Tiger that is not an amazing improvement (well, there is the slow =20
preview, but that is PDFkit and Preview suffers from that problem too).

-- Gary=

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

Subject: Re: [OS X TeX] bibdesk 1.1
From: "Adam R. Maxwell" 
Date: Thu, 9 Jun 2005 06:58:04 -0700

Hello Michael,

On Jun 8, 2005, at 22:55, Michael Gedalin wrote:

> The following is produced by downloading from the adsabs abstract  
> service:
>
> @ARTICLE{2004JGRA..10903106G,
>    author =3D {{Gedalin}, M. and {Balikhin}, M.},
[...]
> }
>
>
> After Saving As from Bibdesk 1.1 I get the following:
>
> @article{2004JGRA..10903106G,
>     Adsnote =3D {Provided by the Smithsonian/NASA Astrophysics Data  
> System},
[...]
> }
>
> and the bib file becomes not portable: the first one is properly  
> opened by the corresponding software on a PC (Windows), the latter  
> does not show most of the fields.
> Is there any reason why Bibdesk changes the order of the fields in  
> the bib file ? (It is the order which makes the file not portable.)

I believe we change the order of the fields so that it's  
deterministic, and you have a guaranteed order (alphabetized) when  
adding new fields.  This makes diffs in CVS easier.  Since BibTeX  
itself doesn't care about the order of the fields (unless we've  
missed something for the last few years), this is acceptable and  
portable.

What software are you using that doesn't recognize this?  JabRef  
should work fine, for instance.

Adam


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

Subject: Re: [OS X TeX] bibdesk 1.1
From: "Adam R. Maxwell" 
Date: Thu, 9 Jun 2005 06:59:44 -0700


On Jun 9, 2005, at 06:46, Norm Gall wrote:

> Are you sure that it is the order and not the capitalisation of the  
> field names?  I've had a feature/bug request in for months about that.

Just curious: what's the problem with capitalization of field names?

Adam


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

Subject: Re: [OS X TeX] Font problem?
From: "Fran=E7ois G. Schmitt" 
Date: Thu, 9 Jun 2005 16:12:18 +0200

> The command texhash is part of the base install and should be there.  
> So, either your path is not set properly, or something is seriously 
> wrong with your tex install.  At this point it is a mystery as to what 
> is going wrong.  Try the following:
>
> ls -la /usr/local/teTeX/bin/powerpc-apple-darwin6.8/texhash
>
> you should get the following result:
>
> lrwxrwxrwx  1 root  admin  8 30 Mar 18:10 
> /usr/local/teTeX/bin/powerpc-apple-darwin6.8/texhash@ -> mktexlsr
>
I get:
lrwxrwxrwx  1 root  wheel  8  8 Jun 17:13 
/usr/local/teTeX/bin/powerpc-apple-darwin6.8/texhash -> mktexlsr

> You could always just try to reinstall using the i-installer.  This is 
> a bit drastic, but sometimes it helps to fix what's broken and saves 
> the time that would otherwise be spent debugging.
>
I re-installed already several times, using basic install or full 
install...
Should I clean something before next try?

Best regards
Francois Schmitt



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

Subject: Re: [OS X TeX] bibdesk 1.1
From: "Norm Gall" 
Date: Thu, 09 Jun 2005 08:12:11 -0600

I use carbon Emacs (not surprisingly) and various built-in functions  
(like bibref) gag on them.  I have some lisp that converts back, but  
it sometimes take a while to do a 500 entry database.

n

On 9-Jun-05, at 07:59 hrs, Adam R. Maxwell wrote:

>
> On Jun 9, 2005, at 06:46, Norm Gall wrote:
>
>
>> Are you sure that it is the order and not the capitalisation of  
>> the field names?  I've had a feature/bug request in for months  
>> about that.
>>
>
> Just curious: what's the problem with capitalization of field names?
>
> Adam
>
> --------------------- 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: 
>
>
>

-- 
"No man was ever taken to hell by a woman unless he already had a
ticket in his pocket, or at  least had been fooling around with  
timetables."
-- Archie Goodwin  


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

Subject: Macs and Intel
From: "Rene Borgella" 
Date: Thu, 9 Jun 2005 10:19:49 -0400

Folks:

I've notice postings from several list members re. this big change. 
I  have found the following articles to be interesting and 
informative.  Perhaps you will too . . .   I think the most 
informative of these are the universal binary documents from Apple 
and the anatech ones.  In Apple's you will find some of the 
limitations of the transition and older software (what Bruno was 
commenting about the other day).


1-What the others say

< http://www.theinquirer.net/?article=3D23769 >

  WWDC 2005 - Apple to Move to Intel Processors in 2006


Apple's Move to x86: More Questions Answered


John Siracusa mourns the Power PC


MacInTouch




2-What Apple and those actually involved in developing Say

Apple Developer Transition


Apple's Documentation

NB - look especially at Appendix A, Rosetta

The folks behind "Rosetta"


Early Preview of Apple's Development Hardware (what comes w/the transition =
kit)


Apple Developers Begin Testing Intel-Powered Mac



cheers,

Rene



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

Subject: Re: [OS X TeX] bibdesk 1.1
From: "Adam R. Maxwell" 
Date: Thu, 9 Jun 2005 07:23:23 -0700


On Jun 9, 2005, at 07:12, Norm Gall wrote:

> I use carbon Emacs (not surprisingly) and various built-in  
> functions (like bibref) gag on them.  I have some lisp that  
> converts back, but it sometimes take a while to do a 500 entry  
> database.

Funny, I parsed that as "I use carbon Emacs ".  Anyway, we use  
capitalized names since they are used as keys in a dictionary, and  
things break internally if we change a character in the key.  We  
could probably lowercase them on saving, but shouldn't bibref be  
fixed to understand the keys, since they're correct BibTeX?

Adam



>
> On 9-Jun-05, at 07:59 hrs, Adam R. Maxwell wrote:
>
>
>>
>> On Jun 9, 2005, at 06:46, Norm Gall wrote:
>>
>>
>>
>>> Are you sure that it is the order and not the capitalisation of  
>>> the field names?  I've had a feature/bug request in for months  
>>> about that.
>>>
>>>
>>
>> Just curious: what's the problem with capitalization of field names?
>>
>> Adam
>>
>> --------------------- 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: 
>>
>>
>>
>>
>
> -- 
> "No man was ever taken to hell by a woman unless he already had a
> ticket in his pocket, or at  least had been fooling around with  
> timetables."
> -- Archie Goodwin 
> --------------------- 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: Re: [OS X TeX] Font problem?
From: "Bruno Voisin" 
Date: Thu, 9 Jun 2005 16:33:03 +0200

Le 9 juin 05 =E0 16:12, Fran=E7ois G. Schmitt a =E9crit :

> I re-installed already several times, using basic install or full =20
> install...
> Should I clean something before next try?

Just in case: on your setup, what's the output (in Terminal) of:

     echo $PATH

Bruno Voisin

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

Subject: Re: [OS X TeX] Font problem?
From: "Peter Dyballa" 
Date: Thu, 9 Jun 2005 16:38:41 +0200


Am 09.06.2005 um 15:20 schrieb Fran=E7ois G. Schmitt:

> I tried to run `sudo texhash'  but I get 'sudo: texhash: command not=20=

> found'. is there something to be done before? I am not using Terminal=20=

> very often.
>
>> This looks very bad! The command `basename=B4 is usually found in=20
>> /usr/bin. I think you need to fix your ~/.MacOSX/environment.plist=20
>> and your environment. Could you check ~/.MacOSX/environment.plist and=20=

>> open Terminal and invoke there 'env | grep -i path'?
>
> Where is located the '~/.MacOSX/' folder? If this is in my home=20
> directory, I could not find it.
> The commands 'env | grep -i path' and  'updmap --listmaps'  receive as=20=

> answers 'command not found'.

OK, your UNIX shell environment seems to be in the garbage bin on your=20=

desktop ... but we can get it out of it! First I'll give this public=20
advice, then I'll send you my edited environment.plist file privately,=20=

because attachments are not passed to the list members.

Open a Terminal and type

	/bin/mkdir ~/.MacOSX

Then go to a Finder window and type Shift-Cmd-g or from the Goto Menu=20
-> Go to folder. Fill in ~/.MacOSX and press OK. Now you see that empty=20=

directly you just openned before. Another way to open ~/.MacOSX is to=20
type in Terminal

	/usr/bin/open ~/.MacOSX

--
Mit friedvollen Gr=FC=DFen

   Pete

Time flies like an error
but fruitflies like a banana


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

Subject: Re: [OS X TeX] PPC to Intel
From: "Joseph C. Slater" 
Date: Thu, 09 Jun 2005 10:36:28 -0400


On Jun 9, 2005, at 7:55 AM, Bruno Voisin wrote:

> Le 9 juin 05 =E0 13:34, Joseph C. Slater a =E9crit :
>
>
>> I wouldn't be surprised if from a consumer standpoint they try to =20
>> sell it as no different than going from a G4 to a G5.
>>
>
> Not really. Did you look at the WWDC keynote's webcast? Steve Jobs =20
> presented the transition PPC -> PIV as the 3rd one for the Mac, the =20=

> first two being: (1) 68k -> PPC; (2) OS 9 -> OS X.
>

Right, but that presentation was to developers, not consumers. I'm =20
sure the marketing will hype the new chip, and downplay that it means =20=

anything other than speed. The mantra in the early 90s was "The PPC =20
is a Mac". It was a hard sell. They may learn from that and smooth it =20=

over better in the consumer's eyes this time. To offset the Osborne =20
effect, I wouldn't be surprised if they downplayed the difference =20
when they are selling products using differing CPUs. I wouldn't be =20
surprised if the plan turns into a dual architecture strategy... high =20=

end using PPC, low end using Intel... or what ever mix they decide is =20=

best. The problem for them is how to get developers to commit to dual-=20=

binaries. They've probably done that as much as possible now. In 1.5 =20
years, if they say that high end workstation machines will retain PPC =20=

architecture, I wouldn't be surprised. However, they have to do it in =20=

a way that doesn't upset high-end developers who invest a lot in =20
transitioning. IBM might cave and meet some of Job's demands just to =20
get back in this game. The only thing I'm sure of is that nobody =20
really knows how it's going to play out.
Joe=

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

Subject: Re: [OS X TeX] Font problem?
From: "Fran=E7ois G. Schmitt" 
Date: Thu, 9 Jun 2005 16:39:21 +0200

>> I re-installed already several times, using basic install or full 
>> install...
>> Should I clean something before next try?
>
> Just in case: on your setup, what's the output (in Terminal) of:
>
>     echo $PATH
>

the output is
/usr/bin:/bin:/usr/sbin:/sbin:/Users/francois_schmitt


Francois Schmitt


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

Subject: PPC, x86, Linux performence
From: "Rene Borgella" 
Date: Thu, 9 Jun 2005 11:07:20 -0400



No more mysteries: Apple's G5 versus x86, Mac OS X versus Linux
< http://anandtech.com/mac/showdoc.aspx?i=3D2436 >

I am not qualified to understand, let alone comment, on much of what 
the article said.  This, however, caught my eye:

'Let us summarize: in theory, the PowerPc 970FX is a very wide, 
deeply pipelined superscalar monster chip, with excellent Branch 
prediction and fantastic features for streaming applications. And let 
us not forget the two parallel FPUs and the SIMD Altivec unit, which 
can process up to 4 calculations per clock cycle.

The disadvantages are the rather coarse way that the 970FX handles 
the instruction flow and the high latency to the RAM.'

and, later:

'Mac OS X is incredibly slow, between 2 and 5 times slower, in 
creating new threads, as it doesn't use kernel threads, and has to go 
through extra layers (wrappers).


Not saying it's true, but I wonder if there was some limitations of 
the PPC chip, power needed, heat output, and these all added up to no 
G5 3GHz processors and no Powerbook anytime soon.  Jobs may have 
simply been pissed at IBM because Apple couldn't deliver on its 
promise of a 3GHz G5 in the time frame that Jobs promised.  Result: a 
pissed off Jobs likes to see heads roll (remember ATI?). Others have 
speculated that being that Sony and Microsoft are using PPC chips in 
their upcoming products, Apple saw the writing on the wall and 
realized that IBM would have their attention spread out too thin for 
Jobs.

Who knows, but the fact that OS X has been ported to both 
architectures from its inception, suggests to me that this switch 
isn't something that came up "all of the sudden".  Indeed, Intel has 
been attempting to woo Apple several years now.

Rene



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

Subject: Yet Another New Adapted pdftricks Package
From: "Herbert Schulz" 
Date: Thu, 9 Jun 2005 10:08:59 -0500

Howdy,

I've updated the adapted pdftricks package so that using classes that  
don't have (or use) the ``standard'' point size class options (i.e.,  
10pt (default), 11pt, 12pt) still works with pdftricks. If the  
standard options are used the pdftricks figures are defaulted to that  
point size; in all other cases (e.g., the memoir class at 14pt or a  
class that doesn't define \@ptsize and then read in a class option  
file based on its value) the default is 10pt.

I've also added options local to this pdftricks of 10, 11 and 12  
(notice no `pt' - to prevent interference with class options) so you  
can change the default behavior of this pdftricks.

This is in addition to the previous:

i)figure processing change to get better Bounding Box information in  
the figure .pdf; and
ii)AutoRotate of figures is turned off by default (there is an  
autorotate option to get back to default behavior).

As usual, please let me know of any problems.

Oh, before I forget (again)... You can get it from my download site,  
.

Good Luck,

Herb Schulz
(herbs@wideopenwest.com)



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

Subject: Threads on MacIntel
From: "Simon Spiegel" 
Date: Thu, 9 Jun 2005 17:25:01 +0200

Sorry to be spoil sport here, but could we please restrict the =20
discussion on the PPC -> Intel change to LaTeX related issues? I'm =20
also very surprised and excited about this development, but there are =20=

discussions all over the web on this (I recommend the Mac Achaia on =20
ArsTechnica), and I really don't see why we have to start another one =20=

in this mailgroup. Maybe I'm the only one who thinks like this, but =20
this mail list already produces enough mails (which is good) and =20
keeps me busy reading that I think we should try to stay a bit focused.

Sorry for the rant.

simon
--
Simon Spiegel
Mutschellenstr. 97
8038 Z=FCrich

Telephon: ++41 43 535 81 71
Mobophon: ++41 76 459 60 39

http://www.simifilm.ch

"I'm not that easy to impress. =96 O, a blue car." Homer Simpson




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

Subject: Re: [OS X TeX] Threads on MacIntel
From: "Jon Guyer" 
Date: Thu, 9 Jun 2005 11:38:59 -0400


On Jun 9, 2005, at 11:25 AM, Simon Spiegel wrote:

> Sorry to be spoil sport here, but could we please restrict the 
> discussion on the PPC -> Intel change to LaTeX related issues?
:
:
> Maybe I'm the only one who thinks like this,

Nope. You're not.


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

Subject: Re: [OS X TeX] Font problem?
From: "Aaron Jackson" 
Date: Thu, 9 Jun 2005 11:53:27 -0400

On Jun 9, 2005, at 10:39 AM, Fran=E7ois G. Schmitt wrote:

>>> I re-installed already several times, using basic install or full=20
>>> install...
>>> Should I clean something before next try?
>>
>> Just in case: on your setup, what's the output (in Terminal) of:
>>
>>     echo $PATH
>>
>
> the output is
> /usr/bin:/bin:/usr/sbin:/sbin:/Users/francois_schmitt

Your path is not set correctly.  However, the i-installer should have=20
properly set this for you.  You can try to set it yourself so you can=20
run texhash to see if that fixes your font problem.  If you have bash=20
type:

PATH=3D/usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
export PATH

or if you have tcsh type:

setenv PATH /usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH

The problem is that whichever of the above commands works needs to be=20
in either ~/.bashrc or ~/.tcshrc respectively to make it permanent, but=20=

you should never have to do this if everything was installed properly=20
in the first place (the path is changed in the system initialization=20
file not your personal initialization file).

The only thing that I can suggest is to do a reinstall (nothing needs=20
to be cleaned up beforehand), but keep careful note of exactly what you=20=

do.  That way somebody on this list will be able to spot what is going=20=

wrong.  You are experiencing problems that should not occur...

Aaron



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

Subject: [OS X TeX] Threads on MacIntel
From: "Rene Borgella" 
Date: Thu, 9 Jun 2005 11:45:59 -0400

At 11:38 AM -0400 6/9/05, Jon Guyer wrote:
>On Jun 9, 2005, at 11:25 AM, Simon Spiegel wrote:
>
>>Sorry to be spoil sport here, but could we=20
>>please restrict the discussion on the PPC ->=20
>>Intel change to LaTeX related issues?
>:
>:
>>Maybe I'm the only one who thinks like this,
>
>Nope. You're not.
>
>-


My apologies, then.  I'm sincerely sorry if I=20
offended anyone or caused any one to feel that=20
they wasted their time reading posts off the=20
topic of TeX.  I hesitated to post this type of=20
info here, but saw that several others were=20
seemingly interested in this thread, and so I=20
posted two messages.

Just for the record, I DON'T mind when others on=20
this list do occasionally post what is not always=20
strictly TeX related, as the folks on this list=20
generally have thoughtful, provocative ideas=20
about all manner of things -- including TeX!

Ren=E9

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

Subject: Re: [OS X TeX] Font problem?
From: "Herbert Schulz" 
Date: Thu, 9 Jun 2005 11:05:41 -0500


On Jun 9, 2005, at 10:53 AM, Aaron Jackson wrote:

>
> Your path is not set correctly.  However, the i-installer should  
> have properly set this for you.  You can try to set it yourself so  
> you can run texhash to see if that fixes your font problem.  If you  
> have bash type:
>
> PATH=3D/usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
> export PATH
>
> or if you have tcsh type:
>
> setenv PATH /usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
>
> The problem is that whichever of the above commands works needs to  
> be in either ~/.bashrc or ~/.tcshrc respectively to make it  
> permanent, but you should never have to do this if everything was  
> installed properly in the first place (the path is changed in the  
> system initialization file not your personal initialization file).
>
> The only thing that I can suggest is to do a reinstall (nothing  
> needs to be cleaned up beforehand), but keep careful note of  
> exactly what you do.  That way somebody on this list will be able  
> to spot what is going wrong.  You are experiencing problems that  
> should not occur...
>
> Aaron
>
>

Howdy,

It may be that the CLI option was not checked when the i-installer  
did the TeX Configuration step. The easiest way around this is to re- 
run the Configuration stage of the TeX i-package. Do an `Expert'  
install and uncheck everything except but the CLI option. That will  
have the proper changes made to /etc/profile, etc., so that the  
proper paths are followed.

By the way, if the Ghostscript i-package is installed I think /usr/ 
local/bin/ should also be part of the $PATH. Is that there?

Good Luck,

Herb Schulz
(herbs@wideopenwest.com)



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

Subject: Re: [OS X TeX] A suggestion for NewPdftricks (or for pdftricks in general)
From: "Alain Matthes" 
Date: Thu, 9 Jun 2005 18:15:27 +0200


Le 9 juin 05 =E0 14:57, Herbert Schulz a =E9crit :

> Howdy,
>
> Hmmm...
>
> I knew that I was going to run into a problem but I didn't expect =20
> it this fast. I'll have to try to work around it. I can require the =20=

> definition of \@ptsize so if it isn't already defined it will get =20
> the value defined as an option to the pdftricks package. Note that =20
> with \providecommand a point size designation as an option to =20
> pdftricks will NOT override one by the class if it exists; is that =20
> the behavior one wants? It is easy to make it an override but I =20
> worry about other packages that follow pdftricks that need the =20
> original value. Give me a bit of time to think about it.
>
> Good Luck,
>
> Herb Schulz
> (herbs@wideopenwest.com)
>

Thanks !

Fine for me !!!

Alain Matthes=

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

Subject: Re: [OS X TeX] Font problem?
From: "Fran=E7ois G. Schmitt" 
Date: Thu, 9 Jun 2005 18:16:53 +0200

> Your path is not set correctly.  However, the i-installer should have 
> properly set this for you.  You can try to set it yourself so you can 
> run texhash to see if that fixes your font problem.  If you have bash 
> type:
>
> PATH=3D/usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
> export PATH
>
> or if you have tcsh type:
>
> setenv PATH /usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
>
> The problem is that whichever of the above commands works needs to be 
> in either ~/.bashrc or ~/.tcshrc respectively to make it permanent, 
> but you should never have to do this if everything was installed 
> properly in the first place (the path is changed in the system 
> initialization file not your personal initialization file).
>
I have changed the path (using the first alternative using bash):
the command 'sudo texhash' now runs, but other commands are not found:
sudo texhash
/usr/local/teTeX/bin/powerpc-apple-darwin-current/texhash: line 2: 
sort: command not found
/usr/local/teTeX/bin/powerpc-apple-darwin-current/texhash: line 2: 
uniq: command not found
/usr/local/teTeX/bin/powerpc-apple-darwin-current/texhash: line 147: 
tty: command not found

BTW I could not find the folder  ~/.bashrc:
cd ~/.bashrc
-bash: cd: /Users/francois_schmitt/.bashrc: No such file or directory

> The only thing that I can suggest is to do a reinstall (nothing needs 
> to be cleaned up beforehand), but keep careful note of exactly what 
> you do.  That way somebody on this list will be able to spot what is 
> going wrong.  You are experiencing problems that should not occur...
>
I will follow this advice.
thanks
Francois Schmitt


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

Subject: Re: [OS X TeX] Threads on MacIntel
From: "Jon Guyer" 
Date: Thu, 9 Jun 2005 14:01:27 -0400


On Jun 9, 2005, at 11:45 AM, Rene Borgella wrote:

> My apologies, then.  I'm sincerely sorry if I offended anyone

No need to apologize. Certainly I'm not offended and I don't get the 
sense that Simon is, either. I was just supporting his /request/ that 
this list stay on topic. I was also one who previously /requested/ that 
this list steer clear of generic TeX, non-OS X TeX questions that have 
other fora. That request has been ignored, making the list less 
valuable for me, but evidently more valuable for the majority of people 
here. So it goes.

I'm on a number of pretty high-volume lists (MacOSX-TeX is only in the 
middle of the pack). They're hard to keep up with under the best of the 
circumstances, but when they go off into the weeds (as most of them did 
this week) it gets impossible. Life /for me/ is better when lists stick 
to talking about what they say they're going to talk about. That's all.


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

Subject: Re: [OS X TeX] Font problem?
From: "Aaron Jackson" 
Date: Thu, 9 Jun 2005 15:02:09 -0400

On Jun 9, 2005, at 12:16 PM, Fran=E7ois G. Schmitt wrote:

>> Your path is not set correctly.  However, the i-installer should have =
=20
>> properly set this for you.  You can try to set it yourself so you can =
=20
>> run texhash to see if that fixes your font problem.  If you have bash =
=20
>> type:
>>
>> PATH=3D/usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
>> export PATH
>>
>> or if you have tcsh type:
>>
>> setenv PATH /usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
>>
>> The problem is that whichever of the above commands works needs to be =
=20
>> in either ~/.bashrc or ~/.tcshrc respectively to make it permanent, =20=

>> but you should never have to do this if everything was installed =20
>> properly in the first place (the path is changed in the system =20
>> initialization file not your personal initialization file).
>>
> I have changed the path (using the first alternative using bash):
> the command 'sudo texhash' now runs, but other commands are not found:
> sudo texhash
> /usr/local/teTeX/bin/powerpc-apple-darwin-current/texhash: line 2: =20
> sort: command not found
> /usr/local/teTeX/bin/powerpc-apple-darwin-current/texhash: line 2: =20
> uniq: command not found
> /usr/local/teTeX/bin/powerpc-apple-darwin-current/texhash: line 147: =20=

> tty: command not found

OK, this is very bad!  sort, uniq and tty are system utilities (all =20
UNIX systems have them in fact).  Do they exist on your mac?:

jackson% ls -l /usr/bin/sort
-r-xr-xr-x  1 root  wheel  39976 16 Apr 02:33 /usr/bin/sort

jackson% ls -l /usr/bin/uniq
-r-xr-xr-x  1 root  wheel  14388 16 Apr 02:34 /usr/bin/uniq

jackson% ls -l /usr/bin/tty
-r-xr-xr-x  1 root  wheel  14520 16 Apr 02:33 /usr/bin/tty

If they don't then, your system is in an inconsistent state.  If they =20=

do exist, then there's something screwy with the PATH variable.  sudo =20=

should use the PATH that your current shell uses, which means in this =20=

case:

/usr/local/teTeX/bin/powerpc-apple-darwin-current:/usr/bin:/bin:/usr/=20
sbin:/sbin:/Users/francois_schmitt

so these utilities should be found by texhash.

Try:

Start a new terminal window

  	echo $PATH
	PATH=3D/usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
	export PATH
  	echo $PATH

  then

	sudo texhash

What do each of these commands print out?

>
> BTW I could not find the folder  ~/.bashrc:
> cd ~/.bashrc
> -bash: cd: /Users/francois_schmitt/.bashrc: No such file or directory
>

It's not a directory, it's a file.  The file just contains shell =20
commands that are executed when the shell starts up.  You can create it =20=

with any program that can save as pure text.

Aaron=


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

Subject: Re: [OS X TeX] Font problem?
From: "Gerben Wierda" 
Date: Thu, 9 Jun 2005 22:06:19 +0200

It seems that not all of the BSD environment is there. Maybe it wasn't =20=

installed when you installed the OS?

G

On Jun 9, 2005, at 21:02, Aaron Jackson wrote:

> On Jun 9, 2005, at 12:16 PM, Fran=E7ois G. Schmitt wrote:
>
>>> Your path is not set correctly.  However, the i-installer should =20
>>> have properly set this for you.  You can try to set it yourself so =20=

>>> you can run texhash to see if that fixes your font problem.  If you =20=

>>> have bash type:
>>>
>>> PATH=3D/usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
>>> export PATH
>>>
>>> or if you have tcsh type:
>>>
>>> setenv PATH /usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
>>>
>>> The problem is that whichever of the above commands works needs to =20=

>>> be in either ~/.bashrc or ~/.tcshrc respectively to make it =20
>>> permanent, but you should never have to do this if everything was =20=

>>> installed properly in the first place (the path is changed in the =20=

>>> system initialization file not your personal initialization file).
>>>
>> I have changed the path (using the first alternative using bash):
>> the command 'sudo texhash' now runs, but other commands are not =
found:
>> sudo texhash
>> /usr/local/teTeX/bin/powerpc-apple-darwin-current/texhash: line 2: =20=

>> sort: command not found
>> /usr/local/teTeX/bin/powerpc-apple-darwin-current/texhash: line 2: =20=

>> uniq: command not found
>> /usr/local/teTeX/bin/powerpc-apple-darwin-current/texhash: line 147: =20=

>> tty: command not found
>
> OK, this is very bad!  sort, uniq and tty are system utilities (all =20=

> UNIX systems have them in fact).  Do they exist on your mac?:
>
> jackson% ls -l /usr/bin/sort
> -r-xr-xr-x  1 root  wheel  39976 16 Apr 02:33 /usr/bin/sort
>
> jackson% ls -l /usr/bin/uniq
> -r-xr-xr-x  1 root  wheel  14388 16 Apr 02:34 /usr/bin/uniq
>
> jackson% ls -l /usr/bin/tty
> -r-xr-xr-x  1 root  wheel  14520 16 Apr 02:33 /usr/bin/tty
>
> If they don't then, your system is in an inconsistent state.  If they =20=

> do exist, then there's something screwy with the PATH variable.  sudo =20=

> should use the PATH that your current shell uses, which means in this =20=

> case:
>
> /usr/local/teTeX/bin/powerpc-apple-darwin-current:/usr/bin:/bin:/usr/=20=

> sbin:/sbin:/Users/francois_schmitt
>
> so these utilities should be found by texhash.
>
> Try:
>
> Start a new terminal window
>
>  	echo $PATH
> 	PATH=3D/usr/local/teTeX/bin/powerpc-apple-darwin-current:$PATH
> 	export PATH
>  	echo $PATH
>
>  then
>
> 	sudo texhash
>
> What do each of these commands print out?
>
>>
>> BTW I could not find the folder  ~/.bashrc:
>> cd ~/.bashrc
>> -bash: cd: /Users/francois_schmitt/.bashrc: No such file or directory
>>
>
> It's not a directory, it's a file.  The file just contains shell =20
> commands that are executed when the shell starts up.  You can create =20=

> it with any program that can save as pure text.
>
> Aaron
> --------------------- 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: Re: [OS X TeX] PPC to Intel
From: "Bruno Voisin" 
Date: Thu, 9 Jun 2005 22:25:40 +0200

Le 9 juin 05 =E0 16:36, Joseph C. Slater a =E9crit :

> To offset the Osborne effect,

That really puzzled me, after seeing this very same expression in a =20
message by Gerben two hours earlier. So, to those like me who had =20
never paid attention to this expression before, here's what a bit of =20
googling returned:



And they even mention WWDC2005.

Brunoe=

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

Subject: Re: [OS X TeX] PPC to Intel
From: "Gary L. Gray" 
Date: Thu, 9 Jun 2005 16:31:21 -0400


On Jun 9, 2005, at 4:25 PM, Bruno Voisin wrote:

> Le 9 juin 05 =E0 16:36, Joseph C. Slater a =E9crit :
>
>
>> To offset the Osborne effect,
>>
>
> That really puzzled me, after seeing this very same expression in a =20=

> message by Gerben two hours earlier. So, to those like me who had =20
> never paid attention to this expression before, here's what a bit =20
> of googling returned:
>
> 
>
> And they even mention WWDC2005.

Speaking of the Osborne effect, I need to continue this thread by =20
pointing you to today's "I, Cringely" column:

http://www.pbs.org/cringely/pulpit/pulpit20050609.html

It is VERY interesting reading.

-- Gary

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

Subject: Re: [OS X TeX] Font problem?
From: "Bruno Voisin" 
Date: Thu, 9 Jun 2005 23:02:29 +0200

Le 9 juin 05 =E0 18:16, Fran=E7ois G. Schmitt a =E9crit :

>> The only thing that I can suggest is to do a reinstall (nothing =20
>> needs to be cleaned up beforehand), but keep careful note of =20
>> exactly what you do.  That way somebody on this list will be able =20
>> to spot what is going wrong.  You are experiencing problems that =20
>> should not occur...
>
> I will follow this advice.

As Aaron and Gerben just said, things look pretty bad. It might be =20
you'll have to:

- First re-install Panther (in Archive & Install mode), clicking on =20
Personalize at the step where you can, and making sure BSD subsystem =20
is selected.

- Then re-install the TeX i-Package, making sur the last item (CLI =20
activation) is selected.

Warning: Archive & Install is a rather painful (or at least time-=20
consuming) process, in that you'll have to make sure that, for all =20
the additional software that you had installed through installers, =20
all the pieces that had been put inside /Library/ (like plugins, =20
printer drivers, PPDs, etc.) and which have been displaced to /=20
Previous Systems/Previous System1/Library/ by Archive & Install are =20
put back in place. Plus all the additional software installed in =20
invisible directories like /usr/local/ (the default location for =20
software installed by i-Installer) will need to be re-installed.

An alternative solution which might work:

- Get the first Panther CD and, in the Optional Installs folder, =20
double-click the symlink BSD Subsystem and proceed.

- Then re-install the Tex i-Package.

If everything goes well, you should eventually get something like:

$ echo $PATH
/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/teTeX/bin/=20
powerpc-apple-darwin-current

/usr/local/bin is added, for example, if you installed the =20
GhostScript i-Package, and /usr/local/teTeX/bin/powerpc-apple-darwin-=20
current by the TeX i-Package. There may be additional directories in =20
case you installed additional software like Fink or DarwinPorts.

HTH,

Bruno Voisin


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

Subject: What Happened to My Lucida Bright?
From: "Herbert Schulz" 
Date: Thu, 9 Jun 2005 16:06:18 -0500

Howdy,

I just loaded the latest TeX i-installer package and now all of my  
Lucida Bright fonts no longer work. I'm getting bitmapped versions  
and it is all very ugly.

Good Luck,

Herb Schulz
(herbs@wideopenwest.com)



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

Subject: Re: [OS X TeX] Threads on MacIntel
From: "Bob Kerstetter" 
Date: Thu, 9 Jun 2005 16:23:43 -0500


On Jun 9, 2005, at 10:45 AM, Rene Borgella wrote:

> At 11:38 AM -0400 6/9/05, Jon Guyer wrote:
>
>> On Jun 9, 2005, at 11:25 AM, Simon Spiegel wrote:
>>
>>
>>> Sorry to be spoil sport here, but could we please restrict the  
>>> discussion on the PPC -> Intel change to LaTeX related issues?
>>>
>> :
>> :
>>
>>> Maybe I'm the only one who thinks like this,
>>>
>>
>> Nope. You're not.
>>
>> -
>>
>
>
> My apologies, then.  I'm sincerely sorry if I offended anyone or  
> caused any one to feel that they wasted their time reading posts  
> off the topic of TeX.  I hesitated to post this type of info here,  
> but saw that several others were seemingly interested in this  
> thread, and so I posted two messages.
>
> Just for the record, I DON'T mind when others on this list do  
> occasionally post what is not always strictly TeX related, as the  
> folks on this list generally have thoughtful, provocative ideas  
> about all manner of things -- including TeX!
>

The discussion has been fine, Rene. It's not exactly off-topic. A few  
people will comment on the topic for a few days and then it will go  
away. No big deal.  It's just like any other conversation---sometimes  
it strays a little. That's a good thing, now and then.

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


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

Subject: Re: [OS X TeX] What Happened to My Lucida Bright?
From: "Bruno Voisin" 
Date: Thu, 9 Jun 2005 23:24:36 +0200

Le 9 juin 05 =E0 23:06, Herbert Schulz a =E9crit :

> I just loaded the latest TeX i-installer package and now all of my =20
> Lucida Bright fonts no longer work. I'm getting bitmapped versions =20
> and it is all very ugly.

Latest TeX i-Package here too, but Lucida fonts working OK. Did you =20
run texhash, and updmap as required afterwards? How's /Library/teTeX/=20
share/texmf.local/web2c/updmap.cfg? Are the corresponding lines =20
uncommented out, namely:

     # Y&Y's Lucida Bright and  Lucida New Math supporting "Berry"-style
     # tfm names (commercial fonts):
     Map lucidabr.map
     Map lumath.map

     # Y&Y's Lucida Bright and  Lucida New Math supporting "Y&Y"-style
     # tfm names (commercial fonts):
     Map lucidabr-o.map
     Map lumath-o.map

> Good Luck,

Wishing to yourself?

Bruno ;-)=

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

Subject: Re: [OS X TeX] Font problem?
From: "Claus Gerhardt" 
Date: Thu, 9 Jun 2005 23:24:43 +0200

I think a simple "Upgrade" of the OS will do, only make sure that the  
BSD subsystem is selected. If in doubt, use the customization option  
and not the easy install.

Claus

On Jun 9, 2005, at 23:02, Bruno Voisin wrote:

>
> - First re-install Panther (in Archive & Install mode), clicking on  
> Personalize at the step where you can, and making sure BSD  
> subsystem is selected.


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

Subject: Re: [OS X TeX] What Happened to My Lucida Bright?
From: "Herbert Schulz" 
Date: Thu, 9 Jun 2005 16:33:03 -0500


On Jun 9, 2005, at 4:24 PM, Bruno Voisin wrote:

> Le 9 juin 05 =E0 23:06, Herbert Schulz a =E9crit :
>
>
>> I just loaded the latest TeX i-installer package and now all of my =20=

>> Lucida Bright fonts no longer work. I'm getting bitmapped versions =20=

>> and it is all very ugly.
>>
>
> Latest TeX i-Package here too, but Lucida fonts working OK. Did you =20=

> run texhash, and updmap as required afterwards? How's /Library/=20
> teTeX/share/texmf.local/web2c/updmap.cfg? Are the corresponding =20
> lines uncommented out, namely:
>
>     # Y&Y's Lucida Bright and  Lucida New Math supporting "Berry"-=20
> style
>     # tfm names (commercial fonts):
>     Map lucidabr.map
>     Map lumath.map
>
>     # Y&Y's Lucida Bright and  Lucida New Math supporting "Y&Y"-style
>     # tfm names (commercial fonts):
>     Map lucidabr-o.map
>     Map lumath-o.map
>
>
>> Good Luck,
>>
>
> Wishing to yourself?
>
> Bruno ;-)


Howdy,

Ok! As happened once before... I also installed the latest ConTeXt =20
beta and that messed the fonts up. Once I got rid of that and re-=20
configured TeX via the i-installer everything is back to normal. Sigh...

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: