-
Notifications
You must be signed in to change notification settings - Fork 3
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
LuaTeX support #2
Comments
As can be seen at luatex-doc(Page 24, section 2.3.2), the macro Most important is that by simply renaming the macro there wouldn't be any backwards compatibility. I'd suggest to add the [Because of the open question regarding the naming and since I didn't dug into the doc code yet (might be subject to change as well), I didn't do a pull request. In addition I'm not sure if this is the right way of contributing to this project (or if there has to be some mailinglist action or something else)] |
@hmenke Is there any plan to fix this one? I guess the only stable way to resolve this permanently would be changing the user Syntax (probably backwards compatible for pdfLaTeX). I could do such changes if that would help. Or are there any other ideas? |
Seems, this is not as complicated as it seems. Quick dirty fix: Changing Line 227 in the .sty to I'm only a LaTeX user and no package author, so this is maybe dirty code and does not meet the standards, but probably someone knows a better solution. |
I currently use the hook management to workaround it, so |
You’re right, that‘s why I called it a quick dirty fix. I didn’t want to recommend this solution for the package maintainer, but for me it is better than not to be able to use the package at all. Just wanted to share this workaround with others. |
Brief outline of the bug
pgf-umlcd
doesn't work with LuaTeX because ofMinimal working example (MWE)
The text was updated successfully, but these errors were encountered: