Greg wrote:

It sounds like you want the ability to publish from OpenOffice.org to these different blog engines. Why not write that?

See my answer to (IIRC) Vladimir. Synthesizing:

* I am already doing the non CMS part of it * I think it would be wrong to do a monolithic Ooo -> (drupal or any other cms) publishing plugin.

My contention is that your offline command line import tool would fail miserably in a multi editor environment. And I don't think you've said anything to change my mind on that.

??? I didn't try for one moment to do it. I have already said that in other scenarios the current architectures are better.

So are you talking about one author or a lot or...It's tough to find the right solution when you keep changing the requirements/focus.

Sometimes one has to start to ask questions just to _find_ what the right questions to ask are. I am engaged in different projects. This command line input is something I need only for one of them.

Said this, I find that you too, surely in good faith, keep missing the points or giving the same answers which I already commented:

You want spell checking that uses the same dictionary file on all your sites. That seems best implemented as a browser extension so your dictionary is in the browser across the sites...

I told you I don't want to enter the same data I already have in openoffice, and you answer saying "re-enter all them in the browser"?

With respect to cms usefulness, drupal handbooks and all the rest of your comments: sorry if I got us side-tracked. As far as I am concerned, I'll drop that subthread, we can discuss it some other time.

From now on, I'd rather discuss on this list only the

missing piece: "how can one import stuff in drupal from the command line"? Regardless of which and how many scenarios actually need it.

Ciao, O.