this post was submitted on 04 Nov 2023
308 points (95.0% liked)

Programmer Humor

32054 readers
1520 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
top 50 comments
sorted by: hot top controversial new old
[–] Dirk@lemmy.ml 76 points 10 months ago (1 children)

grep --groß--und-kleinschreibung-der-buchstaben-ignorieren

[–] yetAnotherUser@feddit.de 41 points 10 months ago (2 children)

grep --Groß--und-Kleinschreibung-der-Buchstaben-ignorieren

[–] hinterlufer@lemmy.world 21 points 10 months ago (1 children)
[–] nickwitha_k@lemmy.sdf.org 8 points 10 months ago

MacOS, is that you?

[–] BlushedPotatoPlayers@sopuli.xyz 9 points 10 months ago (1 children)

But you just told the computer to ignore case...

load more comments (1 replies)
[–] nobloat@lemmy.ml 69 points 10 months ago* (last edited 10 months ago) (9 children)

I hope this is a joke because the Arabic translation is so wrong. It's also confusing because Arabic is written from right to left so it'll just create a mess. The translators are using "letter case" and translated it literally to Arabic. The word used doesn't mean "letter" as in a letter in the alphabet but "letter" as in what you send in the post office. These are totally different words in Arabic.

[–] Railcar8095@lemm.ee 33 points 10 months ago (1 children)

Spanish is also wrong, this one means "ignore-letter-size". I'm not sure if there is an official correct way to say in a short manner, I would say "ignorar-capitalizacion" but I think it's just a barbarism.

Ber ber ber ber ber ber ber ber

[–] Rom@hexbear.net 11 points 10 months ago

Also why did they use Arabic script for the Arabic but not hiragana/kanji for the Japanese?

load more comments (7 replies)
[–] clearleaf@lemmy.world 62 points 10 months ago (2 children)
[–] FooBarrington@lemmy.world 57 points 10 months ago* (last edited 10 months ago) (2 children)

tar --extrahieren --volle-ausgabe --gezippt --folgende-datei

[–] geizeskrank@feddit.de 33 points 10 months ago (1 children)

tar --auspacken --volle-ausgabe --reissverschlussverschlossen --folgende-datei

[–] 7heo@lemmy.ml 11 points 10 months ago* (last edited 10 months ago) (1 children)

I mean, in the spirit of true internalization, it should really be

teer --auspacken --volle-ausgabe --reissverschlussverschlossen --folgende-datei datei.teer.gz

load more comments (1 replies)
[–] nxdefiant@startrek.website 23 points 10 months ago (2 children)

you have concisely convinced me how terrible an idea this is.

load more comments (2 replies)
[–] LudwigvanBeethoven@sh.itjust.works 50 points 10 months ago (2 children)

Hungary presents: grep --kis--és-nagybetűk-figyelmen-kívül-hagyása

Yeah that is a resounding no. PS: I am not exaggerating. That is the first translation that came into mind

load more comments (2 replies)
[–] hackris@lemmy.ml 46 points 10 months ago (5 children)

This looks like the final layer of hell. Your coworker writes their scripts in another language and now you have to decipher what the hell they mean. Who has a problem woth English for development tools, etc.? It's really not a monumental task to learn it, and I'm not even a native speaker.

[–] Knusper@feddit.de 20 points 10 months ago (2 children)

May I introduce you to the concept of Microsoft Excel?

One time, someone from HR asked me, if I could help them with an Excel formula. So, I quickly looked up how to do something like that in Excel, adapted it as needed on my laptop, then sent it to them. And well, it didn't work on their system, because I coded it in English, whereas their OS was in German.

[–] hackris@lemmy.ml 6 points 10 months ago (2 children)

Yep, this sort of behaviour translates to Windows paths also. Why would they name a directory "C:\Users\Example\Desktop", when they can replace "Desktop" with a locale-specific name, which is not just a link to "Desktop", but a completely different directory which breaks any scripts expecting "Desktop".

We know MS well, their choice is clear :)

load more comments (2 replies)
load more comments (1 replies)
[–] ToxicWaste@lemm.ee 15 points 10 months ago (1 children)

