man page outdated

[skyper]

The man page is really outdated as java-5 is still mentioned as supported.

[bastiK]

@skyper: It's basically the text from the Debian package. Any help with the updates is welcome.

[bastiK]

josm man page (old)

[skyper]

Replying to bastiK:

@skyper: It's basically the text from the Debian package. Any help with the updates is welcome.

I have created ManualPage and added the attachment. Please recheck licence. Try to update when finding some time.

[skyper]

It seems to me that there is already a script processing Help/CommandLineOptions to include the command line help within the jar file. Maybe something similar can be done for the man page ?

[dpaleino]

I'll update the manpage as soon as I get some spare time :)

Once done, I'll consequently update the Debian package, and attach it to this bugreport. Assigning the bug to me :)

Kindly,
David

[skyper]

@dpaleino:
Is it easier to maintain the man page in debian or better within the JOSM wiki ? E.g. the wiki will probably invite more users to edit. How does translation of man pages work ?

[dpaleino]

The wiki is a great idea, but... is there a way to automate a process such that, from the wiki, a manpage is automatically generated and committed to svn?
Also, since nroff is not a "common" language, I guess that -- being hosted in a wiki -- the manpage would end up full of errors (both stylistic and semantic). We can try though :)

Translation for manpages involves putting localized manpages into /usr/share/man/<lang>/man1 (for example, for section 1). These are usually "manually" translated, i.e. with no po-files or such.

The only way I'm aware of to use po-files is using ​po4a. Can't tell how well that integrates with ant, though.

[dpaleino]

I've updated the manpage in the wiki, and ​committed it to the Debian git repository.

Will be available in the official repositories with the next package upload.

Kindly,
David

[skyper]

Replying to dpaleino:

The wiki is a great idea, but... is there a way to automate a process such that, from the wiki, a manpage is automatically generated and committed to svn?

There we need the help of stoecker.

Also, since nroff is not a "common" language, I guess that -- being hosted in a wiki -- the manpage would end up full of errors (both stylistic and semantic). We can try though :)

Just using one page is probably too minimalistic. Maybe, we could use some system like StartupPage, e.g. one page for the source and one page where the output is shown (compiled pdf). We could have two pages for each language and use the wiki translation system. Maybe a small control system could help find errors but if the source if processed live to get the second page, errors should get visible right away.

Translation for manpages involves putting localized manpages into /usr/share/man/<lang>/man1 (for example, for section 1). These are usually "manually" translated, i.e. with no po-files or such.

Manual translation would work perfectly within the wiki.