The first? Algol 68 allowed implementations to have language-specific versions of keywords. I remember seeing a French language Algol 68 book in the stacks at the OU library that had listings with French keywords. I don't remember what they did with the portmanteau words that Algol 68 (and much more so in the Revised Report) favored, like "ouse" and "elif".
Citrine: Localized Programming Language
21–30 of 72 posts
Re: Citrine: Localized Programming Language
#22I think a localized programming language like this could be useful as a stepping stone while teaching gifted kids, for instance (before moving on to a “real” programming language like Python or Java).
Re: Citrine: Localized Programming Language
#23The grammar of localized programming language should be specifically designed.
Only replacing the keywords and operators seems strange in some sense.
Besides, the example in my first language is unreadable.
Re: Citrine: Localized Programming Language
#24Weird how a language that exists to be more welcoming and accessible uses needlessly gendered language on its website.
"Designed to allow every man to write code in his mother tongue" could easily be written as "designed to allow every person write code in the language they are most comfortable with."
Re: Citrine: Localized Programming Language
#25The Chinese version looks like just bad machine translation.
`Object` is translated to `宾语` which means the grammar component object in subject, verb, object, etc.
The `power` operator is translated to `功率` which means A measure of the effectiveness that a force producing a physical effect has over time.
`Ceil` is translated to `细胞` which means Cell ???
:-(
Re: Citrine: Localized Programming Language
#26The Chinese version looks like just bad machine translation. `Object` is translated to `宾语` which means the grammar component object in subject, verb, object, etc . The `power` operator is translated to `功率` which means A measure of the effectiveness that a force producing a physical effect has over time. `Ceil` is translated to `细胞` which means Cell ??? :-(
> `Object` is translated to `宾语` which means the grammar component object in subject, verb, object, etc.
Sounds right (though OOP treats objects artificially as grammatical subjects, they are the things on which functions operate, and thus more like what would normally be grammatical objects; they are the patients rather than the agents of actions.)
Re: Citrine: Localized Programming Language
#27> designed to allow every man to write code in his mother tongue. Hopefully, by doing so, Citrine will make coding accessible to a wider audience. One day that audience might extend to women.
My thoughts exactly! but it looks like op is Dutch in which language google translation tells me "mens" can mean "person", so hopefully it is just an esl thing
Well, no, 'mens' translates to 'human' and wouldn't normally be used in this sentence (it'd put unnecessary emphasis on the species of who would be programming, which just feels weird).
I can't think of a Dutch version of the same sentence that wouldn't make the subject explicitly male (well, there are some archaic versions that would use 'alleman' but I can't think of one that wouldn't sound weird).
Re: Citrine: Localized Programming Language
#28I'd love to have this sort of i18n for Python or JavaScript, and a good kid-friendly environment. Scratch does i18n well. Text-based programming doesn't. There's a gap in age between programming and English fluency.
What's odd to me is the page is internationalized. Their explanation: "As a developer, you have to know some English. Nobody is going to change that anytime soon."
Re: Citrine: Localized Programming Language
#29If curious see also
Re: Citrine: Localized Programming Language
#30Is anyone aware of tooling or languages in existence that allow for maintaining codebases with multiple supported languages? I'm imagining something similar to a git hook that performs translation at an AST level, where library can provide a "strings database" that maps it's public members into arbitrarily many languages. I could imagine for multinational companies, it might even be worth hiring dedicated translators to maintain manual translations as part of such a system, although it would definitely be desireable for it to fall back to machine translation.
That way, anyone could check out a version of the code that's localized to their native language, including language primitives, standard library calls, variable names, comments, etc. without fracturing the whole library ecosystem by language boundaries.