-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Rémy,
On 11/26/18 10:05, Rémy Maucherat wrote: > On Mon, Nov 26, 2018 at 3:46 PM Christopher Schultz < > ch...@christopherschultz.net> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> André, >> >> On 11/26/18 08:35, André Warnier (tomcat) wrote: >>> On 26.11.2018 13:29, Rémy Maucherat wrote: >>>> On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet >>>> <l.pe...@senat.fr> wrote: >>>> >>>>> Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat >>>>> a écrit : >>>>>> On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas >>>>>> <ma...@apache.org> wrote: >>>>>> >>>>>>> - French has increased from 18% to 64% coverage >>>>>>> >>>>>> >>>>>> Done (well, close enough, a few tribes/ha remain) ! >>>>> A single translation remains to be performed. >>>>> >>>>> Jump to https://poeditor.com/join/project/NUTIjDWzrl and be >>>>> the one to complete the French translation. ;-) >>>>> >>>> >>>> Ok, you could have finished it, I was busy. >>>> >>>> Now we can try to harmonize terms, fixes are then easy to do >>>> with the search feature >>>> >>>> Common ones we have right now: - "socket" (usually >>>> untranslated or cleverly omitted): ? - "endpoint" (for >>>> websockets, and for the Tomcat connectors, so possibly two >>>> different terms): "point d'entrée" ? >>> >>> That sounds like exactly the opposite of "endpoint" to me. >>> Although I must say that even in English, the vocabulary used >>> in some reference documents (in particular everything to do >>> with XML-based protocols, such as SOAP, SAML, OASIS and the >>> like) is sometimes mysterious and counter-intuitive. What about >>> "cible" here ? Or more literally, "point final" ? >> >> I disagree. >> >> An "endpoint" is a thing to which clients connect... an "entry >> point", as Rémy suggests. >> > > French and English constructs are the opposite in a lot of cases so > that's why I though that "point d'entrée" was pretty good, as you > stay the endpoint for the client is the "startingpoint" for the > server (but there it sounds really bad). > > >> >>> For "socket", "soquet" (like the piece in which you insert a >>> plug, or a lightbulb) sounds ok to me. >> >> This sounds okay to me, thought I don't know French at all. :) >> >>>> - "thread" (often it is untranslated elsewhere): "fil >>>> d'exécution" ? - "membership" (that's the clustering >>>> object): "gestionnaire de membres" ? >>> >>> "Membership" refers to "le fait d'être membre", no ? "adhésion" >>> ? (like "cluster members" -> "adhérents au cluster" (with the >>> appropriate French pronounciation for "cleustère") :-) >> >> What would you call a list of people who belong to a certain >> fancy club or society? That's the word that should be used, >> here. >> > > So ... In that case it would simply be "liste de membres". Which > after a quick check actually looks quite good in the context of the > Tribes strings. > > I have another difficult one for Tribes: that "replicated map" > which should be ?? "structure répliquée" ? I used various terms for > that annoying one ... I'm a bug fan of naming things what they *mean*, not what they are. For example, seeing this in code: Map<String,Class<?>> mapOfStringToClass = ...; Is totally worthless from a self-documenting code perspective. This is much better: Map<String,Class<?>> beanImplementationClasses = ...; I think we should do the same thing with our descriptions, here. So, for example, the fact that it's called "replicatedMap" in English probably doesn't matter. The "replicated" part is important. The "map" probably isn't. It could be any collection of objects. So, "replicated structure" seems reasonable, here. On the other hand, when saying "something is wrong with the MacGuffin[1]", translating the word "MacGuffin" may make things worse. If you want to know how to look it up in the documentation and/or code, it needs to agree with what's there. Since the code is (nominally) in English, the term might need to be in English. A corollary of this is that the error messages and the documentation should agree with each other. Do we have French-language documentation for this stuff? >>> (Sorry for the missing c cédille, can't type it here) (PTHT = >>> Protocol de Transport Hyper-Texte) >> >> HTTP should always be spelled HTTP and never PTHT, just like UTC >> is always spelled UTC, even in English (where the acronym makes >> no sense to Englist speakers). >> >> I think maybe you were kidding, but ... just in case :) >> > > We were super serious, like for Apache Matou :) :) I like that as a (silly) name (Apache Dead?), but didn't get the actual joke. :( - -chris [1] https://tvtropes.org/pmwiki/pmwiki.php/Main/MacGuffin -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv8GNcACgkQHPApP6U8 pFj4pQ//QTq8mPf7kuyNIzflzjylSTlcHoAhnjusGhNOlG4pyqIazc8JVllPAHo1 dZUbj9gMcJOBYks7n4sUNBibz4bpmWTWsd2jnu8g4MxvKAXZ40/KRRkqWcyNOQZ/ PB30KH58TrKvZA1gQfy/c7BHeAWEGs6WMHKtFiN+egzAMLI+SFqr0RRN1EEliZhB ankng0iC8bHDurDrLxI46CTCrMZsbJaKVwTNG9Ic/piALGqrGzn51GnqVBMDWREv 3WnWzUp9Q2yFiDHMJHizVECOvTLvk3Wk/e6Wea8Ngia8hwkVpF7HHLJVZDT+b+Eu r2SNwfN72mG8CvJLr82RhTC07xf098vVvpyawpyNkQC0FRXBLMZEnAyakZ+OTOm3 VYqUAVmxM0VJUOlzGNzUA7Zyq9RMYcYKnYQjDqs00aXtqjsxPMye+IT8Mpv7WPxE E4CpEk8lGXi12Rh8feu6IfUeIK9nsTsHHYrKQkSkcwQ7FxO8WpADh0UHpEMkVauJ 6fzBGhDOnQ9XBCi4COoyg58NfrJ2GEhD5LXxdmYar7D0awyvPAEAhB77dnp71yF8 iFeFDcyMXduRZYY8HEG9wCi4Jv59Y0gydwuOuMs8Jmzl7qvLBRywEBXiRheGqOca Uls0BP955KObtj5bwPZAPJSHgpssV5jp5RbpPuXwbI5Ow7Xs2Gk= =cd6a -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
