Upgrade StorageWhitespace in East Asian names
This problem is posted in the CSL style forum as well, but I think I might ask here as well.
East Asian names are traditionally written in the form "family name""given name" without any whitespace between the two. CSL handles that nicely. But adding whitespace has become quite common, it is more of the normal case in Korean anyway, and many journals in Japan ask for such whitespace -- but no colon!
There is another case where foreign names are written in katakana in Japanese publications. The do need a whitespace or the more commen "nakaten" "・", otherwise they are unreadable.
Unfortunately I do see no way to work on name parts in a CSL style or locale, and whitespace as prefix or suffix seems to be stripped anyway. Furthermore, there needs to be an identification of names in Katakana, which should then have an option to be separated either by whitespace or nakaten.
As long as this problem is not solved, it is quite useless to post the Japanese CSL styles that I have created in the recent days.
Is there anything I can do about it?
East Asian names are traditionally written in the form "family name""given name" without any whitespace between the two. CSL handles that nicely. But adding whitespace has become quite common, it is more of the normal case in Korean anyway, and many journals in Japan ask for such whitespace -- but no colon!
There is another case where foreign names are written in katakana in Japanese publications. The do need a whitespace or the more commen "nakaten" "・", otherwise they are unreadable.
Unfortunately I do see no way to work on name parts in a CSL style or locale, and whitespace as prefix or suffix seems to be stripped anyway. Furthermore, there needs to be an identification of names in Katakana, which should then have an option to be separated either by whitespace or nakaten.
As long as this problem is not solved, it is quite useless to post the Japanese CSL styles that I have created in the recent days.
Is there anything I can do about it?
Thanks a lot, it seems that I had checked this option earler on a wrong web page; it was outdated, and after reading some remarks on the web about JurisM I concluded that JurisM is not developed any more.
Thanks to your link, I downloaded the version, it works great with my Zotero data, it feels more like a PlugIn, and now I will check all options and get used to it.
The problems I mentioned in this thread are solved anyway. We can close it.