Localization on Views part1 #1008
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#1008
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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 involves printed text in views as titles and button names
Views to change
Not entirely sure how to handle these toggle buttons as certain languages translate into longer words than their english counterparts, which makes them not fit inside.
I suppose one solution is to come up with shorter abbrevations in the language translation .json files, but I'll leave that for last.
I changed the "views.id#.title" rows in the localization .jsons (sv.json and en.json) because they were effectively "magic numbers" which is something we want to avoid, and they also caused an issue making localization of the AddCardModal.js impossible to fully localize (at least to my understanding).
They now have names reflective of what they actually are.
views.id1.title->views.TemperatureView.titleviews.id2.title->views.ParkingView.titleetc.
We might want to change their naming convention around though, so instead of
views.TemperatureView.titleit could be
views.title.TemperatureViewI'll leave that up to the leaders to decide.
@a23timgu wrote in #1008 (comment):
Yes i agree you could wait with all buttons, and make the PR without it.
@a23timgu wrote in #1008 (comment):
Add cardModal have an PR that have fixed searching for the localized title translations so that is not a part of this issue
@c24danli wrote in #1008 (comment):
I'll revert it, but I can't see why we have unclear identifiers like "id1". It doesn't say a whole lot and will result in the issue I mentioned.
I expect some more conflicts between the team 1 and team 2 branch for next merge in this area.
These are now done. I will move on to the ones in #1010
Has been merged in pr #1148