From MacOSX-TeX@email.esm.psu.edu Sun Jul 31 19:49:58 2005
Received: from engremail.engr.psu.edu ([130.203.201.4]) by ENGRMAIL1.engr.psu.edu with Microsoft SMTPSVC(5.0.2195.6713);
Sun, 31 Jul 2005 19:49:58 -0400
Received: from email.esm.psu.edu ([130.203.247.204]) by engremail.engr.psu.edu with Microsoft SMTPSVC(5.0.2195.6713);
Sun, 31 Jul 2005 19:49:57 -0400
Date: Sun, 31 Jul 2005 20:00:13 -0400
Message-ID: <84813.23881@email.esm.psu.edu>
Subject: MacOSX-TeX Digest #1450 - 07/31/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: 31 Jul 2005 23:49:57.0859 (UTC) FILETIME=[8ECE1330:01C5962A]
MacOSX-TeX Digest #1450 - Sunday, July 31, 2005
BibDesk and CrossRefs
by "Jon Hanson"
Bibliotex?
by "Kevin Walzer"
Re: [OS X TeX] BibDesk and CrossRefs
by "Adam R. Maxwell"
WARMFigTo"EPS"?
by "Jung-Tsung Shen"
Re: [OS X TeX] memoir: Why can't appendix be in the back matter?
by "Johan Almqvist"
Re: [OS X TeX] memoir: Why can't appendix be in the back matter?
by "Bruno Voisin"
Re: [OS X TeX] memoir: Why can't appendix be in the back matter?
by "Johan Almqvist"
Re: [OS X TeX] memoir: Why can't appendix be in the back matter?
by "Bruno Voisin"
Re: [OS X TeX] BibDesk and CrossRefs
by "Norm Gall"
Re: [OS X TeX] BibDesk and CrossRefs
by "Adam R. Maxwell"
Re: [OS X TeX] WARMFigTo"EPS"?
by "Gary L. Gray"
Re: [OS X TeX] Hand-Writing Style Mathematical Formula for Keynote Blackb
by "Gary L. Gray"
----------------------------------------------------------------------
Subject: BibDesk and CrossRefs
From: "Jon Hanson"
Date: Sat, 30 Jul 2005 22:17:39 -0400
>> I finally have a bibtex database that has a large number of entries
>> that are candidates for using the crossref feature, but I am having
>> a bit of trouble understanding how BibDesk 1.1.2 deals with
>> automatically copying information into the child entry.
>>
>
> < snip >
>
> Well, it seems that I was doing something wrong, but I have no idea
> what it was. the title is being copied correctly into booktitle when
> I create a book and creating the child copies correctly.
>
> I deleted my preferences before and it still did not work correctly.
> I logged out then in after deleting the prefs and it works correctly.
>
> Corrupted prefs, I guess.
>
You are not crazy! This is the same phenomenon that I posted about a
few weeks ago. See the digests of July 2-4. In short, like me, the
only thing that you did "wrong" was that you created a child record
from a parent that did not have a Booktitle field. Apparently, due
to the way BibTeX operates, it has always been necessary to enter
Booktitle in any book record that you use as a parent.
With the preferences that you have set, BibDesk will copy Title down
to Booktitle when you create a *new* book record, but it will not add
Booktitle, if missing, to an existing book record when you create a
child from it. These existing parent records with no Booktitle
produce offspring that appear mixed up: they have Booktitle blank,
and what should be the Booktitle is in the Title field. To the eye
of a newbie, it appears that Title from the parent is being assigned
to the wrong location.
(Side note: When operating as designed, BibDesk links the Title field
in the child record from the Title field in the parent. I regard
this as undesirable, since the reason for the record being a child in
the first place is that its title is *not* the same as the parent's.
My only experience, however, is with the book--> incollection
combination. Could more experienced users please weigh in on whether
there are cases when one would want Title in the child filled from
Title in the parent?)
I fixed the problem by re-entering the parent records, though I guess
I could have added the Booktitle field manually with a text editor.
Perhaps there is a way that this could be automated with some kind of
script that would add Booktitle to all existing book records that do
not yet have it, filling Booktitle with the contents of Title?
In sum, anyone who thinks they might use cross-references in the
future -- and they are really cool -- should set the preferences in
BibDesk so that Title gets copied to Booktitle when entering new
records. There is no harm in doing this, even for books that will
not become parents, and it could save quite a bit of work down the road.
Cheers,
Jon Hanson
----------------------------------------------------------------------
Subject: Bibliotex?
From: "Kevin Walzer"
Date: Sat, 30 Jul 2005 23:41:39 -0400
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Does anyone on the list use Bibliotex instead of Bibdesk or another
tool? If so can you share your experiences?
- --
Cheers,
Kevin Walzer, PhD
WordTech Software--Open Source Applications and Packages for OS X
http://www.wordtech-software.com
http://www.kevin-walzer.com
http://www.smallbizmac.com.
mailto:sw@wordtech-software.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC7EhyJmdQs+6YVcoRAoa7AJ9gwoGmLwa+WTPKPx8XLDPGnJZ9FACdGMDx
1iKowKMD9VOgamQ/mCAdmho=3D
=3DjnEo
-----END PGP SIGNATURE-----
----------------------------------------------------------------------
Subject: Re: [OS X TeX] BibDesk and CrossRefs
From: "Adam R. Maxwell"
Date: Sat, 30 Jul 2005 21:10:32 -0700
On Jul 30, 2005, at 19:17, Jon Hanson wrote:
>>> I finally have a bibtex database that has a large number of entries
>>> that are candidates for using the crossref feature, but I am having
>>> a bit of trouble understanding how BibDesk 1.1.2 deals with
>>> automatically copying information into the child entry.
>>>
>>>
>>
>> < snip >
>>
>> Well, it seems that I was doing something wrong, but I have no idea
>> what it was. the title is being copied correctly into booktitle when
>> I create a book and creating the child copies correctly.
>>
>> I deleted my preferences before and it still did not work correctly.
>> I logged out then in after deleting the prefs and it works correctly.
>>
>> Corrupted prefs, I guess.
>>
>>
>
> You are not crazy! This is the same phenomenon that I posted about
> a few weeks ago. See the digests of July 2-4. In short, like me,
> the only thing that you did "wrong" was that you created a child
> record from a parent that did not have a Booktitle field.
> Apparently, due to the way BibTeX operates, it has always been
> necessary to enter Booktitle in any book record that you use as a
> parent.
>
> With the preferences that you have set, BibDesk will copy Title
> down to Booktitle when you create a *new* book record, but it will
> not add Booktitle, if missing, to an existing book record when you
> create a child from it.
That is correct, and this is the intended behavior (according to the
developer who implemented it). He says that we only add the
Booktitle to the potential parent when its Title field is changed;
observing all the possible ways a relation could change would cause a
massive slowdown.
> (Side note: When operating as designed, BibDesk links the Title
> field in the child record from the Title field in the parent. I
> regard this as undesirable, since the reason for the record being a
> child in the first place is that its title is *not* the same as the
> parent's. My only experience, however, is with the book-->
> incollection combination. Could more experienced users please
> weigh in on whether there are cases when one would want Title in
> the child filled from Title in the parent?)
We're not selective there; presumably the user is going to change
that field. We don't inherit the metadata fields such as date added/
modified, because they're added by BibDesk.
>
> I fixed the problem by re-entering the parent records, though I
> guess I could have added the Booktitle field manually with a text
> editor. Perhaps there is a way that this could be automated with
> some kind of script that would add Booktitle to all existing book
> records that do not yet have it, filling Booktitle with the
> contents of Title?
There was an AppleScript posted on the BibDesk developer list for
this purpose, I think; it shouldn't be difficult to write a script if
you can't find that one, given the scripts here for
reference.
-- Adam
----------------------------------------------------------------------
Subject: WARMFigTo"EPS"?
From: "Jung-Tsung Shen"
Date: Sun, 31 Jul 2005 00:11:21 -0700
Hi, I started using WARMFigToPDF just now, and am now able to place
the LaTeX labels on the figures after a couple of times of practice. I
was wondering, however, if it's possible to have an applescript
WARMFigToEPS? Many journals in my field (physics) still prefer the
authors provide .eps files but not pdf.
Thanks.
JT
----------------------------------------------------------------------
Subject: Re: [OS X TeX] memoir: Why can't appendix be in the back matter?
From: "Johan Almqvist"
Date: Sun, 31 Jul 2005 12:29:24 +0200
On Jul 30, 2005, at 14:38, Morten H=F8gholm wrote:
> On Sat, 30 Jul 2005 14:30:08 +0200, Johan Almqvist =20
> wrote:
>
>
>> Hi
>>
>> Why does the following work, but not ork if the \backmatter line =20
>> is in there (the appendices lose their numbers and the ToC looks =20
>> wrong)?
>>
>
> It works as I expect it too ;-)
>
> "The \backmatter declaration makes no change to the pagination or =20
> folios but does prohibit sectional division numbering, and =20
> captions, etc., will be numbered continuously."
>
> Quote from the memoir manual.
Sometimes I feel the answers on this list aren't quite what I'd hoped =20=
for, but I guess I'm just not asking the questions very well. Anyhow. =20=
The question I meant to ask was "How can I get appendix numbering =20
even though I'm in the \backmatter in memoir" and the answer is =20
"issue the \setsecnumdepth{chapter} command as the first thing in the =20=
\begin{appendices} environment (and use \setcounter{secnumdepth}{-10} =20=
to turn it off again later)".
-Johan
--=20
Johan Almqvist
johan@almqvist.net
----------------------------------------------------------------------
Subject: Re: [OS X TeX] memoir: Why can't appendix be in the back matter?
From: "Bruno Voisin"
Date: Sun, 31 Jul 2005 12:49:12 +0200
Le 31 juil. 05 =E0 12:29, Johan Almqvist a =E9crit :
> On Jul 30, 2005, at 14:38, Morten H=F8gholm wrote:
>
>> "The \backmatter declaration makes no change to the pagination or =20
>> folios but does prohibit sectional division numbering, and =20
>> captions, etc., will be numbered continuously."
>>
>> Quote from the memoir manual.
>
> Sometimes I feel the answers on this list aren't quite what I'd =20
> hoped for, but I guess I'm just not asking the questions very well. =20=
> Anyhow. The question I meant to ask was "How can I get appendix =20
> numbering even though I'm in the \backmatter in memoir" and the =20
> answer is "issue the \setsecnumdepth{chapter} command as the first =20
> thing in the \begin{appendices} environment (and use \setcounter=20
> {secnumdepth}{-10} to turn it off again later)".
But then the sequel is: why use \backmatter at all, if you're =20
precisely willing to avoid what it does (i.e. suppress section =20
numbering)? Or differently: is there something else that \backmatter =20
does, other than suppressing section numbers, that make you want to =20
use it, in spite of your wanting indeed section numbers?
Bruno Voisin
----------------------------------------------------------------------
Subject: Re: [OS X TeX] memoir: Why can't appendix be in the back matter?
From: "Johan Almqvist"
Date: Sun, 31 Jul 2005 13:09:59 +0200
On Jul 31, 2005, at 12:49, Bruno Voisin wrote:
> Le 31 juil. 05 =E0 12:29, Johan Almqvist a =E9crit :
>> Sometimes I feel the answers on this list aren't quite what I'd =20
>> hoped for, but I guess I'm just not asking the questions very =20
>> well. Anyhow. The question I meant to ask was "How can I get =20
>> appendix numbering even though I'm in the \backmatter in memoir" =20
>> and the answer is "issue the \setsecnumdepth{chapter} command as =20
>> the first thing in the \begin{appendices} environment (and use =20
>> \setcounter{secnumdepth}{-10} to turn it off again later)".
> But then the sequel is: why use \backmatter at all, if you're =20
> precisely willing to avoid what it does (i.e. suppress section =20
> numbering)? Or differently: is there something else that =20
> \backmatter does, other than suppressing section numbers, that make =20=
> you want to use it, in spite of your wanting indeed section numbers?
I have some other "chapters" before the appendices that I don't want =20
numbered (such as a glossary).
-Johan
--=20
Johan Almqvist
johan@almqvist.net
----------------------------------------------------------------------
Subject: Re: [OS X TeX] memoir: Why can't appendix be in the back matter?
From: "Bruno Voisin"
Date: Sun, 31 Jul 2005 13:55:58 +0200
Le 31 juil. 05 =E0 13:09, Johan Almqvist a =E9crit :
> I have some other "chapters" before the appendices that I don't =20
> want numbered (such as a glossary).
An alternative solution is to use \chapter* (unless the glossary is =20
produced automatically, as with MakeIndex). But I must admit I'm not =20
familiar with the memoir class.
Bruno Voisin=
----------------------------------------------------------------------
Subject: Re: [OS X TeX] BibDesk and CrossRefs
From: "Norm Gall"
Date: Sun, 31 Jul 2005 09:13:45 -0600
On 30-Jul-05, at 10:10 hrs, Adam R. Maxwell wrote:
>
> On Jul 30, 2005, at 19:17, Jon Hanson wrote:
>
>
>>>> I finally have a bibtex database that has a large number of entries
>>>> that are candidates for using the crossref feature, but I am having
>>>> a bit of trouble understanding how BibDesk 1.1.2 deals with
>>>> automatically copying information into the child entry.
>>>>
>>>>
>>>>
>>>
>>> < snip >
>>>
>>> Well, it seems that I was doing something wrong, but I have no idea
>>> what it was. the title is being copied correctly into booktitle when
>>> I create a book and creating the child copies correctly.
>>>
>>> I deleted my preferences before and it still did not work correctly.
>>> I logged out then in after deleting the prefs and it works
>>> correctly.
>>>
>>> Corrupted prefs, I guess.
>>
>> You are not crazy! This is the same phenomenon that I posted
>> about a few weeks ago. See the digests of July 2-4. In short,
>> like me, the only thing that you did "wrong" was that you created
>> a child record from a parent that did not have a Booktitle field.
>> Apparently, due to the way BibTeX operates, it has always been
>> necessary to enter Booktitle in any book record that you use as a
>> parent.
>>
>> With the preferences that you have set, BibDesk will copy Title
>> down to Booktitle when you create a *new* book record, but it will
>> not add Booktitle, if missing, to an existing book record when you
>> create a child from it.
>>
>
> That is correct, and this is the intended behavior (according to
> the developer who implemented it). He says that we only add the
> Booktitle to the potential parent when its Title field is changed;
> observing all the possible ways a relation could change would cause
> a massive slowdown.
>
This all makes sense with respect to what I have seen here... I had
missed the previous discussion.
I just reviewed the archives and I cannot find an explanation why the
developer doesn't simply map title -> booktitle. Why create a dummy
field in the parent? The 'linked' information displayed when looking
at a child's record isn't from the child at all, but from the parent.
The whole idea of a crossref in bibtex is to bring the information
missing from the child's entry from the parent's entry. The booktitle
of a child is the title of the parent.
ng
--
"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: Re: [OS X TeX] BibDesk and CrossRefs
From: "Adam R. Maxwell"
Date: Sun, 31 Jul 2005 08:41:26 -0700
On Jul 31, 2005, at 08:13, Norm Gall wrote:
>>> With the preferences that you have set, BibDesk will copy Title
>>> down to Booktitle when you create a *new* book record, but it
>>> will not add Booktitle, if missing, to an existing book record
>>> when you create a child from it.
>>>
>>>
>>
>> That is correct, and this is the intended behavior (according to
>> the developer who implemented it). He says that we only add the
>> Booktitle to the potential parent when its Title field is changed;
>> observing all the possible ways a relation could change would
>> cause a massive slowdown.
>>
>>
>
> This all makes sense with respect to what I have seen here... I had
> missed the previous discussion.
>
> I just reviewed the archives and I cannot find an explanation why
> the developer doesn't simply map title -> booktitle. Why create a
> dummy field in the parent? The 'linked' information displayed when
> looking at a child's record isn't from the child at all, but from
> the parent. The whole idea of a crossref in bibtex is to bring the
> information missing from the child's entry from the parent's entry.
> The booktitle of a child is the title of the parent.
See this message for an explanation; the behavior is a workaround for
a BibTeX bug, and we implemented it based on requests from crossref
users.
Adam
----------------------------------------------------------------------
Subject: Re: [OS X TeX] WARMFigTo"EPS"?
From: "Gary L. Gray"
Date: Sun, 31 Jul 2005 17:26:50 -0400
On Jul 31, 2005, at 3:11 AM, Jung-Tsung Shen wrote:
> Hi, I started using WARMFigToPDF just now, and am now able to place
> the LaTeX labels on the figures after a couple of times of practice. I
> was wondering, however, if it's possible to have an applescript
> WARMFigToEPS? Many journals in my field (physics) still prefer the
> authors provide .eps files but not pdf.
>
Some of the early versions generated both EPS and PDF files. I can
send you some of them to try, but I can't guarantee anything.
As for journals wanting only EPS, we simply convert our PDFs to EPS
and send them to the journal. Acrobat allows you to do that.
-- Gary
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Hand-Writing Style Mathematical Formula for Keynote Blackboard Theme?
From: "Gary L. Gray"
Date: Sun, 31 Jul 2005 19:43:26 -0400
On Jul 29, 2005, at 10:57 AM, Michael S. Hanson wrote:
> On Jul 29, 2005, at 9:49 AM, Gary L. Gray wrote:
>
>
>>> Is such a thing possible?? In particular, I would like to
>>> have PDF equations "attached" to bulleted text in a list, and
>>> have the list build in "by bullet". Right now, I see no way to
>>> place an equation image in-line with bulleted text and have it
>>> build in correctly -- the equations show up either before or
>>> after all the bullet points in the list. Is what I'm after
>>> possible?
>>>
>>
>> I build everything except the slide title in LaTeX (via LaTeXiT),
>> so I can integrate equations in bulleted lists without any
>> trouble. You will see this in the sample slides I posted (they
>> don't contain bulleted lists, but I can readily add a slide with
>> one).
>>
>
> Hmm. At the risk of asking you to do more work, I for one
> would be interested in seeing such a slide. I tend to use Keynote
> schemes that were given away to .Mac account holders some time back
> (such as "Frames" frames.html> or "Basic Research" content/pages/set4.html>, with the text/math customized to Palatino
> or Utopia), and these use custom bullets. I'd like to retain these
> bullets and the ability to use the powerful build tools of Keynote
> to control how information appears on the screen, but imbed in-line
> equations into these bullet items. I have a feeling that I am
> asking too much of the current technology.... Thanks for any
> pointers or suggestions.
As far as I know, you are asking too much. :-)
-- Gary
----------------------------------------------------------------------
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: