Skip to content
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

Improving default name rendering in Japanese #234

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

frianasoa
Copy link

@frianasoa frianasoa commented Oct 7, 2023

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

Edit 1

I also have this style that requires a half-width space between Family and Given in the bibliography. I do not know much if it is needed for other styles but I hope we could agree on a more flexible way to render Japanese names (delimiters, etc.).
http://kyosei.hus.osaka-u.ac.jp/wp-content/uploads/2022/06/4f3b74173143db2e36ba1b05b19c1121.pdf

Edit 2

Seems like I have already implemented putting affixes to name-part to allow punctuation (space for my use case) between family and given in Japanese names (here). However, I am not sure whether affixing can be used for that. Apparently it is for names with affixes like Jr. etc, according to the comment below. It would be great if someone could point me to the right direction.

I’ve never encountered a need for affixes (like Jr or III) in Japanese. It’s perfectly possible that I missed something there, but in any case the CSL-M spec and the processor do not anticipate them. @fbennett

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 variable if needed.

Romanesque names

Force to follow Romanesque rules instead of Japanese.

In the original Romanesque names 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

I am sorry this is the same content as Issue 228 as I did not receive feedback yet.

Thank you!

@bwiernik
Copy link
Contributor

bwiernik commented Oct 7, 2023

@fbennett you know the most about Japanese name rendering, do you think you could take a look at this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants