Bruce D'Arcus

I'm not sure that specific a recommendation would be appropriate, given diverse platforms and installation methods? But it could be included as an example for linux. Care to submit a...

No progress; I've not really thought about it since adding this issue. But to clarify, this is just on parsing; we no longer restrict what we import into the cache,...

> Pinging [@bdarcus](https://github.com/bdarcus) in case there has been relevant discussion in CSL/citeproc forums. I can't think of anything, other than to note that this was of course integrated into the...

I'm a fan, so agree; the latest release added typography features that bring it up to par now with the best of the LaTeX world. But I also don't use...

> Looks like the support CSL files! Docs: https://typst.app/docs/reference/model/bibliography/ Yes, I do know that; I submitted the original FR for that. I assumed you knew. I don't know, however, what...

Hey @ashton314 I've not for awhile had my head in this code, so nothing immediately occurs to me. But I'm wondering, now that I think about it, if it would...

> * Discoverability would be hampered: Typst users would need to not only know about Citar but the `citar-typst` package as well. Possible solution: something like what `embark-consult` does and...

> Since we already have [`parsebib`](https://github.com/joostkremers/parsebib), and `parsebib` already supports Bib(La)TeX and CSL-JSON, it might make sense to add support for Hayagriva to it? Seems a great idea, though I...

> What kind of facilities do you think would be useful? Navigation, a capf for keys, and validation checker maybe? I imagine ideal would be auto-completion of fields and entries,...

> I'm a bit out of my element on this, since I've never used Emacs for editing bib files; or at least not creating them. But if you want to...