We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
unit
1\zw
A test input is:
\documentclass{ltjtarticle} \usepackage{kanbun} \begin{document} \begingroup \parindent0\zw% \setkanbun{kumi=beta, unit=1\zw}% \Kanbun 壱弐参‘所以’(ゆゑん)。 \EndKanbun \printkanbun \endgroup \begingroup \parindent0\zw% \setkanbun{kumi=beta, unit=2\zw}% \Kanbun 壱弐参‘所以’(ゆゑん)。 \EndKanbun \printkanbun \endgroup \begingroup \parindent0\zw% \setkanbun{kumi=beta, unit=3\zw}% \Kanbun 壱弐参‘所以’(ゆゑん)。 \EndKanbun \printkanbun \endgroup \begingroup \parindent0\zw% \setkanbun{kumi=aki, unit=1\zw}% \Kanbun 壱弐参‘所以’(ゆゑん)。 \EndKanbun \printkanbun \endgroup \begingroup \parindent0\zw% \setkanbun{kumi=aki, unit=2\zw}% \Kanbun 壱弐参‘所以’(ゆゑん)。 \EndKanbun \printkanbun \endgroup \begingroup \parindent0\zw% \setkanbun{kumi=aki, unit=3\zw}% \Kanbun 壱弐参‘所以’(ゆゑん)。 \EndKanbun \printkanbun \endgroup \end{document}
Process it with lualatex and, we will get a result: kanbun-test-multikanji-ruby.pdf
lualatex
For any unit, the ruby ゆゑん for multikanji 所以 should be placed only along with the characters of multikanji.
ゆゑん
所以
The text was updated successfully, but these errors were encountered:
The cause seems that kanbunzwtosp in lua is not updated when unit, or \kanbun_zw is changed.
kanbunzwtosp
\kanbun_zw
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Ruby typeset for multikanji might be misplaced when
unit
is not1\zw
How to reproduce
A test input is:
Process it with
lualatex
and, we will get a result: kanbun-test-multikanji-ruby.pdfExpected Results
For any
unit
, the rubyゆゑん
for multikanji所以
should be placed only along with the characters of multikanji.The text was updated successfully, but these errors were encountered: