-
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
A Few Minor Suggestions #19
Comments
I myself don't like this style as well, I created the style mainly Also note that this was my first LaTeX package and was originally
I think it isn't used anymore, I've just removed it.
Thanks, I must admit that I can no longer understand all internal
Probably yes, I can take a look at this.
It should print localization string in the main document language. It This is one of insanities of ISO 690, or it's Czech interpretation, that
Ah I see. The code to print titles and subtitles seems pretty hacky, it
and macros
It is requested by the norm, but maybe we could provide option for
Probably yes. Maybe some better way to support it exists now?
pages should be printed in main document language, so we want to
What is the purpose of this?
I've added that. I think it should be in main document language and I
OK Thanks for all your input, it was really useful. |
Thank you for the nice response, I'm very impressed by the swiftness with which you implemented the suggestions.
To get
(Yes I have used small caps again, I just can't bring myself to use all caps.)
I think you are right, technically it doesn't print punctuation, but it alters the punctuation tracker, which I find undesirable, if I were to write a macro using I consider it cleaner to not let
OK that is just horrible, I had no idea how to deal with that in an sufficiently elegant way. But your solution with
I'm not a big fan of putting punctuation into the
together with
from the TeX.SX question above gives a more A similar scheme would have to be introduced for those drivers (
Ugh, they require all caps? (Is that because they can't get their typesetting system to support proper small caps?
No, I don't know of a more elegant solution, I was quite impressed by this after I found out what it does. Normally people requesting support for multiple ISSNs/ISBNs are fobbed off saying that one should cite the exact source one has, which should only have one ISBN (leave aside the issue of ISBN-10 vs ISBN-13 for a second).
It allows people to switch the punctuation between the name and title very efficiently (i.e. by redefining One thing I only just noticed is that some drivers and macros introduce additional unwanted white space, you can see this very clearly in a fullcite which is followed by text, e.g. Some of the offending macros are
But I think the biggest part of spaces is introduced by the drivers. Where we need a |
Excerpts from moewew's message of 2015-09-08 08:52:55 +0200:
Thanks for the suggestions, it really helped me to fix many issues
Thanks, this seems to work nice. I've defined new command
Thanks, I modified this code a little bit and it works nice. It is
I don't know why they require all caps, but I suspect it is the same
I was probably influenced by the fact that my source was librarian
Ok, I suspect more similar biblatex macros should be used somewhere :)
Yeah, there was some unwanted white space. I've commented out linebreaks There are still many issues when I try to compile biblatex-examples.bib, |
It seems like you can get rid of the
I would have liked it better not to redefine With the change, the formats
There are not that many special punctuation macros (off the top of my head I can only think of Instead of defining
and then As well as
It seems that the two lines
do nothing. The standard definition is
then. I did some checks with the full One thing you could add is a "catch-all" entry type. Right now if an entry types is not known, because it doesn't have a driver, we get an error. That could be prevented by re-routing all unknown types to I noted some problems with The With URL entries it seems weird to me that one gets
The punctuation around "[besucht am 2006-10-01]" seems excessive, in this case I would at least expect capitalisation of the text in brackets. For
block to the end of each driver. |
I'm currently doing some clean-up of the code and found
in I would like to use the standard definition of The entire file seems a bit weird since
should that be What about the delimiters between names in citations? In the bibliography one should use a semicolon, I gather, but how about citations, would a comma be OK there? |
I've added author-title mainly for completeness, it doesn't seem to be officially recommended. so if we want to keep it, it should be definitely based on standard |
(the end of comment #19 (comment)) The last bit from this comprehensive issue is probably the "related" mechanism, but I suppose it won't be as easy as adding a few lines of code at the end of each driver, since macros |
Thank you for this very nice ISO 690 style (I myself don't particularly like the style imposed by ISO here, but this is an entirely different matter).
I thought I would share some thoughts on your code containing a few minor changes.
iso.cbx
iso.cbx
can be made even more compact by not redefiningcite:labelyear+extrayear
to include a comma, but using the appropriate command\renewcommand*{\nameyeardelim}{\addcomma\addspace}
otherwise things go pear shaped when using\textcite
(See #16). Unfortunately then if one has alabel
there is no comma between the label and the date, that would need to be solved byThe file would then look like
BTW: I'm not sure about the purpose of
iso.cbx
, I don't think one is supposed to usestyle=iso
, soiso.bbx
is essentially your version ofstandard.bbx
(which does not come with astandard.cbx
). Maybe you can get rid of it.authoryear-iso.cbx
Same goes for
authoryear-iso.cbx
. There I find\DeclareNameFormat{labelname}{#1}
very destructive (it essentially disables all ofbiblatex
's thought-through name features, one of the effects can be seen in #12). If you just want no small caps, there are far less intrusive ways to do that. (Change\mkbibnamelast
to small caps in\AtBegiBibliography
and leave it on#1
in the document.)authoryear-iso.bbx
I'm always wary of commands such as
\printextrayear
bringing their own punctuation. I think it to be cleaner to add punctuation using the "surrounding" macros. (That would require a bit more reworking.)The check in
could probably be gotten rid of by placing the macro inside the conditionals in
names:primary
, I also think it could have adverse effects for@inbook
entries.iso.bbx
I'm not sure what exactly
\mainsstring
and friends should do, but maybe there is another way possible that uses more ofbiblatex
's standard commands.The code used to display the colons with spaces in front seems to introduce a full stop at times (cite the entry
ctan
ofbiblatex-examples.bib
to see an example; that entry reveals another problem: missing support forlabel
in the bibliography). Maybe you can be inspired by http://tex.stackexchange.com/q/130448/35864.I'm no friend of
\MakeUppercase
for last names, I find\textsc
far more aesthetically pleasing, but then don't know exactly what the norm asks for here.Are the
\do
implementations into support multiple ISSNs?
In
\printfield{pagetotal}\usebibmacro{loc:pages}
I think an appropriate field format forpagetotal
should make the macroloc:pages
superfluous (and it will also be more flexible, what if there is a language that has the string in front of the number here?)should be enough to do the same thing, but making use of
biblatex
's localisation machinery.The use of
\setunit{\labelnamepunct}\newblock
instead of\newunit\newblock
after the author instandard.bbx
is a nice feature thatiso.bbx
could also benefit from (after thenames:primary
macro).Regardless of what one thinks of back-references, it could not hurt to support them by having
\setunit{\bibpagerefpunct}\newblock \usebibmacro{pageref}%
close to the end of the drivers (just asstandard.bbx
does).I would expect drivers to end in
\usebibmacro{finentry}
and not\finentry
. (Where normally we have\newbibmacro*{finentry}{\finentry}
, but it can be useful to be able to hook into the end of an entry)The text was updated successfully, but these errors were encountered: