Creating Glossary

[sobolevn]

Sorry, that I have missed it earlier. But, when working together on some kind of scientific articles, it is highly important to stick to the same terms for the same objects and events.

So, what I suggest:

• [x] creating a glossary of all existing terms in elixir
• [ ] creating a dictionary of abbreviations
• [ ] refactor existing violations in the completed texts
• [ ] provide this information in the translation guidelines

[rtrv]

We could extract terms from each complete chapter one-by-one, maybe it'd be better to charge one person to do it.

Offtop: I'm thinking of some tool for convinient translation of md-based repos. First of all, to track changes of main repo and mark affected translated paragraphs some way as outdated. Second purpose could be a glossary helpers. In case we translate from English only and there is only two forms of each word (singular and multiple) it doesn't have much overhead for glossary content.

[sobolevn]

An example: https://github.com/doomspork/elixir-school/blob/master/GLOSSARY.md

@rtrv something like this? https://elixirschool.com/ru/lessons/basics/enum/

[rtrv]

We would make glossary in JSON or YAML, then generate markdown. We'd use it for some automation so.

@sobolevn partly. There are translations and the source in the same repo, but in our case we need to track work on original repository and match changed lines with our translated MD. The simple way: create issues for every original repo commit manually. Better way: create issues for every original repo commit automatically. The best way: also pull both repos and have a tool to highlight the lines to update.

[jarosluv]

Sorry, for my silence.

@sobolevn About glossary. You read my mind :) We already have a glossary, that turned out when we translate articles for Wunsh and Habr. I will try to publish it at this weekends.

@rtrv About tool for collaborative translation. I had the same idea. Please, see this repos https://github.com/wunsh/docdog-app and https://github.com/wunsh/docdog-engine. First, for public application and second for the opensource engine. I have not progressed a single step, but I have a certain vision. And this groundwork.

[jarosluv]

The first version of glossary here https://github.com/wunsh/elixir-docs-ru/wiki/Glossary