- Traductions_FR

Documentations en anglais
by Patrick ZAJDA 13 Jun '21

13 Jun '21

Hello, Puisque Sylvie et Sof nous rejoignent, et en attendant une documentation en français évoquée sur TeamTalk, voici la documentation sur la traduction des différents éléments de NVDA : https://github.com/nvaccess/nvda/wiki/Translating Bon courage. -- Patrick ZAJDA

1 0

Re: [Traductions_FR] [HS] Processus des extensions NVDA
by cyrille.bougot2＠laposte.net 31 May '21

31 May '21

Salut Patrick Je t'avoue que le processus est un peu flou en ce moment. Voici ce que j'ai compris: 1. Tu fais une release sur ton GitHub 2. (optionel?) Tu envoies un message pour informer de la release sur la liste nvda-addons. Vu que c'est une mise à jour, pas besoin de revue je pense. 3. Tu crées une pull request pour changer le lien de téléchargement dans le fichier http://github.com/nvaccess/addonFiles/pulls‌get.php du repo addonfiles. Attention, ce repo a migré chez nvaccess. Tu peux prendre exemple sur celles déjà ouvertes: https://github.com/nvaccess/addonFiles/pulls‌ 4. Ta pull-request doit être revue. et approuvée Je crois que seuls Joseph, Noelia et NVAccess ont les droits. 5. Une fois aprouvée, la PR est mergée par NVAccess (Reef Turner aka @feerrenrut); parfois ça peut prendre qq jours voire qq semaines. Pour la traduction, j'ai pas bien compris si le lien entre SVN et le fork de ton add-on fonctionne encore bien ou pas. Je vois que Noelia fait des traductions de ses extensions dans son coin à base d'actions GitHub. Et que Joseph publie aussi des mises à jours de traductions, mais je ne sais pas comment il les a intégrées. Faut que je me penche dessus et que je publie justement les traductions pour Outlook Extended en même temps que la compa 2021.1. Tout n'est pas très clair car on est un peu au milieu du gué, dans l'attente (qui se prolonge) d'un nouveau framework de publication des extensions (add-on store). A+ Cyrille De : "Patrick ZAJDA" A : traductions_fr(a)nvda-fr.org Envoyé: lundi 31 Mai 2021 15:04 Objet : [Traductions_FR] [HS] Processus des extensions NVDA Hello, Vu que je sais qu'il y en a parmi nous au moins deux (Abdel et Cyrill) qui ont eu l'occasion de publier récemment des versions de leur extension NVDA, serait-il possible de m'expliquer comment ça se passe maintenant SVP ? Parce qu'apparemment, je ne fais plus parti de l'organisation nvdaaddons, du coup niveau traduction de l'extension Dropbox c'est largement périmé ;) Qui a accès à addon-files pour mettre à jour le fichier php de téléchargement de chaque extension ? Je crois que j'ai besoin d'une remise à niveau :) Merci, -- img {white-space: pre;} Patrick ZAJDA -- Traductions_FR mailing list Traductions_FR(a)nvda-fr.org http://litchi.site-meganet.com/cgi-bin/mailman/listinfo/traductions_fr

2 1

[HS] Processus des extensions NVDA
by Patrick ZAJDA 31 May '21

31 May '21

Hello, Vu que je sais qu'il y en a parmi nous au moins deux (Abdel et Cyrill) qui ont eu l'occasion de publier récemment des versions de leur extension NVDA, serait-il possible de m'expliquer comment ça se passe maintenant SVP ? Parce qu'apparemment, je ne fais plus parti de l'organisation nvdaaddons, du coup niveau traduction de l'extension Dropbox c'est largement périmé ;) Qui a accès à addon-files pour mettre à jour le fichier php de téléchargement de chaque extension ? Je crois que j'ai besoin d'une remise à niveau :) Merci, -- Patrick ZAJDA Certification NVDA 2019

1 0

Rel. 2021beta1 imminente: Diffs sur le fichier symbols
by cyrille.bougot2＠laposte.net 22 May '21

22 May '21

