Re: [TSVN] TortoiseSVN FAQ

Lübbe Onken wrote:
>> - What about our docs? Is there a way to include them in drupal?
>> (I've seen some discussion about a docbook-import-plugin, but
>> nothing has come out of it yet).
> For the time being, there's no out of the box solution. The quickest
> way would be to store the docs outside drupal.

Do we gain anything by including them in drupal anyway?

>> If not, is there a way to insert the sourceforge
>> logo into every generated html page?
> That's easy. I'd only need to create a site specific css that
> overrides some standards.

I think we should store the docs a little differently:

Ship CHM with the product only, no separate download.
Re-site HTML to SourceForge as an online reference.
Drop PDF altogether. SVN needs multi-platform readability, but we don't.

The online version should still be generated from the latest release
tag, not HEAD. Otherwise we are documenting features which only exist in
the nightly and that will generate more 'why doesn't this work like the
manual says' queries. The nightly has its own CHM anyway.

If we want the HEAD docs generally available, then I think it should be
as well as the released version.

>> Otherwise we can't upload the
>> docs there and Simon will protest every time we update the docs on
>> tigris.org and he's updating his CVS working copy...
> You haven't heard me sighing when I do the same. ;-)

I'm working up a good crescendo for next time ;-)

Simon

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org