Hi,
How are built these pot files?
There are macro and tag in spec(ification) files, that accept options to allow translations:
Summary -> Summary(fr) %description -> %description -l fr
So, as packager of some programs, I always add the french translation of description and summary in the spec file.
But it seems that these translations aren't used to build the summary and desc fr.po files.
Why?
Regards
Le Sunday 09 September 2007 12:30:28 Alain PORTAL, vous avez écrit :
Hi,
How are built these pot files?
There are macro and tag in spec(ification) files, that accept options to allow translations:
Summary -> Summary(fr) %description -> %description -l fr
So, as packager of some programs, I always add the french translation of description and summary in the spec file.
But it seems that these translations aren't used to build the summary and desc fr.po files.
Why?
Nobody can answer?
Le Mer 12 septembre 2007 09:56, Alain PORTAL a écrit :
Le Sunday 09 September 2007 12:30:28 Alain PORTAL, vous avez écrit :
Why?
Nobody can answer?
Because the rh localisation team decided years ago they wanted localisation in one place not spread over every package in the distro. IMHO this was a short-sighted decision as centralization does not scale and screws third-party repositories (basically anything the central project does not now of beforehand is not localised)
But anyway: 1. you're looking for specspo 2. it'd be nice if you could talk with the people behind transifex to figure how to put localisation back in the individual packages where it belongs
Regards,
On Wed, 2007-09-12 at 10:36 +0200, Nicolas Mailhot wrote:
Le Mer 12 septembre 2007 09:56, Alain PORTAL a écrit :
Le Sunday 09 September 2007 12:30:28 Alain PORTAL, vous avez écrit :
Why?
Nobody can answer?
Because the rh localisation team decided years ago they wanted localisation in one place not spread over every package in the distro. IMHO this was a short-sighted decision as centralization does not scale and screws third-party repositories (basically anything the central project does not now of beforehand is not localised)
Actually, nothing says that additional repos can't have their own specspo-type package as well. And if you drop a macro file defining %{_i18ndomains} as the current value + your repo's value, then with pirut, it'll now follow that rather than just using redhat-dist.
Also, moving the translations into the spec files is pretty painful also. It makes the spec file _much_ more complicated to actually edit and work with and it also means the package has to be rebuilt to get translations of package metadata added. And going through and rebuilding every package to add translations to package headers at the last minute doesn't work either.
All of the above said, specspo probably _isn't_ the right answer... but just moving everything to be back in the spec files isn't the answer either. If someone would like to work on what a better answer is, it would definitely be a welcome and long-overdue improvement
Jeremy
Le mercredi 12 septembre 2007, Nicolas Mailhot a écrit :
But anyway:
- you're looking for specspo
- it'd be nice if you could talk with the people behind transifex to
figure how to put localisation back in the individual packages where it belongs
I don't want translation be put in package spec file, I just want that if a french translation exist, this translation have to be got and merge in the fr.po. That's why I wanted to know how are build these pot an po files.
Regards
-
Alain PORTAL -
Alain PORTAL -
Jeremy Katz -
Nicolas Mailhot