[Bibdesk-users] 1.5.8 and 1.6.0: Tex preview bug difference
I don't remember this being reported. When I use Tex Preview (which I have customized a little to get the output style I want), if there's a non ASCII character in the abstract field of the Bibdesk record (eg a greek character), v 1.5.8 reports an error (though the log doesn't tell you what it is), but v 1.6.0 just runs indefinitely and you have to quit the app. Both work once you've cleared out the offending character(s) (I cut and paste to/from the Abstract field using BBEdit to replace non standard chars). DN __ Research School of Astronomy Astrophysics Mt Stromlo Observatory Australian National University -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] 1.5.8 and 1.6.0: Tex preview bug difference
On Mar 2, 2013, at 10:55, David Nicholls wrote: I don't remember this being reported. When I use Tex Preview (which I have customized a little to get the output style I want), if there's a non ASCII character in the abstract field of the Bibdesk record (eg a greek character), v 1.5.8 reports an error (though the log doesn't tell you what it is), but v 1.6.0 just runs indefinitely and you have to quit the app. Both work once you've cleared out the offending character(s) (I cut and paste to/from the Abstract field using BBEdit to replace non standard chars). DN There are two different problems here. The first is special characters, which can be a problem with tex. Unless you're using special TeX programs like XeTeX those aren't accepted. That's not in any way a problem in BibDesk, it really is a feature: it warns you that your data is not compatible with the tex program you use, which really is the primary purpose of the TeX preview. So it;s a problem with your data. The crash in 1.6.0 has nothing to do with special characters. There is a known problem with (external window) Text TeX preview in 1.6.0. It crashes in a child process. The BibDesk program itself isn't crashing, so you don't need to quit. The bottom-window preview (View Bottom Preview TeX) does not have this problem. This was fixed in the nightly builds, so you may want to get that. Those should be safe to use, only the localizations are disabled (shouldn't be a problem for you.) Christiaan -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] 1.5.8 and 1.6.0: Tex preview bug difference
On 02/03/2013, at 10:11 PM, Christiaan Hofman cmhof...@gmail.com wrote: On Mar 2, 2013, at 10:55, David Nicholls wrote: I don't remember this being reported. When I use Tex Preview (which I have customized a little to get the output style I want), if there's a non ASCII character in the abstract field of the Bibdesk record (eg a greek character), v 1.5.8 reports an error (though the log doesn't tell you what it is), but v 1.6.0 just runs indefinitely and you have to quit the app. Both work once you've cleared out the offending character(s) (I cut and paste to/from the Abstract field using BBEdit to replace non standard chars). DN There are two different problems here. The first is special characters, which can be a problem with tex. Unless you're using special TeX programs like XeTeX those aren't accepted. That's not in any way a problem in BibDesk, it really is a feature: it warns you that your data is not compatible with the tex program you use, which really is the primary purpose of the TeX preview. So it;s a problem with your data. The crash in 1.6.0 has nothing to do with special characters. There is a known problem with (external window) Text TeX preview in 1.6.0. It crashes in a child process. The BibDesk program itself isn't crashing, so you don't need to quit. The bottom-window preview (View Bottom Preview TeX) does not have this problem. This was fixed in the nightly builds, so you may want to get that. Those should be safe to use, only the localizations are disabled (shouldn't be a problem for you.) Christiaan Thanks, Christiaan, I had never explored the bottom preview window, and it work very nicely! I just occasionally need to cut/paste the preview (saves time in generating a \bibitem) so I'll await the full release of 1.6.1 DN -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] 1.5.8 and 1.6.0: Tex preview bug difference
On Mar 2, 2013, at 13:02, David Nicholls wrote: On 02/03/2013, at 10:11 PM, Christiaan Hofman cmhof...@gmail.com wrote: On Mar 2, 2013, at 10:55, David Nicholls wrote: I don't remember this being reported. When I use Tex Preview (which I have customized a little to get the output style I want), if there's a non ASCII character in the abstract field of the Bibdesk record (eg a greek character), v 1.5.8 reports an error (though the log doesn't tell you what it is), but v 1.6.0 just runs indefinitely and you have to quit the app. Both work once you've cleared out the offending character(s) (I cut and paste to/from the Abstract field using BBEdit to replace non standard chars). DN There are two different problems here. The first is special characters, which can be a problem with tex. Unless you're using special TeX programs like XeTeX those aren't accepted. That's not in any way a problem in BibDesk, it really is a feature: it warns you that your data is not compatible with the tex program you use, which really is the primary purpose of the TeX preview. So it;s a problem with your data. The crash in 1.6.0 has nothing to do with special characters. There is a known problem with (external window) Text TeX preview in 1.6.0. It crashes in a child process. The BibDesk program itself isn't crashing, so you don't need to quit. The bottom-window preview (View Bottom Preview TeX) does not have this problem. This was fixed in the nightly builds, so you may want to get that. Those should be safe to use, only the localizations are disabled (shouldn't be a problem for you.) Christiaan Thanks, Christiaan, I had never explored the bottom preview window, and it work very nicely! I just occasionally need to cut/paste the preview (saves time in generating a \bibitem) so I'll await the full release of 1.6.1 DN You can just as well copy the text from the bottom preview. The next release won't provide anything more than that, apart from allowing you to do it in the separate window. The old Text preview will be gone, as it (now) crashes and anyway has always been problematic. Oh, and you are aware that you can copy the fully prepared \bibitem? Christiaan -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] 1.5.8 and 1.6.0: Tex preview bug difference
On 02/03/2013, at 11:43 PM, Christiaan Hofman cmhof...@gmail.com wrote:
You can just as well copy the text from the bottom preview. The next release
won't provide anything more than that, apart from allowing you to do it in
the separate window. The old Text preview will be gone, as it (now) crashes
and anyway has always been problematic. Oh, and you are aware that you can
copy the fully prepared \bibitem?
Christiaan
No, I wasn't aware, but its layout needs to be (typically) in Astrophysical
Journal layout: e.g.
\bibitem[Nicholls et al.(2011)]{Nicholls11}Nicholls, D.~C. et al. 2011, \aj,
142, 83
How do I do that? I would be very useful.
DN
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
Bibdesk-users mailing list
Bibdesk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] 1.5.8 and 1.6.0: Tex preview bug difference
On 03/03/2013, at 12:33 AM, David Nicholls da...@mso.anu.edu.au wrote:
On 02/03/2013, at 11:43 PM, Christiaan Hofman cmhof...@gmail.com wrote:
You can just as well copy the text from the bottom preview. The next release
won't provide anything more than that, apart from allowing you to do it in
the separate window. The old Text preview will be gone, as it (now) crashes
and anyway has always been problematic. Oh, and you are aware that you can
copy the fully prepared \bibitem?
Christiaan
No, I wasn't aware, but its layout needs to be (typically) in Astrophysical
Journal layout: e.g.
\bibitem[Nicholls et al.(2011)]{Nicholls11}Nicholls, D.~C. et al. 2011, \aj,
142, 83
How do I do that? I would be very useful.
OK, it looks like it's effected by Edit Copy As LaTeX, but the result
requires further editing. Is there any source file I can edit to generate the
layout I want?
DN
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
Bibdesk-users mailing list
Bibdesk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] 1.5.8 and 1.6.0: Tex preview bug difference
You can have as many layouts you want, you simply have to write the template
and install it using BibDesk's preferences Templates.
Regards,
Andreas
ETH Zurich
Prof. Dr. Andreas Fischlin
Systems Ecology - Institute of Integrative Biology
CHN E 21.1
Universitaetstrasse 16
8092 Zurich
SWITZERLAND
andreas.fisch...@env.ethz.chmailto:andreas.fisch...@env.ethz.ch
www.sysecol.ethz.chhttp://www.sysecol.ethz.ch
+41 44 633-6090 phone
+41 44 633-1136 fax
+41 79 595-4050 mobile
Make it as simple as possible, but distrust it!
On 02/03/2013, at 15:13 , David Nicholls wrote:
On 03/03/2013, at 12:33 AM, David Nicholls
da...@mso.anu.edu.aumailto:da...@mso.anu.edu.au wrote:
On 02/03/2013, at 11:43 PM, Christiaan Hofman
cmhof...@gmail.commailto:cmhof...@gmail.com wrote:
You can just as well copy the text from the bottom preview. The next release
won't provide anything more than that, apart from allowing you to do it in the
separate window. The old Text preview will be gone, as it (now) crashes and
anyway has always been problematic. Oh, and you are aware that you can copy the
fully prepared \bibitem?
Christiaan
No, I wasn't aware, but its layout needs to be (typically) in Astrophysical
Journal layout: e.g.
\bibitem[Nicholls et al.(2011)]{Nicholls11}Nicholls, D.~C. et al. 2011, \aj,
142, 83
How do I do that? I would be very useful.
OK, it looks like it's effected by Edit Copy As LaTeX, but the result
requires further editing. Is there any source file I can edit to generate the
layout I want?
DN
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
Bibdesk-users mailing list
Bibdesk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
Bibdesk-users mailing list
Bibdesk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] 1.5.8 and 1.6.0: Tex preview bug difference
On Mar 2, 2013, at 6:13, David Nicholls da...@mso.anu.edu.au wrote:
On 03/03/2013, at 12:33 AM, David Nicholls da...@mso.anu.edu.au wrote:
On 02/03/2013, at 11:43 PM, Christiaan Hofman cmhof...@gmail.com wrote:
You can just as well copy the text from the bottom preview. The next
release won't provide anything more than that, apart from allowing you to
do it in the separate window. The old Text preview will be gone, as it
(now) crashes and anyway has always been problematic. Oh, and you are aware
that you can copy the fully prepared \bibitem?
Christiaan
No, I wasn't aware, but its layout needs to be (typically) in Astrophysical
Journal layout: e.g.
\bibitem[Nicholls et al.(2011)]{Nicholls11}Nicholls, D.~C. et al. 2011, \aj,
142, 83
How do I do that? I would be very useful.
OK, it looks like it's effected by Edit Copy As LaTeX, but the result
requires further editing. Is there any source file I can edit to generate
the layout I want?
Sure, change the .bst and edit the TeX preview template to use your preferred
.sty or other setup. There's a button for this in the prefs where you set up
the TeX preview.
Adam
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
Bibdesk-users mailing list
Bibdesk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
[Bibdesk-users] Citing Ancient Sources utilizing BibDesk
I am looking fora solution to implement the style described in the following article (enclosed). Is there a package combination and BibDesk solution that would permit one to follow the format described? -Kevin Guidelines for Citing Ancient Sources Prof. Eva von Dassow The same principles and purposes underlie citation practices no matter what types of items are the objects of reference – ancient sources (texts and artifacts), works of art, or works of modern scholarship. Citation of ancient sources differs in form, but not in principle, from citation of modern works; likewise, citation of artifacts differs in form, but not in principle, from citation of texts. All citations and references must include specific and accurate identification of: 1) the item in question, 2) its publication or the publication in which it is found (if published; otherwise, its provenience and location), and 3) the part(s) of the item cited or referred to; furthermore, 4) the item’s author(s) or creator(s) must be identified and credited, if individual author(s) or creator(s) exist and are known. Ancient texts and artifacts are normally accessed through modern publications. Thus, when citing or referring to these types of primary sources, it is necessary to identify both the ancient source and the modern publication, distinguishing the former clearly from the latter, according to each of the criteria enumerated above. A reference to a modern publication provides the following information: author; publication title; facts of publication; and indication of the place within the publication to which reference is made (usually by page numbers). This simple scheme is complicated by a variety of factors. For instance, if the publication in question is a component of a larger work, such as an article within a book, an entry within an encyclopedia, or a volume in a series, the larger work must be distinguished from its component, both by title and by editor or author; thus, the reference gives the information about the larger work along with the information about the component (usually the facts of publication are identical and therefore not repeated). In an analogous fashion, a reference to an ancient source should include both the information about the modern publication and the information about the ancient source, as follows: title or other identification of the ancient source; modern author, translator, or editor; title of the modern publication; facts of publication; indication of the place within the modern publication where the ancient source is found (usually pages); and, as applicable, indication of the place within the ancient source to which reference is made (on this, see further below). Students must use, and accurately follow, a handbook of style in order to learn how to cite and refer to modern publications, both in bibliographic entries and in notes or parenthetical references (note the differences among these!). The most comprehensive such handbook is the Chicago Manual of Style, 14th ed. (Chicago: University of Chicago Press, 1993). I recommend that students use Mary Lynn Rampolla’s Pocket Guide to Writing in History, 5th ed. (Boston: Bedford/St. Martin’s, 2007), a concise handbook which provides documentation models based on the guidelines established by the Chicago Manual of Style. Since there exists no handbook for students which provides guidelines for citing ancient sources other than the Bible and classical Greek and Latin literature, I have written up the following instructions and examples to explain how to cite ancient sources of various types. • Ancient literary works Standard book, chapter, and paragraph or verse divisions exist for classical works of literature and for biblical books. Citations of classical works give the name of the author, the title of the work (this can be omitted if only one work is known for that author), and the book and paragraph numbers, or line numbers in the case of poetry, for the passage cited; examples follow: • According to Homer, Odysseus landed in Egypt and, after a fierce battle between his men and the Egyptians, stayed there for seven years as a guest of the king (Homer, Odyssey, XIV.257-287). • The poems of Homer formed a common cultural reference point for classical Greek authors; both Herodotus and Thucydides quote them and refer to them (see, e.g., Herodotus, 2.116-7, and Thucydides, 1.3, 1.9, and 4.24). Books of the Bible are cited in a similar manner, but normally without naming authors: • Whereas according to II Samuel 24.1 it is God’s anger against Israel that caused David to take a census of his people, the Chronicler makes Satan the agent who incited David to do this (I Chron. 21.1). • There are numerous stories and motifs that appear both in biblical literature and in ancient Greek literature. For
Re: [Bibdesk-users] Citing Ancient Sources utilizing BibDesk
Thanks for the pointers. I specifically want to use Latex not word or pages since the formatting is reducible once defined. I am a student so just learning Latex. I am blind and I have found that Latex gives me a much more secure experience than word or pages because word and pages really don't reliably format a doc unless one confirms that it looks correctly on the screen. Seeing actually placement on the screen is not something that the Mac Voiceover or windows screen reading software supports. THus Latex is perfect in that it supports command based formatting. I have found that much of BibDesk is accessible via Mac Voiceover so when I received the enclosed requirements I first turned to BibDesk. The requirements appear to be Chicago style with some modifications required to support archeological and historical sources that are cited through other primary sources. Since there are extra fields required there must be some interplay between BibDesk and perhaps a modified style. -Kevin On Mar 2, 2013, at 11:26 AM, Dr. Adam M. Goldstein PhD MSLIS z_californianus-dated-1362677208.ea8...@shiftingbalance.org wrote: Well, that's a little more than most of us on the BibDesk users list can read without drifting off...is there a specific example you can give us from one of these kinds of sources? The best place for this question is probably a BibTeX users list, because the question is really about the style files. You should probably check out biblatex because of the enthusiasm people have for how easy it is to customize. If you are looking for references you can export to Word or Pages, you can design templates using BibDesk. Adam -- Adam M. Goldstein PhD, MSLIS -- z_california...@shiftingbalance.org http://www.shiftingbalance.org http://www.twitter.com/shiftingbalance -- http://www.itis.gov/servlet/SingleRpt/SingleRpt?search_topic=TSNsearch_value=180621 -- (914) 637-2717 (msg) -- Dept of Philosophy Iona College 715 North Avenue New Rochelle NY 10801 http://www.iona.edu/faculty/agoldstein On Mar 2, 2013, at 12:01, Kevin Fjelsted kfjels...@gmail.com wrote: I am looking fora solution to implement the style described in the following article (enclosed). Is there a package combination and BibDesk solution that would permit one to follow the format described? -Kevin Guidelines for Citing Ancient Sources Prof. Eva von Dassow The same principles and purposes underlie citation practices no matter what types of items are the objects of reference – ancient sources (texts and artifacts), works of art, or works of modern scholarship. Citation of ancient sources differs in form, but not in principle, from citation of modern works; likewise, citation of artifacts differs in form, but not in principle, from citation of texts. All citations and references must include specific and accurate identification of: 1) the item in question, 2) its publication or the publication in which it is found (if published; otherwise, its provenience and location), and 3) the part(s) of the item cited or referred to; furthermore, 4) the item’s author(s) or creator(s) must be identified and credited, if individual author(s) or creator(s) exist and are known. Ancient texts and artifacts are normally accessed through modern publications. Thus, when citing or referring to these types of primary sources, it is necessary to identify both the ancient source and the modern publication, distinguishing the former clearly from the latter, according to each of the criteria enumerated above. A reference to a modern publication provides the following information: author; publication title; facts of publication; and indication of the place within the publication to which reference is made (usually by page numbers). This simple scheme is complicated by a variety of factors. For instance, if the publication in question is a component of a larger work, such as an article within a book, an entry within an encyclopedia, or a volume in a series, the larger work must be distinguished from its component, both by title and by editor or author; thus, the reference gives the information about the larger work along with the information about the component (usually the facts of publication are identical and therefore not repeated). In an analogous fashion, a reference to an ancient source should include both the information about the modern publication and the information about the ancient source, as follows: title or other identification of the ancient source; modern author, translator, or editor; title of the modern publication; facts of publication; indication of the place within the modern publication where the ancient source is found (usually pages); and, as applicable, indication of the place within the ancient source to which reference is made (on this, see further below). Students must use, and
Re: [Bibdesk-users] Citing Ancient Sources utilizing BibDesk
If you open Bibdesk's preferences, there is a group of preferences called Fields. In that group, you find a button Edit, next to a line saying Custom BibTeX Types and Fields. It is the first Edit button you reach when tabbing through the window. After selection that Edit button, you can specify which entry types contain which fields, and thus add extra fields needed for a specific biblatex style. Cheers, Jan On 2013-03-02, at 6:46 PM, Kevin Fjelsted kfjels...@gmail.com wrote: Thanks for the pointers. I specifically want to use Latex not word or pages since the formatting is reducible once defined. I am a student so just learning Latex. I am blind and I have found that Latex gives me a much more secure experience than word or pages because word and pages really don't reliably format a doc unless one confirms that it looks correctly on the screen. Seeing actually placement on the screen is not something that the Mac Voiceover or windows screen reading software supports. THus Latex is perfect in that it supports command based formatting. I have found that much of BibDesk is accessible via Mac Voiceover so when I received the enclosed requirements I first turned to BibDesk. The requirements appear to be Chicago style with some modifications required to support archeological and historical sources that are cited through other primary sources. Since there are extra fields required there must be some interplay between BibDesk and perhaps a modified style. -Kevin On Mar 2, 2013, at 11:26 AM, Dr. Adam M. Goldstein PhD MSLIS z_californianus-dated-1362677208.ea8...@shiftingbalance.org wrote: Well, that's a little more than most of us on the BibDesk users list can read without drifting off...is there a specific example you can give us from one of these kinds of sources? The best place for this question is probably a BibTeX users list, because the question is really about the style files. You should probably check out biblatex because of the enthusiasm people have for how easy it is to customize. If you are looking for references you can export to Word or Pages, you can design templates using BibDesk. Adam -- Adam M. Goldstein PhD, MSLIS -- z_california...@shiftingbalance.org http://www.shiftingbalance.org http://www.twitter.com/shiftingbalance -- http://www.itis.gov/servlet/SingleRpt/SingleRpt?search_topic=TSNsearch_value=180621 -- (914) 637-2717 (msg) -- Dept of Philosophy Iona College 715 North Avenue New Rochelle NY 10801 http://www.iona.edu/faculty/agoldstein On Mar 2, 2013, at 12:01, Kevin Fjelsted kfjels...@gmail.com wrote: I am looking fora solution to implement the style described in the following article (enclosed). Is there a package combination and BibDesk solution that would permit one to follow the format described? -Kevin Guidelines for Citing Ancient Sources Prof. Eva von Dassow The same principles and purposes underlie citation practices no matter what types of items are the objects of reference – ancient sources (texts and artifacts), works of art, or works of modern scholarship. Citation of ancient sources differs in form, but not in principle, from citation of modern works; likewise, citation of artifacts differs in form, but not in principle, from citation of texts. All citations and references must include specific and accurate identification of: 1) the item in question, 2) its publication or the publication in which it is found (if published; otherwise, its provenience and location), and 3) the part(s) of the item cited or referred to; furthermore, 4) the item’s author(s) or creator(s) must be identified and credited, if individual author(s) or creator(s) exist and are known. Ancient texts and artifacts are normally accessed through modern publications. Thus, when citing or referring to these types of primary sources, it is necessary to identify both the ancient source and the modern publication, distinguishing the former clearly from the latter, according to each of the criteria enumerated above. A reference to a modern publication provides the following information: author; publication title; facts of publication; and indication of the place within the publication to which reference is made (usually by page numbers). This simple scheme is complicated by a variety of factors. For instance, if the publication in question is a component of a larger work, such as an article within a book, an entry within an encyclopedia, or a volume in a series, the larger work must be distinguished from its component, both by title and by editor or author; thus, the reference gives the information about the larger work along with the information about the component (usually the facts of publication are identical and therefore not repeated). In an analogous fashion, a reference to an ancient source should include both the
