[Debian-l10n-commits] r1231 - /reports/todo/debconf8_i18n.txt

bubulle at users.alioth.debian.org bubulle at users.alioth.debian.org
Mon Aug 25 06:18:11 UTC 2008


Author: bubulle
Date: Mon Aug 25 06:18:11 2008
New Revision: 1231

URL: http://svn.debian.org/wsvn/?sc=1&rev=1231
Log:
Mor eprogress in the report

Modified:
    reports/todo/debconf8_i18n.txt

Modified: reports/todo/debconf8_i18n.txt
URL: http://svn.debian.org/wsvn/reports/todo/debconf8_i18n.txt?rev=1231&op=diff
==============================================================================
--- reports/todo/debconf8_i18n.txt (original)
+++ reports/todo/debconf8_i18n.txt Mon Aug 25 06:18:11 2008
@@ -93,23 +93,26 @@
 --------------------------
 (notes taken by Marc Hymers)
 
-Notes
-Various constraints and desirable characteristics were discussed 
-Out-of-band translation updates 
-Only installing useful translations on systems 
-Reducing bandwidth usage 
-Avoiding archive bloat 
+"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
 source package would be provided, including all translations, and that
-dpkg class support should be added to allow filtering at install time.
-
-Summary
-One tdeb per source package 
-
-dpkg class support needed; see http://www.dpkg.org/dpkg/Classes
-(possible uses go way beyond translation, e.g. tagging doc files)
+dpkg class support (http://www.dpkg.org/dpkg/Classes)
+should be added to allow filtering at install time.
 
 Using the class support, .tdebs would be easily splittable into
 smaller, per language tdebs. This may be considered at stable
@@ -119,22 +122,44 @@
 translation updates (similar to bin-nmu style versioning)
 
 Translation-Version: would be used in Packages files to indicate the
-most up-to-date tdeb instead of having full Package: entries
+most up-to-date tdeb instead of having full Package: entries.
 
-This work is aimed at lenny+2 due to the changes needed in the deb toolchain 
+For new translations, we'll need some form of source; to be decided.
+
+This work is aimed at lenny+2 due to the changes needed in the deb toolchain
+(those being for lenny+1).
 
 There needs to be discussion with the dpkg, apt, debian-installer and
 debhelper people.
 
 ftpmaster is happy with the one tdeb per source package and +t[0-9]+ syntax 
 
-The plan is to meet in Extremedura (post-lenny) to continue the
-discussion and start the work.
+The plan is to meet in Extremedura (post-lenny) to continue the discussion
+and start the work. The meeting should gather i18n representatives, Neil
+Williams who did the first implementation of tdebs for EmDebian purposes,
+ftpmasters and hopefully at least one dpkg maintainer (Raphaël Hertzog who
+could be there for the QA meeting anyway?).
 
-Post-discussion notes
+i18n work sessions 4: DDTP/Extremadura meeting
+----------------------------------------------
+The DDTP/DDTSS infrastructure is now running solid on churro. Michael
+re-summarized the various possibilities that translators have to adjust
+their work process to the interface.
 
-For new translations, we'll need some form of source; to be decided
-(noted by weasel / Ganneff)
+The discussion about the "openess" of the system is still strong. In out
+i18n community, we clearly have two visions:
+- "open to everybody with low constraints": this is the original design of
+the DDTP: everybody can show up and start translating. This allows for a
+quick growth of the amount of translations to the expense of their uality
+- "control the quality": this is wished by the most structured teams
+and a concern bringed by many maintainers
+
+Felipe explained how he tries to balance this for the Brazilian Portuguese
+team by basically controlling that nobody is translating outside the team
+and following the work process for the team as well as assigning tasks in
+the team.
+
+.../...
 
 
 




More information about the Debian-l10n-commits mailing list