Even if everyone is using English, there will be cultural differences. I used to work at a company which had a lot of indian externals working on their code base. Whenever I had to work on a mainly Indian developed project i had to get used to how they wrote things. Usually things where named a bit different. Not by much, but enough tho throw me off a couple of times before i got used to it.

IMPORTANT: I am not shitting on how they used English, merely pointing out that they used it differently from how i would have expected.

[–] hackris@lemmy.ml 7 points 10 months ago (1 children)

In this case they were still using English, with minor differences. Imagine one of the Indian externals writing an internal script that utilizes the Indian localisation. You'd have to whip out a translator or dive into the docs for a tool which you may have already used countless times and know how it works when instead, they could have simply learned the English arguments for the tool.

Nothing against people not being native speakers of English, I'm not one either. I just think that this creates more problems than it solves.

load more comments (1 replies)
[–] darkpanda@lemmy.ca 11 points 10 months ago (3 children)

To be fair, sometimes I look at my own code and think it was done in another language, and I only know English.

load more comments (3 replies)
[–] HiddenLayer5@lemmy.ml 9 points 10 months ago* (last edited 10 months ago) (4 children)

Wouldn't it be easy to convert the code to any language if this was the case though? Any human-language programming is already an abstraction, so why can't a programming language be abstracted to more than one human language? Literally just swap the command words out for words in the other language, seems like something modern IDEs can trivially do if a language like that existed.

Also, non-English speaking countries exist. Some have actually developed programming languages in their own language so the idea of non-English programming isn't exactly unheard of. There is no reason that code that won't be edited by English speakers should always be written in English, it's not like it's the one perfect human language for interfacing with computers or anything. So I suspect that should this become a reality, you wouldn't even notice anything's changed unless you live in a non-English speaking country. Either way your company can still always just require code to be in English, the same way companies have requirements for formatting and software design philosophies.

load more comments (4 replies)
load more comments (1 replies)
[–] Spore@lemmy.ml 40 points 10 months ago* (last edited 10 months ago) (2 children)

This reminds me of a similar experience.

