Repository navigation
Conversation
|
Code 0 seems to be correct, the minus sign comes from cmsy10 whose encoding table is on page 31 of http://texdoc.net/texmf-dist/doc/latex/base/encguide.pdf No idea yet why that should have bad dimensions. |
|
I think the minus-sign character has nonzero depth in the font, and tftopl (the official implementation of parsing tfm files) agrees. Is this actually a case of failing to detect the baseline correctly? There's a text.latex.preview parameter that could be related, but I'm running out of time to debug now. |
|
Thanks -- it could be all of those things, but I haven't really been able to investigate yet either. I tried |
|
I don't think this release critical. Bumping this to 2.0.1 |
NelleV
modified the milestones:
2.0.1 (next bug fix release),
2.0 (style change major release)
|
Side note, the table is now an pg 33 of http://texdoc.net/texmf-dist/doc/latex/base/encguide.pdf |
QuLogic
modified the milestones:
2.0.1 (next bug fix release),
2.0.2 (next bug fix release)
tacaswell
modified the milestones:
2.1.1 (next bug fix release),
2.2 (next feature release)
|
Closing in favor of #16366 which applies the same fix in |
For some reason, the minus sign is coming in as character code "0", and therefore it uses the wrong height and depth for that character, which I feel must be wrong.
Cc: @jkseppan as our resident DVI expert. Any ideas why that may be the case?