legesher / legesher-docs

All documentation for the Legesher package and further portfolio
Other
10 stars 30 forks source link

Complete Keyword Table (In English) #1

Open madiedgar opened 5 years ago

madiedgar commented 5 years ago

Hello πŸ‘‹ Thank you so much for joining with us in this!

Issue #1: Complete Keyword Table (in English)

This is a very important document that will act as the backbone of the Legesher portfolio. Probably the best part is that no experience in code is necessary, for we will walk you through every step of the way!

The Guide

This keyword table guide is the main definition hub for translating the code for Legesher, and the main document you will be modifying in this issue. To begin, we need a very thorough Keyword Definition Table in English to best equip our multilingual creators to translate programming languages that were once only in English to be in their native language. SO AWESOME 😎

The Table

In the document described above, We need help in filling out the definitions and categories in where each of these keywords fall, so that for each new spoken language that is added (and programming language) the translations are 1:1.

A simple breakdown of the Python keywords, definitions, and categories can be found in the glossary

An Example

Here's an example of what a keyword would look like in the table.

Keyword Definition Languages Category Notes
FALSE Boolean logic for what is considered false python, c++, c#, javascript, julia, ocaml, ruby, rust, scala, swift,typescript truth-values

This is what the code above looks like when you're editing it in Markdown (the .md file extension). It can be useful for this issue to install a "Markdown Preview" extension on your text editor to help with the formatting.

| Keyword        | Definition     | Languages      | Category       | Notes          |
| :------------- | :------------- | :------------- | :------------- | :------------- |
|  FALSE | Boolean logic for what is considered **false** | `python`, `c++`, `c#`, `javascript`, `julia`, `ocaml`, `ruby`, `rust`, `scala`, `swift`,`typescript` |  `truth-values`  | |

The Branch

For this issue, we will be making changes on the branch called glossary-table. When we have all reached a complete list with our collaboration, we'll then merge the glossary-table branch into the master legesher-docs branch to be used for the Legesher project.

This is a huge task, so the more, the merrier! PR's will be merged if at least 10 full entries are added to the table (you can always do more than 10 πŸ˜„).

charberg commented 4 years ago

Hey @madiedgar , the link to the keyword table guide seems to lead to a 404.

I have a couple of hours to kill, so I'll take a look and try to add a few things!

madiedgar commented 4 years ago

This would be an AMAZING issue to help out with @charberg! I updated the issue description with the correct link!

I know this issue has a lot of work, but would love to add any progress you make! πŸ˜„

charberg commented 4 years ago

@madiedgar thoughts on where a word like 'char' or 'int' might fall? Unsure if it's a variable declaration, or if we want a 'data type' category perhaps?

charberg commented 4 years ago

Also I'll write a script to fill the languages column - Might be sometime next week though

charberg commented 4 years ago

Made a small PR with progress for the day. tough to think of appropriate containers for some of the words. Have a good weekend

madiedgar commented 4 years ago

I like the idea of a data type category! That would help me learn the different types of variables. πŸ‘

YES! Love the scripting - definitely will be big need here and in the individual dialect .yml files. Would love your insight and thoughts on how we can make this happen. πŸ˜„

charberg commented 4 years ago

@madiedgar Maybe if you could write up some reqs for each yml type, I could see what I can do? I can add the scripts to the repo as well if they want to be run again in the future too.

madiedgar commented 4 years ago

@charberg sounds like a great idea! I'll work on that and link the issue in here πŸ‘Œ

charberg commented 4 years ago

@madiedgar See my PR at https://github.com/legesher/legesher-docs/pull/46 - Can give a bit more of a write up/answer any questions in a bit.

mehnazyunus commented 4 years ago

Hi @madiedgar, I've made a PR to add a description for some C++ keywords. Please let me know if I should go ahead in a similar format for other C++ keywords

madiedgar commented 4 years ago

I'll check it out @mehnazyunus! Thank you so much for doing that πŸ‘

saurabh042 commented 2 years ago

Hi @madiedgar , @charberg, @mehnazyunus , @ChristinaPfaff Can I please contribute towards adding description for some of the keywords as a part of Hactoberfest 2021?

madiedgar commented 2 years ago

Absolutely @saurabh042 - that would be very helpful. I'll assign you to the issue and let me know if you have any questions!

saurabh042 commented 2 years ago

Hi @madiedgar Could you please review the PR and let me know the changes (if any) I need to make.

TomerPacific commented 2 years ago

@madiedgar, would you like more assistance with this?