There is still a lot of room to improve the i18n support across the Web UI:

• Moving i18n package translation locally here (cli and ui).
• Find a way to support i18n in front-end JavaScript assets (see expandable component)

Other components impacted in the top of my mind:

• home/overview (a lot of text injected from code)
• network (for edges labels)
• locker

I think the goal is to successfully tokenize everything.