Hi Wayne,
> That tutorial example is very nice. > > As to to Tools though, it seems like yet another new tool is required. > Don't be frighten, at the end, it's just bytes in files... :) > > I checked debian for DITA editors and got no answers. > Don't consider Debian as a reference for having up-to-date softwares. Proof: they don't have jalv2 nor jallib ! > > I checked for XML editors and got > [...] > > which are all new, to me, anyway. > But it's just XML in anyway. That said, having a XML editor with DITA flavors can help. As I mentioned before, XXE and Serna seem nice candidates (and don't apt-cache searc, you won't find anything) > > I seem to recall that OpenOffice, a multi-platform suite, was mentioned. > It can produce the same results as the current PDF and, if the setup was > distributed, anyone could add pages/section/etc for inclusion in the > final result. Did I mention that OpenOffice is FREE, works great here > and I have been using it for over 7 years. I would think just about > everyone on the list has it installed. > > If Openoffice is not in the mix of tools, I wonder why. > Yeah, I can remember. Still, nobody has answered the following questions. Regarding Open Office: - is it possible to generate HTML and PDF, automatically ? Can OO be integrated in automatic builds and produce different outputs while building ? Mandatory. - is it possible to put OO files under SVN, so content can be followed (diff) line by line ? (by default, content is considered binary, so no diff possible). Very important. - is it possible to aggregate different files into a single one ? - can you reference a particular section in another file and put this section's content into the current file ? Aggregating and content referencing aren't just gadgets: there are many source of documentation out there, and many of them could re-use, just like you would re-use code instead of reinventing the wheel. Regarding this analogy with code, I (like to) consider documentation just like code: under SVN, automatic builds, reusable, refactoring, etc... As I said, I'm trying to find the appropriate tool for our documentation, but that's an easy task. I've tried some candidates (like Docbook, LaTEX, ASCIIDOC) and DITA seems to fit our needs. But that's XML, may require an editor, and surely will require some kind of investment. I can help by writing docs explaining how to use DITA, still users will have to invest some time. So far I haven't heard many feedback, feelings, and most importantly suggestions. Except OO. If OO can do this, and if we all agree, then I'd be happy to trash DITA ! For now, as a POC, I convert my tutorials from jalliblog into DITA files, so you can see for real how it looks like, on a real-life example. Cheers, Seb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
