-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the language field for citations items #222
Comments
And actually, it would be great to also have the ability to modify the values of multiple Zotero at once. |
Does a language only apply to the title of a work? I guess this is also a problem with the Quickstatements translator? Or would it correctly export a Zotero item (not a citation) with the language set? Depending on the complexity, the ability to apply changes to multiple citations at once could get a bit complicated interface-wise. In such a case I might be inclined to go more in the direction of something like an API endpoint #148 so that you could use your programming tool of choice to make modifications to Cita's data as you see fit. But if this feature would be broadly useful to others, and relatively simple enough to implement, I'd be happy to. |
No, it's the language of the entire work and the QS translator also add the "langue of the work" property. I've opened an issue on the github of the translator. I don't think it would be that complicated, really it should look like the window to add/modify "saved search". |
Okay, I just found out, it's supported by Zutilo for Zotero items, it's not straightforward but it's there ! |
the language field in Zotero is not about the language of the title or the
content. The Language field in Zotero passes a value to the CSL exporter to
tell the CSL which locale to use. For example, use APA citation format for
french. One can still have a french title with in an english citation
locale. There is no field currently in Zotero for language of the metadata
or language of the work.
- Hugh
…On Fri, Dec 9, 2022 at 11:33 AM Futurer ***@***.***> wrote:
Depending on the complexity, the ability to apply changes to multiple
citations at once could get a bit complicated interface-wise.
Okay, I just found out, it's supported by Zutilo
<https://github.com/wshanks/Zutilo> for Zotero items, it's not
straightforward but it's there !
—
Reply to this email directly, view it on GitHub
<#222 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAJ2JWCFX7ZVB3J2WQID2LWMOCQDANCNFSM6AAAAAASTP442I>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Oh wow okay, that's not logical at all to me. I'm sure I'm missing something. I'm not using this field like that at all, and frankly it's saving me a lot of time to use it as I do. And actually as this issue is for citations only, not Zotero items, we can interpret the language value as we want anyway right ? It doesn't interfere with Zotero items. |
same as #99 |
Is your feature request related to a problem? Please describe.
When exporting citations with the Quickstatements translator, I have to manually change the languages of each "title" (i.e und: to fr:) and "Label" (i.e Len to Lfr), because this info is not stipulated in citation items and not editable through the citation editor.
Describe the solution you'd like
A "language" field in the citation editor and the ability to "paste"/modify a field value to multiple items at once.
For example, selecting multiple items with Maj+Left-click and then doing right-click to show a menu and selecting an option called like "modify values" that opens a window where I could select the name of the field and put a value that will be applied to all the items I've selected. That window could look like the window to modify or create "saved searches".
Describe alternatives you've considered
For now I can export citations with the quickstatements translator and edit the data manually in a spreadsheet or I can re-import the citation items back into Zotero in BetterBibTex and edit it manually there (I prefer QS for now).
The text was updated successfully, but these errors were encountered: