[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#234903: xfree86: [INTL:fr] French debconf templates translation

On Fri, Feb 27, 2004 at 07:21:16AM +0100, Christian Perrier wrote:
> Quoting Branden Robinson (branden@debian.org):
> > > Please find attached the french debconf templates update, proofread by the
> > > debian-l10n-french mailing list contributors.
> > 
> > Thank you!  I'll be checking this in to SVN shortly.
> > 
> > There is one fuzzy template (probably a false positive due to a
> > missing-word typo fix in English), and one untranslated template.
> Hmm. Looks like the untranslated one is due to a recent change in SVN,
> I guess (the explanations about the <> key...good idea by the
> way-->I'm always wondering whether I should use pc104 or pc105....).

Glad to hear it's more useful.  I took the liberty of adding a period to
the end of the translated sentence, thus:

"Les types « pc102 » et « pc105 » sont les versions des modèles « pc101 » et "
"« pc104 » respectivement, que l'on trouve fréquemment en Europe. Si votre "
"clavier comporte une touche « <> » (touche comportant les symboles « "
"inférieur à » et « supérieur à »), il est probablement de type «pc102 » ou « "
"pc105 » ; si vous choisissez alors « pc101 » ou « pc104 », cette touche ne "
"fonctionnera probablement pas."

It's been over 20 years since I had any instruction in French, so this
change could be wrong; please me let me know.

> Attached is the new fr.po file. I used this occasion for turning it to
> the style we now use for the french templates (short descriptions for
> string templates turned into "prompts").

Okay.  Please note that it is more difficult than it should be to merge
your changes because:

1) The message strings are not line-wrapped correctly;
2) Whatever tool you are using keeps adding the template field names and
   types to comments above the msgids, even if the comments are already
3) You reverted the changes I made to the fr.po file's comment header.

For example:

-#. Type: select
-#. Description
+#  Type: select
+#  Description
+#  Type: select
+#  Description
 #: ../xdm.templates:4
 msgid "Select the desired default display manager."
 msgstr "Gestionnaire graphique de session par d#faut :"

Unfortunately, I don't know what the recommended best practices
(including tools) for translation updates are.  Perhaps you could ask
Denis Barbier?

> BTW, could you consider giving some kind of write access to
> translators in the SVN repository, similarly to what we currently do
> in Debian Installer. This would probably speed up translations a lot
> (I will soon push the current d-i translators to have a look at
> xfree86 templates translations as these are obviously a good first
> target).
> The d-i experience is really very positive for that matter.

Yes, if you promise to resolve the problems 1), 2), and 3) above.  :)

If you can agree to that, I'd be happy to.  Just send the username you'd
like and an .ssh/authorized_keys file I can use for it to
<branden@debian.org>.  Please GPG-sign the mail (you can encrypt it as
well, if you like).

> Another suggestion is to move the SVN repo to alioth, but you may have
> your own reasons for keeping it elsewhere.

I do, but some of them may be cancelled by the release of Subversion

As long as I am far and away the primary committer to XSF repos, I think it
probably makes sense for me to have administrative control over them.
However, if that changes (and it could change soon), alioth might become
a more logical choice.

I will note that in the event I am hit by a bus, the XFree86 repo is
dumped nightly to the Web, so Debian XFree86 SVN could be moved to
alioth without my direct involvement.

I am aware that similar procedures need to be set up for the other repos
(Render, Xcursor, Xft, Xrender).

G. Branden Robinson                |
Debian GNU/Linux                   |      Please do not look directly into
branden@debian.org                 |      laser with remaining eye.
http://people.debian.org/~branden/ |

Attachment: signature.asc
Description: Digital signature

Reply to: