Variants for locales in Japanese

[mariashinoto]

I would like to work on the locale for Japanese, which is not yet complete. But there is an additional problem in Japanese, since

• several terms are in some journals expressed in English (e.g. "p." instead of "項")
• sometimes a word is written in syllables, sometimes in Chinese characters (e.g. ほか or 他)
• sometimes a shortened version is used, sometimes not (e.g. "訳" instead of "翻訳")

There are many other cases, such that it might be helpful to set up several Japanese locales. But these would not fit to the official language code.

Another solution is not to use a locale for Japanese papers at all and instead write styles for Japanese journals with fixed prefixes and suffixes.

Since I am now setting up several styles for Japanese journals in the Humanities, I would like to get this problem solved before starting with CSL.

[adam3smith]

Thanks -- looking forward to seeing this and happy to help where we can. The way to do this is to encode the most widely accepted/used version in the Japanese locale (but erring on the side of using the Japanese term when in doubt) and then using the locale section of the specific journal CSL style to redefine terms that differ from the main locale as described here: http://docs.citationstyles.org/en/stable/specification.html#locale

[mariashinoto]

Thanks for the quick help.

I will try it this way, although it means that several settings of the earlier contributor -- which are correct -- will be changed. You can then decide when I send a pull request.

I am not sure whether this is a good solution, and in the long term, I can imagine that creating additional versions for attributes can be added to the frequent "single" and "multiple", e.g. "kanji", "kanji-abbreviated", "kana"; the alphabetical version could then stay as is, and according to the journal's requirements, one can choose single and multiple "p." / "pp." and the kana version of et al. beside an abbreviated kanji version for translator.

But I see that this needs additional programming in the CSL processor which may be difficult, beside the discussions about what to add and what not.

So I will work on "hard coded" Japanese CSL styles for the time being as well. -- The locale will be my first pull request, so bare with me.

Am 01.04.2020 um 11:18 schrieb Sebastian Karcher [email protected]:

Thanks -- looking forward to seeing this and happy to help where we can. The way to do this is to encode the most widely accepted/used version in the Japanese locale (but erring on the side of using the Japanese term when in doubt) and then using the locale section of the specific journal CSL style to redefine terms that differ from the main locale as described here: http://docs.citationstyles.org/en/stable/specification.html#locale

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[mariashinoto]

Sebastian,

today I uploaded a version of the Japanese locale. But I am not happy with it and need to test it.

I did not know how to test without having that locale registered, so I sent a pull request.

But now I see that I could set up a CSL style with a special locale tag at the beginning where I can set up all elements and attributes to test. I could later update the existing locale, when I have tested the individual locale elements in the CSL files.

Do I understand that correctly? That would make working with all these different versions in Japanese paper really easy, and there is no need to officially post the version I have uploaded (though it should be OK).

After all, I have to say that CSL and the locale XML is much easier and a lot better developed than the fragile BibLatex / Biber environment that I have tested for years now. I would wish for some more CSL variables for the multilingual work I am doing, but at least, a stable and easy to understand environment is already there.

Best, Maria

Am 01.04.2020 um 11:18 schrieb Sebastian Karcher [email protected]:

Thanks -- looking forward to seeing this and happy to help where we can. The way to do this is to encode the most widely accepted/used version in the Japanese locale (but erring on the side of using the Japanese term when in doubt) and then using the locale section of the specific journal CSL style to redefine terms that differ from the main locale as described here: http://docs.citationstyles.org/en/stable/specification.html#locale

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.