gmane.linux.debian.devel.announce

Debconf 8 internationalization sessions report

During Debconf 8, we handled four work sessions around
internationalization as well as more informal work around i18n
infrastructure.

This long-overdue report summarizes the discussions during these
meetings as well as other i18n-related work that happened during
Debcamp and Debconf.

Please accept our apologies for us being very late sending this.

===============================================================
During Debconf 8, a lot of work happened around i18n, either during Debcamp,
informal sessions during Debconf and four formal 1-hour sessions.

i18n work session 1: infrastructure
-----------------------------------

During that work session, several contributors of Debian i18n
presented the recent progress about i18n infrastructure in Debian, 
mostly the dedicated server named "churro", aka i18n.debian.net.

churro is hosted in Merida, Extremadura, Spain, since September 2006, the
first i18n session held in Extremadura.

Since then, several services were developed on churro (see
http://i18n.debian.net/wiki):

Nicolas François summarized the work around l10n material collection.
Several scripts on churro gather the translation material and process it to
provide:

(Continue reading)

headers

Filipus Klutiero | 8 Nov 23:32

Translation debs (Re: Debconf 8 internationalization sessions report)

Le November 8, 2008 09:46:48 am Christian Perrier, vous avez écrit :

>
> i18n work session 2: tdebs
> --------------------------
> (notes taken by Marc Hymers)
>
> "tdebs" or "translation debs" are an attempt to achieve two goals, by
> splitting localization material out of packahes:
>
> - reduce space usage on systems with low resources (goal pushed from
> EmDebian) - allow desynchronized updates of translations without requiring
> a full upload or package recompile (therefore potentially allowing l10n
> updates to stable, for instance)
>
> Various constraints and desirable characteristics were discussed:
>  - Out-of-band translation updates
>  - Only installing useful translations on systems
>  - Reducing bandwidth usage
>  - Avoiding archive bloat
>
> Discussion noted that "Reducing bandwidth usage" by providing small,
> individual tdebs per package per architecture and "Avoiding archive
> bloat" were contradictory. Instead it was suggested that one .tdeb per

Small note, I was confused at first when I red about TDebs and thought that 
those proposing them wanted to create a new file format (.tdeb). This is not 
actually the case, so unless a reason appears to make a new format desirable, 
TDebs can be assumed to be simple Debian packages and can be called "tdeb"-s, 
but not .tdeb-s, which is confusing. "Translation Debs" refers to the concept

(Continue reading)