Traduc

traduc@traduc.org

2806 discussions

Démarrer une nNouvelle discussion

unsuscribe
by Samuel Tribehou 20 Mai '01

20 Mai '01

unsuscribe

1 0

[ANN] C-C++-Beautifier en attente de diffusion
by Nicolas Chauvat 19 Mai '01

19 Mai '01

Tout est dans le titre et le document est dans ftp://www.traduc.org/pub/HOWTO/encours/relus/ -- Nicolas Chauvat http://www.logilab.com - "Mais où est donc Ornicar ?" - LOGILAB, Paris (France)

1 0

Re: [Traduc] Traduction de la GNU Free Documentation License
by Bernard Choppy 19 Mai '01

19 Mai '01

Le Jeudi 17 Mai 2001 14:22, vous avez écrit : > Salut, > > J'ai attaqué la traduction du DocBook-Install mini-howto. L'auteur a > placé ce document sous la GFDL pour la propriété intellectuelle. > > Il a joint en annexe le texte de cette licence. > > Plusieurs problèmes se posent à moi : > > 1 - Cette licence n'a de valeur que dans sa version > originale. D'ailleurs elle le proclame. Je devrais de fait la laisser > en VO dans le document, quitte à en fournir également la > traduction. En effet, supprimer la vo reviendrait à supprimer la > license. Bon, je vous rassure, je me suis résolu à ne mettre que la > VF, avec un beau warning DocBook sur la non-valeur de la traduc et un > lien sur le site de la copyleft, vu que c'est, il me semble, la > pratique la plus courante. > Des réactions ? A mon sens, tu aurais meilleur compte de laisser la VO dans le texte, puisque c'est la seule valable, mais demande à l'auteur ce qu'il préfère. Détermine aussi ta latitude en ce qui concerne la version traduite par tes soins en termes de choix de licence. J'ajouterais la VF _en plus_ dans un chapitre séparé avec : - une note d'avertissement sur la non-validité légale ; - l'origine de la VF que tu utilises avec éventuellement un pointeur vers l'autre VF disponible. Ainsi le lecteur a tout : le beurre la VO), l'argent du beurre (la VF insérée) et la crémière (le lien vers l'autre VF). Sinon, je ne conseille pas d'en faire une énième, pour ma part. Si toutefois aucune des deux traductions ne te satisfaisait pleinement, je te propose d'écrire au traducteur pour lui proposer tes modifs. En hopant que ça helpe, -- Amitiés, Bernard Choppy <choppy(a)imaginet.fr>

6 6

New PO file for `libc-2.2.3'
by Translation Project Robot 18 Mai '01

18 Mai '01

Hello, members of the French team at `traduc(a)traduc.org'. This is a message from the Translation Project robot. I`m happy to announce that a new file, available as: > http://www.iro.umontreal.ca/contrib/po/teams/PO/fr/libc-2.2.3.fr.po has been integrated in the central PO archives, and is now kept with all other accepted French translations. The file should soon be made available in mirror sites as: > ftp://ftp.unex.es/pub/gnu-i18n/po/teams/PO/fr/libc-2.2.3.fr.po > ftp://ftp.chg.ru/pub/doc/gnu-i18n/teams/PO/fr/libc-2.2.3.fr.po In this file, 874 messages have been translated already, accounting for 68% of the original text size (in raw bytes). Still, 271 messages need to be attended to. Most probably, there is a translator already assigned to the domain `libc' in your team. Else, the team leader (if any) should inform the translation coordinator of who will become responsible for it. Please translate the remaining messages for the benefit of users of the French language. Once the translation completed, send the result to the address given below, using: > Subject: TP-Robot libc-2.2.3.fr.po in your message header. You may contact either your team leader or me, if any question arises. In the meantime, this PO file has been submitted to the maintainer of programs using the textual domain `libc'. Thanks! The following HTML pages should also be updated by tomorrow. > http://www.iro.umontreal.ca/contrib/po/HTML/domain-libc.html > http://www.iro.umontreal.ca/contrib/po/HTML/team-fr.html The Translation Project robot, in the name of your kind translation coordinator. mailto:translation@iro.umontreal.ca

1 0

New PO file for `libc-2.2.3'
by Translation Project Robot 18 Mai '01

