[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Akademy 2014, notes of the Localization BoF
From:       Luigi Toscano <luigi.toscano () tiscali ! it>
Date:       2014-09-12 13:00:43
Message-ID: 2846420.OCfpi8fKXX () themys
[Download RAW message or body]

Hi all, 
here you can find the notes from the Localization BoF which happened during 
Akademy (source: merged notes from Sebastien and me)
Feel free to comment/ask!

# Essentials
For KF5, as previously stated, no minimum is required to ship translation. It 
is up to downstream to decide if they ship or not translation.

For plasma and applications, three choices:
- no thresold (which could encourage people to join translation team)
- a thresold
- a thresold per language

Difficult balance between user reactions: "this translation is bad!" vs "oh, I
can contribute to imporve the translations"

Some other project examples:
- Firefox : up to QA team decision
- LibreOffice : no thresold
- Qt and Apache OpenOffice : high thresold
- Gnome : 0 for non supported apps and high thresold for supported apps and 
libs to call them "supported", but all shipped

We agree on a low thresold that should consider core file from framework as a 
whole. The % and the files to consider need to be decided on mailing list.


# Qt broken things
- issue on translations for pure Qt Frameworks

Current process: string (ts) extracted in pure Qt Frameworks; lconvert
converts them to po file given to translators.

-> lupdate mangles/breaks the context.

WONTFIX on Qt side (fixing lupdate)

Solution: directly extract po from Qt frameworks, so the context are correct;
requires few changes on the infrastructure


# Qt5 translations
Qt5 needs to be translated upstream, translation teams need to be updated


# Indian languages
A small ping to KDE.in for increasing the translations of Indian languages


# Updates on centralized translation assignment 
Updates on centralized translation assignment system (tosky), still not
complete (deployment stopped by the work on KDocTools/KF5), project will be
revamped


# Use summit workflow officially
Some questions / issues
- perf / infrastructure issues
- would it be possible to avoid per team merging by making scripty directly 
work on summit branch ? (need to talk to Chusslove to ensure feasability)
- people in BoF mostly agree. Need to be discussed.

-- 
Luigi
[prev in list] [next in list] [prev in thread] [next in thread]