On Tue, Oct 12, 2010 at 01:09:15PM -0400, David Prévot wrote: > Package: po4a > Version: 0.40.1-2 > Severity: wishlist > Tags: upstream > > Hi, > > Currently, po4a-build doesn't seem to include addenda support. > > It's a shame that such a convenient feature is ignored in po4a-build: > po4a itself use po4a-build in the building process and therefore can't > use it's own features. > > Recent modifier feature in addenda handling permit the use of an > addendum only if the file exists: ???????, and even permit the use of > multiple addenda configured in one file: ???@???, so the po4a-build > configuration file might stay unmodified, and consider an addenda > default configuration file, as the one suggested in po4a(7) example: > > man/po4a/add_$lang/$lang.add
For the records, for fragmaster perl script with embedded pod documentation, I have been experimenting with a hacked po4a-build that supports addenda to the pod file (this was for pod), so addenda gets included in generated formats. Approach is a bit rude, paths are hardcoded and not configurable, and I changed things only for pod, but seems to work for my needs. Change I use is attached. Hope it helps, -- Agustin
--- /usr/bin/po4a-build 2011-04-15 00:13:42.000000000 +0200 +++ po4a-build 2011-05-13 13:22:40.485166625 +0200 @@ -169,7 +169,8 @@ if [ -n "$PODFILE" ]; then for file in $PODFILE; do LOCAL=`basename $file` - wrap_langs "[type:pod]" "$file" "\$lang:$BASEDIR/pod/1/\$lang/$LOCAL" + LOCAL_ADD="add_\$lang:?$PODIR/../pod/\$lang.add" + wrap_langs "[type:pod]" "$file" "\$lang:$BASEDIR/pod/1/\$lang/$LOCAL $LOCAL_ADD" done fi if [ -n "$POD5FILES" ]; then
