Upgrade StorageFeature Request: Extending “original” fields across item types
A small suggestion: the recently added “original publisher” and “original place” fields for books and book chapters have been extremely helpful in practice. I’ve been able to build much more robust multilingual CSL styles thanks to them.
It would be great to extend these fields to other item types for consistency. In particular, reports seem like a natural next step, and journal articles could benefit as well now that they have publisher and place fields. More generally, having an “original title” field available across all item types would be very useful.
Original fields would also make a difference for things like preprints, manuscripts, and web pages, where tracking original versions can matter just as much.
I realize that multilingual citations aren't supported at all, but these new additions already go a long way for those of us who rely on CSL hacks and workarounds. And with the planned ability to hide and rearrange fields, this shouldn’t add much friction for users who don’t need them.
It would be great to extend these fields to other item types for consistency. In particular, reports seem like a natural next step, and journal articles could benefit as well now that they have publisher and place fields. More generally, having an “original title” field available across all item types would be very useful.
Original fields would also make a difference for things like preprints, manuscripts, and web pages, where tracking original versions can matter just as much.
I realize that multilingual citations aren't supported at all, but these new additions already go a long way for those of us who rely on CSL hacks and workarounds. And with the planned ability to hide and rearrange fields, this shouldn’t add much friction for users who don’t need them.
Had you seen this new plugin that add multilingual support?
https://github.com/boan-anbo/cite-non-english
Thanks for the tip about plugin, I have to test it. Although I'm not sure whether it would be able to handle all the styles I need. Many of them are quite specific, so in many cases it's easier to just build a custom CSL for myself.
According to the plugin's readme, it uses some custom fields AND custom CSL. So I'd rather use native fields and build a CSL based on them.