Am 09.11.2013 08:50, schrieb Raphaël Jakse:
> Le 09/11/2013 07:43, Philippe Sigaud a écrit :
>>
>>
>>     On Friday, November 08, 2013 20:16:44 Timothee Cour wrote:
>>      > french as well (although living in US).
>>      > A great start would be lobbying so that they teach D in French
>>     Engineering
>>      > schools ... instead of ocaml.
>>
>>
>> Did they teach you ocaml? I had C, with maybe a dash of C++.
>
> I've been taught OCaml (to introduce functional programming) and C at
> the university. No C++, but ADA. Java is also taught.
>

Actually I find very positive that people get introduced to ML family of languages.

It is a nice way to learn functional programming.

My university had a strong focus in ML (Caml Light back then) and Prolog as well, so I have beed brain damaged since mid 90's always looking forward to using those concepts in the industry. :)

--
Paulo

On Saturday, 9 November 2013 at 10:31:05 UTC, matovitch wrote:
> Thanks. I forked the D template tutorial of Philipp Sigaud to start a french translation : https://github.com/matovitch/D-templates-tutorial. Feel free to clone ! :-)
>
> Templates are a strong features of D and I think they deserve to be promoted.

It would be great if you could subscribe the french forum and
start a topic about this, we can talk about this and help :)

Also Raphaël Jakse please contact me :)

