Add glossary

[maddhruv]

Contains:

• Generally used NF terms
• Node core terms
• General Programming/JS terms

These are some of the terms I found, feel free to modify.

NOTE: Syntax of JSON file as per the crowdin-glossary .fromFile() function

Resolves #81

[maddhruv]

added do-not-merge
wait until we build a sufficient glossary covering almost all possible terms.
have to read the whole docs again, I guess 😝

[maddhruv]

@zeke
Please have a look at it

[ryo-a]

I think callbacks also can be translated.

[laosb]

Actually I'm thinking words and phrases like "Foundation", "Board of Directors", full expressions of committee names should be translated for better understanding.

[maddhruv]

Actually I'm thinking words and phrases like "Foundation", "Board of Directors", full expressions of committee names should be translated for better understanding.
@laosb actually these words have a meaningful translation to the respective languages which would somehow change the real meaning for them

e.g: Node.js Foundation in Hindi would be node.js नींव -> node.js foundation | node.js groundwork | node.js base

that we shall not expect here I guess

[laosb]

Actually listing all those terms in a “don’t-translate” list would cause the sentence being too noisy and uneasy for non-native speakers. It might looks fine for those who could understand English words, but a disaster for those who don’t understand. Long unpronounceable and nonsense English phrases make a reader quickly sleepy, and extra explanations would be needed for those phrases, which can be self-explaining if they are properly translated.

[zeke]

e.g: Node.js Foundation in Hindi would be node.js नींव -> node.js foundation | node.js groundwork | node.js base

Great point. But instead of just adding "do not translate" in the glossary, we should say something like "The Node.js Foundation is the institution that manages the Node.js project". This will give translators the context they need to translate the word using the appropriate sense.

[RichardLitt]

Wait until we build a sufficient glossary covering almost all possible terms.

I think we should probably merge this is and use it, as opposed to the current long-open PR. Then, we can iterate. So - mind if we remove do-not-merge and merge this?

[maddhruv]

Thanks @RichardLitt for the update, +1 from my end

[nodejs-crowdin-zz]

Looks like this has been updated to include only Node.js-specific terminology. Let's ship it!

[zeke]

(Posting as my real self @zeke this time).

Looks like this has been updated to include only Node.js-specific terminology. Let's ship it!