Thinking about l10n copyright, an idea is to modify po/Makefile.in.in and gnome-doc-utils.make so that the header of .po files are installed. l10n copyright is described in the head of each .po files.
Since most of .spec files call intltoolize but not gnome-doc-prepare, it's easy for me to modify intltoolize. It means SUNWzzgnome-l10n.copyright has the following contents: The copyright is described in each .po files and please refer /usr/share/locale/$LOCALE/LC_MESSAGES/copyright.gz or /usr/share/gnome/help/$MODULE/$LOCALE/copyright.gz The license is described in each base package. For the avoidance of doubt, except that if any license choice other than GPL or LGPL is available it will apply instead, Sun elects to use only the General Public License version 2 (GPLv2) at this time for any software where a choice of GPL license versions is made available with the language indicating that GPLv2 or any later version may be used, or where a choice of which version of the GPL is applied is otherwise unspecified. -------------------------------------------------------------------- What do you think? If I need to modify each .spec to add the internal script instead of intltoolize, it will need time. Thanks, fujiwara -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: intltool-02-g11n-branding-copyright.diff URL: <http://mail.opensolaris.org/pipermail/jds-review/attachments/20080331/2056a8d1/attachment.ksh> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: SUNWzz-gnome-l10n.spec.diff URL: <http://mail.opensolaris.org/pipermail/jds-review/attachments/20080331/2056a8d1/attachment-0001.ksh> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: intltool.spec.diff URL: <http://mail.opensolaris.org/pipermail/jds-review/attachments/20080331/2056a8d1/attachment-0002.ksh>
