#267 Review the state of i18n and l10n
Closed: Won't fix by aday. Opened by aday.

This was proposed as a useful topic for a future WG meeting. @petersen , would you be happy to lead that session? Is there a particular time we should do it?


Metadata Update from @petersen:
- Issue assigned to petersen

Yes, I would

How about we aim to do it before the end of March?
I also need a little time to prepare my thoughts.

I will try to note down some of them down here before then.

So some of the topics we could discuss are fonts, input methods, locales and langpacks, translations

Fonts/rendering: we have some good progress in F36 with Noto and plan to do more.
- more default coverage
- hiding unwanted fonts?
- user installation of fonts

Input methods: two main areas are probably UI/UX consistency and regressions/Wayland issues though more things have been fixed overall now for F36 compared to F35
- improving gnome-control-center
- anaconda?
- emoji input

Langpacks: modularity
- more flexibility
- installation by geo instead of just locale?

How about we discuss this on 10th May say, or later if that is better.
(With the F36 release out I think we should have a good baseline for discussion.
I will try to flesh out this comment a bit more before then -
also please comment with any specific topics you think should be covered.)

Thanks @petersen !

How about we discuss this on 10th May say, or later if that is better.

The 10th sounds good to me. I'll confirm closer to the time.

We will talk about this today

Looking forward to the discussion as this is one of my special areas (as a Swedish translator for GNOME and Fedora for around 3-3,5 years)

Thanks for the presentation at today's working group meeting, @petersen . It was very informative.

It would be good if we could use this issue to identify potential actions or initiatives that the working group can take in relation to i18n. My list possibilities from the session is:

  • Solutions for font management on Silverblue?
  • The input method experience with Wayland (hopefully the issues are behind us now, though)
  • Better testing for input issues (there is some support for iBus in OpenQA, but not much)
  • Input methods are often neglected when it comes to UX. It would be good to give them more attention.
  • Improving language configuration and setup:
    • Filtering the language list in GNOME / Anaconda
    • Allowing multiple input sources to be setup in Anaconda / gnome-initial-setup
    • Better GDM behaviour for input sources

Sure, thanks too

For reference https://petersen.fedorapeople.org/ws-i18n-202205.html are the slides I showed today.
(generated by: pandoc -s [-t slidy] https://petersen.fedorapeople.org/ws-i18n-202205.md)
There is also a single-page version.

Here is a more detailed summary with most of the major points raised and potential future work:

Languages, locales and langpacks

Supported languages?

  • do we need a consistent threshold for translated languages (anaconda vs gnome)?
  • "support" is nebulous - it is really a spectrum range of i18n and l10n support for each language/script across numerous projects, but maybe some minimal criteria could be made
  • untranslated languages could also be moved to a lower tier in the UI

Any way to measure language/locale usage of Fedora (WS) users?

  • there is a GNOME tool for data collection which could maybe be enhanced to also record locale

Installation of langpacks by geo location (currently only by locale) in gnome-software

(added) Further harmonization of glibc locales with CLDR

Translations statistics:

  • https://transtats.fedoraproject.org/
  • https://languages.fedoraproject.org/

Revisit only installing a subset of rpm translation files by default (like flatpak does)?

Fonts

  • With F36 the core fonts had a big change with the switch to Noto
  • For F37+ hoping to add/move more langs to Noto default fonts to improve default lang coverage further

  • User font installation for Silverblue: a simple solution could be a tool to explode fedora font rpms into the home directory (or/and revive Lettercase?)

  • Fedora packaging tool in the pipeline

  • maybe exposing some OpenType features (eg anchor points) to users through some tool

Input/methods

  • seen a lot of regressions particularly for Korean Hangul
  • bit more work still needed to iron out remaining Wayland issues
  • upstream/downstream CI for Gnome and ibus desirable to catch regressions early
  • (added) improve anaconda's UI for keyboard layouts
  • implementing the Gnome Control Center designs for improving keyboard/input-method selection
  • KDE issues with ibus need attention and help from both sides
  • more improvements to Emoji input consistency
  • (added) enhancements to predictive text input UI
  • (added) OSK (on-screen keyboard) improved i18n/IM support
  • improve the input source support in GDM

No updates here for 6 months, so closing.

@petersen , feel free to create any separate issues for items that you want to track.

Metadata Update from @aday:
- Issue close_status updated to: Won't fix
- Issue status updated to: Closed (was: Open)

Just noting that I have recently been splitting some these out into i18n issues, which I am listing in https://pagure.io/i18n/issue/158

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/workstation/tickets/issues/267

Please continue any further discussion there.

Metadata