Bonjour à tous A voir le repo Github et les commentaires, la release NVDA 2021.1beta1 semble imminente (une seule issue ouverte dans le milestone 2021.1 et commentaire indiquant des tests pendant ce WE sur le nouveau commit de eSpeak avant la beta). J'ai envoyé un message ci-dessous sur la liste internationale des traducteurs concernant le fichier des symbols. Mais je ne travaille pas sur sa traduction en français, le but n'étant pas de faire le travail 2 fois en parallèle. Michel, habituellement, je pense que c'est toi qui le traduis. Prévois-tu bien de le faire durant ce WE? J'ai vu que tu as déjà traduit l'interface et le guide utilisateur (merci!) Si tu ne peux pas ou si tu as des difficultés, je veux bien essayer de m'y atteler. Mais je ne suis pas sûr d'avoir tout le temps... Donc si tu as du temps, je préfère te laisser à la manoeuvre. Je pourrai corriger à la marge si nécessaire. Pour les symbols math, j'avais déjà effectué ce type de traduction que tu peux trouver dans l'extension Access8Math. A+ Cyrille ---------- mail transféré ---------- Envoyé: vendredi 21 Mai 2021 18:13 De : "Cyrille via groups.io" A : nvda-translations(a)groups.io Objet : Re: [nvda-translations] what's happened to symbols.dic? Sorry, the attachment was missing. Here it is.‌ De : "Cyrille via groups.io" A : nvda-translations(a)groups.io Envoyé: vendredi 21 Mai 2021 18:09 Objet : Re: [nvda-translations] what's happened to symbols.dic? Hello all Reef Turner indicated in the Github issue that converting back the line ending would result in a new full file diff, which is indesirable. So translators have to go forward with this new file. If it helps, I have made a diff between the old symbol file (commit b413305a70db75c3591ad85698901e61649916a8:source/locale/en/symbols.dic) and the new one (commit a3b6c23f05d8e613a27effbd68715395d6255407) ignoring manually line ending modifications. It is attached to this message. For reference the commits are the following: The old commit is the last merge of alpha into beta in NVDA Github repo before the release2020.4: commit b413305a70db75c3591ad85698901e61649916a8 Merge: e62a39eee 376edfcf0 Author: Reef Turner <feerrenrut(a)users.noreply.github.com> Date: Thu Nov 19 18:35:25 2020 +0800 Merge pull request #11844 from nvaccess/master Merge alpha into beta The new commit is the last commit found on the beta branch in NVDA Github repo: commit a3b6c23f05d8e613a27effbd68715395d6255407 (HEAD -> beta, nvaccess/beta) Author: Reef Turner <feerrenrut(a)users.noreply.github.com> Date: Fri May 21 17:00:06 2021 +0800 Update espeak to latest master (PR #12449) Hope this helps. Cheers, Cyrille De : "Cyrille via groups.io" A : nvda-translations(a)groups.io Envoyé: jeudi 20 Mai 2021 17:52 Objet : Re: [nvda-translations] what's happened to symbols.dic? Hello Sorry, my first analysis was wrong. ‌There is of course a big diff due to line re-ordering. But the PR that adds math symbols also seems to have converted line ending characters for all lines. I do not think it was intended. Thus I have commented at http://github.com/nvaccess/nvda/pull/11467 and CCed NVAccess people. Let's wait for their recommandations. Cheers, Cyrille De : "Cyrille via groups.io" A : nvda-translations(a)groups.io Envoyé: jeudi 20 Mai 2021 10:49 Objet : Re: [nvda-translations] what's happened to symbols.dic?  Hello The answer is this point: “Added some more mathematical symbols and restructured for better overview” The order of the lines in the symbol file has been modified. Unfortunately for translators it gives a lot more of work to check for diffs. It would have been better to separate the PR in 2: one for math symbols and the second for re-ordering. Now we have to deal with it. Cheers, Cyrille De : nvda-translations(a)groups.io <nvda-translations(a)groups.io> De la part de José Manuel Delicado Alcolea via groups.io Envoyé : jeudi 20 mai 2021 10:05 À : nvda-translations(a)groups.io Objet : Re: [nvda-translations] what's happened to symbols.dic? Hi Simone, After running the command "git log source/locale/en/symbols.dyc" inside the NVDA repository (master branch), I imagine the answer to your question is in the last 2 commits. I paste the result below. commit 90dd4e9ab9afa4bb058d1650530b68918e13e98c Author: Cyrille Bougot <cyrille.bougot2(a)laposte.net> Date: Mon Feb 1 01:03:36 2021 +0100 Fix-up of #11467 in symbol file: (#12017) - deleted extra tab - removed duplicate symbol definition commit 2e0ebb5691b4eabff6bdceaab4f45a5485fca026 Author: Adriani90 <adriani.botez(a)googlemail.com> Date: Thu Jan 21 02:49:30 2021 +0100 Added some mathematical symbols (#11467) * Added some mathematical symbols * Addressed missing tab character and a missing level * Added some more mathematical symbols and restructured for better overview * Fixed some symols to match different languages (i.e. see issue #11502 * Addressed review actions and removed the ordinal symbols because they cause issues in many lating languages. Those ordinal symbols should be controlled by the synthesizers. * Addressed review actions (removed the mathematical constants and the incremental symbol to avoid confusions and improved consistency in ortographics) Regards. El 20/05/2021 a las 9:57, Simone Dal Maso escribió: Hello, today I started looking into the new modifications of symbols.dic file, but I am quite confused. In the differences.txt file, I can see that all lines are removed and then readded. We have the minus sign for all the file and then the plus sign. So, the question is, what is changed? Thank you! -- José Manuel Delicado Alcolea Equipo de gestión web y desarrollo Asociación Comunidad Hispanohablante de NVDA - Tel.: (+34) 910 05 33 25 ext. 2001 - jm.delicado(a)nvda.es - www.NVDA.es - @nvda_es ***Este mensaje y sus adjuntos están dirigidos a su destinatario y pueden contener información exclusiva o confidencial. La utilización, copia o divulgación de los mismos por parte de alguien diferente a dicho destinatario no está permitida sin autorización. Si ha recibido este mensaje por error, le rogamos que lo comunique por esta misma vía y seguidamente lo destruya.*** _._,_._,_ Groups.io Links: You receive all messages sent to this group. View/Reply Online (#2477) | Reply To Group | Reply To Sender | Mute This Topic | New Topic Your Subscription | Contact Group Owner | Unsubscribe [cyrille.bougot2(a)laposte.net] _._,_._,_

