[TYPO3-dev] A few thoughts about extension manuals.

[Stephen Bungert]

Hi Daniel,

I haven't done this I'm afraid. I only really use OOo for TYPO3 manuals and 
wasn't sure how to do this, I did ask once on the list if we had to and was 
told we didn't!
I shall in future! Although it does add to the overall size of the ext.


"Daniel Bruessler" <danielb at typo3.org> schrieb im Newsbeitrag 
news:mailman.1.1266831708.16709.typo3-dev at lists.typo3.org...
> Hello,
>
> perfection is the problem. We have a good solution, and that can be
> optimized. First is to help with removing rendering-problems. Another is
> pdf. Everybody can export an OpenOffice-manual to pdf with just a click.
> Why is just a little number of people who do this?
>
> Cheers!
> Daniel
>
> == DocTeam ==
> Want to help? Just see what topics you're interested in and join us!
> http://typo3.org/teams/documentation-team/
> http://forge.typo3.org/projects/show/team-docteam
>
> :: Daniel Bruessler - Emilienstr. 10 - 90489 Nuernberg
>
>
>
>> Hi,
>>
>>> do it! I did also say that if an open readable format was required it
>>> would
>>> quite easy to get the ter to export the content of the manual as html
>>> with
>>> images. No css. just plain html. Can't get more open and accessable than
>>> that. At present you have to have OOo installed to read the manual...
>>> does
>>> anyone every actually do that by the way? Something my network admin has
>>> restricted. I have to rely on HTML manuals while at work.
>>
>> I do ave OOo installed and use it to read the manuals. But I agree that
>> I don't like it either as it is way too slow to start in regard to a PDF
>> document. Now, having an OOo document allows me to modify the manual
>> whenever it's required without having to rely on yet another software
>> (such as a XML / DocBook editor) but, well... I guess nothing is perfect
>> for all use cases.
>>