-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Titles refactoring #45
Conversation
Another issue appeared with |
I'm not sure if it is really safe to drop the |
Of course, I took this references into account as well, but according to the norm, there is no mention of printing such titles in "titles section" of the references. However, now I've realized that |
Mhhh, I think especially The decision whether to use |
No, I can't see such situation in the norm where a part of a multi-volume work is cited. The only one meaningful place for this really seems to be the series. For sure there are some differences between those fields, but no matter which field will be used, I would say it should be included in the "series section". |
Mhhh, OK. But then I would at least expect a way to get "backwards compatibility" for |
Finally, I have had a look into multiple interpretations of the norm and found that |
Titles related macros needed refactoring as well, so here it is:
pub:title
handled some checking onmaintitle
andbooktitle
, which was causing problems e.g. withknuth:ct
works (addressing A Few Minor Suggestions #19 -- at the end of this comment)maintitle
orbooktitle
is not worth to print if it is related to@book
entry type. Hencetitle
is enough.pub:title
has been renamed tohost:titles
and rewritten to be applied to use for printing host item (book, collection, etc.) of the reference.medium-type
macro has been extracted as a separate macro into the drivers@periodical
entry types are handled as follows:titles
macro, for avoiding duplication of the code