3 3

Traduction du change log 2020.4
by cyrille.bougot2 15 Dec '20

15 Dec '20

<div style="font-family:Arial, Helvetica, sans-serif; font-size:12px;">Hello Corentin et à tous @Corentin: J'ai vu dans le log des commits que tu avais supprimé des diffs sur le change log car tu es en train d'y travailler. J'ai quelques questions/remarques à ce sujet: * Si tu as un travail en cours, même incomplet, je pense que ça serait bien de le committer. Il semble que la release 2020.4 beta 1 va sortir d'ici très peu de temps: les derniers tickets Github encore ouverts dans le milestone 2020.4 ont été reporté à 2021.1, donc plus rien n'empêche la release. Egalement, Reef a ouvert depuis peu ce ticket <a href="https://github.com/nvaccess/nvda/pull/11941">https://github.com/nvaccess/nvda/pull/11941</a> ce qui laisse penser à une release imminente. * D'une manière générale, je pense qu'il est préférable que tu supprimes les sous-dossiers de "changes-newRevisions" en même temps que tu committes ton travail ou juste après. Ainsi, si pour une raison ou une autre (maladie, folle histoire d'amour,...) tu ne peux pas committer ta traduction, c'est plus facile pour un autre de prendre le relais. Michel, corrige-moi si je me trompe. A+ Cyrille  </div>

3 2

Discussion - Raccourcis dans l'interface
by cyrille.bougot2＠laposte.net 21 Nov '20

21 Nov '20

