Fix localization concatenation + Cleanup unused strings #4239
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#4239
Loading…
Reference in a new issue
No description provided.
Delete branch "fix-localization-concat"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is a draft proposal before I go ahead to fully implement the changes.
Proposed changes:
See the commit messages for further details.
The last 2 commits are examples of the cleanup work; if this PR is wanted, then more of these commits will come.
Fixes #4202 and others.
just delete these
drop this
Ah, we can just safely delete strings. Ok, will do.
PR Checklist
Please check all that apply to this PR using "x":
PR Type
What kind of change does this PR introduce?
Fixes
Issue Number: Fixes #4202 and others + general cleanup.
What is the current behavior?
What is the new behavior?
I still leave some unused strings around as they look useful for future use (e.g. those about encrypting wallets, etc.)
@ -47,3 +48,4 @@
Skip: <Button {...skipButtonProps} button="link" label={__('Skip')} />,
}}
>
If you'd like to participate our %rewards_program% to earn credits, please complete one of the steps below
I think you should remove the LF (end of line) after word *below *, to be translatable with the string from app-strings.json file
Why not make it 'Read more.' (for consistency with other files), and remove the duplicate 'Read more ' from strings?
@ -47,3 +48,4 @@
Skip: <Button {...skipButtonProps} button="link" label={__('Skip')} />,
}}
>
If you'd like to participate our %rewards_program% to earn credits, please complete one of the steps below
Yeah, I noticed that with a few other sentences as well. I agree that it makes string-searching hard(er).
I left it as is since there were few other similar instances, so I don't know if it was intentional or not.
After all of this, I found https://github.com/lbryio/lbry-desktop/issues/3440. I guess this could be a pre-cursor to #3440, but would be obsolete when that happens.
for future reuse e.g.
OK. then make it here 'Read more.' (It's a sentence) and leave also the 'Read more' in string list.
But where did you find this? I can't find it.
token:button:%read_more%
"%read_more% or refresh the page to fix it."
Also I searched for this strings below and I can't find them anywhere.
"%duration% minute ago": "%duration% minute ago",
"%duration% seconds ago": "%duration% seconds ago",
"%duration% second ago": "%duration% second ago",
"%duration% ago": "%duration% ago",
As I said, "future, e.g.".
As for %duration%, the string ID is generated on runtime. Search for
%duration%
, or delete it on your local runtime and see it being automatically added.OK, also there are some strings like "Earn %rewards_link% for inviting your friends. Read our %referral_faq_link% to learn more." from "ui\component\inviteNew\view.js" that for some reasons are not translated. Everything seems fine in code, the text is already there in Transifex translated, but on the app interface is not translated. Maybe you can spot what could be the cause. I can't find anything wrong.
Ah, I've fixed that bug earlier this week, and Sean has merged into the next RC. There was a mistake in the
<i18nMessage>
that only translated the tokens and not the entire sentence.