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

spieman.cls spoils document title #997

Closed
Grief opened this Issue May 15, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@Grief

Grief commented May 15, 2018

Input:

\documentclass[12pt]{spieman}

\title{Some title}

\begin{document} 
\maketitle
\end{document}

spieman.cls can be found here: https://github.com/I2Cvb/spie-jei-2015/blob/master/spieman.cls
Output:

<document xmlns="http://dlmf.nist.gov/LaTeXML">
  <resource class="ltx_align_left" src="LaTeXML.css" type="text/css"/>
  <resource class="ltx_align_left" src="ltx-article.css" type="text/css"/>
  <date class="ltx_align_left" role="creation"/>
  <pagination class="ltx_align_left" role="newpage"/>
  <para class="ltx_align_left ltx_noindent" xml:id="p1">
    <p><text font="bold" fontsize="160%">Some title</text></p>
  </para>
  <para class="ltx_noindent" xml:id="p2">
    <break class="ltx_align_left"/>
  </para>
  <para xml:id="p3">
    <break/>
  </para>
</document>

While I understand that the issue is can be more with the class-file itself, is it possible to workaround it somehow to leave <title>Some title</title> unchanged?

@dginev dginev added this to the LaTeXML-0.8.4 milestone May 15, 2018

@brucemiller

This comment has been minimized.

Owner

brucemiller commented May 19, 2018

I assume this is with --includestyles, and it is because the class file (re)defines \title. I guess the safest thing here is to lock the definition (if a class file redefines it w/different argument pattern, it'll likely mess up anyway). So, hopefully fixed? Thanks for the report!

@Grief

This comment has been minimized.

Grief commented May 20, 2018

@brucemiller thank you very much! I've just tested - results are perfect. I really appreciate that you consider to fix such corner cases like this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment