uqbar-project/wollok-language

Deal with internationalization and localization

Open

#28 opened on Nov 9, 2019

View on GitHub
 (2 comments) (0 reactions) (2 assignees)Wollok (14 forks)auto 404
help wantedquestion

Repository metrics

Stars
 (8 stars)
PR merge metrics
 (PR metrics pending)

Description

Extracted from discussion on #26 .

We should think how to deal with translations and localization in this project to reuse as much as possible.

Besides the general discussion of where and how we should store translations and similar stuff, there are some concrete issues to discuss:

  • The method Object.generateDoesNotUnderstandMessage(target, messageName, parametersSize) is currently implemented as native. This is, as I understand, mainly because it relies on localization (please, correct me if I'm wrong), but it would be nice to have it shared.
  • Date toStrings depend on localization which is not tested anywhere. I believe it would be good to avoid this dependency or model the localization in the language somehow, otherwise we are coupled with the fact the code runs on an IDE that knows the system language.
  • The text of exceptions could be shared by all implementations if we move it here.

Contributor guide

Research direction
Investigate existing internationalization approaches in programming languages and propose a strategy for Wollok, considering code sharing across implementations.
Tech stack
None
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Internationalization conceptsWollok language basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40