Larry wrote:
Another fact to consider is that most WYSIWYG word processors (Word, OOo Writer, KWord, etc.) generally produce output that is tailored for a printer. Their web-targeted output is by and large attrocious and breaks very very easily...unless you do a dramatic amount of cleanup,
yes, but this is very easily done automatically, outside and before the scope of my original rant, with the right FOSS tools and a bit of initial planning:
* write in openoffice defining ad-hoc styles and using them consistently. * convert the opendocument files to html in openoffice or (in the near future, when ready) any of the command line converters to html * run html tydy * import result in cms
Oh, and using an HTML editor as you suggest, means just ignoring the most on-topic bottleneck, ie how to not load anything in drupal manually...
by which point it's frequently easier to just copy and paste the text out of it.
You surely were kidding here, right? Pasting from OpenOffice into an HTML text area looses all formatting (distinguishing heading from chapters, preserving URLs, etc....)
Ciao, O.
yes, but this is very easily done automatically, outside and before the scope of my original rant, with the right FOSS tools and a bit of initial planning:
- write in openoffice defining ad-hoc styles and using them consistently.
- convert the opendocument files to html in openoffice or (in the near future, when ready) any of the command line converters to html
- run html tydy
- import result in cms
Ithat would loose a lot in the convertion. Surely it would be far more beneficial to write a converter from OOo to an html subset for use with a cms, for example drupal. But then probably it would be easier to write an OOo pluging to export to drupal directly. And if you want automation you can always do this from the command line - open office is nicely scriptable. There remains just one tiny problem - doing it.
On 7/4/06, Vladimir Zlatanov vlado@dikini.net wrote:
yes, but this is very easily done automatically, outside and before the scope of my original rant, with the right FOSS tools and a bit of initial planning:
- write in openoffice defining ad-hoc styles and using them consistently.
- convert the opendocument files to html in openoffice or (in the near future, when ready) any of the command line converters to html
- run html tydy
- import result in cms
Ithat would loose a lot in the convertion. Surely it would be far more beneficial to write a converter from OOo to an html subset for use with a cms, for example drupal. But then probably it would be easier to write an OOo pluging to export to drupal directly. And if you want automation you can always do this from the command line - open office is nicely scriptable. There remains just one tiny problem - doing it.
I don't know about HTML, but there's a OD->Markdown script out there: http://www.freewisdom.org/projects/python-markdown/odt2txt.php
The Markdown module for Drupal could then be used to filter this. Markdown has the added benefit of being quite readable as ASCII text, so if you have less html-savvy users, it'll make a lot more sense than all the angle brackets, if editing in the textarea would need done.
I suppose it'd be possible to use a script like that to make an OpenDocument input filter for Drupal, which could take the content of the node from an attached OD file -- now *that* would be cool.
Op dinsdag 4 juli 2006 13:12, schreef Vladimir Zlatanov:
But then probably it would be easier to write an OOo pluging to export to drupal directly.
In a previous mail I talked about how I "talked" to Drupal using XMLRPC and blogapi and Ruby. Well, I even managed to pipe some output from kword/KDE (which has far better APIs then OOo) into Drupal:
Rightclick on a .kwd or open document file, I got an entry called "post to Drupal". that would pipe the contents of that file into a node.
As proof of concept it worked. But you would need to spend some more time if you really want to make something like this usable (ie, answer questions like what to do with files/images).
Bèr