Internationalization of the UI

Open
  • Is something wrong?
#1,470 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the EW UI entry points and reviewing Adobe’s official translation setup and Aladdin integration requirements. The issue calls for onboarding EW to manual translations, integrating Aladdin, and rendering the UI in the user’s preferred language; done means all three are supported. The issue does not name specific files or tests.

Written by the indexing model from the issue text.

Description

ew

EW UI must support translations, therefore:

  • onboarding of EW to the Adobe official translation set up, including manual translations
  • Extraction of all strings for simple translation workflows
  • using user's browser language to render EW
Dominant language
JavaScript
Stars
36
Forks
76
Avg merge
2d 19h
Merged PRs (30d)
56

Getting set up

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.

More from adobe/da-live

All issues in adobe/da-live

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.