You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is a simple LaTeX parser written in EBNF. The parser is restricted to only be able to process the subset of LaTeX that we care about. It is more powerful than the search-and-replace approach that unicodeit uses currently. It handles several cases correctly that unicodeit does not handle, e.g.:
I am interested in contributing this parser for the Python package to unicodeit, where it would largely replace the implementation of the Python package. My draft implementation is not bug-free, I will work on this and the integration into unicodeit if I get a confirmation from you that you are willing to review a PR with such a major change.
I have little experience with Javascript, so I cannot offer to help with improving that implementation.
The text was updated successfully, but these errors were encountered:
Today, I published a first release of unicodeitplus based on the concept. I am still open toward merging my project back into unicodeit. I fixed the bugs I still had in the concept code, it now works as expected.
I am also open to become co-maintainers of unicodeit, if you have no time to work on this project.
I developed the concept for a LaTeX parser for unicodeit here https://github.com/HDembinski/essays/blob/master/parse_latex.ipynb
It is a simple LaTeX parser written in EBNF. The parser is restricted to only be able to process the subset of LaTeX that we care about. It is more powerful than the search-and-replace approach that unicodeit uses currently. It handles several cases correctly that unicodeit does not handle, e.g.:
#27
I am interested in contributing this parser for the Python package to unicodeit, where it would largely replace the implementation of the Python package. My draft implementation is not bug-free, I will work on this and the integration into unicodeit if I get a confirmation from you that you are willing to review a PR with such a major change.
I have little experience with Javascript, so I cannot offer to help with improving that implementation.
The text was updated successfully, but these errors were encountered: