DocTEAM

The bitsoffice extension import the whole document into one content element.

It is not usefull to work with an large document in one content element only. The rte is still loading - but even if it would work i do not believe that someone could think it would be an acceptable alternative for writing documents in word or openoffice.

I expected something like that:

1. import document -> for each heading 1 we get an page, for each heading 2-4 we get an content element
2. than we could easily edit the content elements, restructuring etc.
3. after that an export of that tree structure has to be possible

But it seems, that it is not possible at the moment. Perhaps we should work on it? I do know if that would make sense.

1. bitsoffice
2. tx_rlmpofficeimport
3. general office displayer
4. office documents

if we only want to display the manual, we should use "office documents" (perhaps we could check, if that is the same extension as on typo3.org).

So i would dig for an hook or typoscript that we can add comments on an per "page" base.

english version below!

Ich würde jetzt vorschlagen:

Im 1. Schritt nur eine Anzeige mit Kommentarfunktion, Rating und Anbindung an snippets schaffen.

Und in einem 2. Schritt die bitsoffice extension (oder eine andere) so abzuändern, dass sie einen Seitenbaum erzeugt der dann editiert werden kann.

Dafür wäre in 2A notwendig einen Seitenbaum in sxw oder docbook auszugeben. Dann könnten wir auch ohne den Importer das Schreiben in TYPO3 austesten. Wenn wir dann feststellen, dass das super ist und gut läuft, dann könnten wir den Importer im Schritt 2B entsprechend umbauen, dass er Seiten und Inhaltselemente erzeugt.

denglish:
i would suggest:

We should implement at first the possibility to show the documents and add comment per "page", ratings and an integration to snippets.

Then we should write some typoscript/extension to export an page-tree into an sxw or docbook. If that works, we could test with an small amount of documentation if it is usefull to use TYPO3 for writing manuals.

After that we could change bitsoffice (or another extension) to create an page-tree with content element instead only one content element.

Hello Martin,

thanks for testing these!

I suppose you used 0.9.0 of bitsoffice. I just compared it with the version in the TYPO3-installation we have on Virgils Server, there is 0.8.2

The 0.8.2 really created pages for every section! It also created the structure as pages - not just a plain list.

=> I think the 0.9.0 has a switch: all in one text-element or as pages. Please look for that in the manual or in the extension-config.

We don't need a displaying extension of docbook, sxw - because we HAVE to import it.

Cheers!
Daniel

ok, version 0.8.2 of bitsoffice does the job.

It is possilbe to import sxw-files.

So, next step would be to rewrite it to import docbook (do we need that?)

Notice: Ingo Renner told me, that he did some stuff about docbook etc. - i should ask him about, what he did:)

Hello Martin,

hey very good, thanks! So now we can import 50 pages in one upload. I just asked the author, if we can optimize it together. I tell you, when I know more.

And yes: We do need docbook-import, because the core-manuals will be docbook in some months!

Cheers!
Daniel

@Martin
good news!! Jochim Karl has updated the ext and the problem is now solved. It also can import ODT now! Please update it, when you've got time for it.

Cheers!
Daniel