Bonjour à tous Je profite de commits récents de Michel et Corentin pour discuter un peu des raccourcis dans l'interface. Ca a été un sujet remis sur la table dans une polémique récente. Et je pense qu'il est effectivement intéressant de clarifier les choses entre nous et d'échanger nos avis sur le sujet. Voici les principes ou questions que j'ai constaté dans l'attribution de touches d'accès rapide dans l'interface: 1. Mettre des touches d'accès rapide en Français sur les contrôles qui en ont en anglais. -> Je pense que tout le onde s'accorde là-dessus. Pas de discussion. 2. Mettre des touches d'accès rapide en français sur des contrôles qui ne l'ont pas à l'origine en anglais: Je constate que ça a été fait plusieurs fois (dernier commit de Michel entre autre). Je suis plutôt pour, avec deux bémols: * Certains contrôles n'ont peut être volontairement pas de touche d'accès rapide pour éviter qu'ils soient mis en focus ou activés par inadvertance. Par exemple l'élément de menu NVDA "Réinitialiser la configuration aux valeurs par défaut" ou la case "Réinitialiser la configuration aux valeurs par défaut" dans le panneau des paramètres avancés n'ont pas de raccourci. Et je pense qu'il faut les laisser sans raccourci. * Pour les contrôles pour lesquels des raccourcis manquent, je pense qu'il est encore mieux de proposer le changement dans la version anglaise de NVDA afin que ça ne profite pas qu'aux francophones. Si j'ai du temps, je regarderai s'il y a déjà une issue GitHub à ce sujet. 3. Eviter de modifier les raccourcis d'une version à l'autre de NVDA. Cela évite aux gens qui ont déjà appris ces raccourcis de devoir en apprendre de nouveaux. En pensant tout particulièrement aux gens qui ont plus de difficulté d'apprentissage. C'était un argument avancé par Bachir. Je n'y avais pas pensé auparavant mais ce point de vue m'a semblé pertinent. Evidemment, ce principe trouve ses limites lorsque d'autres raisons motivent à changer le raccourci. 4. Eviter les doublons dans un même menu ou dialogue: Exemple: commit de cette semaine de Corentin. Je suis pour. Lorsqu'on change l'un des deux raccourcis, je pense qu'il faut cibler le moins utilisé ou le plus récent, en pensant aux gens qui vont devoir réapprendre ce nouveau raccourci. 5. Pas de caractère exotiques (lettres accentuées, symbole ou ponctuation) Je n'ai rien constaté de tel dans NVDA français. Je pense que c'est important, particulièrement pour les utilisateurs aveugles que nous sommes. Car il est parfois plus difficile avec la synthèse de savoir que: - alt+à signifie "alt plus a accent grave" - alt+? Signifie "alt plus point d'interrogation Voilà. J'espère lire vos réactions, que vous soyez d'accord ou pas, pour en discuter si besoin. Bon week-end. Cyrille -----Message d'origine----- De : NVDA localisation <noreply+nvdaL10n(a)nvaccess.org> Envoyé : samedi 21 novembre 2020 09:25 À : Michel such <michel.such(a)free.fr>; Patrick ZAJDA <patrick(a)zajda.fr>; Remy Ruiz <remyruiz(a)gmail.com>; Abdelkrim Bensaid <abdelkrim.bensaid(a)free.fr>; Cyrille Bougot <cyrille.bougot2(a)laposte.net>; Corentin BacquÃ©-Cazenave <corentin(a)progaccess.net> Objet : SRT Changeset [59554]: fr - Interface - Added a navigation shortcut in the Braille dialog (for new show messages) michelsuch committed Changeset [59554]: fr - Interface - Added a navigation shortcut in the Braille dialog (for new show messages) fr - Interface - Added a navigation shortcut in the Braille dialog (for new show messages) Files Affected: M /fr/nvda.po Files count: 1 Commit (by michelsuch)

1 0

Equipe des traducteurs
by cyrille.bougot2＠laposte.net 13 Nov '20

13 Nov '20

