Translations
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
- csharp
- Domain
- desktop, internationalization
Research direction
Read ROADMAP.md and the existing XAML strings, view model labels and toasts, and AccessibleNames to map the localization scope. Review the Avalonia resource options and the InvariantGlobalization and LayoutTests constraints before proposing a dated decision. Done means the decisions are recorded in ROADMAP.md and the issue has a milestone with its own checklist.
Written by the indexing model from the issue text.
Description
Prompuff in languages other than English.
Today every interface string is an English literal in the XAML (Text, Content, ToolTip.Tip) or in a view model, such as the Settings section labels and the toasts. There are no .resx files and no localizer, and AccessibleNames builds screen-reader names from that same text.
What has to be settled before this gets a milestone
- Where strings live. Resources (
.resx) with a markup extension in the XAML is the usual Avalonia route. Moving every literal is a large but mechanical change, and it can land screen by screen. - Dates and numbers. The app runs with
InvariantGlobalization, so the AppImage doesn't depend on the host's ICU version (2026-10-07), and dates use English month names. A translated interface either keeps that, bundles its own month names, or revisits the ICU decision. - Voice. Puff's lines are cute, concise and lightly playful. Translators need a short guide, and some lines may need rewriting rather than translating.
- Layout.
LayoutTestschecks the 960 × 600 minimum window in English, and longer languages have to pass it too. - Who translates. Community contributions through pull requests. The app makes no AI calls, so nothing is translated at run time.
- What's in scope. The app first. The user guide and the website are separate questions.
Done when
- The settled answers are a dated decision in ROADMAP.md, and this issue gets a milestone with its own checklist.
- Dominant language
- C#
- Stars
- 0
- Forks
- 1
- Avg merge
- 1h 21m
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hazeliscoding/prompuff
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hazeliscoding/prompuff#34 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hazeliscoding/prompuff#22 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
hazeliscoding/prompuff#14 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
hazeliscoding/prompuff#13 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hazeliscoding/prompuff#12 ·
Maintainers usually reply within 1 day
All issues in hazeliscoding/prompuff
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
AvaloniaUI/Avalonia#22568 ·
Maintainers usually reply within 2 days
-
[bug] 截图失败日志冲爆硬盘Open
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
babalae/better-genshin-impact#3846 · 2 comments ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
lugassawan/swe-workbench#823 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/fluentui-blazor#5518 ·
Maintainers usually reply within 1 day
-
devtools
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day