GNOME Bugzilla – Bug 363348
Tarballs misses the translated manuals
Last modified: 2006-10-20 16:50:25 UTC
Hi, the translated help is missing from eog 2.16.1: bee% ls help C ChangeLog eog.omf.in Makefile.am Makefile.in CVS has them though: bee% ls help bg ChangeLog de es fr ja Makefile.am uk zh_TW C CVS eog.omf.in eu it ko sv zh_CN Bye,
Fixed in CVS. The fix will go into the next patch release. Thank you for your bug report.
The fix I did consists in removing some obsolete files in the manual translations that are already ported to g-d-u, and now those translations (es, fr, uk) are shipped in tarballs. However, all other non ported to g-d-u are not shipped, leaving a lot of translations outside of tarballs. I am not sure how to fix this, so I'll reopen this bug in the meanwhile.
Fixed in HEAD and gnome-2-16 branches. 2006-10-19 Claudio Saavedra <csaavedra@alumnos.utalca.cl> * configure.in: Add several help/*/Makefile to AC_OUTPUT. * help/Makefile.am: Add non g-d-u translations directories to SUBDIRS. Add some missing manual translations to the tarballs. This is a temporary fix for those manuals which are not yet converted to g-d-u. (Fixes bug #363348).
This brought back the manuals but broke --disable-scrollkeeper which I'm currently working around.
Yes. The --disable-scrollkeeper stuff is pulled in from gnome-doc-utils. The extra translations still depend on the old system. Until the translations are moved across to g-d-u, --disable-scrollkeeper will remain broken (unless you want to dive into the Makefile.am code for each translation and add the correct rules and interactions with configure).
(In reply to comment #4) > This brought back the manuals but broke --disable-scrollkeeper which I'm > currently working around. I must be really ignorant regarding the documentation systems, but I don't understand clearly the problem. Does this mean that when configuring with --disable-scrollkeeper, scrollkeeper is still used?
Claudio, ScrollKeeper requires documents to be explicitly registered when installed. But it only understands how to register things at the system level. If you're just building something for your own machine, then --disable-scrollkeeper doesn't matter. It mostly matters to packagers. Packagers use the install target with the $DESTDIR environment variable to copy all the installed files to a directory. Tarring that directory gives you a very basic binary package. But they do not want to register things with ScrollKeeper whenever they build a package.