Localization (Serbian)
I have managed to translate 100% of Zotero to Serbian (locales sr and sr_RS). But, we use both Cyrillic (default) and Latin. As for the latin script it is easily generated by GNU Gettext command:
recode-sr-latin < cyrillic.txt > latin.txt
Note that I have just requested to add Serbian Latin at the official Transifex page, so I can handle both cyrillic and latin translations from there or this could be automatised (through recode-sr-latin).
Note 2, the Latin should be included as sr@latin and sr_RS@latin locales if possible.
recode-sr-latin < cyrillic.txt > latin.txt
Note that I have just requested to add Serbian Latin at the official Transifex page, so I can handle both cyrillic and latin translations from there or this could be automatised (through recode-sr-latin).
Note 2, the Latin should be included as sr@latin and sr_RS@latin locales if possible.
Upgrade Storage
I can see Serbian (Serbia) on the Zotero Transifex project, but not a separate Serbian Latin language. Could you advise whether sr-Latn-RS can be added to Transifex and Zotero’s supported locales, and what submission format you prefer? I can provide the source files once the locale/workflow is confirmed.
I have also prepared Serbian Latin translations for some independent third-party plugins; I will submit those to their respective maintainers rather than mix them with Zotero core.
Thank you,
Branislav Kapetanovic
For a researcher who reads and writes primarily in Latin script, switching between a Latin-script manuscript and Zotero's Cyrillic menus and dialogs makes routine work less consistent and less comfortable. This is a practical interface choice, not a claim that one script is more correct than the other. At present, using our prepared Latin translation requires a local workaround; ordinary users cannot simply select it in Zotero, and local changes can be lost or complicated by updates. An official selectable locale would let each user choose the script they use, while Cyrillic users would see no change.
The translation is already prepared and locally tested, with review files at https://github.com/Kadzo/zotero-sr-latin-translation . We would appreciate a review and a path to making it available in Zotero without leaving a completed community translation indefinitely inaccessible to users. Could the localization team enable a separate Serbian Latin locale in Transifex and advise which locale identifier and remaining technical or review steps are required for inclusion in a future Zotero release? We are ready to maintain and correct the translation through the official workflow.
But it looks like you made some improvements to the existing strings when creating the Latin locale, so if we were to use sr-RS as the source, you'd need to apply those improvements there. Would you be willing to do that?
Dear Zotero Team,
I am following up on the inclusion of Serbian Latin in Zotero Desktop.
Nearly a month has passed since our previous correspondence, and I have installed at least two updates during that time. However, Serbian Latin is still unavailable in the language selection — only Serbian Cyrillic is offered.
The Serbian Latin translation on Transifex is currently 100% complete, and I regularly translate newly added strings. I would therefore appreciate a concrete explanation: what is preventing Serbian Latin from being included, and what step is still missing?
If anything else needs to be translated, reviewed, or tested, please let me know. I would be happy to help and continue maintaining the translation. However, I would like to understand why it remains unavailable to users despite the time that has passed and the updates released.
Please also let me know when we can expect its inclusion, if you can provide an approximate timeframe or target release.
Thank you for your time and response.
Kind regards,
Branislav Kapetanović
Thank you for your reply and for confirming that Serbian Latin will be included in Zotero 11.
Regarding your question, I would prefer to maintain the Latin-script version separately for now. I have previously noticed terminology inconsistencies and wording in the Cyrillic translation that does not sound entirely natural in Serbian. Automatic transliteration would carry these issues over into the Latin-script version.
If automatic transliteration were necessary, I would first need to review the entire Cyrillic translation, compare it with the Latin-script version, and prepare the necessary corrections. This would be a substantial additional task. Only after that review and alignment of the translations could we consider such an approach.
It would also be important to agree on an ongoing review process so that future changes to the Cyrillic source do not reintroduce terminology inconsistencies into both versions. For these reasons, separate maintenance currently seems the safer way to preserve the quality of the Latin-script translation. I am happy to continue maintaining it regularly on Transifex.
I apologize for posting the same message in multiple places. I will keep any further discussion in this thread.
Kind regards,
Branislav Kapetanović
You're already translating sr-RS on Transifex, so the simplest path seems to be making your improvements in the Cyrillic translation, and then we'd have two well-maintained locales for Serbian.
This doesn't require a full review up front. About three quarters of your Latin strings are a straight transliteration of the current Cyrillic, so only the roughly 800 you changed would need to be carried over. We can send you that list, with the current Cyrillic next to your Latin converted back to Cyrillic, have you check and fix the conversions, and apply the Cyrillic changes to Transifex for you. Any later fixes can then go into Cyrillic as you find them.
Would that work?
Thank you for your concrete proposal and your offer to prepare the comparison. This approach would work for me.
Please send me the list of differences, showing the current Cyrillic translation alongside my Latin translation converted to Cyrillic. If possible, please also include the English source text, the string identifier, and the corresponding filename so that I can reliably check the meaning and context.
I would review these entries carefully, file by file, correct any transliteration errors, and ensure consistent terminology before the changes are applied. Further corrections could then be made to the Cyrillic source as we find them.
Please let me know how you would send me the comparison files and how I should return the reviewed changes. Exchanging the files by email would work well for me, so please confirm whether that would also suit you and which address I should send the completed files to. If you prefer another method or a particular file format, please let me know.
Thank you for your help.
Kind regards,
Branislav Kapetanović
Note that you seem to have recently added several hundred Latin strings to the Cyrillic locale. Those are included in a separate tab in the spreadsheet. Be sure to only enter Cyrillic in sr-RS going forward.
I have replied to your email and returned the reviewed spreadsheet with the corrected Cyrillic translations.
In my email, I also clarified my suggestion to prepare the Cyrillic translation and a checked Latin-script version together, keeping both consistent and avoiding transliteration errors.
Thank you for your help and cooperation.
Kind regards,
Branislav Kapetanović