Updates to translations.
A couple of things will change soon that affect translations. @all All this is now done, please update translations.
Issue #94 needs to be closed, so adding instructions on updating the gpg keys will needed.
This is now done, please update.
If nobody objects to issue #92 I will make the install guide generic, so updates against that would be needed.
Done. Please update translations based on a few corrections I've made.
I need to close issue #99. Please make any recommendations whilst I am updating this.
This is closed, please update against latest full disk encryption guide.
I need to update the dbus-free-software list, without doing too much here.
This is done. Please update against the latest from master, which will not change for a while now.
I need to close issue #73 which I will do when I have a chance to test the best way to change these documents.
This is now done, please update network-configuration and migrate-to-ascii translations.
I changed from '>' to '>>' in Devuan-without-DBus closing issue #100 .. this should help prevent accidental removal of user configurations based on our suggestion. So a small update may be prefered there.
Index pages need to be updated. Install guide is now under all releases, removed link to polish translation we don't have. Please also add a link to your translation in your language.
I will update this list if there is anything that's really important to add. But this will remain a short list.
Contributors who made small changes should feel welcome to help close this as well, with my thanks.
1 Related Merge Request
-
mentioned in merge request !27 (merged)
-
mentioned in commit 7711358c
-
'de' branch updated an merged into 'development'.
-
@Jochen could you also merge this master? I'm thinking the development branch has fallen behind, and for that reason may not be a good idea anymore
-
mentioned in issue #107 (closed)
-
I think 'es' is done.
-
@dev1fanboy There is a conflict now. I think because you edited the string 'Ascii' to 'ASCII' in master. How can I solve that conflict? I'm not so familiar with git.
-
mentioned in commit 2c513fd3
-
@Jochen the only way I can think of right now is backing up your local repo, then clone the repo and copy/paste there, push then merge again. I'm sure there must be a better way though, and I'll see if I can find a solution.
Edited by dev1fanboy -
@dev1fanboy I recreated the de branch and copied my saved files in. Now when I try to merge that into master I get the following error: "Validate branches Cannot Create: This merge request already exists: ["De Translations"]"
-
@Jochen it looks like you managed to get the merge to go through. Is everything ok there now?
-
@dev1fanboy Yes, looks ok now. Do you have some instructions how to manage translations? What is the correct workflow? The development branch is unnecessary, right? Why not edit translations directly in master? Why branch and merge every edit?
Edited by Jochen -
The master branch is protected, so the other branches are just a buffer against a bad push or accidental deletion. It turns out we don't need the development branch anymore, it's just redundancy and confusing so it should go soon.
