Hey there. I agree with some of the comments out there - a new language in Spanish does not make much sense in the pragmatic way: understanding English is a requirement for every coder out there.<p>However, most of the technical projects out there do not have to be usable by everyone or have an interesting goal. So kudos for creating a language from zero (I saw the code on Github and I am sure you learnt a lot doing this). Some people may think this is just "translating back to English and running Python", but you are the doing the whole parsing, so I think it is awesome.<p>Try to avoid the negativity that you may find in HN and be happy with this!<p>Abrazo che!
This reminds me of Latino [1] and Si [2].<p>Time to add Vainilla to the list [3].<p>[1] <a href="https://www.lenguajelatino.org/" rel="nofollow">https://www.lenguajelatino.org/</a><p>[2] <a href="https://akercheval.github.io/si/" rel="nofollow">https://akercheval.github.io/si/</a><p>[3] <a href="https://www.wikipedia.org/wiki/Non-English-based_programming_languages" rel="nofollow">https://www.wikipedia.org/wiki/Non-English-based_programming...</a>
I like it! I'm reminded of Apple's attempts at localizing AppleScript.<p>In addition to the standard English-like AppleScript syntax, Apple also developed [1] localized dialects including French and Japanese, as well as a "professional" query language syntax:<p><pre><code> English: the first character of every word whose style is bold
Japanese: スタイル＝ボ-ルドであるすべての単語の最初の文字
French: le premier caractère de tous le mots dont style est gras
Professional: { words | style == bold }.character[1]
</code></pre>
(Any transcription errors are mine.)<p>The dialects apparently shared a common internal representation so you could write a script in one language and then view/edit it in another (of course comments would still be in the original language.)<p>From an interesting retrospective by one of its designers:<p>[1] AppleScript, HOPL '07 <a href="https://dl.acm.org/doi/abs/10.1145/1238844.1238845" rel="nofollow">https://dl.acm.org/doi/abs/10.1145/1238844.1238845</a>
Office 95 (and maybe 97?) had localized versions of Visual Basic, where the keywords and VBA objects were translated into the respective local language. I’m not sure if Spanish was supported, although the following page at least lists Spanish object libraries: <a href="https://mskb.pkisolutions.com/kb/211404" rel="nofollow">https://mskb.pkisolutions.com/kb/211404</a><p>In any case, you might want to install a Spanish Office 95 version in a VM for inspiration ;). Microsoft soon dropped the localized VB versions due to interoperability considerations.
Supongo eres hablante nativo, pero la sintaxis es horrible:<p>"Para i=1 hasta 7 hacer"<p>no hace ningún sentido. En todo caso sería " Para i en (1..7)" o "Desde i=1 hasta 7" o "Para i=1 mientras i < 7; i++"<p>In any case, all these copy-paste-just-literally-translate-the-keywords languages offer nothing new.
There was a lightning talk about a Spanish Python at PyCon earlier this month: <a href="https://youtu.be/xQ0-aSmn9ZA?t=34" rel="nofollow">https://youtu.be/xQ0-aSmn9ZA?t=34</a>
Before Linux and GNU got internationalization, I worked on a French product cleverly named Ligne-X (Line X) to translate all of the display text (error messages, etc). Ironically, I don't speak French. But I didn't need to, since another team did that part.<p>That was an exasperating workload. So kudos to you on this. It looks like you put a lot into it.<p>Some people are going on about English being mandatory for programming. It isn't necessary for non-English speaking people learning programming to learn both English and Programming at the same time, so I disagree with that. Professionally, sure. But this is a learning language, and it looks nice and clean.<p>And there are a lot of people who code for fun, just for themselves, too. They don't need to learn English just to accomplish that.<p>I wonder how many people realize some Lisp implementations are localized to similar effect. Set the language, and then the keywords change to something more appropriate for those languages.
I feel programming languages for interactive fiction are the only place where non-english projects have any chance of being useful.<p>Inform7 in spanish would be neat to have for kids, for example. It's not about programming, it's more about expressing themselves through a game.
of this is cool a language specifically to help new programmers to learn programming when their primary language is spanish?<p>honestly this would a be godsend for my girlfriend. Most algol programming languages are super focused on english keywords that are very intuitive for a natibe speaker but nto so much for a Spanish speaker.<p>case in piint. "if" in spanish is "si", but "si" is also spanish for "yes"<p>as you can imagine, trying to explain with teh language barrier can get difficult
Not a native Spanish speaker, but i think they mixed up <i>sino</i> and <i>si no</i>.<p>This is a common typo and they are etymologically the same.<p>I guess by collapsing multiple words into a single token they collapse the two phrases. Eg. I look again and see <i>finsi</i> which seems strange from a Spanish grammatical sense (just like <i>endif</i> is clearly not English)
As far as I remember, in Algol 68 the physical representation of the program was separated from the syntax. So, in theory one should have been able to write<p><pre><code> hacer
...
recah</code></pre>
As a spaniard, please don't.<p>I'm fine with programming in english, this only complicate things for everyone involved. Imagine if every popular language out there had their own adaptations or even their own programming languages.<p>Also, you must know english for coding. There is no way you can be a good developer without a good english knowledge - docs, specs, protocols, guides, tools, books, remote jobs with international teams... everything is in english.