@Bruce_D_Arcus1
opened 03:49AM - 14 Sep 23 UTC
The default display for Japanese contributors seems to be hard-coded in citeproc… -js.
I would like to suggest new rendering defaults that take into consideration katakana and original non-Japanese authors' names, which should not be displayed the same way as Japanese names.
## Japanese names
Keep as the current default: always Family Given
## Katakana names
* Given Family: マイケル・ジャクソン
* Family Given (name-as-sort-order): ジャクソン, マイケル
As far as I know, this is how katakana names are written in general, at least in my field. I could be mistaken though. Still, I think this is a better default than the current one. For now I am hard-coding the punctuation "・" but we could attach that to a value if needed.
## Romanesque names
Force to follow romanesque rules instead of Japanese.
This inadvertently follows Japanese name rendering when the language is "ja", which is not appropriate. I wonder if the current default makes sense in certain contexts/fields.
## Options
In case the old default works for other people, an option to keep the legacy defaults or activate the new defaults could be added.
I understand we cannot cater for every language irregularities but I believe that with this, it will make more sense to use citeproc-js for Japanese in certain fields such as mine.
I am new to the community so I might have missed something as well. In this case, I would be glad if someone could point me to the right direction.
## Links
* Here is the full discussion on "Citation Style Language discourse"<br/>
https://discourse.citationstyles.org/t/is-it-possible-to-render-name-part-affixes-in-japanese-author-names/1828
* Here is my copy for the changes I suggest<br/>
https://github.com/frianasoa/citeproc-js
* Related issues<br/>
https://github.com/Juris-M/citeproc-js/issues/225
If allowed, I will submit a pull request, but first, I would like to know if my suggestion makes sense to be added.
Thank you!
Was just reminded of this thread. I’m working on a new project, called Citum (see elsewhere in the forum).
It’s a priority for me to get multilingual right in this project, even though I myself have been a monolingual scholar. So am definitely looking for help/input.
Anyway, I implemented support for this today, described in this spec .
In this project, I keep the template system simple, and use configuration options for features like this. For example:
options:
multilingual:
name-mode: primary
scripts:
katakana:
delimiter: "・"
sort-separator: "、"
cjk:
use-native-ordering: true
delimiter: ""
There may be lessons for CSL if it evolves in that direction.
cc @mayfair @frianasoa @Maria
1 Like
Thank you very much for letting us know about the new project. Looks very interesting! I’ll give it a try and share my impressions as soon as possible. Where is the right place to post comments regarding the Citum project?
The core repo; either the issue tracker (for bugs or feature requests), or the discussion forum:
Next generation citation styling system in Rust
This demo page does show a bit of the multilingual support.
Added a news post with details and instructions: