Philippe Faist

The function `nodelist_to_latex()` should not be relied upon. See my comment in #89. I'm hoping to add the ability to regenerate latex code from a node's properties in the future....

Hi, thanks for the issue. I've been thinking a bit about how to handle powers and subscripts but there are some edge cases I want to make sure that I...

Hi @nemeer, I think your issue is an inherent limitation of Unicode—as far as I know, there is no way to represent `M_\odot` in unicode. (Only a very specific subset...

Thanks for the pointer to the list of unicode sub/superscripts. For the reasons that were mentioned above, it isn't straightforward to implement this. I'm thinking about some upgrades to how...

Hi, great question. This is slightly tricky because the default latex2text replacement texts aren't context-aware. I mean, the replacement text for "\item" is generated by default without knowing whether the...

Hi and thanks for the report. There are two points to unpack here. First, you're seeing an error mainly because `pylatexenc` does not really support the `\newcommand`/`\newenvironment` family of commands...

My latest commit should fix the weird chained exception that you reported. I'm leaving the issue open as an enhancement to enable `\newenvironment` wrapping another environment. This should be support...

Hi, thanks for reporting this issue. The trouble here is that some macros, especially ones that define new macros or new behavior (such as `\newcommand`, `\def`, `\newcolumntype`, etc.) cannot be...

`\def` is a command with a complex argument structure. It is not yet supported. You need to write your own argument parser for it. Note that I am reworking how...

Thanks for reporting this. In LaTeX, the URL-related commands (like ``\href``, ``\url``, and ``\email``) parse their URL argument in a special fashion to deactivate any special characters (such as `$`,...