refly-ai / refly-ai/refly

i18n Translation Cleanup, Remove Unnecessary Translation Texts

Open
#725 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug good first issue
Dominant language
TypeScript
Stars
7.5k
Forks
729
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
This issue involves reviewing and cleaning up the internationalization (i18n) translation files to remove redundant, unused, or obsolete translation texts. The goal is to streamline the translation files, improve maintainability, and remove any unnecessary translations that are no longer used in the project's codebase.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

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

The issue does not name translation files, keys, tests, or entry points. First identify the i18n resource files and search the codebase for translation-key usage; done means redundant or obsolete texts are removed without deleting keys still referenced by the application.

Written by the indexing model from the issue text.

Assessment

Domain
internationalization, localization
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.