<div style="font-family:Arial, Helvetica, sans-serif; font-size:12px;">Bonjour à tous‌ Suite aux derniers messages sur la liste internationale des traducteurs NVDA (cf deux derniers messages ci-dessous qui font suite à d'autres plus anciens), je pense qu'on ne va pas pouvoir rester sans rien répondre au risque de laisser monter encore un peu plus la mayonnaise, même si je n'approuve pas vraiment cette manière de prendre tout le monde à témoin pour faire une relance à Michel.  Il y a au moins deux demandes en suspens pour l'équipe française (et Michel plus particulièrement): - Bachir demande à être réintégré dans l'équipe de traduction - Afik propose son aide Je ne compte pas la demande d'exclusion de Corentin de la part de Bachir qui, à mon sens, est très mal amenée de la part d'une personne qui ne fait plus partie de l'équipe de traduction et qui souhaite la réintégrer. De plus, j'ai bien l'impression que Bachir ne va pas lâcher l'affaire. Pour info, je n'ai aucun lien étroit avec Bachir, ni avec Corentin, et mes échanges personnels avec l'un ou l'autre se résument probablement à moins d'une dizaine de mails. Les questions qui se posent à nous sont: - avons-nous quelques critères pour définir si une personne peut faire partie de l'équipe de traduction et/ou être en charge de telle ou telle tâche? - si ce n'est pas le cas, devons-nous en définir ? (je pense que oui) - avons-nous besoin de main d'oeuvre supplémentaire ou pas ? Si on accepte que Bachir revienne, il faut clarifier ces conditions de fonctionnement pour que chacun respecte l'autre et qu'on ne discute que des actes des uns et des autres, pas des personnes. Si on n'accepte pas qu'il revienne, il faut l'exprimer clairement et avoir de bons arguments. Voilà, je vous envoie tout ça pour en discuter ensemble. Bonne journée. Cyrille  </div>   <div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">---------- mail transféré ---------- Envoyé: jeudi 12 Novembre 2020 15:23 De : "Afik Souffir" A : "nvda-translations(a)groups.io" Objet : Re: [nvda-translations] About the NVDA's French translation crisis <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <div> </div> Hi, i can help with french..    <div dir="ltr">Sent from my Iphone</div> <div dir="ltr">  <blockquote type="cite">On 12 Nov 2020, at 15:36, Bachir Benanou <ben_bach(a)mail.fr> wrote:  </blockquote> </div> <blockquote type="cite"> <div dir="ltr">         Hello everybody, I hope everything is fine with you. Just a quick note to let everybody know that the situation within the French team is just the same. I haven’t had any contact from Michel Such, nor had I any hope of being able to translate NVDA into French again in cooperation with other French team members. I again, ask for Corentin to be removed from the translation system because of his aggressiveness and his incompetence as far as translation is concerned. I also kindly ask that my Yahoo! Address be put back into the automatic NVDA translation workflow. I’ll continue to follow this closely. Thank you.   Have a nice day, all of you and stay safe. All the best, Bachir       <div class="moz-cite-prefix">On 21 October 2020 at 08:33, Michel Such wrote:</div> <blockquote cite="mid:7d5959e5-f0e6-6435-79f8-bfa9204464ae@free.fr" type="cite"> Hi Bachir and all, This wille be my only intervention in this thread, hopefully shorter than yours. I started working on french translation in 2007, in the early stage of the project, I think I was among the 2 or 3 first to start a translation. Along the years, several people joined me to do the job, some doing it for a short while (most of us have many other things to do), and others like you stayed longer and we formed a small team. At the moment, we are only 2 people translating, Corentin and I. Even if I was the first to do the job, I never pretended to manage things, I prefer when decision are taken aafter discussing with others in an open minded way. Among the people working on the project, you were probably the best translator. But, when working in a team, the most important is not to be the best, the most important is to be able to maintain good relation with the other members of the team. And here is the problem: You are unable to accept ideas of people younger or presumably less experimented than you. It began with Patrick long ago and began even more difficult when Corentin joined us. I won't detail all that happened because it is of no interest for the community of translators, but having as only argument "I'm right because I am the more graduated" is not something admissible. Because I was uncomfortable with this situation, I tried many times to discuss with you to reduice tension with others. After each conversation, I felt that problems were fixed, but they came back later, even worse. Some months ago, you told me you did not want to continue working on translation and it was a real relief for me. But after that, you began to plag Corentin with insulting mails (mails we have kept). Seeing that, we decided to revoke you from the translation system, because we thought you became able to even destroy our work. To end with all this, I will say that yes, there was a problem in the french translation team, and this problem was your toxic attitude.   <div class="moz-signature"><a href="mailto:michel.such@free.fr" moz-do-not-send="true">Michel Such</a> <hr> <div><NVDA Certified Expert.png></div> </div> <div class="moz-cite-prefix">Le 20/10/2020 à 18:49, Bachir Benanou a écrit :</div> <blockquote cite="mid:09bb9881-2dd1-f53d-acdb-2aa329e4d18b@mail.fr" type="cite">   Dear translators, NVDA contributors, and NVAccess Staff, My name is Bachir BENANOU and I am a member of the NVDA French Translation team since 2010. I am also a former university student with an MA degree in English and an MA degree in computer sciences applied to Technologies and Disabilities. I first heard of NVDA through ACB Radio (The American Council of the Blind Radio Station) back in 2007. I was beginning my studies within the field of Accessibility at that time. I speak Arabic, French, Spanish, Italian, Portuguese and I am also an Esperantist. I can read and write Braille grade I and grade II in Arabic, French and English.   I am writing this message to tell you about the problems I am facing within the French Translation Team, particularly beginning 2019. I strongly hope to be as clear as possible, as this is a bit complex to explain.   When Mr. Such, the maintainer of the NVDA French Translation asked for volunteers to help translate NVDA’s ChangeLog and interface, I was very happy to lend a hand, putting all my competence to help the Screen Reader grow. I would have continued like this for many years to come, except that misunderstandings began to arise since 2013, when I joined the Automated Translation System. I began to notice that my corrections and suggestions were not accepted by the youngest French team member at that time, Patrick ZAJDA. When the maintainer asked publicly for help on a French list dedicated to Free and Open-source Accessible Software, (ALLOS), Patrick was the first to object that we have not to be scores and hundreds to correct spelling. That was the first glimpse of the atmosphere. So, I tried as hard as I could to avoid glitches and maintain communication to make things easy for everyone, until I asked for an invitation to Assembla and got an invitation to join in.   Mr. Mesar Hameed, the developer and maintainer of the Automated Translated workflow very kindly sent Michel SUCH and Patrick a message asking them to coach me through Skype so as I can familiarize myself with the tools to translate. That’s how I found myself cooking in the stew and started translating the ChangeLog and suggesting improvements to the interface, both in conformance with Microsoft Windows terminology and with my knowledge of translation universal rules. I am convinced that for a translator to be efficient, she/he must be able to handle different data aspects and fluently handle ESP, (English for Specific Purposes) as well as ETP (English for Technical Purposes), the latter applies, of course, to NVDA’s interface. The field of linguistics is vast and fascinating.   MR. SUCH explained how to deal with revisions and showed ma how to control information before sending it. Mr. ZAJDA reproached my way of communicating with him publicly arguing that he was not there to teach people nor to make friends but to work. Shortly afterwards, while working on the user’s guide, I received a message from him stating that he’s working on the guide, that if I touch it, he will lock it. So much for the coaching. One day I forgot to remove a BOM from the encoded t2t file and he sent a message to the French team stating that people come around without knowing what they were up to and that this is elementary to remove a BOM. So, from that point on, communication was very difficult with him, mainly because of his sarcasms, his unkind answers and his disrespect mail. I tried to settle things in private for a while until I became convinced that it was no use, back in 2014. One day, Mr. Such asked us what we thought about remapping some keys to facilitate transition from another screen reader to NVDA, proposing a complete scheme. I said it was a good idea, but that this can be problematic for some, adding that the suggestion was good to be considered. Mr. ZAJDA answered that we are JAWS free Edition partisans, that we did not know what we were talking about, that I was a very convincing man, that I have convinced him of course. This irony continued on and on for years, making the cooperation very difficult for me.   On September 2016, we translated the NVDA Remote Add-on into French and we managed to do the job in an acceptable environment and ended the translation with no incident. It was relieving to know that at least communication significantly improved. But after we did this translation, silence fell.   Things went on till beginning 2019. The NVDA French translation team stopped communicating by mail and dialog became inexistent altogether. I guess our goal was to work on the ChangeLog and the interface avoiding conflicts by not communicating. Submissions to NVDA’s interface and ChangeLog went on smoothly despite the problems with the translation system, but no clashes where to be noticed simply because Mr. ZAJDA stopped translating. The SVN logs can prove what I am stating here.   On March the 28th 2019, a teenager who does not speak English was invited to the translation system. I personally do not know who added him in the first place, I would have said (No), knowing the boy by disrepute on French discussion lists. This boy has many accounts on Assembla: miclchlaus, Oreonan1, Oreonan2, and another account by the name of Corentin. Things being as they were, I sent him a private welcome message inviting him to communicate and exhorting him to cooperate with us. He did not answer. On July the 24th at 22:48 I received a message from Corentin the teenager, asking me to stop messing with his work that he wanted to put the symbol % instead of the word percent to translate the string related to the announcement of battery charge, that in his opinion, Michel Such is the only habilitated person to supervise what he does and that if I were to restore the string to its original state, he would put back his translation replacing mine. I replied the next day that the English text is a word and that one has to find a word to translate. When it’s a word, one cannot put a symbol in the translation. Corentin did not reply. By Autumn 2019, I began thinking of contacting NVAccess to inform the staff that NVDA’s French interface was in danger, but I waited hoping for things to straighten out. They didn’t. Things worsened as you will see.   Soon afterwards, I began noticing the use of automatic translation in the ChangeLog and mistakes and omissions attracted my attention, so I corrected all I could correct. For example, Track Changes was translated to Changement de pistes in French. For those who do not speak French, Changement de pistes can mean the change of a musical track. It can also mean a path change for runners. It was none of this, in fact, it was about tracking changes in Microsoft Word. But when I re-translated the sentence, Corentin used the log to protest.   By December 2019, I could not handle the situation any longer. Oreonan2, (Corentin) began playing with the log and posting unkind comments. One day I woke up to find an e-mail generated by SVN entitled: (Go to correct my work). So, I began asking for help. I contacted the maintainer on December 9th I wrote Mr. Such for advice. He replied that if it is about the ping pong match between me and Corentin, he didn’t want to arbiter our quarrels. Next, I contacted Joseph Lee. We had a nice long discussion about the overall French translation quality and what can be done to improve the situation, emphasizing that if the teenager does not want to cooperate, Joseph would have a talk with him, which he kindly did on April 9th 2020. Joseph tried to talk to the teenager and encourage dialog again by telling him to talk to his fellow translators.   I also contacted the NVAccess staff and sent them a copy of the interface for safeguard purposes. Mr. Curran answered that globally contributors are doing very well together, but that NVAccess is taking note of what is happening within the French team, adding that if the teenager does not speak English, he did not mind him being removed.   Shortly before that, On March 4th 2020 Patrick ZAJDA wrote the nvda-translations to complain that I am against hard spaces in documents, asking whether these were disallowed in the ChangeLog. I can assure you it was a false problem. Can you imagine a team where we can’t even agree in non-breaking spaces or hard spaces or no break spaces and the like? Come on! This is absolute dribble! When I read what Patrick ZAJDA wrote, I wrote to Mesar the same day a message entitled (It’s not hard spacing, It’s lack of communication) Here is an excerpt: “In short, it's not about hard spaces or non-breaking spaces as they are sometimes called, it is about a child, OreoNan who doesn't accept any correction or spelling fix made by someone else. Patrick who is twenty-five, I think, protects him.) end of excerpt. I sincerely think that these people want me to go away. They don’t want me to be around and that’s all they want. Strangely, they seemed to forget that NotePad++ just does not generate these signs as one writes.   When Oronan2 –Corentin) started arbitrarily changing the interface hotkeys, I tried to explain to him that we have spent years designing these, that users might have trouble learning NVDA if shortcuts were to change too often. I spent an hour and a half on April 9th 2020 to try and make myself clear. All to no avail. By the Middle of June, I was completely discouraged. So I wrote Mr. Such to thank him for the help he provided since 2010. I also wrote him that I am forced to stop, that the atmosphere within the French translation team was unbearable. He kindly answered that as far as he’s concerned my suggestions are welcome. But today, I think I will come back to safeguard NVDA and contribute translation again. I downloaded NVDA 2020.3 and saw that many changes were made to the interface: not only the hotkeys were changed again without any consultation, but the strings were re-translated to Corentin’s liking. Please, please, help. NVDA’s French interface is being tampered with.   A few days ago I went to GitHub to see what is going on with NVDA’s development. I noticed that my mail address was removed. I do not know what caused this, but it was surprising. So, yesterday, October 19th, 2020 I asked Patrick ZAJDA and Corentin three questions: <ol start="1" type="1"> <li class="MsoNormal">What logic are they applying when they changed the hotkeys and why?</li> <li class="MsoNormal">Why are they using TeamTalk to hold meeting without informing me they did so.</li> <li class="MsoNormal">I have been contributing to NVDA since 2010. Why is Patrick protecting Corentin against me despite our cooperation all these years?</li> </ol> I gave them 24 hours to answer, but they did not, so I decided to write this message to inform the community of what is going on.   Ladies and gentlemen, as I am writing this, I am feeling ashamed of what is going on, but I’d like to emphasize the fact that the level degraded to such an extent no cooperation with Patrick ZAJDA and Corentin Bacqué-Cazenave is possible. I, therefore, hereby, ask publicly that all the accounts belonging to Corentin be removed from Assembla. I’d like to thank you all for reading this long message and I strongly hope that NVAccess will take the appropriate measures to prevent further conflict that can damage NVDA. Thank you and, long live NVDA! Sincerely, Bachir BENANOU   </blockquote> </blockquote> </div> </blockquote> <div style="color:white;clear:both" width="1">_._,_._,_</div> <hr> Groups.io Links: You receive all messages sent to this group. <a href="https://groups.io/g/nvda-translations/message/2262" target="_blank">View/Reply Online (#2262)</a> | <a href="mailto:nvda-translations@groups.io?subject=Re:%20Re%3A%20%5Bnvda-translations%5D%20About%20the%20NVDA%27s%20French%20translation%20crisis" target="_blank">Reply To Group</a> | <a href="mailto:afik.souffir@outlook.com?subject=Private:%20Re:%20Re%3A%20%5Bnvda-translations%5D%20About%20the%20NVDA%27s%20French%20translation%20crisis" target="_blank">Reply To Sender</a> | <a href="https://groups.io/mt/77686208/355336" target="_blank">Mute This Topic</a> | <a href="https://groups.io/g/nvda-translations/post">New Topic</a> <a href="https://groups.io/g/nvda-translations/editsub/355336">Your Subscription</a> | <a href="mailto:nvda-translations+owner@groups.io">Contact Group Owner</a> | <a href="https://groups.io/g/nvda-translations/leave/3221449/1228572923/xyzzy">Unsubscribe</a> [cyrille.bougot2(a)laposte.net] <div style="color:white;clear:both" width="1">_._,_._,_</div> </div>

3 3

Bonjour à tous et test
by cyrille.bougot2＠laposte.net 24 Oct '20

24 Oct '20

Bonjour à tous Voici juste un petit message pour vous saluer et pour tester par la même mon inscription à cette liste. Je ne savais pas quelle existait et me contentais denvoyer des messages aux adresses trouvées dans le fichier address.py du repo SVN. Javais bien vu la proposition de Corentin de créer une liste des traducteurs français. Mais javais dû louper sa création effective. Comme quoi léchange de messages sur nvda-translate aura au moins eu un avantage pour moi. Bonne soirée. Cyrille

1 0

Test
by Corentin Bacqué-cazenave 24 Oct '20

24 Oct '20

Histoire de voir si Cyrille reçoit :) -- Corentin (certifié Expert NVDA 2019) : * Sites Web o ProgAccess <https://www.progaccess.net> o NVDA-FR <https://www.nvda-fr.org> * Réseaux sociaux o Twitter : @Oreonan_ <https://www.twitter.com/Oreonan_> o Discord : Oreonan#4463 o Messenger : corentin.bacquecazenave <https://m.me/corentin.bacquecazenave> o Snapchat : cbc33000 <https://www.snapchat.com/add/cbc33000> o Facebook : corentin.bacquecazenave <https://www.facebook.com/corentin.bacquecazenave> o Instagram : @Oreonan <https://www.instagram.com/Oreonan/> o Skype : live:cbc.bacque <Skype:live:cbc.bacque>

2 1

2025

2024

2023

2022

2021

2020

Traductions_FR