Draft: Separate Sharkey strings from Misskey (#624)
-
Review changes -
-
Download -
Patches
-
Plain diff
What does this PR do? (Please give us a brief description of what this PR does.)
separates all sharkey strings on sharkey-locales
and makes our locales
synced to misskey's. this allows us to have our own translation workflow, which helps sharkey be translated to other languages and also our locales don't get wiped by theirs whenever they update something : )
then, we merge them on build time (our translations overwrite theirs). as simple as possible
considerations:
- translations fallback in this order: Sharkey L10N -> Misskey L10N -> Sharkey English -> Misskey English. i prefer if it's in the user's native language over being in parity with sharkey.
- had to remove the sharkey-only changes that were made through prs because i'd have to manually check each one and it would be super hellish
- we probably want to setup a crowdin, have a cool workflow that copies misskey's for merging locales before merging this lol
- this is as seamless as possible as we don't have to change anything on our side if upstream adds new features
todo:
-
diff en-US and rewrite changes on sharkey-locales
-
revert locales
to upstream -
merge sharkey-locales
andlocales
on build -
setup localization platform -
update ui to show users where to contribute (placeholder link) -
update contributing.md
Contribution Guidelines By submitting this merge request, you agree to follow our Contribution Guidelines
-
I agree to follow this project's Contribution Guidelines -
I have made sure to test this pull request
Edited by piuvas silly
Merge request reports
Loading