Slashdot Mirror


Open Source Document Management and Revision Control?

Ramon M. Felciano asks: "I'm trying to scrape together our development intranet and want to be able to post specs, change reports, etc. that could be in Word, HTML, PDF, etc. Are there any intranet "shells" out there that include at least rudimentary document management facilities (like the ability to post files to a directory structure, receive notifications of new postings, and allow single-click-to-open-inline functionality, rather than download and then open). I've played with the idea of converting everything to PDF but there doesn't seem to be a way to automate this from the source format. Also, integration with CVS for version controlling these docs would be a nice bonus I checked Freshmeat but didn't see any good matches. The closest was Phorum and the other thread / discussion servers, but we don't really need discussion support. Any suggestions? "

2 of 15 comments (clear)

  1. Re:ideas and suggestions by Matts · · Score: 2

    MS Office's XML output is mostly just HTML with CSS. This allows it to be displayed in a normal browser. Then layered on top of that in different XML namespaces are further structuring information that allows you to read it back into Word without losing any information - kind of like an RTF for XML. Things like structured graphics actually go into the file using MS vml tags.

    So converting to HTML would just be a matter of exporting just the HTML namespace bits. Dead easy with perl's XML::Parser:

    use XML::Parser;
    XML::Parser->new(Namespaces=>1,Style=>'Stream')- >parsefile($ARGV[0]);
    sub StartTag {
    print if $_[0]->namespace eq 'html-ns-here';
    }
    sub EndTag {
    print if $_[0]->namespace eq 'html-ns-here';
    }
    sub Text {
    print if $_[0]->namespace eq 'html-ns-here';
    }

    Have fun!

    --

    Matt. Want XML + Apache + Stylesheets? Get AxKit.
  2. Re:ideas and suggestions by Matts · · Score: 2

    Err, that's still just plain XHTML with an extra namespace (marked x: there) for some additional information so that a round trip out to XML and back in won't lose any information. Not a good DTD design for XML output (i.e. it's really just HTML but they get to use the buzzwords without lying!), but it is what it is :)

    --

    Matt. Want XML + Apache + Stylesheets? Get AxKit.