Manual & Icons

[sjek]

just writing it clean what time and head allows .p

there's original etherpad and zoho has revision control but no long time storage or paywalled. otherwise like more of that when its looking written. maybe some paragraph suggestions.. don't know actually.

[psi29a]

Again, this is why we use git...

For example, a comparison between OpenMW master branch and someone's contribution:
https://github.com/OpenMW/openmw/compar ... ManualEdit

If you want to contribute, learn latex:
https://en.wikipedia.org/wiki/LaTeX

and contribute here:
https://github.com/OpenMW/openmw/tree/m ... ual/opencs

[Cramal]

I know latex and i'm willing to help but i've never written any manual neither used the openCS more that for really minor thing.

How can i help?

[psi29a]

Sure! For people wanting to work on it, they should first try to compile the tex files into one pdf (manual) and then read through it. This will serve two purposes:
1) Spell/grammar check for existing content.
2) Give you an overview of what OpenMW-CS can do, at least up to the point the document was updated.

From there, you can correct mistakes, change in functionality and add additional information on new functionality.

[sjek]

many writer's advice:

kill your darling

[Cramal]

I have clone the repository and i will look at it tonight (japan time).
First i will stay on language and latex code correction, later i will go deeper into informative stuff

Be ready for my first commit to openMW...

[Tolchock]

Note: I already did some work rewriting parts of the manual, but my changes have not been merged: https://github.com/Bodillium/openmw/commits/ManualEdit

(so you don't have to spend time doubling up!)

Many apologies for not getting around to finishing -- but my computer died, and then life intervened. In any case, I think I have been sufficiently spurred into fixing up these sections before the end of Friday (AU time).

[psi29a]

Do a pull request and see if you get comments!

[Cramal]

it looks like you mostly worked on "files and directory" .tex file.

If it too difficult to merge with my change, you can overwrite them (or by the way who decide which commit are accepted in master branch?)

[Cramal]

Do you think puting a step by step tutorial for some really basic add-on at the end of the manual could be a good idea?

I was thinking about somthing with screenshot, precise description of the action to be done for example add-ons like :

- modification of an object (like weight/price or something like that)
- modification of a pnj (like change what service it can offer)
- basic scripting (like launch a spell when an object is picked up)
- basic dialogue change (like add a topic to a pnj with specific text)