-
Notifications
You must be signed in to change notification settings - Fork 162
Viewer translation #121
Comments
@roloyar This is something we hope to add this year. Naturally we'd want to let readers change the language within the embed chrome, but as you say, choosing the default is tough. What's a more likely proxy for the reader's language: the organization/publisher, or the document content? My gut says the former, because a Russian-language organization is likely to be publishing for Russian-language readers. But there's a significant argument for the latter: that if the reader is expected to be able to read the embedded document in a given language, then the viewer interface can safely reflect that. We may need to survey some of our non-English organizations to get their input. @roloyar: Your vote is for defaulting to the document language? |
Just to summarize the things i've discussed with @roloyar and @nathanstitt in the past, the stance i've taken is as follows: News organizations publish in a particular language. That should be previously specified, and so it should be sane to ask them to identify the display language for the viewer as embedded on their properties. In the event that an org publishes in multiple languages (Say the CBC, which publishes in both french and english) we perhaps do want people to be able to specify on a per document case what the display language for the viewer is. Also, it is absolutely the case that we do not want to default to document language. There are many circumstances under-which an organization may publish a document that is not in the language of their publication (english documents on a ukrainian site, or Chinese documents posted on an African news org's site, etc). |
@reefdog, @knowtheory is actually right and I agree with him on this. The bilingual approach also applies to Ukraine, also to such countries as Belarus, Kazakhstan, Georgia, etc., in all of which the population knows Russian to an extent that there are Russian-language media, which also publish content in country's official language. I believe that there should be an account-wide default viewer language setting, which could be overwritten per viewer embed if needed. |
Yup, that all sounds sensible. So a landscape like this then:
|
This is definitely on the roadmap. Moving to |
Reopening this as tracking ticket (cause we're trying out huboard) |
The viewer language defaults to English on any embeds, even if the organization language is set to Russian or Ukrainian. If viewer is opened from within the workspace, it's in the language the workspace is but it defaults to English on embeds.
As far as I know this is an issue with viewer not getting language data from the servers on initiation. I suggest default the viewer language to document language instead of the org language, I kind of feel this way we could pass the language info more easily, but that's IMHO.
The text was updated successfully, but these errors were encountered: