> $ cd help/C
> $ yelp viking.xml
or maybe:
yelp file:///`pwd`/viking.xml
> The PDF version can be produced like this:
> $ cd help/C
> $ dblatex viking.xml
> $ evince viking.pdf
On my Debian box:
aptitude install dblatex
...........
"Need to get 465MB of archives. After unpacking 783MB will be used."
Hmmm, I'll pass on that for now (0.5Gb just to create a pdf I won't look at)!
> 2010/5/25 Guilhem Bonnefille :
>> Hi,
>>
>> I've just merged my 'help' branch on 'master'. The help content is
>> based on wiki UserManual page (I did my best to create a clean DocBook
>> document with all these info, but there is certainly things to fix).
>> This help is also accessible via Help->Help. :-)
>>
>> Comments and fixes are welcome. You can also add some info (manual is
>> big but there is still many details to explain).
What is the process for fixing the documentation?
via git
or
via the wiki
I think directly on the wiki, and then import into the codebase for releases.
NB I don't think Viking comes under the 'Development' category (viking.omf.in)!
Probably "Science" is best, at least that matches the Debian Gnome menu entry.
>> I still have to release a new viking version, clean the wiki, and
>> upload PDF version of the manual (easy to do).
>>
>> Now, I go and eat. :-)
Did you have anything nice ? Curry for me later...
_________________________________________________________________
http://clk.atdmt.com/UKM/go/197222280/direct/01/
We want to hear all your funny, exciting and crazy Hotmail stories. Tell us now
------------------------------------------------------------------------------
_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/
