Project

General

Profile

Feature #16095

Curate the list of languages in Tails Greeter

Added by sajolida 9 months ago. Updated about 1 month ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Internationalization
Target version:
Start date:
11/04/2018
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:
Greeter

Description

We currently have many languages or languages variants that are poorly or not translated at all (either in Debian and GNOME in general or for our internal tools). It's the case for example of "Chinese, mandarin" and probably many others.

Having such a long list makes it harder to know which languages are actually well translated and for the user to know what's her best option is, without trial and errors.

I think we should filter this list to only display the languages that are reasonably well translated.

If we base ourselves on the PO files for our internal tools, we might be able to automatically generate a list of languages during the build. Making sure that our internal tools are well translated in a given language before listing it sounds like a good criteria too.

Once we've curated this list, we'll need to remove all language packs (e.g. Tor Browser's) that can't possibly be used (because they're not listed in the Greeter).


Related issues

Related to Tails - Bug #16093: Remove untranslated Chinese languages from Tails Greeter Confirmed 11/04/2018
Related to Tails - Feature #14544: Spend software developer time on smallish UX improvements In Progress 08/31/2018
Related to Tails - Feature #15807: Define & apply clear criteria for including dictionaries, fonts and language packs Resolved 08/18/2018
Related to Tails - Feature #9956: Consider replacing the additional fonts we ship with Noto Duplicate 08/09/2015
Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed 03/22/2019
Blocks Tails - Feature #16688: Core work 2019Q3 → 2019Q4: User experience Confirmed

History

#1 Updated by sajolida 9 months ago

  • Related to Bug #16093: Remove untranslated Chinese languages from Tails Greeter added

#2 Updated by sajolida 9 months ago

  • Related to Feature #14544: Spend software developer time on smallish UX improvements added

#3 Updated by mercedes508 8 months ago

  • Status changed from New to Confirmed

#4 Updated by sajolida 4 months ago

  • Related to Feature #15807: Define & apply clear criteria for including dictionaries, fonts and language packs added

#5 Updated by intrigeri 4 months ago

We currently have many languages or languages variants that are poorly or not translated at all (either in Debian and GNOME in general or for our internal tools). It's the case for example of "Chinese, mandarin" and probably many others.

I'm fine with hiding options that would result in most of the desktop being in English, at least when there's a close enough alternative that's better translated (e.g. a close variant of the same language). When there's no such alternate option, I'm worried that removing the option implies the user will have no choice but using English, and I'm not sure if it's better or worse than, say, 90% English and 10% in their preferred language; I guess it's a matter of "at least some bits are translated and thus easier to understand i.e. better than nothing" vs. "context/languages switching has a cost and is evil".

If we base ourselves on the PO files for our internal tools, we might be able to automatically generate a list of languages during the build. Making sure that our internal tools are well translated in a given language before listing it sounds like a good criteria too.

I'd be curious to see what this heuristics yields and whether the resulting list indeed would be likely to help users pick an option that will work better for them.

#6 Updated by intrigeri 4 months ago

  • Description updated (diff)

#7 Updated by sajolida 4 months ago

Ok, so what's the next step here?

Is it to build a table with:

  • Language name, all the ones we have in Tails Greeter
  • Percentage of translation of: core GNOME? all packages included in Tails?
  • Percentage of translation of Tails software

So we can have concrete examples?

I would know how to compute the percentage of translations of Tails software but not the rest.

#8 Updated by intrigeri 4 months ago

#9 Updated by intrigeri 4 months ago

  • Type of work changed from Discuss to Research

Ok, so what's the next step here?
Is it to build a table with: […]

I would start with Tails software only: if this gives us good enough results, it's by far the cheapest to implement initially and to maintain on the long run.

#10 Updated by intrigeri 4 months ago

  • Related to Feature #9956: Consider replacing the additional fonts we ship with Noto added

#11 Updated by sajolida 4 months ago

  • Assignee set to sajolida
  • Target version set to Tails_3.15

Ok, next step is to build this list.

#12 Updated by sajolida about 1 month ago

  • Blocks Feature #16688: Core work 2019Q3 → 2019Q4: User experience added

#13 Updated by sajolida about 1 month ago

  • Target version changed from Tails_3.15 to Tails_3.16

Also available in: Atom PDF