We actually use SVN for our .Net projects via the AnkhSVN plugin for Visual Studio .Net 2008. It's better than Sourcesafe 6 but not as good as Team System 2005.
If they are using docbook, XSL stylesheets can be used to enforce formatting guidelines, and since XML is a text format, SVN would be fine for revisioning and change control. On Thu, Aug 28, 2008 at 9:53 AM, willhill <[EMAIL PROTECTED]> wrote: > Here's an interesting question a friend had about documentation. The > hospital > where I did my rotation used Microsoft Word. They were relatively "clued > up" > but I hate to give my enthusiastic friend an answer like that. > > Has anyone migrated to a wiki? Is anyone using subversion? > > On Thursday 28 August 2008, my friend wrote: > > .... > > As part of ISO-17025 requirements we have to have a clean and > > accurate documentation system. He [his bos] started off using LaTeX > > some years ago then found DocBook and hasn't looked back. > > > > On the face of it docbook sounds cool. It goes a level higher than > > TeX/LaTeX to concentrate the writer's attention almost solely upon > > content (ostensibly a goal of LaTeX but even TeX doesn't escape > > some effort in devotion to layout). > > > > If you have heard of anything like docbook or perhaps something > > even more powerful do let me know. I was wondering, for example, > > what the really clued-up quality assurance physicists use in the > > smarter/smaller medical physics institutions, since if anyone would > > know or rely upon elegant documentation systems they would, > > I'd guess. I'd imagine a fair few hackers involved in large developer > > base collaboration projects would also use tools highly fit for > > purpose. > > > > _______________________________________________ > General mailing list > [email protected] > http://mail.brlug.net/mailman/listinfo/general_brlug.net >
_______________________________________________ General mailing list [email protected] http://mail.brlug.net/mailman/listinfo/general_brlug.net
