Comments (5)
That's actually expected behaviour: the only locators included by the CSL spec are: book, chapter, column, figure, folio, issue, line, note, opus, page, paragraph, part, section, sub-verbo, verse, volume.
This means these are the only ones that we can expect to be rendered by a CSL style (that implements them).
I think that it should be possible to use a generic unqualified locator and let the styles handle it as-is. E.g. cite:[iso:27001, "Clause 6.1.2 c 2"]
could be rendered as expected. Than might make more sense instead of trying to cover every possible case? (That's what BibTeX&co do.)
Another option would be to use a custom formatter (say, enriching the TeX-like one). But again, if one comes from the TeX world she probably expects to be able to give arbitrary locators.
from asciidoctor-bibliography.
Or maybe just:
cite:[iso:27001, prefix="Clause 6.1.2 c 2 of "]
cite:[iso:27001, suffix="Section 3"]
?
I can't figure out how to use those locators -- the underlying CSL style needs to support them first, right?
from asciidoctor-bibliography.
Branch citations
implement prefix, suffix, all standard CSL locators and a custom "locator" locator. TeX macros will require a bit more thought.
from asciidoctor-bibliography.
Should we close this due to #39?
from asciidoctor-bibliography.
Problem is solved for CSL citations but not yet for TeX ones.
However #38 is a better place to discuss that in order to keep things separated. Closing.
from asciidoctor-bibliography.
Related Issues (20)
- Bug with custom attributes when translating to DocBook HOT 3
- Question: own styles HOT 1
- :bibliography-database: not set via asciidoctor-epub3 for included documents HOT 6
- Bib entry with identical author and year HOT 18
- Minor APA format issue HOT 4
- Converting directly with Ruby HOT 2
- Variable interpolation breaks include
- anomalies when using Asciidoctor's ifeval::[] and asciidoctor-bibliography HOT 3
- Errors with asciidoctor-pdf HOT 2
- Numbered bibliography
- Comparison with asciidoc-bib and asciidoctor-bibtex
- A problem building Nokogiri, when installing on Windows HOT 7
- Migrate to GitHub Actions from Travis
- Change default branch to main HOT 1
- Asciidoc-bibliography messes with section levels after include
- The generated bibliography is incomplete HOT 6
- Citations get parsed within inline source code environment HOT 2
- Multi-Citation of more than two keys not working HOT 5
- [enhancement] nocite macro for bibliography entry without expicit citation HOT 1
- Incompatibility with asciidoctor version >= 2.0 HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from asciidoctor-bibliography.