Open wg030 opened 1 year ago
@michal-h21 and @wg030, hey, how are you doing? Any chance this could be moved forward? My high school requires my graduation thesis to use ISO 690:2022, so this would be quite useful (even though I can probably get away with ISO 690:2010)... Any way I can help?
You can try to use this work-in-progress style. The new ISO version is unfortunately quite complex, so it is pretty hard to support automatic bibliography formatting.
@michal-h21 and @wg030, hey, how are you doing? Any chance this could be moved forward? My high school requires my graduation thesis to use ISO 690:2022, so this would be quite useful (even though I can probably get away with ISO 690:2010)...
As @michal-h21 said, the most current version of the ISO 690:2021 implementation is given in my temporary repository https://github.com/wg030/biblatex-iso690_2021 and work will continue there until it is has been tested enough and is finally ready to be merged here.
Any way I can help?
I see that you are a Czech native speaker?! So one thing you could do to help us is provide a Czech translation by filling the empty language template newlang-iso690_2021.lbx. Besides it would also help us a lot if you tested your own bibliography against the latest version of the style and report any entries which do not look like you would expect them to look like according to the rules of the ISO 690:2021 norm.
I have tried to improve on this style for the last few months with respect to the latest edition of the ISO 690 (see #83) and with this PR I like to publish my work. I am going to open a new issue for a discussion whre I am going to explain more about it.
Altough this version 0.1 of a "ISO 690:2021 Biblatex Bibliography Style" is cosnidered a beta version for testing since it is still incomplete and likely quite error-prone, it solves a few of the open issues:
mediumdesignator
as suggested by moewew.volume
is now idepentend from the fieldmailtitle
. To be able to distinguish I introduced a newmainvolume
field.eid
field.translationof
orcommentaryon
.noenddot
option is still implemented.urldate
andurl
is now supposed to be the other way round.