Giter Club home page Giter Club logo

biblatex-bookinarticle's People

Contributors

maieul avatar

Watchers

 avatar  avatar  avatar

Forkers

edmundhighcock

biblatex-bookinarticle's Issues

bookinarticle and biblatex style=authortitle-dw

Do you see a simple way to reconcile your very useful bookinarticle entry type with the style=authortitle-dw of the biblatex-dw collection of styles, so as it works with verbose?

In concreto:

At the moment using authortitle-dw

  • the first entry (MemFecunda) is perfectly typeset in the bibliography
  • the second entry (PetrusUrbeVet) is set without colon and space between author and title

Thank you!

@bookinarticle{MemFecunda,
 title          = {Memoria fecunda [Bologna 1425]},
 bookauthor = {Pack, Roger A.},
 maintitle      = {An Ars memorativa from the Late Middle Ages},
 journaltitle   = {Archives d'histoire doctrinale et littéraire du Moyen Age},
 volume     = {54},
 year       = {1979},
 pages      = {221--275}
}

@bookinarticle{PetrusUrbeVet,
 author     = {{Petrus de Urbe veteri}},
 title          = {Ars memorie artificialis [Bologna 1418]},
 bookauthor = {Zappacosta, Guiglielmo},
 maintitle      = {Artis memoriae artificialis libellus ex quodam saeculi XV Codice Ms},
 journaltitle   = {Latinitas},
 volume     = {20},
 year       = {1972},
 pages      = {290--302}
}

Editions splitted in two different volumes

Dear Maieul,
I'm sorry to bother you with such frequent requests, even in this deadly heat.

I don't know if this has ever happened to you in the past: editions in journals divided into several issues or even in different journals.

It seems that this package does not support these cases. Here is an example:

% !TeX root = biblatex-bookinarticle-test.tex
% !TeX program = xelatex
% !TeX encoding = UTF-8
% !TeX spellcheck = it_IT

\begin{filecontents}[overwrite]{biblio.bib}
@Article{Luedwich1917,
  author           = {Lüdwich, Arthur},
  date             = {1917},
  journaltitle     = {Philologus},
  title            = {Über die homerischen Glossen des Apions},
  pages            = {205--247},
  volume           = {74},
}
@Article{Luedwich1918,
  author           = {Lüdwich, Arthur},
  date             = {1918},
  journaltitle     = {Philologus},
  title            = {Über die homerischen Glossen des Apions},
  pages            = {95--127},
  volume           = {75}
}
@Bookinarticle{Apion,
  author           = {Apion},
  title            = {Glossae Homericae},
  keywords         = {auctores},
  crossref         = {Luedwich1917,Luedwich1918},
  shorthand        = {Apion \dots\ L.},
}
\end{filecontents}
\documentclass[b5paper,11pt,twoside]{memoir}

\usepackage[%
	backend=biber,%
	bibstyle=bookinother,%
	citestyle=authoryear, %
	]{biblatex}
\addbibresource{biblio.bib}

\begin{document}
\nocite{*}
\printbibliography

\printbiblist[]{shorthand}
\end{document}

Evaluate for yourself whether to integrate this function. Many thanks in advance!
Domenico

field name / inheritance properties

Many remarks of @ClintEastwood on #10 made me thinking we should change the field name and the property, and think to a better datamodel.

What are the contrainst for evolution:

  • not changing the meaning of the field of standard biblatex type.
  • changing as little as possible the field names of biblatex-bookinarticle.

Here is the actually existing model.
biblatex-bookinarticle-crossref.pdf

We need to think to a better datamodel. Here is example with @mvcollection

Contrainst are :

  • Going from @mvcollection to @bookinincollection, by the the step of @collection and @incollection.
  • Have coherent name, as possible.
  • Be able to refers to the editor of:
    -* the @mvcollection
    -* the @collection
    -* the @bookinincollection

So we have to make distinction between two package:

  • one for the bottom level : the @book-in-something
  • one for adding translator/editor for the @mvcollection when being in @collection.

So what I would do is to write a new datamodel, and submit you. After that, take one week to be sure, and code only next week-end.

So @ClintEastwood, @moewew, @sonator, @Doc73, what do you think of the general idea?

add: bookinproceedings

I have now another peculiar new type that seesm to be worthy of inclusion into your package: an edition of an ancient text published in the proceedings of a conference:

%!TEX TS-program = lualatexmk
\documentclass{scrartcl}
\usepackage{fontspec}
\usepackage[backend=biber,style=authortitle-comp,abbreviate=false]{biblatex}
\usepackage{biblatex-bookinarticle}
\usepackage{filecontents}
\begin{filecontents}{\jobname.bib}
@proceedings{doe:proceedings:2012,
    Editor = {John Doe},
    Eventdate = {2010-01-01/2010-01-05},
    Location = {Paris},
    Publisher = {Publisher},
    Series = {Name of a Series},
    Number = {13},
    Subtitle = {A Nice Collection of Papers},
    Title = {A Very Nice Collection},
    Titleaddon = {Proceedings of a Very Nice Conference},
    Venue = {Conference Hall at the Sorbonne},
    Year = {2012}}
@bookinproceedings{aristotle:doe:proceedings:2012,
    Author = {Aristotle},
    Title = {The Ancient Text},
    Crossref = {doe:proceedings:2012},
    Pages = {100--155},
    Titleaddon = {\bibstring{byeditorin} Editor's Name}}
\end{filecontents}
\addbibresource{\jobname.bib}
\begin{document}
This is the proceedings: \cite{doe:proceedings:2012} and this is the edition published in the proceedings: \cite{aristotle:doe:proceedings:2012}.
\printbibliography
\end{document}

Please note: this is not a case of a bookininproceedings but of a bookinproceedings -- so one may also think about a bookincollection in addition to the bookinincollection.

Many thanks again!
ClintEastwood

Bookineditor missing in bookinbook

Here is a sample:

@Bookinbook{Antiatticista2015,
  author       = {Antiatticista},
  year         = {2015},
  bookineditor = {Valente, Stefano},
  crossref     = {Valente2015},
  shorthand    = {Antiatt.},
}

@Book{Valente2015,
  author    = {Valente, Stefano},
  location  = {Berlin -- Boston},
  publisher = {Walter De Gruyter},
  title     = {The Antiatticist. Introduction and Critical Edition},
  year      = {2015},
  number    = {16},
  series    = {S. G. L. G.},
}

Ancient Work in a series

Dear Maieul,
I'm sorry to bother you always!

I'm searching a way to cite ancient texts published in series as Grammatici Graeci, Commentaria in Aristotelem Graeca etc. etc.
These are series published in many years by lots of editors.
Until now, I used the bookinbook entry, but the results aren't optimal.

An example:

  • Ancient text: Apollonius Dyscolus, De Pronominibus
  • Modern editor: Richard Schneider
  • Published in: Grammatici Graeci Pars II, vol. I.1
    All the works of ApDysc are published in Grammatici Graeci II, but its volume I.1 is by Schneider, while the volume I.2 is by Uhlig (I think because the former was died).

Grammatici Graeci Pars I is devoted to Dionysius Thrax; pars III to Herodianus. All these volumes are by different editors...

As you see, the situation is very complex and I can not find a standard method for proper indexing.

Your bookinincollection doesn't fit this sort of cases, if I understand correctly.

Do you think is possible to integrate complex cases like this in your precious package?
I would be really grateful if you could find a way. However, I have no urgency. Take the time you need! 😃

Bring some field formats in line with `@article`

Currently the fields volume and series (actually also number) inherit the default formats from biblatex.def, @article's format differs from the standard for those fields. Since @bookinarticle seems closer to @article than say @book when it comes to those fields, it could be a nice idea to have

\DeclareFieldFormat[inarticle,bookinarticle]{series}{% series of a journal
  \ifinteger{#1}
    {\mkbibordseries{#1}~\bibstring{jourser}}
    {\ifbibstring{#1}{\bibstring{#1}}{#1}}}
\DeclareFieldFormat[inarticle,bookinarticle]{volume}{#1}% volume of a journal
\DeclareFieldFormat[inarticle,bookinarticle]{number}{#1}% number of a journal

to move the output of @bookinarticle closer to @article.

Typo in doc

Manual pag. 2 sections 2.1 and 2.2.

substitle (2 times) instead of subtitle

Typo in doc pag. 2?

At page 2 we read:

Notes that the bibliography’s style automatically loads bibliography’s style, which means it is compatible with all the verbose-xxx and bibliography’s styles of biblatex, because all of them are identical to the bibliography style.

But I can't understand the meaning of this phrase: it seems something is missing.

Many thanks,
Domenico

Book edited in a chapter of an article written by two scholars

Dear Maieul,
I am not sure of how to treat a particular case, where an ancient book is edited in a chapter of an article written by two authors. The only method I found is the collection, but this method is not satisfactory, because it lacks the journal field.

Here is my bib sample:

@Bookinincollection{Collectio1891--1893,
  author     = {{Collectio~proverbiorum~cod.~Vat.~gr.~306}},
  pages      = {238--253},
  year       = {1891--1893},
  crossref   = {Cohn1891--1893},
  subtitle   = {cum recensione D2 fere concinens},
  titleaddon = {\bibstring{bypublisher} L. Cohn},
}

@Incollection{Cohn1891--1893,
  author    = {Cohn, Leolpold},
  title     = {Zur Ueberlieferung des alphabetischen Corpus},
  year      = {1891--1893},
  pages     = {224--267},
  crossref  = {Crusius1891--1893},
}

@Collection{Crusius1891--1893,
  author    = {Crusius, Otto and Cohn, Leolpold},
  title     = {Zur handschriftlichen Ueberlieferung, Kritik und Quellenkunde der Paroemiographen},
  year      = {1891--1893},
  number    = {Suppl. 6},
  pages     = {201--324},
  addendum  = {(= C.P.G. Suppl. Nr. IV)},
  journal   = {Philologus},
}

rewriting handbook

linked to #12. Now, the handbook show all type, and, finally, speak about crossref. I think we should do the thing in other way: for each type, present data inheritance, and meaning of the field (with the graph).

  1. More readable.
  2. People will be incited to use crossref mechanism, which it is the good way, and avoid mistake in the fields name.

So for each new type, we will have:

  1. What does it do.
  2. An formated example.
  3. A graph of cross-ref.
  4. The description of the specific field.
  5. A .bib example.

so, as for previous issue, what do you think ?

@ClintEastwood, @moewew, @sonator, @Doc73

[Feature request] Bookineditor not working in bookinbook

Please, consider this issue as a reminder for when you have time!

As in subject bookineditor isn't workin inside bookinbook entry type. Here is a sample:

@Bookinbook{ScholiainThucydidem1927,
  author       = {{Scholia~in~Thucydidem}},
  year         = {1927},
  bookineditor = {Hude, C.},
  crossref     = {Hude1927},
  shorthand    = {sch. Thuc.},
}

@Book{Hude1927,
  author    = {Hude, C.},
  location  = {Lipsiae},
  publisher = {B. G. Teubner},
  title     = {Scholia in Thucydidem ad optimos codices collata},
  year      = {1927},
}

Many thanks in advance.

Typo in Doc

Pag. 17, chapter 6: the date of v. 2.1.1 is wrong! 😄

add: bookinphdthesis

Dear Maïeul,
Once more our paths are crossing... I am very happy that you coded this package here. WOUld you mind adding also a bookinphdthesis type?
Phd-theses were (and still are!) not always published but still may contain editions/translations of ancient texts. There is currently no way to treat editions/translations published in or as PhD-theses adequately.
Thanks and keep up the good work!
ClintEastwood

Try biblatex-bookinother and biblatex-morenames

Dear @ClintEastwood and @doc75,

I have finished – I hope – to implement the requirement for #5, #11, #12, #13, #14, #15.

Now there is two new "packages":

  • biblatex-morenames, which adds new bookineditor for a @bookinbook entry (and also other field)
  • biblatex-bookinother, successor of biblatex-bookarticle, which adds new entry type, and also bookineditor field (and bookeditor field).

Could you try theme.

Here the two packages:
biblatex-bookinother.zip
biblatex-morenames.zip

What I mean by "testing":

  • Reading the handbook and tell me if not clear.
  • Testing the feature with your own need as asked on #5, #11, #12, #13, #14, #15 and by email.
  • Make feedback. If there are problems, please do one bullet by problem.

changing name

@moewew, @sonator, @Doc73 @clinsteastwood : what do you think about changing the name of this package, to have a less restricted name ? maybe:
bookinsomething ? bookinothertype ?

it will be also a changing of number, but without breaking compatibility.

unwanted phrase "volume" in 'bookinjournal'

there is an unwanted phrase 'volume' before the "volume.number" of the journal in the bookinjournal type.

Example:
Author, Name. Title Name: Yeah. In: Journaltitle volume 27.3 (2017), 39–60.

Can you please remove the "volume" phrase here?

bookinincollection

J'ai utilisé votre aidant data typ bookinincollection avec un résultat très bon. Merci!

for bookinother: add @bookinjournal

You started your fine idea with the package bookinarticle. An entry for this would give the following result:

Author of Work. Title of Work. Subtitle of Work Edited by Author of Article. In: Author of Article. "Title of Article. Subtitle of Article". In: Journal No. 4 (2016), 16–39.

An example would be:

Aristotle. De lineis insecabilibus. Edited by John Doe. In: Jon Doe. "A brief Work of Aristotle Newly Discussed". In: Journal No. 4 (2016), 16–39.

This is perfect if the title of the "Title of Work" and the "Title of Article" are different from each other.

However, I realised that very often (!) the "author of the article" decided to call his/her article by the name of the Title of the Work of the Author of the Work, so that the "Title of Work" and the "Title of Article" are precisely not the same.

For example:

Jon Doe. "Aristotle. De lineis insecabilibus". In: Journal No. 4 (2016), 16–39.

In that case your bookinarticle would give the following:

Aristotle. De lineis insecabilibus. Edited by John Doe. In: Jon Doe. "Aristotle. De lineis insecabilibus". In: Journal No. 4 (2016), 16–39.

This I find inadequate, because it simply gives twice the author of the work and the title of the work. Since this happens so often, would you agree that we should also have a @bookinjournal which would give the following result:

Author of Work. Title of Work. Subtitle of Work Edited by Author of Article. In: Journal No. 4 (2016), 16–39.

An example would be:

Aristotle. De lineis insecabilibus. Edited by John Doe. In: Journal No. 4 (2016), 16–39.

New fields

Cf talk with @ClintEastwood in #16

  • editor for a @bookinbook means the editor of the including book, not the editor of the included book. Cf the biblatex handbook "The editor(s) of the title, booktitle, or maintitle, depending on the entry type. Use the editortype field to specify the role if it is different from �editor�. See � 2.3.6 for further hints."
  • for translator, it seems that is the same point. "The translator(s) of the title or booktitle, depending on the entry type. If the translator is identical to the editor, the standard styles will automatically concatenate these fields in the bibliography.". So a bookineditor could be useful. However using for a @bookinbook saw it is the editor of included book. Maybe we could ask to @plk to clarify the handbook
  • for annotator, it is the annotator of included book ("The author(s) of annotations to the work. If the annotator is identical to the editor and/or translator, the standard styles will automatically concatenate these fields in the bibliography. See also commentator.")
  • also for commentator ("The author(s) of a commentary to the work.")
  • also for "introduction" ("The author(s) of an introduction to the work.")

shortauthor field in bookinarticle entry

Is it possible to activate the shortauthor field of a bookinarticle entry, too; so as the shorttitle field of the MWE is working? At the moment shortauthor will be ignored.

@bookinarticle{LodovicoPirano,
keywords = {quelle},
hyphenation = {latin},
author = {{Lodovico da Pirano}},
shortauthor = {{Lod\adddotspace da Pirano}},
title = {Regulae memoriae artificialis},
shorttitle = {Regulae mem\adddotspace artif\adddot},
bookauthor = {Baccio Ziliotto},
maintitle = {Frate Lodovico da Pirano e le sue Regulae memoriae artificialis},
journaltitle = {Atti e memorie della Società Istriana di archeologia e storia patria},
volume = {49},
year = {1937},
pages = {189--224}
}

Year not printed ?

from @Doc73
"year" field of bookinarticle is not prited.
I load biblatex in this way:

\usepackage[%
style=philosophy-classic,%
backend=biber,%
dashed=true,%
url = false,%
isbn = false,%
firstinits=true,%
uniquename=init%
]{biblatex}
\usepackage{biblatex-bookinarticle}

Here is a sample of bibtex entry:

@Bookinarticle{Boethus1985,
author = {Boethus},
bookauthor = {Dyck, Andrew R.},
journal = {«Harvard Studies in Classical Philology»},
pages = {75--84},
title = {Lexicorum platonicorum fragmenta},
volume = {89},
year = {1985},
keywords = {auctores},
maintitle = {Notes on platonic lexicography in antiquity},
shorthand = {Boeth.}
}

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.