Open zaknelson opened 9 years ago
That sounds like the right behavior to me when hike.io gets more content (although implementation wise would probably use Angular - https://docs.angularjs.org/guide/i18n)
Currently though, there are only a couple of hikes written in anything other than English. So switching to another language would be completely devoid of content.
I didn't know Angular could i18n. Great!
Just a thought to add: I hike in Japan. Many signs on trails are in Japanese, often pretty complex characters with uncommon pronunciation that even locals can't read. If I see a hike guide in English, I still need the Japanese spelling to find my way, if only to visually recognize them on a sign.
I have some GPX I want to upload, will put Japanese names together with romanized in the text.
How about this: interface itself would be generated via sinatra-r18n (i18n) and each hike would have a "language" property. When viewing the site in language X, that language hikes would show in search and discover.