-
Notifications
You must be signed in to change notification settings - Fork 24
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
toBiblatex can't handle CJK author names #106
Comments
Partial workaround that uses R package stringi:
|
A more complete workaround:
|
@kijinosu thank for your report. I'm not able to reproduce the behaviour you describe on my machine/locale; I get an error just creating your
Can you elaborate on this? Are you able to submit a pull request? |
* tools::encoded_text_to_latex(text, UTF-8) can fail when text contains Japanese characters, replacing valid text with questions marks * Add escape hatch to return origin/unformatted/unescaped text if this occurs * Closes #106
This worked partially:
|
Did you install the branch I mentioned with e.g. |
Matrix products: default locale: time zone: Asia/Tokyo
|
Did you see my previous message? #106 (comment) Are you able to install R packages from GitHub? |
Yes |
* See toBibtex.person, braces seem necessary if no family name is detected * Addresses #106
How about replacing tools::encoded_text_to_latex with dplR::latexify? |
What are the benefits? |
It uses stringi, which is a wrapper for the International Components for Unicode, and handles CJK properly.
Sent from [Proton Mail](https://proton.me/mail/home) for iOS
2024年9月25日 (水) 13:20, Mathew W. McLean ***@***.***(mailto:2024年9月25日 (水) 13:20, Mathew W. McLean <<a href=)> 送信:
…> How about replacing tools::encoded_text_to_latex with dplR::latexify?
What are the benefits?
—
Reply to this email directly, [view it on GitHub](#106 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/A6QXORHMDZE7VCMGKCGDJUDZYI2XXAVCNFSM6AAAAABOMREY52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZSHA4DINRXGY).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
By handles CJK properly, you mean leaves it as is? That's what the PR currently does without adding an extra package as a dependency. |
* See toBibtex.person, braces seem necessary if no family name is detected * Addresses #106
I mean that it uses stringi, which is a wrapper for ICU4C , a part of the Unicode standard https://icu.unicode.org/. |
* Add latexify() from dplR instead of tools::encoded_text_to_latex to improve conversion of non-ASCII characters to valid latex * Fixes #102, #105, #106 Signed-off-by: Mathew W. McLean <[email protected]>
* Add latexify() from dplR instead of tools::encoded_text_to_latex to improve conversion of non-ASCII characters to valid latex * Fixes #102, #105, #106 Signed-off-by: Mathew W. McLean <[email protected]>
* Add latexify() from dplR instead of tools::encoded_text_to_latex to improve conversion of non-ASCII characters to valid latex * Fixes #102, #105, #106 Signed-off-by: Mathew W. McLean <[email protected]>
I am trying to use RefManageR for biblatex bibliographies that
include CJK text. While most of the bibliography is handled
splendidly, toBiblatex replaces author names with question marks.
My understanding that this is caused by using the old utils::person
object.
Are there any workarounds or other ways to avoid this?
The text was updated successfully, but these errors were encountered: