> The ddts can provide po files with all translated packages and build
> own deb packages with this file. I put the first po files on
> http://auric.debian.org/~grisu/ddts/po/.
In this way, we can't use add-on l10n catalogs. For example, say a third
party makes his or her own deb package. Because the translation of the
package isn't included in ddts's mo package, dpkg can't display its
translation. It is little evil to include the third party's translation
in ddts. I have made such a gettext-based translation system of dpkg and
faced above problem.
How about the following solution?
* All packages which include description translations locate po files
into /usr/share/dpkg/description/<LANG>/<package>.po or something like
that, not dpkg-desc.mo itself.
For example,
/usr/share/dpkg/description/ja/ddts.po or debian.po?
/usr/share/dpkg/description/ja/debian-jp.po
/usr/share/dpkg/description/ja/debian-kr.po
/usr/share/dpkg/description/ja/progeny.po
* These packages invoke `update-descriptions' or something like that in
postinst and postrm. 'update-descriptions' merges all the <package>.po
files, invokes `msgfmt' and locates the generated mo file into the
designated location as dpkg-desc.mo.
Best regards
----
Masato Taruishi - Debian Official Developer <taru@debian.org>
Debian-JP Project Vice President <taru@debian.or.jp>
Graduate School of Electro-Communications
Course in Computer Science and Information Mathmatics