Note that there are some explanatory texts on larger screens.

plurals
  1. POAsian URLs or English slugs in webpages
    primarykey
    data
    text
    <p>Here's a tough one:</p> <p>I'm working on a website where most of the content is in Japanese.</p> <p>But consider this url:</p> <p><a href="http://www.stackoverflow.com/%E8%B3%AA%E5%95%8F/%E6%97%A5%E6%9C%AC%E8%AA%9E%E3%81%AEURL%E3%81%AF%E3%81%A9%E3%81%86%E3%81%99%E3%82%8B">http://www.stackoverflow.com/質問/日本語のURLはどうする</a></p> <p>Most URL parsers, including stackoverflow's, don't know where to delimit URLs that contain Japanese. Not good.</p> <p>I haven't checked with other browsers yet, but Google Chrome will display URL-decoded Japanese urls in Japanese -- and when you copy the url, it URL-encodes it:</p> <p><a href="http://www.stackoverflow.com/%E8%B3%AA%E5%95%8F/%E6%97%A5%E6%9C%AC%E8%AA%9E%E3%81%AEURL%E3%81%AF%E3%81%A9%E3%81%86%E3%81%99%E3%82%8B">http://www.stackoverflow.com/%E8%B3%AA%E5%95%8F/%E6%97%A5%E6%9C%AC%E8%AA%9E%E3%81%AEURL%E3%81%AF%E3%81%A9%E3%81%86%E3%81%99%E3%82%8B</a></p> <p>That's the right thing to do, but it's not exactly the most friendly. So, I thought, I'd have the content providers just type in short English slugs, like this:</p> <p><a href="http://www.stackoverflow.com/questions/what-to-do-with-japanese-urls">http://www.stackoverflow.com/questions/what-to-do-with-japanese-urls</a></p> <p>Awesome. But there's two problems with this:</p> <ol> <li>Most of the people providing the content speak a modicum of English --- but they speak more Engrish than English. So they're likely to write something like "what-do-to-with-japenese-ulrs".</li> <li>Google Japan might not be as interested in the English URL as it might be in the Japanese one.</li> </ol> <p>Any thoughts on the best course of action? :D</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload