refly-ai/refly

i18n Translation Cleanup, Remove Unnecessary Translation Texts

Open

#725 opened on Apr 16, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (7,331 stars) (712 forks)user submission
buggood first issue

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

Tech stack
typescript
Domain
internationalizationlocalization
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with i18n conceptsAbility to identify unused translation keysAccess to locale directory
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Start by examining the project's i18n configuration and locating the translation files (likely under a 'locales' or 'i18n' directory). Use grep or a tool like 'i18next scanner' to identify keys that are not used in the codebase. Remove these keys from all language files, being careful not to remove keys that are used conditionally. Test the application to ensure no missing translations appear. Refer to the i18n library documentation for best practices on cleanup.