codecombat / codecombat/codecombat

Provide Diplomats with Glossary

Open
#2,295 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
8.6k
Forks
4.2k
Avg merge
1d 4h
Merged PRs (30d)
39

Description

CodeCombat is unlike anything you've previously translated. Prepare for some archaic phrases and out-of-this-world concepts. In order for you to work more efficiently, we're compiling a glossary of some of the more esoteric phrases and concepts. New diplomats should look up their glossary (or create it) to ensure that their contributions fit with contributions from other diplomats.

For example, a lot of the boards have humans and ogres in them. The word "human" probably has a few different translations in any given language, and the feel of things is so much better if the same word is used for this concept everywhere. In the same, but opposite way, "ogre" is quite likely to not have a translation, and the diplomat would be faced with choosing one of (possibly many) words for vile creatures.

If you start to see a lot of boards with, e.g., "The Mirewood Fells" or something, and it becomes a CodeCombat meme, you could add that so that translators could agree on how to translate it.

I suggest a top-level i18n type called "Glossary." Along with that would be a page where a diplomat would be able to see the current glossary for his language (the current i18n UI might suffice).

Finally, the glossary should be populated with board-related things like gem, ogre, hero, Sarven. The entries would have to be tagged if they're a given name for something, or a species of beast or whatever, to help diplomats.

e.g. on the page https://codecombat.com/i18n/glossary/objects (does not exist (yet))

Description English Translation
Gem (awarded by game) Gem Juvel
Hero (protagonist) Hero Helt

And perhaps on the page https://codecombat.com/i18n/glossary/places

Description English Translation
Hilderbalad (in third campaign) Hilderbalad Hildeballade
The Frozen Forest The Frozen Forest Den forfrosne skog

A cheat-sheet page where the whole glossary (all types of glossary) could be kept open in a browser tab (no-frills) so that I can "ctrl+f" my way around it, with my entire glossary would be very useful.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the current i18n UI and the proposed glossary URLs, /i18n/glossary/objects and /i18n/glossary/places. Define how glossary entries, language-specific translations, categories, and tags should be represented, then verify that diplomats can browse a complete glossary and search it with the browser.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
internationalization, localization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.