blog: Fixing Up Japanese Language Tags (draft)
This commit is contained in:
parent
a761f45afd
commit
b732238c20
1 changed files with 27 additions and 0 deletions
27
content/blog/2025/fixing-up-japanese-language-tags.md
Normal file
27
content/blog/2025/fixing-up-japanese-language-tags.md
Normal file
|
@ -0,0 +1,27 @@
|
|||
---
|
||||
title: "Fixing Up Japanese Language Tags"
|
||||
date: 2025-01-07T13:33:20-08:00
|
||||
draft: true
|
||||
tags:
|
||||
- Meta
|
||||
- Hugo
|
||||
- japanese
|
||||
---
|
||||
|
||||
Two years ago, I took a trip to Japan with Tess. I wrote up my experiences on
|
||||
that trip in various posts, and shared several photos.
|
||||
|
||||
Feeling perhaps overly-confident in my ability to read Japanese and my website
|
||||
engine's ability to handle non-ASCII content, I tagged many of those pages with
|
||||
Japanese language tags:
|
||||
[日本]({{< ref "/tags/japan" >}}),
|
||||
[日本語]({{< ref "/tags/japanese" >}}),
|
||||
[東京]({{< ref "/tags/japan-tokyo" >}}),
|
||||
[京都]({{< ref "/tags/japan-kyoto" >}}).
|
||||
|
||||
This led to some difficult URLs because of how Hugo rendered the Japanese
|
||||
language tags names into ASCII when generating file paths.
|
||||
|
||||
It's always bothered me a bit to have paths that look like this, so I went
|
||||
through today and updated those tags to have ASCII slugs, and Japanese titles. I
|
||||
went a step further
|
Loading…
Add table
Add a link
Reference in a new issue