Le 09/11/2013 11:28, Jacob Carlborg a écrit :
> On Saturday, 9 November 2013 at 08:32:24 UTC, Jonathan M Davis wrote:
>
>> Given French's more limited vocabulary and resistance to adding new
>> words,
>> translating technical terms has got to be a royal pain (and then
>> L'Académie
>> Française gets ticked when folks use English words for new stuff). I
>> had my
>> desktop in French for a while at one point, which definitely improved my
>> vocabulary. For better or worse, a lot of technical words seem to get
>> translated very literally, which gets interesting sometimes
>> (particularly when
>> there doesn't seem to really be a direct translation available). But I
>> expect
>> that it's often the same in other languages, though maybe some of them
>> are
>> more open to just using the English word.
>
> I can tell you that when I talk about programming or computers in
> Swedish I use a lot of English words. Many words don't have a good
> translation and just sound weird. If I would to translate "slice" into
> Swedish it would probably be "skiva", especially if we're talking about
> a slice of bread. But if I would say "skiva" when talking about
> programming to someone else they would probably say "WHAT?" and have no
> idea what I'm talking about.

We surely would get the same kind of reaction for "tranche" in French. But you are not sure people will understand "slice" correctly, even if they can be kind of familiar with the word (e.g. because of the slice method of the Array object in Javascript). To understand "slice", maybe some people will even try to translate it.

I think it is just a matter of habit, and your Photoshop example tend to confirm it.
When you used the word one time and explained it, people will start to understand you, and as you use it, people will get used to it and start employ it. Or not, an then it is time to fall back to the Enligh version of the word. So why being concerned by trying the native word first? Well, because it is native and it can help the appropriation of the concept behind it for people which don't master it. Maybe I'm wrong.

For slice, it seems it is a concept to be defined for each programming language anyway.

It still remains important to give the English word in lessons to be able to communicate with the rest of the word, and to be understood by people who already know the English word. Agreed.


>
> I'm using all my software in English. One time I was going to use
> Photoshop at school and they had the Swedish version. I couldn't find a
> single thing by looking at the names. Just hoping you're remembering the
> locations of the buttons and the menus.
>
> --
> /Jacob Carlborg

On Saturday, 9 November 2013 at 10:24:18 UTC, Raphaël Jakse wrote:

> Yes, it makes sense. I thought about it and got to the same conclusion as you.
>
> I would title the chapter "Les modèles (templates)" with "templates" in italic, or "Les modèles et le mot clé template" with "template" in a monospace font.
>
> keywords are not translated and are writen in a monospace font (or whatever style dedicated for writing code) and concepts, ideas, topic or whatever, get translated.

Sounds good. I like the idea of putting the English word in the title as well.

--
/Jacob Carlborg

Le 09/11/2013 11:38, Raphaël Jakse a écrit :
> people which
who*

On Sat, Nov 9, 2013 at 8:21 AM, John J <john.joyus@gmail.com> wrote:

> On 11/09/2013 01:40 AM, Philippe Sigaud wrote:
>
>> I don't even know how to say 'template' in French.
>>
>>
> Do they really need to translate keywords like 'template' into French, for that matter into any other language?
>
>
Not the keyword, but the, er, concept, the idea that you can write 'code blueprints'. 'range' is also an idea that could be translated (or not, btw).

Am 09.11.2013 08:21, schrieb John J:
> On 11/09/2013 01:40 AM, Philippe Sigaud wrote:
>> I don't even know how to say 'template' in French.
>>
>
> Do they really need to translate keywords like 'template' into French,
> for that matter into any other language?
>

It is a cultural thing, so whoever is translating needs to be aware how people expect technical documentation to look like.

For example, in Portugal and African Portuguese speaking countries, we rather mix English technical terms with Portuguese even when a translation does exist, whereas in Brazil they tend to choose other words.

My experience leaving in Germany tells me that you only hear people using German official terms in very traditional (aka old) companies, the new generations mix English technical terms with German.

In Spain, you tend to get almost everything translated as well.

Then you also have the problem when a technical term has a translation, it might not be the same across all variations of the language. Spreasheet is "Folha de Cálcul"o in Portugal and "Planilha Electrônica" in Brazil, as an example.


--
Paulo

On Sat, Nov 9, 2013 at 8:43 AM, Raphaël Jakse <raphael.jakse@gmail.com>wrote:

> Le 09/11/2013 08:21, John J a écrit :
>
>  On 11/09/2013 01:40 AM, Philippe Sigaud wrote:
>>
>>> I don't even know how to say 'template' in French.
>>>
>>>
>> Do they really need to translate keywords like 'template' into French, for that matter into any other language?
>>
>>
> I've still not translated the chapter about template so I have not decided anything yet.
>
> My guideline is to translate everything (I hate speaking/reading about computer science with people who use three English works by French sentance) and give the English counterpart the first time to be able to find help in the English world.
>

That seems OK.


>
> Also, using French words when speaking about computer science helps speaking about computer science with people who are not into it, I'm really attached to this.
>
> The French translation for template is "modèle", I think I'll use this one. I'm okay with also giving the English "template" in my translation, but not use it (If somebody disagrees, I'm open to talk)
>
> I had a really hard time translating "slice". I opted for "tranche". That can sound weird but what "slice" really means, unless I am mistaken. If somebody has a better translation, please suggest!
>

extrait?

partie?

Le 09/11/2013 11:39, Jacob Carlborg a écrit :
> On Saturday, 9 November 2013 at 10:24:18 UTC, Raphaël Jakse wrote:
>
>> Yes, it makes sense. I thought about it and got to the same conclusion
>> as you.
>>
>> I would title the chapter "Les modèles (templates)" with "templates"
>> in italic, or "Les modèles et le mot clé template" with "template" in
>> a monospace font.
>>
>> keywords are not translated and are writen in a monospace font (or
>> whatever style dedicated for writing code) and concepts, ideas, topic
>> or whatever, get translated.
>
> Sounds good. I like the idea of putting the English word in the title as
> well.

For templates, the English word is so widespread and "Modèle" (maybe also "template") is such an abstract word that putting the English word in the title seems necessary and useful and that could ease comprehension and searches in the tutorial :-)

>
> --
> /Jacob Carlborg

Le 09/11/2013 11:43, Philippe Sigaud a écrit :
>
> On Sat, Nov 9, 2013 at 8:43 AM, Raphaël Jakse <raphael.jakse@gmail.com
> <mailto:raphael.jakse@gmail.com>> wrote:
>
>     Le 09/11/2013 08:21, John J a écrit :
>
>         On 11/09/2013 01:40 AM, Philippe Sigaud wrote:
>
>             I don't even know how to say 'template' in French.
>
>
>         Do they really need to translate keywords like 'template' into
>         French,
>         for that matter into any other language?
>
>
>     I've still not translated the chapter about template so I have not
>     decided anything yet.
>
>     My guideline is to translate everything (I hate speaking/reading
>     about computer science with people who use three English works by
>     French sentance) and give the English counterpart the first time to
>     be able to find help in the English world.
>
>
> That seems OK.
>
>
>     Also, using French words when speaking about computer science helps
>     speaking about computer science with people who are not into it, I'm
>     really attached to this.
>
>     The French translation for template is "modèle", I think I'll use
>     this one. I'm okay with also giving the English "template" in my
>     translation, but not use it (If somebody disagrees, I'm open to talk)
>
>     I had a really hard time translating "slice". I opted for "tranche".
>     That can sound weird but what "slice" really means, unless I am
>     mistaken. If somebody has a better translation, please suggest!
>
>
> extrait?
>
> partie?
>
>

To be considered :-)
However, these two words do not seem to imply continuity that "tranche" seems to imply.

Maybe we should vote for the translation of this word.