> 1. Are we allowed to have the latex engine set for xelatex and assume the user has this feature (if they care about compiling the pdf doc)? (The only other exception is uplatex for the Japanese docs.) If not, do we want to make that a dependency specifically for the Chinese translation pdf building?
it's allowed, we in principle support pdflatex, xelatex, and lualatex. However, can lualatex be used instead? That's what CI is running, and that's what TeXperts recommend - xelatex is no longer developed. Okay, then let's go with lualatex. Thanks for replying on the PR about that. > 2. The bot on the PR is failing the docbuild, possibly because of the previous question/point. Although I can't figure out how to get at the actual log to actually check because the output shown is completely useless. (This has become an issue for all doc building since moving to GH.) Does anyone know how to verify this? I'm not sure what your problem is there. The output is exactly what it is for the local build (except the the parts need to be unfolded by clicking on the corresponding tags) Ah, I see. I could click on the little triangle within the log to unfold the part beyond clicking on the tag to get the full log (which I knew about and only gave me the abbreviated log). That was *really* hidden and not obvious. That being said, I still don't see where the error or the failure is in the log. There doesn't see, to be any useful information contained in it. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/dbed0c44-3d0e-4a5b-bb0b-2faa8fa5e270n%40googlegroups.com.
