Jed Brown

I'd suggest it needs to be documented back in the other repo even if the implementation lives in ruby-cff.

I see you just strip out the `{` and `}` characters, then wrap the whole title in braces for BibTeX. This isn't sufficient: different bib styles require different capitalization styles...

Ah, and your fix only addresses the BibTeX issue, not the mangled APA output I also reported. Here's an example of mangled APA output. 

As for finishing the fix, it seems like incomplete implementations of the schema are not a reason to avoid documenting the schema. And also, it would be valuable for the...

LFAToolkit was just a handy example. Let's extend my initial example slightly; we want the BibTeX ``` title={{XYZ}: An {ABC} alternative to {libfoo}} ``` so that it can be rendered...

I don't agree that the entirety of the title field is a proper name. This package has `title: Ruby CFF Library` and could perhaps equally have `title: "ruby-cff: A Ruby...

What's the advantage of having both fields? If someone doesn't know/care, they can just put unprotected case in `title` -- it's exactly what we have now. If they care, they...

Let's assume that a naive user just provides `title` with no markup. Are the BibTeX/rendered results clearly worse if CFF allows markup in that field than if not? Seems to...

Thanks for renaming "transitive credit". > Therefore, the references section is best updated automatically during build/CI. We're doing this in a Java project using the CFF Maven Plugin. How does...

Honestly, I don't think it's a big deal. The BigFloat here is for reference values to measure accuracy of the f32/f64 computation. But we can compute reference values using Zygote...