LaTeX blocks with tags don't render correctly about orgro HOT 10 CLOSED

I think it's going to be quite hard to get this to work with all possible layout scenarios:

• LaTeX blocks that are too wide should be allowed to scroll horizontally; in that case, where should the tag go?
• For LaTeX blocks that are narrower than the window, must the tag hug the right side?

Prior to v1.18.0 the equation environment was simply dropped, so this was not an issue (the tag was suppressed). Suppressing the tag through some mechanism could be the best solution if people aren't wedded to the tag being shown.

from orgro.

Things that are easy to do:

• Remove tags entirely
• Show tags at a fixed offset from the right edge of the main content (not aligned to the right of the screen)

from orgro.

@fountainer Can you comment on what you expect in terms of how tags should be presented?

from orgro.

@fountainer Can you comment on what you expect in terms of how tags should be presented?

I personally don't care much about the tags. I prefer the solution that tags are removed. However, I also accept other solutions as long as they don't overlap with the formulas.

from orgro.

Another option is to put tags on the left side of the formulas.

from orgro.

I think I will go with

Show tags at a fixed offset from the right edge of the main content (not aligned to the right of the screen)

and if you don't want tags shown at all then you can use equation* instead of equation.

from orgro.

This is addressed in v1.18.1, which is now available in Test Flight.

from orgro.

The equation numbers are always one. Is it a bug?

from orgro.

It's a limitation of the current implementation. Each block has its own context, and I don't know how to share the context such that the numbering could continue.

from orgro.

Actually it seems that it's a limitation of the rendering engine itself. If you want meaningful tags you need to specify the contents manually like \tag{foo}.

This is wrong; KaTeX can correctly auto-number equations. I've opened amake/flutter_tex_js#9 to track this, but I don't think I'm going to be able to solve this any time soon.

from orgro.