-
Notifications
You must be signed in to change notification settings - Fork 95
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
LaTeXML postprocessing #68
Comments
Actually, you’ve uncovered (at least) 3 bugs: Dealing with the last issue is a longer term prospect, I guess I should leave this open as a reminder, |
Dear Bruce, I have been dispatched to try and help patch the postprocessing to an extent that would allow some meaningful input for [MathWebSearch](http://www.mathweb.org/mws/) to run on. This error report came from Stefan who is currently developing that very application. Since you point out a long term solution would be a tough nut to crack, would you have a preference to a short term “patch up” that would allow us to get some helpful temporary results? I’m currently investigating this (or trying to) and would pop up with more follow up comments later this week. |
Hi Deyan; Note that a superscript can easily be “converted” to a power by Ultimately, it’s a question of finding insufficiently characterized |
remembering these problems, I just added semantic markup for all exponentials in sTeX in my GenCS slides. But of course this is no solution to the general case :-). |
So, coming back to this. Bruce, how would you conceive a first temporary patch taking the following shape: Now, obviously, this will be wrong at a lot of cases, but it will be correct in the most widespread one and is certainly better than the current broken markup. OTOH, you mentioned these heuristics are to be made on the LaTeXML level and not during postprocessing. So, I have a second version of this proposal, following this scenario: I know I am discussing a rather isolated case with a single case heuristic fix, yet that’s what I can see myself doing as a starting point. Writing code inside of the modules is still looking quite challenging in my eyes, although I am comfortable with writing contained subroutines here and there. |
I've fixed the sub/superscript bug by generating I started using an imaginary cd "latexml" until rev 952. |
correction: I used cd="ambiguous" for this symbol, |
[Originally Ticket 1392, reported by sanca]
In the ContentMathML annotation for math formulas, all subscripts/superscripts are broken, i.e. instead of x/m:ci2/m:cn/m:power, the output is a broken tag as follows:
x/m:ci2/m:cn/m:apply
The text was updated successfully, but these errors were encountered: