<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Localization on Armstrong Yan</title><link>https://yanqian.github.io/tags/localization/</link><description>Recent content in Localization on Armstrong Yan</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 22 Jul 2026 00:18:29 +0800</lastBuildDate><atom:link href="https://yanqian.github.io/tags/localization/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Human-Gated Bilingual Publishing Pipeline with Obsidian and Hugo</title><link>https://yanqian.github.io/posts/publish/building-a-human-gated-bilingual-publishing-pipeline-with-obsidian-and-hugo/</link><pubDate>Wed, 22 Jul 2026 00:18:29 +0800</pubDate><guid>https://yanqian.github.io/posts/publish/building-a-human-gated-bilingual-publishing-pipeline-with-obsidian-and-hugo/</guid><description>&lt;p&gt;In &lt;a href="https://yanqian.github.io/posts/publish/building-a-personal-blog-with-obsidian-hugo-and-github-pages/" class="external-link" target="_blank" rel="noopener"&gt;Building a Private-to-Public Publishing Pipeline with Obsidian, Hugo, and GitHub Pages&lt;/a&gt;, I described the boundary that keeps my private vault separate from my public website.&lt;/p&gt;
&lt;p&gt;That solved where an article should live. It did not solve what happens when the same article needs to exist in two languages.&lt;/p&gt;
&lt;p&gt;At first, bilingual publishing looked like a translation task: send the Markdown to a model, ask for Chinese or English, and save the response beside the original. In practice, that was the least interesting part of the problem.&lt;/p&gt;</description></item></channel></rss>