https://inktrace.rxchi1d.me/en/tags/localization/Recent content in Localization on InkTrace｜RxChi1dHugo -- gohugo.ioenrchildlin@gmail.com (RxChi1d)rchildlin@gmail.com (RxChi1d)© 2026 RxChi1dMon, 31 Aug 2026 22:21:40 +0800https://inktrace.rxchi1d.me/en/posts/engineering/immich-geodata-tech-03-strategies/Wed, 26 Aug 2026 10:00:00 +0800rchildlin@gmail.com (RxChi1d)https://inktrace.rxchi1d.me/en/posts/engineering/immich-geodata-tech-03-strategies/<p>The <a href="https://inktrace.rxchi1d.me/en/posts/engineering/immich-geodata-tech-01-reverse-geocoding/" >first</a> <a href="https://inktrace.rxchi1d.me/en/posts/engineering/immich-geodata-tech-02-pipeline/" >two posts</a> covered the mechanism and the pipeline: Immich reads place names from <code>cities500.txt</code>, and that file is produced from national mapping data by <code>extract</code> and <code>release</code>. Technically, &ldquo;how to swap the data&rdquo; is a settled question. The genuinely hard part is something else: <strong>what should a foreign place name look like so that it reads naturally to a Taiwanese user?</strong></p> <p>immich-geodata-zh-tw currently handles five regions, and it gives five different answers. This post is about the criterion behind those answers.</p>