wpilibsuite/vscode-wpilib

Full i18n Support

Open

#81 opened on Sep 17, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)TypeScript (121 stars) (63 forks)auto 404
help wanted

Description

FRC is international, so it would be a nice touch if the tools could be easily translated, whether officially or by the community.

  • It's easier to build the support now. Even if the UI is all English right now, it's easier to do this now rather than finding all the UI strings later.
  • The process for translating and contributing translations can be defined at a later time
  • Anything exposed to the user should be supported (in rough descending priority)
    • UI elements and messages
    • Webviews
    • Extension Marketplace metadata
  • No need to internationalize logging
  • Fallback to English if no translation exists

See also: #68

Contributor guide

Tech stack
typescript
Domain
developer experience
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.
1-2 days
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.
clear
Prerequisites
GitTypeScriptVSCode extension development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Research VSCode i18n support (e.g., vscode nls or localize API), identify all UI strings in the extension, and set up a localization structure with English as default.