18 Mai '01

Hello, members of the French team at `traduc(a)traduc.org'. This is a message from the Translation Project robot. I`m happy to announce that a new file, available as: > http://www.iro.umontreal.ca/contrib/po/teams/PO/fr/libc-2.2.3.fr.po has been integrated in the central PO archives, and is now kept with all other accepted French translations. The file should soon be made available in mirror sites as: > ftp://ftp.unex.es/pub/gnu-i18n/po/teams/PO/fr/libc-2.2.3.fr.po > ftp://ftp.chg.ru/pub/doc/gnu-i18n/teams/PO/fr/libc-2.2.3.fr.po In this file, 132 messages have been translated already, accounting for 46% of the original text size (in raw bytes). Still, 101 messages need to be attended to. Most probably, there is a translator already assigned to the domain `libc' in your team. Else, the team leader (if any) should inform the translation coordinator of who will become responsible for it. Please translate the remaining messages for the benefit of users of the French language. Once the translation completed, send the result to the address given below, using: > Subject: TP-Robot libc-2.2.3.fr.po in your message header. You may contact either your team leader or me, if any question arises. In the meantime, this PO file has been submitted to the maintainer of programs using the textual domain `libc'. Thanks! The following HTML pages should also be updated by tomorrow. > http://www.iro.umontreal.ca/contrib/po/HTML/domain-libc.html > http://www.iro.umontreal.ca/contrib/po/HTML/team-fr.html The Translation Project robot, in the name of your kind translation coordinator. mailto:translation@iro.umontreal.ca

1 0

Re: [Mailman-i18n] Japanese characters in Mailman archive (fwd)
by Ousmane Wilane 17 Mai '01

17 Mai '01

---------- Forwarded message ---------- Date: Wed, 16 May 2001 22:42:59 -0400 From: Barry A. Warsaw <barry(a)digicool.com> To: Tokio Kikuchi <tkikuchi(a)is.kochi-u.ac.jp> Cc: mailman-i18n(a)python.org Subject: Re: [Mailman-i18n] Japanese characters in Mailman archive >>>>> "TK" == Tokio Kikuchi <tkikuchi(a)is.kochi-u.ac.jp> writes: TK> Yes, please. It would be useful to have a japanese discussion TK> forum even if our Japanization is finally integrated into TK> i18n-Mailman. I agree. I've added an i18n link to the main Mailman pages (only available through CVS at the moment). I've only got an entry for Japanese resources at the moment, but I envision adding additional pointers for other languages, so... If anybody has specific links you'd like me to add for your language, please send them to me. TK> Many thanks to this great software development team! You're very welcome! -Barry _______________________________________________ Mailman-i18n mailing list Mailman-i18n(a)python.org http://mail.python.org/mailman/listinfo/mailman-i18n

1 0

Re: [Traduc] Traduction de la GNU Free Documentation License
by Bernard Choppy 17 Mai '01

17 Mai '01

