Language Selection

[cityofaustin]

Language Selection

[cthibaultatx]

@mateoclarke from a city staff member at Asian American Resource Center:
Hi Celine,

Thanks for calling us. Sorry for the late reply. Following are my personal point of view.

From my personal experience, I didn’t pay attention on the abbreviations. So I did some research, I noticed that they usually use simplified Chinese and Traditional Chinese. For Simplified Chinese, it is 简体中文，traditional Chinese is 繁體中文.

The abbreviation you mentioned is for typing Chinese on computer only. People will not use it in everyday life. If you want to tell people there has Chinese service for them, 简体中文 will be the best one for people reading simplified Chinese, and繁體中文 for people reading traditional Chinese.

Hope it helps! If you have any further questions, feel free to contact me.

Thanks,

[mateoclarke]

With PR #86 being the last of many stabs at this issue, I think we are good to close this issue.

[mateoclarke]

This will have significant interaction with the Joplin API. @benweatherman, we need to coordinate on how we flip the language switch and request that from the API instead. I'm also thinking about text in global site components like Headers and Footers and form validation/error text. I guess that should live as content data with translations in Joplin too? How would we add this to the Django models? Currently we are hardcoding from the mocks.

[mateoclarke]

Looks like you are already thinking about some of this in cityofaustin/joplin#17

[mateoclarke]

This PR #46 starts to work on language selection in terms of appearance, but only partially. And it has some discussion about the bigger picture problems yet to be solved:

• the mechanics of setting a language cookie in the client for the server to access
• updating routing to follow best practice, ex: austin.gov/es/.

[mateoclarke]

Another issue to solve here:

• when a user has set a language, any link they click should be prefixed by the language code. We need to research if there is a react-router way to do this? Or how it might work without react router too.