@tv: can the translator team contribute a better translation? Do you know if other translated man pages related to urpmi need an update?

CC: (none) => thierry.vignaud

1) Of course they can.
2) Probably

Keywords: (none) => Junior_job
Priority: Normal => Low

assigning to i18n

CC: (none) => marja11
Assignee: bugsquad => mageia-i18n

I didn't know, urpmi was available in our svn.

Developers should _really_ tell i18n what to translate and where to find it.
They know what we imported, I don't :/

CC: (none) => oliver.bgr

I can't find the translation of the man pages related to urpmi on our SVN repository (soft/rpm/urpmi), but only the original man pages in soft/rpm/urpmi/trunk/pod.

Are those somewhere on SVN, or should we provide patches using the man pages from the RPM?

CC: (none) => remi

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

This bug report is still valid for Mageia 2 (and most probably for Cauldron since the man-pages-fr project is dead since 2008[1]).

I suggest either dropping man-pages-fr if most pages are outdated (because we'd rather have people struggling with English but having accurate man pages than outdated pages in French), or continuing the project by ourselves (but I don't really know if it's worth it).

Keywords: Junior_job => (none)
Status: NEW => ASSIGNED
Version: 1 => Cauldron

[1] was: http://manpagesfr.free.fr/

For urpmi, we can just patch its man page.

(In reply to Thierry Vignaud from comment #9)
> For urpmi, we can just patch its man page.

Should we be upstream for the translations of our own man page though?

s/Should/Shouldn't/
I meant to ask whether we should add the man page strings in a pot template so that our translators can work on it without depending on external localised manpages packages.

there's no easy gateway between man pages & gettext... :-(

Actually I just found out that our translations now come from http://traduc.org/perkamon, and the project is still maintained.
So it could be that this bug report is already fixed, and if not, we have an upstream to work with.

(btw they seem to use gettext via po4a to handle translations)

CC: (none) => lists.jjorge

(In reply to Thierry Vignaud from comment #12)
> there's no easy gateway between man pages & gettext... :-(

It can be easily done with po4a. Should I add conversion scripts to the repo? I can keep the files in sync with English original manually (hopefully there are no big chages added frequently).

There are also working schemes based on this:

SSSD:
https://git.fedorahosted.org/cgit/sssd.git/tree/src/man

Libguestfs:
https://github.com/libguestfs/libguestfs/tree/master/po-docs

CC: (none) => yurchor

(In reply to Rémi Verschelde from comment #13)
> Actually I just found out that our translations now come from
> http://traduc.org/perkamon, and the project is still maintained.

And actually this Debian page is more up-to-date: https://alioth.debian.org/projects/perkamon/
Geez, how hard it is to put a banner telling that the project moved to a new home?...

For what I found:
French is the only translated urpmi man page.
It come from mansupfr.tar.bz2 which is supplied by Dr Delafond at http://www.delafond.org/traducmanfr/mansupfr.tar.bz2
He incorporates the translations which are sent to him. Thus, this is manual process.
Thus, I suggest that we set a repository for such pages on transifex and store them on our git.
urpmi is not the only resources, I found:
urpm                urpmi               urpm::lock          urpm::removable
urpm::args          urpmi.addmedia      urpm::main_loop     urpm::select
urpm::bug_report    urpmi.cfg           urpm::md5sum        urpm::signature
urpm::cdrom         urpmi.files         urpm::media         urpm::sys
urpm::cfg           urpmihowto          urpm::mirrors       urpm::util
urpm::download      urpm::install       urpm::msg           urpm::xml_info
urpme               urpmi.removemedia   urpm::orphans       urpm::xml_info_pkg
urpmf               urpmi.update        urpm::prompt        
urpm::get_pkgs      urpm::ldap          urpmq
rurpmi

urpm::* and urpm are perl functions. Some of them are already translated, but I think it's not important to have them translated.
Thus we have:
urpmi
urpmi.addmedia
urpmi.cfg
urpmi.files
urpmihowto          
urpme               
urpmi.removemedia
urpmf               
urpmi.update
urpmq
rurpmi
rurpme
proxy.cfg

Source pages are in POD format. Man pages are generated when the package is generated.
http://gitweb.mageia.org/software/rpm/urpmi/tree/pod/8
http://gitweb.mageia.org/software/rpm/urpmi/tree/pod/5

CC: (none) => yves.brungard_mageia