Official translations for first distribution release #18
Labels
No labels
Security
TeX
board
done
board
ready
board
todo
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS#18
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?
For the first release of the default distribution, which translations will we officially support?
These translations will be required to be complete in all official apps.
My proposal is to start with only German.
Additionally, I propose we only enable translations by default in AlekSIS-Core (
settings.py) that are >= 75% complete in all apps.Additionally, I propose we remove all translations for now that are < 50% complete.
@all Please provide your opinions.
changed the description
What do you mean by "removing"?
man 1 rmOkay, and what is with the work that has been already done e. g. for France or Latin?
If it got us to less than 50% coverage, the work was not done thoroughly enough.
If you find someone who actually maintains the language, good (and in that case, there always is
git revert).Okay, that was the answer I wanted to hear.
Then I agree with your suggestion.
But maybe first ask the people who worked on the translations whether they want to compelte it (and get featured) for the release.
assigned to @nik
created merge request !146 to address this issue
mentioned in merge request !146
We simply disable the incomplete translations in core settings.