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.
half day
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
Basic shell scriptingUnderstanding of gettext or i18n concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests adding i18n support for non English users. The provided example (bash i18n example) can be used as a reference. Research existing i18n implementations in shell scripts, such as gettext. Look at the project's existing codebase to identify strings that need to be wrapped for translation. Consider proposing a localization framework compatible with shell.
Add i18n support · todotxt/todo.txt-cli#232 | Good First Issue
