gufw-developers team mailing list archive
-
gufw-developers team
-
Mailing list archive
-
Message #00700
[Bug 688601] Re: file conflict in mo files and license issue
Hi,
I pushed a branch that should fix these problems.
https://code.launchpad.net/~knitzsche/gui-ufw/i18n-l10n-fixes
The branch implements python-distutils-extra for i18n support.
With this branch, there is a po/ directory that contains LANG_CODE.po
files and a POTFILES.in file.
The po files were downloaded from LP on 17 Dec. Here's the link: http://launchpadlibrarian.net/60806909/launchpad-export.tar.gz
(Not sure how long that link will be good.)
Note that the branch also provides completed translations for zh_CN
(Chinese/Simplified).
When you build the pkg, it creates gufw.mo files for each locale. These
are automatically installed in the correct location:
/usr/share/locale/LANG_CODE/
You can update translations by replacing the target po file (or po files) and running (from src pkg root dir):
'./setup.py build_i18n -m'
The source pkg still contains a locale-langpack/ directory, but I
believe this is no longer referenced or needed and it should be deleted.
(This is the directory that contains the .mo files, which should not be
included in a source package.)
See merger proposal 44278.
Cheers,
Kyle
--
You received this bug notification because you are a member of Gufw
Developers, which is subscribed to Gufw.
https://bugs.launchpad.net/bugs/688601
Title:
file conflict in mo files and license issue
Status in Gufw:
New
Status in “gui-ufw” package in Ubuntu:
New
Bug description:
Hi,
This package has a couple issues:
* Its translation files (the gufw.mo files, one for each language) are installed into /usr/share/locale-langpack/... However, this location is reserved for Ubuntu language pack .mo files. If this pkg ever moves into Ubuntu Main (which means language packs would install gufw.mo files into /usr/share/locale-langpack/... ), there would be a file conflict (two binary pkgs trying to install the same file). This would prevent installation of whichever pkg was installed second.
- FIX: This can be fixed by releasing a new verson of the package that installs the .mo files into the package's location: /usr/share/locale/...
* The source pkg in the archives contains .mo files instead of .po files. The proper appoach is for the src package to contain .po files in a directory named po/. that directory should to include a file named POTFILES.in that lists the path to every file with translatable messages. (Doing this enables intltool.) Then the .mo files need to be created on each build of the pkg. (Note, containing .mo files in the src package may be a license violation).
Cheers,
Kyle
Follow ups
References