Le Jeudi 17 Mai 2001 18:10, vous avez écrit : > Salut, Bon, troisième tentative de réponse, j'ai eu un souci avec kmail :-( > Ce qui me laisse perplexe dans cette solution, pourtant séduisante, > c'est que pour un mini-howto, on arrivera vite à un volume supérieur > pour la licence que pour le howto réel. Vrai, mais que dit l'auteur ? Sinon, ce n'est pas une catastrophe, en faisant un chapitre spécifique, on peut le sauter facilement :-) > Tu n'as pas répondu sur la liste, c'est voulu ? Non, le Reply-to a dû sauter :-( > Il faudrait que le maximum de personne en discute sur > la liste pour prendre une décision collégiale. Tout à fait mon avis. C'est pourquoi, si tu le souhaites, je t'autorise explicitement à forwarder mes deux réponses sur la liste. -- Amitiés, Bernard Choppy <choppy(a)imaginet.fr>

1 0

Re: [Traduc] [Mailman-i18n] Final i18n integration (fwd)
by Ousmane Wilane 17 Mai '01

17 Mai '01

>>>>>>> Nicolas Chauvat wrote: NC>> I'm hoping to release a new alpha of Mailman 2.1 some time this week, NC>> and I would love to finalize the integration of the i18n stuff. Below NC>> are my current thoughts on the CVS and distribution structures NC>> necessary to accomplish this. Please comment! NC> NC>T'as contribué une VF, non ? J'ai déjà les 'templates' et je travail sur le catalogue. Si quelqu'un est interesse par la relecture je lui envoie les fichiers! NC> NC>On va pouvoir l'utiliser sur traduc.org :-) ?? C'est la raison pour laquelle j'adores ce modele de dev! Amities! -- -- Ousmane Wilane -- "I beg special forgiveness from those whose barains I haven't get -- inside well enough to incorporate their ideas" -- Larry Wall -- Apocalypse 2

1 0

[Mailman-i18n] Final i18n integration (fwd)
by Ousmane Wilane 17 Mai '01

17 Mai '01

---------- Forwarded message ---------- Date: Wed, 16 May 2001 23:22:35 -0400 From: Barry A. Warsaw <barry(a)digicool.com> To: mailman-i18n(a)python.org Subject: [Mailman-i18n] Final i18n integration I'm hoping to release a new alpha of Mailman 2.1 some time this week, and I would love to finalize the integration of the i18n stuff. Below are my current thoughts on the CVS and distribution structures necessary to accomplish this. Please comment! To CVS: - Each supported language can be checked into the Mailman CVS tree as follows (for mythical language `xx'): templates/xx/*.{html,txt} -- these are translated versions of the English templates messages/xx/README.xx -- a README file containing useful information for anybody wanting to use or modify this translation. It should include at a minimum the necessary entry for LC_DESCRIPTIONS. It might also contain an email address to contact the xx language's champion or leader. messages/xx/LC_MESSAGES/catalog.xx mailman.mo -- these are the human readable translation of the mailman.pot file, and the binary .mo file - There will also be a messages/mailman.pot file checked. I will update that file via pygettext.py when I've piled up enough changes to the translatable strings. Distribution - Mailman will come with a default `en' language containing the original template files, but with no mailman.mo file. - Mailman will have a `light' distribution which contains only the English translations. It might also be worthwhile to distribute a `sumo' package which contains all the checked-in languages. - Each language will be separately distributed as a tarball such that you can run the following in your install directory: % tar zxf mailman-i18n-xx.tgz % bin/newlang -l mylist xx and now language xx will be available to your users (after changing mm_cfg.py of course). - Thus, if we have 10 languages checked in, but you're only interested in 3 of them, you can download the light distro and then install only the language packs that you want. I will definitely be looking for volunteers to manage the language distributions, especially because I expect language updates to happen asychronously from Mailman versions. I think it will be too much work for me to keep the languages up-to-date, shepherd the various translation efforts, do all the language check-ins etc. I'm willing to give a few volunteers check-in privs to the Mailman tree if they are willing to manage the language releases. I'll try to write scripts to make packaging language distros fairly easy. Have I missed anything? I'm going to spend a bit of time putting the basics together before I commit stuff to CVS. If anybody has fairly up-to-date translations of both the templates and the catalog, please send me a link. -Barry _______________________________________________ Mailman-i18n mailing list Mailman-i18n(a)python.org http://mail.python.org/mailman/listinfo/mailman-i18n

1 0

Offre de services
by Luc MAIGNAN 17 Mai '01

17 Mai '01

Salut la communauté, je souhaiterais apporter ma contribution en traduisant des documents techniques (notemment des HowTo, mais je suis ouvert à toute proposition). Comment puis-je connaitre la liste des documents qui attendent un traducteur et postuler ? Merci Luc M. __________________________________________________ Voila vous propose une boite aux lettres gratuite sur Voila Mail: http://mail.voila.fr

2 1

Aller à la page :

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

Traduc