Closed sdietzel closed 11 years ago
The prevention to compile the class with xelatex without meta font breaks simplicity when adding support for the "normal" meta font. This is because then always one of the two else statements indicating that xelatex is used without meta font is executed. Any ideas how to fix this without having ugly nested statements when using one of the two metafont options?
How about introducing a new boolean "xetexrequired"? Default false, set to true in both metafont ifs, then have a separate if to check if the boolean was set to true somewhere.
Not perfect, but could work...
On 19.03.2013, at 17:55, cspann notifications@github.com wrote:
The prevention to compile the class with xelatex without meta font breaks simplicity when adding support for the "normal" meta font. This is because then always one of the two else statements indicating that xelatex is used without meta font is executed. Any ideas how to fix this without having ugly nested statements when using one of the two metafont options?
— Reply to this email directly or view it on GitHub.
Currently, UTF-8 support is broken when compiling with xelatex (but without Meta font).