4 ms·

I think I can only echo most of the comments here that of course there are translations of "branch" "implementation" etc., but the norm is to adapt the English

I think I can only echo most of the comments here that of course there are translations of "branch" "implementation" etc., but the norm is to adapt the English one to the language in my experience. Good example is Turkish, there have been a lot of effort into deriving enough words to be able to converse in full Turkish about the CS topics or even Scientific topics, but it was not able to "satisfy the demand". As an example, "feeding data to some service", there is a widely used "veri" for "data", and there is also translation of "to feed", "beslemek". Sometimes when I hear "Servise veri besliyoruz"(We are feeding data to the service) I immediately think of someone feeding some kind of animal. So in my experience talking to Turkish developers, if they are from a "corporate" environment, they are more likely to use these native words but people involved in startups etc. usually say "Servise Data feedliyoruz". (Generalising a lot here, I am sure they are a lot of exceptions) Fun fact: Turkish actually derived a word for "to compute" to avoid confusing it with "to calculate", Although it is not used at all: "bermek". while the "calculating" is "hesaplamak". In case you are interested(Turkish): http://user.ceng.metu.edu.tr/~ucoluk/yazin/berimsel_bir_deneme.html http://user.ceng.metu.edu.tr/~ucoluk/yazin/berimsel_bir_dene...

sanxiyn 6y ago
While "branch" is loaned in Korea, "implementation" is never loaned, the translation 구현 completely satisfied that demand. In my experience, there are better and worse translations of terms, and adoption mostly depends on quality of translation. Edit: Additional explanation. 구현 roughly means "realization", which I think is a better term than even "implementation" itself. Word "implementation" in non-programming context is translated as 시행. In Korean, "implementing an interface" sounds wrong, compared to "realizing an interface".
- yongjik 6y ago
  It's old-fashioned, but branch does have a Korean equivalent: 분기 (literally "branching", or a single branch separating into multiple branches). E.g., 무조건 분기 (unconditional branch), 조건 분기 (conditional branch), 분기문 (branch statement). (I suspect it was imported from Japanese 分岐.)
  - numpad0 6y ago
    Is that branch as in CPU instructions? We(edit: in Japanese) refer to the Git feature as ブランチ(buranchi) and CPU instructions as 分岐命令(bunki meirei). Old CS folks calls computers as 計算機 but normally it’s コンピュータ. Sounds like whether a word is loaned or created/translated varies?
    - yongjik 6y ago
      Ah yes it's CPU instruction. I'm not sure if a git branch is ever called 분기 - I guess most people use the English "branch" for it.
abiogenesis 6y ago
That article is a bit inconsistent. If "ber" is the root word for "compute", then "computing" should be translated as "berleme", not "berimleme" (similar to "hesap -> hesaplama" vs "calculate -> calculation").
marcosdumay 6y ago
It's always mixed, there are some words people translate, some words they don't. A more formal setup asks for more translations, what does make things really hard. One of the hardest parts of writing my master thesis was discovering the translation of "image matching" (for 3D reconstruction). But I got away with English just fine before I had to write it down. Of course, just an year after that I was in a corporate-like environment (in the government) trying to discover the translation of "runway end turnaround area" for airports. It was still too formal to use English, but we could just settle this one by consensus.

sanxiyn 6y ago

While "branch" is loaned in Korea, "implementation" is never loaned, the translation 구현 completely satisfied that demand. In my experience, there are better and worse translations of terms, and adoption mostly depends on quality of translation. Edit: Additional explanation. 구현 roughly means "realization", which I think is a better term than even "implementation" itself. Word "implementation" in non-programming context is translated as 시행. In Korean, "implementing an interface" sounds wrong, compared to "realizing an interface".

yongjik 6y ago
It's old-fashioned, but branch does have a Korean equivalent: 분기 (literally "branching", or a single branch separating into multiple branches). E.g., 무조건 분기 (unconditional branch), 조건 분기 (conditional branch), 분기문 (branch statement). (I suspect it was imported from Japanese 分岐.)
- numpad0 6y ago
  Is that branch as in CPU instructions? We(edit: in Japanese) refer to the Git feature as ブランチ(buranchi) and CPU instructions as 分岐命令(bunki meirei). Old CS folks calls computers as 計算機 but normally it’s コンピュータ. Sounds like whether a word is loaned or created/translated varies?
  - yongjik 6y ago
    Ah yes it's CPU instruction. I'm not sure if a git branch is ever called 분기 - I guess most people use the English "branch" for it.

abiogenesis 6y ago

That article is a bit inconsistent. If "ber" is the root word for "compute", then "computing" should be translated as "berleme", not "berimleme" (similar to "hesap -> hesaplama" vs "calculate -> calculation").

marcosdumay 6y ago

It's always mixed, there are some words people translate, some words they don't. A more formal setup asks for more translations, what does make things really hard. One of the hardest parts of writing my master thesis was discovering the translation of "image matching" (for 3D reconstruction). But I got away with English just fine before I had to write it down. Of course, just an year after that I was in a corporate-like environment (in the government) trying to discover the translation of "runway end turnaround area" for airports. It was still too formal to use English, but we could just settle this one by consensus.