SumianVoice/backroomtest
1
14
Fork
You've already forked backroomtest
1

Make game translation-ready and trandlate to German #25

Closed
Wuzzy wants to merge 3 commits from Wuzzy/backroomtest:translate into master
pull from: Wuzzy/backroomtest:translate
merge into: SumianVoice:master
SumianVoice:master
SumianVoice:a23_major
SumianVoice:test
First-time contributor
Copy link

I've made some string changes to make them translation-ready, then I added a German translation.

One noteworthy string change include the step time. I assumed the unit is in seconds, right?

I only translated things that are player-facing (everything a normal player can access in-game), so debug-only stuff and node names remain untranslated.

I've made some string changes to make them translation-ready, then I added a German translation. One noteworthy string change include the step time. I assumed the unit is in seconds, right? I only translated things that are player-facing (everything a normal player can access in-game), so debug-only stuff and node names remain untranslated.

I'm in a bit of a difficult situation with contributions, since currently (and I should have made this more of a clear statement in the readme from the outset) it's somewhat of a personal project, and I currently have full autonomy and rights over it. If I wanted to make all my code 0-BSD tomorrow, I wouldn't have to ask anyone permission or have any dramas, and I don't need to credit anyone (except the modules like playerphysics, but those are self contained and have their own explicit licenses so it's not an issue). On the other hand if I allow contributions to be offered under 0-BSD so there's no license requirements or asking for permission, people might still dislike if those are not credited, and start drama regardless. That's even the case for a CLA or even transfer of copyright, both of which don't actually prevent those issues.

I think the only real option I have is to allow no contributions that modify already-licensed-by-me files.

I'm hyperaware of the dramas that happen as a result of license or credit issues and how devastating they can be (minetest has no shortage of these), so I'd like to keep this project very very clean; that means what is under my licenses is all my own work, and I maintain full rights over it, and submodules are their own self contained thing. Adding submodules is fine, since they don't add any confusion about credit because they have their own explicit licenses.

As for the translations specifically, it's probably a bit too early since a lot of the game might change (e.g. the flashlight doesn't have a how-to yet). I'll be making things more translatable as I go, but it's low priority.

What I suggest doing is this:

  • wait until translation support is added (or add issue for it and list needed changes) for whatever feature you want to translate
  • rather than modify already licensed files, add translations only in /locale/
  • declare those translations as attribution / MIT or PD equivalent in comments or in a LICENSE file that lists the files added by you

I'm still learning / avoiding learning how translation works so I hope that's possible to do 😅

Summary is:

  • I want to maintain a clean licensing situation, where everything licensed by me I completely own the rights and credit to
  • therefore I can't allow contributions that modify already licensed files
  • submodules that have their own licenses are fine as they are explicit, and can even be completely removed from the project if dramas happen
  • so if translations are added, they need to have their own license and not modify existing licensed code in any way

I also need to shift my focus to making the systems and content, to make it more viable as a game (shouldn't be "game-like", just playable and give some tiny amount of direction). Once I get that going, I'll shift back to polishing and cleaning up.

I'm in a bit of a difficult situation with contributions, since currently (and I should have made this more of a clear statement in the readme from the outset) it's somewhat of a personal project, and I currently have full autonomy and rights over it. If I wanted to make all my code 0-BSD tomorrow, I wouldn't have to ask anyone permission or have any dramas, and I don't need to credit anyone (except the modules like playerphysics, but those are self contained and have their own explicit licenses so it's not an issue). On the other hand if I allow contributions to be offered under 0-BSD so there's no license requirements or asking for permission, people might still dislike if those are not credited, and start drama regardless. That's even the case for a CLA or even transfer of copyright, both of which don't actually prevent those issues. I think the only real option I have is to allow no contributions that modify already-licensed-by-me files. I'm hyperaware of the dramas that happen as a result of license or credit issues and how devastating they can be (minetest has no shortage of these), so I'd like to keep this project very very clean; that means what is under my licenses is all my own work, and I maintain full rights over it, and submodules are their own self contained thing. Adding submodules is fine, since they don't add any confusion about credit because they have their own explicit licenses. As for the translations specifically, it's probably a bit too early since a lot of the game might change (e.g. the flashlight doesn't have a how-to yet). I'll be making things more translatable as I go, but it's low priority. What I suggest doing is this: - wait until translation support is added (or add issue for it and list needed changes) for whatever feature you want to translate - rather than modify already licensed files, add translations only in /locale/ - declare those translations as attribution / MIT or PD equivalent in comments or in a LICENSE file that lists the files added by you I'm still learning / avoiding learning how translation works so I hope that's possible to do 😅 Summary is: - I want to maintain a clean licensing situation, where everything licensed by me I completely own the rights and credit to - therefore I can't allow contributions that modify already licensed files - submodules that have their own licenses are fine as they are explicit, and can even be completely removed from the project if dramas happen - so if translations are added, they need to have their own license and not modify existing licensed code in any way I also need to shift my focus to making the systems and content, to make it more viable as a game (shouldn't be "game-like", just playable and give some tiny amount of direction). Once I get that going, I'll shift back to polishing and cleaning up.
Author
First-time contributor
Copy link

OK, then I just back out then. Btw, you can disable pull requests in your repo.

OK, then I just back out then. Btw, you can disable pull requests in your repo.
Wuzzy closed this pull request 2023年01月17日 18:29:06 +01:00
Author
First-time contributor
Copy link

That having said, I hereby declare all this PR code to be under CC0, to keep things simple. So if you want to salvage the code later, feel free to. But if you want this to be a you-only project, OK. I did not plan to post more PRs anyway.

That having said, I hereby declare all this PR code to be under CC0, to keep things simple. So if you want to salvage the code later, feel free to. But if you want this to be a you-only project, OK. I did not plan to post more PRs anyway.

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
SumianVoice/backroomtest!25
Reference in a new issue
SumianVoice/backroomtest
No description provided.
Delete branch "Wuzzy/backroomtest:translate"

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?