View Revisions: Issue #5126

Summary 0005126: find ways to translate documentation and enable it
Revision 2017-09-27 17:48 by ng0
Additional Information What problem does this solve if it adds more work?

We are aiming for a global usage, this is why we need to be able to offer documentation in more than just English.

---
NOTE:

We need to do A, then B, and afterwards A and B w need to do C
to get to the point where we can work on D. Otherwise work on
D is possible but rather pointless. Nevertheless we can point
out that D needs to be done.

So what I need is something like:
in D: D depends on C.
in C: C depends on B.
in B: B depends on A.



D is in this case 'THIS' ticket, and A,B,C is everything else that needs to be done on the documentation to some extent.
Revision 2017-09-27 16:08 by ng0
Additional Information What problem does this solve if it adds more work?

We are aiming for a global usage, this is why we need to be able to offer documentation in more than just English.

---
Also keep in mind: if Mantis had a priority listing option with different sublevels, this would've been created with the lowest priority in 'documentation'. Precondition is fixing the documentation.
Revision 2017-09-27 10:49 by ng0
Additional Information What problem does this solve if it adds more work?

We are aiming for a global usage, this is why we need to be able to offer documentation in more than just English.
Revision 2017-08-24 10:02 by ng0
Additional Information What problem does this solve if it adds more work?

We are aiming for a global usage, this is why we need to be able to offer documentation in more than just English.

This could be achieved by multiple, external, translation projects.