Samuel

Last fixes:
Spacing bug: Fixed an issue where formulas were sticking to surrounding text after translation.
Unit translation: Reworked unit handling to correctly convert prefix + base units, enabling much more units.

Now the extension is basically finished. Formulas stay intact, and problems are finally readable. The next step would be to generalize to more languages.

The goal was simple: translate without breaking formulas.
My approach was straightforward: find LaTeX tags like \text{} and \mathrm{}, send the content to Google Translate, replace it inside the LaTeX source, and let MathJax re-render.
First problem: MathJax wasn’t updating
My content script runs in an isolated context while MathJax lives in the page’s main context. To fix that, I introduced a background.js script. Instead of calling MathJax directly, content.js sends a message and background.js injects code into the MAIN world where MathJax actually lives.
Second problem: units were being mistranslated
Sending some units to the Google Translate API was producing wrong or inconsistent results, so I built a dictionary mapping each Cyrillic unit directly to its Latin equivalent, bypassing the API entirely for those cases.
Third problem: formulas were still visually broken
Even after the translations were correct, the rendered math was displaced and overlapping with surrounding text. After inspecting the DOM directly, I found that Google Translate was reaching inside the MathJax-rendered elements and wrapping text nodes in tags, duplicating content. The fix was to mark all MathJax elements as notranslate before the Translate engine could touch them..
What’s next
Fix remaining small bugs, drop the hardcoded unit dictionary in favor of a smarter approach, and generalize the extension to work with other languages beyond Russian.

For now, I only used the class notranslate to keep the formulas intact, which helps a little with the visualization, but some parts inside the expressions still end up in Russian, line physics units and subcripts. I’m now trying to deal with these.

Just reshipping the project to physics lab. Also, when I shipped, it was an past version, so it didn’t had changable parameters. Make sure to try the complete version.

I fixed some bugs and finished the basic features, including the border of the pieces, the undo (Ctrl + Z) and the selection of cells for typing (Shift + Click).

Now you can color cells. I will add a function to drag to create pieces with border.

I just finished the basic grid thing. The next steps are:

• Build an X marker for cells
• Allow the user to make his own pieces, like dominos
• Construct an algorithm (maybe C++) to find a covering of the the grid using the given pieces.

I think I finished pretty much everything. You can change the constant of the franctal and explore it, zooming in on click.

Now you can select an object and play.

Now you can change the parameters of the simulation, like the balls scale, velocity, elasticity and quantity.