2 comments (2 comments)0 reactions (0 reactions)0 assignees (0 assignees)Swift8,522 stars (8,522 stars)199 forks (199 forks)batch import
enhancementgood first issuehelp wanted
Description
This issue does not include a description.
Contributor guide
- Tech stack
- swift
- Domain
- localizationdesktop
- 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.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- SwiftXcode project knowledgemacOS app development
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 60
- Research direction
- Investigate how strings are currently handled in the Secretive app. The app likely uses NSLocalizedString for user facing text. Create a default English .strings file and possibly a .stringsdict for plurals. Look at the project structure to determine where to place localization files. Check the two existing comments for any hints about progress or desired languages. Start by extracting all hardcoded strings from the codebase and replacing them with NSLocalizedString calls. Then add localization support (e.g., Japanese) by creating a localization folder and adding translated strings.