In China, when preparing a manuscript in Chinese, the citation for literature in English and Chinese is something like (Smith et al., 2020; 张三等, 2020), where "等" is "et al." Now the standard CSL seems not to support this kind of citation.
I have a style file, which supports that kind of citation, the related part is as follows: <layout locale="en" prefix="(" suffix=")" delimiter=", "> ... </layout> <layout prefix="(" suffix=")" delimiter=", "> ... </layout>
However, CSL validator indicated the code was not valid for CSL 1.0.2.
I can't see the code, but anything you'd do to make this work would use csl-m features and therefore indeed not be valid CSL 1.0.2 -- doesn't mean it doesn't work, but we wouldn't accept it to the repo
I would be very much interested in a Zotero plugin for multilingual support, since I am relying heavily on Juris-m for multilingual citations so far (and not at all for legal citations). Unfortunately, I cannot contribute with coding, but will help with testing, feedback ...
Multilingual support is important on many counts and I would love to see it in Zotero. When I have discussed this on the forums a while back, the advice was Juris-m. My scepticism at the time was its longevity given that it largely relies on one developer and this seems to be proving right (I have never used Juris-m, living with limitations instead, so am judging by comments in this thread only). My concern is that everything outside of the core Zotero, with just one or a couple of champions, will have the same or worse precarity, plugin or not. A reference library should last a career, or multiple careers, and most plugins come and go at too high a frequency, which is to be expected. An addon that takes standard data and does something with it is OK, but custom-structured data will be worse than useless when a plugin dies.
I have a style file, which supports that kind of citation, the related part is as follows:
<layout locale="en" prefix="(" suffix=")" delimiter=", ">
...
</layout>
<layout prefix="(" suffix=")" delimiter=", ">
...
</layout>
However, CSL validator indicated the code was not valid for CSL 1.0.2.
Any hints?