fix: clarity issue with ambiguous string SET#1169
fix: clarity issue with ambiguous string SET#1169znelson merged 4 commits intocrosspoint-reader:masterfrom
SET#1169Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Organization UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (14)
💤 Files with no reviewable changes (7)
🚧 Files skipped from review as they are similar to previous changes (4)
📜 Recent review details⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
🧰 Additional context used🧠 Learnings (3)📓 Common learnings📚 Learning: 2026-02-23T22:11:42.181ZApplied to files:
📚 Learning: 2026-02-23T06:18:08.408ZApplied to files:
🔇 Additional comments (3)
📝 WalkthroughWalkthroughDeleted translation keys Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
| STR_STATE_OFF: "OFF" | ||
| STR_SET: "Défini" | ||
| STR_NOT_SET: "Non défini" | ||
| STR_DIR_LEFT: "Gauche" |
There was a problem hiding this comment.
"Sélectionné" would be the right word but that's very long, alternatively we could use "Actif" in this context. Not a fan of either honestly. What do you think @Spigaw ?
7ecbcca to
84d0f1d
Compare
Co-authored-by: Егор Мартынов <[email protected]>
Co-authored-by: Mirus <[email protected]>
84d0f1d to
16e13f4
Compare
fix: clarity issue with ambiguous string SET (crosspoint-reader#1169)
…er#1169,crosspoint-reader#1031 feat: Auto Page Turn for Epub Reader (crosspoint-reader#1219) fix: clarity issue with ambiguous string SET (crosspoint-reader#1169) feat: slim footnotes support (crosspoint-reader#1031)
## Summary * **What is the goal of this PR?** Add missing strings and tweaks for polish language * **What changes are included?** ## Additional Context * Add any other information that might be helpful for the reviewer (e.g., performance implications, potential risks, specific areas to focus on). --- ### AI Usage While CrossPoint doesn't have restrictions on AI tools in contributing, please be transparent about their usage as it helps set the right context for reviewers. Did you use AI tools to help write this code? _**< YES | PARTIALLY | NO >**_
…t-reader#1169,crosspoint-reader#1031 +tweaks (crosspoint-reader#1227) ## Summary * **What is the goal of this PR?** Add missing strings and tweaks for polish language * **What changes are included?** ## Additional Context * Add any other information that might be helpful for the reviewer (e.g., performance implications, potential risks, specific areas to focus on). --- ### AI Usage While CrossPoint doesn't have restrictions on AI tools in contributing, please be transparent about their usage as it helps set the right context for reviewers. Did you use AI tools to help write this code? _**< YES | PARTIALLY | NO >**_
Summary
Fixes a clarity issue regarding the translation string
STR_SET. The issue lies in the fact that the english word can have different meanings.The only time the string is used is in the language selectio screen, where it has the meaning of selected. (As in The language has been set to French).
Another meaning can be configured. (As in _The KOReader username has been set). This is the meaning many of the translations have taken. The reason that the string is right above
STR_NOT_SET(which is meant as not configured).With this PR I propose to explicitly use the term "Selected". There are two good reasons for this:
Select, communicating the link between the two (the row will be markedSelectedif you press the buttpnSelect. Much clearer than now)Removed the unused strings and added translations for the new string
STR_SELECTEDfor the languages I know.tagging the translators for feedback:
fr: @Spigaw @CaptainFrito
de: @DavidOrtmann
cs: @brbla
pt: @yagofarias
it: @andreaturchet @fargolinux
ru: @madebyKir @mrtnvgr
es: @yeyeto2788 @Skrzakk @pablohc
sv: @dawiik
ca: @angeldenom
uj: @mirus-ua
be: @dexif
Additional Context
specific areas to focus on).
the Issue was introduced in #1020. Previously, if a language was selected it was marked with
[ON](STR_ON_MARKER). I considered reverting it back to that, but the solution I described above seemed superior.AI Usage
While CrossPoint doesn't have restrictions on AI tools in contributing, please be transparent about their usage as it
helps set the right context for reviewers.
Did you use AI tools to help write this code? < NO >