The first release of WSL(2) 1.0 (this versioning alone is worth another post here, but let's not talk about it) have its CLI --help message machine translated in some languages.
That's already evil enough, but the real problem is that they've blindly fed the whole message into the translator, so every line and word is translated, including the command's flag names.

So if you're Chinese, Japanese or French, you will have to guess what's the corresponding flag names in English in order to get anything working.
And as I've said it's machine translated so every word is. darn. inaccurate. How am I supposed to know that "--分布" is actually "--distribution"? It's "发行版" in Chinese and "ディストリビューション" in Japanese.

At last I had to switch my system language to English to set a WSL instance up. From then on I never use any display language other than English for Microsoft products. Sometimes "translated" is worse than raw text in its original language.

Related links if you like to see people suffer:
https://github.com/microsoft/WSL/issues/7868
https://github.com/microsoft/WSL/issues/4111

PS: for the original post, my stance is "please don't make your software interface different for different languages". It's the exact opposite of the author has claimed: it breaks the already formed connection by making people's commands different.
It's the CLI equivalence of scrambling every button to make sure they are placed differently in different languages in GUI. I hope this sounds stupid enough so that no one will try it.
A not-so-stupid way that I can think of is to add a "translation" subcommand to the app that given any supported flags in any language it converts them to the user's language. Which is still not so useful and is not any better than a properly translated documentation, anyway.

[–] hstde@feddit.de 34 points 10 months ago (5 children)

Try using Excel in another language than English. You have to hope someone, that speaks your language had exactly the same problem as you, because all the formulas get translated and Excel doesn't recognize the English version when your language isn't set to English.

[–] isVeryLoud@lemmy.ca 13 points 10 months ago

Oh god the fucking Excel formulas.

I live in Quebec, and all the excels are in French.

[–] barubary@infosec.exchange 11 points 10 months ago

@hstde @Spore Even better, the alphabetical index of function names was generated in English first and then translated, meaning the documentation looks like a scrambled mess in any other language because it is alphabetized according to what the English equivalent would be. #excel

[–] Nahdahar@lemmy.world 7 points 10 months ago

I've learned excel in middle and high school in my native language, I absolutely fucking hate the translations... excel-translator.de coming in clutch.

[–] hinterlufer@lemmy.world 6 points 10 months ago (1 children)

Just wait until you're working with different time/date formats, like, god forbid, sharing such documents to someone who has their Windows time/date format set differently than you have.

load more comments (1 replies)
load more comments (1 replies)
load more comments (1 replies)
[–] MonkderZweite@feddit.ch 25 points 10 months ago* (last edited 10 months ago) (2 children)

The future of the past issues MS had with this shit? Oh, right, programmerhumor.

load more comments (2 replies)
[–] centopus@kbin.social 21 points 10 months ago (1 children)

o.O And I thought translated errors without error codes were the worst cancer in IT world, now you created an IT covid.

[–] agressivelyPassive@feddit.de 13 points 10 months ago

I have to use a German API with weird halftranslations and ultra long names, due to bad model generation. Something like getPersonAntragsPersonAdressDetailEintragList().

Unfortunately, it makes sense, since many of the terms have a very precise legal meaning and can't be unambiguously translated.

[–] emma@programming.dev 20 points 10 months ago (1 children)

I don't get it. Is the joke that i18n for CLIs is unimportant? Or is this an earnest post that just so happened to get posted under humor? I wish I had the source for the image.

[–] sebastiancarlos@lemmy.sdf.org 30 points 10 months ago (3 children)

The joke is that it's hard to tell if this is a joke because the lines between good intentions, corporate jargon, and feasibility have been blurred beyond recognition both here and in the real world.

It's also funny that after all these years, i18n is still a mess. Moreover, even if translations are standard in GUIs and documentation, for some reason, everyone is okay with defaulting to English for the oldest form of computer interaction.

Also, the joke is whatever you want it to be. Follow your dreams.

[–] huf@hexbear.net 22 points 10 months ago

that's because as a non-english native, it's WAY easier to have the whole computer in english. obscuring options and error messages (by translating them) makes it much harder to fix problems.

load more comments (2 replies)
[–] denast@lemm.ee 19 points 10 months ago

Ah yes can't wait to switch keyboard layout mid-command every time, so nice!

[–] Spectacle8011@lemmy.comfysnug.space 17 points 10 months ago (4 children)

Interesting choice to romanize Japanese. Now you have to figure out which romanization system to use (I was surprised を was romanized as o and not wo). But I do get it, I guess, because you have to wonder it would only use Hiragana or mix Kanji in:

  • 大文字と小文字を無視する
  • だいもんじとこもじをむしする

Well, for the sake of being international, we should just use Katakana everywhere. That's the sanest suggestion (who's with me?):

  • ダイモンジトコモジヲムシスル

Of course, you're kind of screwed on a TTY, since they don't generally render unicode...so let's go back to figuring out which romanization system to use.

load more comments (4 replies)
[–] Malgas@beehaw.org 14 points 10 months ago (1 children)

Why is the third one not:

--大文字-と-小文字-を-無視する

?

[–] lukini@beehaw.org 10 points 10 months ago

Because they didn't think it out fully lol

There shouldn't even be dashes imo since they replace spaces and Japanese doesn't use spaces.

[–] Templa@beehaw.org 13 points 10 months ago (1 children)

This might be an old April first joke because I couldn't find anything about it lol

[–] Taringano@lemm.ee 11 points 10 months ago (1 children)

Really ducking hope so. I hate translated software to my native language.

My blood boiled there. Like excel that has functions in all languages. Completely insane.

[–] catacomb@beehaw.org 6 points 10 months ago

Yeah, this is one of those things which sounds great on paper but also introduces problems. I've seen people get really annoyed when exception messages are translated because it makes them harder to search for online. That would need to be solved too.

I've had huge issues collaborating on a spreadsheet with a Spanish client. It tries to open the sheet in your locale and then can't find the functions. Insane that Microsoft didn't even add some metadata to allow me to work on it in Spanish.

[–] ultratiem@lemmy.ca 6 points 10 months ago* (last edited 10 months ago) (1 children)

Or… maybe it’s language that is wrong

[–] nxdefiant@startrek.website 19 points 10 months ago (3 children)

we should all standardize on Esperanto. Not because it is good, but because regardless of which language you know, Esperanto is the last choice, and thus the only equal choice.

load more comments (3 replies)
load more comments
view more: next ›