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

platex-dev: Class bxjsbook Error: The value of hyperref 'unicode' key is not suitable #283

Closed
scottkosty opened this issue May 30, 2023 · 6 comments

Comments

@scottkosty
Copy link

On an updated TeX Live 2023 system, I get an error with platex-dev but not with platex. I am not sure but I wonder if the difference is due to a change in behavior of hyperref. Below is an example and the error:

\documentclass[12pt,oneside,fleqn,japanese,autodetect-engine, dvi=dvipdfmx, ja=standard]{bxjsbook}
\usepackage{lmodern}
\usepackage[T1]{fontenc}
\UseRawInputEncoding
\usepackage{babel}

\usepackage{hyperref}
% need to change?
%\usepackage[unicode=false]{hyperref}

\begin{document}
この文書は
\end{document}

Here's the error:

! Class bxjsbook Error: The value of hyperref 'unicode' key is not suitable
(bxjsbook)              for the present engine (must be false).

I attach the example.log file just in case.

If I indeed set unicode to false, it then compiles. I just wanted to make sure: is this change intended?

@u-fischer
Copy link
Member

well it is not a hyperref change. For some reason platex-def uses e-uptex:

C:\Users\micro\Documents\Tests>platex-dev test-utf8
This is e-upTeX, Version 3.141592653-p4.1.0-u1.29-230214-2.6 (utf8.sjis) (TeX Live 202
C:\Users\micro\Documents\Tests>platex test-utf8
This is e-pTeX, Version 3.141592653-p4.1.0-230214-2.6 (utf8.sjis) (TeX Live 2023) 

and in e-uptex \forcecjktoken is defined and this changes a test in hyperref.

@scottkosty
Copy link
Author

Thanks for taking a look! Should I report at https://github.com/latex3/latex2e/ or at https://github.com/texjporg/platex?

@aminophen
Copy link
Contributor

For some reason platex-dev uses e-uptex:

That’is intended: see https://tug.org/pipermail/tex-live/2023-May/049250.html

@scottkosty
Copy link
Author

@aminophen Thank you! Can you confirm that indeed specifying unicode=false is the correct approach? I don't know much about this stuff. I'm just trying to add a fix/workaround so that LyX's Japanese documents continue to compile.

@u-fischer sorry for the misdiagnosed report, and thank you for very much for starting that ML thread!

@u-fischer
Copy link
Member

I leave that open for now. It is possible that hyperref should adapt to the new platex but I will wait for some feedback from @aminophen

@u-fischer u-fischer reopened this May 31, 2023
@scottkosty
Copy link
Author

I think the issue might be fixed. In any case, after a tlmgr update, tests seem to pass on my side.

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

No branches or pull requests

3 participants