-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Sorry] Update screenshots, Software Manual, Setup page #465
Conversation
First draft of "User Manual" based on existing Software Manual
Blank initial draft
Add clears
Add TOC styling
Add TOC
Oops Server Manual isn't read yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
two letters missing ...
Please Merge in changes, |
If you want to push this to the translate branch to get it in before the next release it's ok by me. |
To the "changes" branch ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's ok for me. Ready to be merged.
No, to 'translate'. If it goes into 'changes' I presume it won't get translated or go live until the release after this one, or at least some time after this release. What I meant was that it's ok by me if it goes into the current 'translate' branch so it can all go live for this release, but it doesn't only depend on me - the other translators would have to weigh in as it kind of "breaks" the translation protocol. |
We've merged them to changes in the hope that a remedial translation can be merged to translate from there. @jujudusud says he can undertake the work... |
Ok, so if I want to update the ES translation I have to do it on changes then? |
To quote @jujudusud: "to translate we just have to go to changes branch, copy past the en file locally (or just read it in raw mode in GH interface) and translate on translate3_8_0 branch." We're talking about 3 files BTW. |
The modifications in english are made to "changes" branch. So, you have to refer to a file in english using something like this place to have the latest english file : https://github.com/jamulussoftware/jamuluswebsite/blob/changes/wiki/en/en-Software-Manual.md the files to be retranslated are :
after translating, open a new PR and merge in translate3_8_0 branch Is it ok for you @ignotus666 ? |
Done. |
Does this need translation?
Changes
Re-arranges Software Manual to cover new features as of 3.8.0 and removing some screenshots to lower maintenance overhead in future. Minor changes to text for style, added TOC.
Angst
I realise of course that I should have done this BEFORE we created the translation branch. Not sure what to do ...