Hi John, thanks for your comments. My responses are interleaved below. On Fri, 2011-05-13 at 22:02 -0400, John Shabanowitz wrote: > On Fri, May 13, 2011 at 9:34 PM, Jean Weber <[email protected]> wrote:
> > > > 3) I have a collection of tutorial type material that I've written, which > > has either been published on my own blog or in a book I've written, but > > which has never been placed on the OOo wiki. Also some items of mine that > > are on the OOo wiki. All of these could become part of the LibO > > documentation set... if I ever find time to do it. > > > > 4) These tutorials and howtos could be published on the blog, but they > > could --IMO should-- also be collected on one or more pages of the wiki, for > > easier reference. Also, some are too long for the blog, so having them on > > the wiki with teasers on the blog could be the way to go. > > > > I follow a blog that has recently changed to that type of format. A tease on > the front page and click through for the article. I don't like it. I want > the whole article there to read when I click from the newsletter. I don't > see it as a problem if it is only within certain blog posts, not as a format > of the blog. I certainly would not like to see the blog use that method as a standard thing, but if the article is in ODT and is longish and has many pictures, then putting it into the blog is extra work (which, for me, won't get done). See my comments below about using the wiki publisher extension. I suspect the same problem would apply to the blog publisher, but I've never tried it. Have you used it for articles that contain graphics? > > > > > 5) Some items might go well in wiki format, unlike the user guides which > > are in ODT with only a download link on the wiki. However, many of my items > > already exist in ODT, so it would be easier and faster to get an initial set > > of material on the wiki in that form. People writing new stuff, especially > > if adapting existing material from the user guides, might find it easier to > > use ODT too. Others might prefer to work directly in the wiki. > > > > IMHO, we should all be working in LibO and then cutting and pasting into the > blog. That way we get important user vision and gain user voice for our blog > posts. There is a post about filtering text in Calc on the users list. Is > that for real? It's so easy, it is all there when you bring up the filter > dialogue box, even the copy to command. I sometimes wonder if we are being > tested by others. > > > > > Any thoughts or comments on any of this? I haven't begun to look at the > > wiki and how best to add this sort of thing to it, but as we are > > reorganising the wiki anyway, this could be part of the reorganisation. I do > > hope David N finds time to work on the reorg, because I've been so involved > > with some of it, I no longer see the problems or what's missing. But wiki > > reorganisation is a topic for a separate note... This one is too long > > already. > > > > It's the wiki that confuses me. LOL. Anyway, there are two extensions for > OO.o, There is a blog poster and a wiki poster. I have been able to use the > blog poster extension to post to blogger but not wordpress. Anyone else use > it? I haven't used the wiki poster extension yet. Do you use it? I have not used the wiki publisher extension to post directly to a wiki, mainly because all of the things I've done so far need manual cleanup after going through the wiki publisher. So I send the results from the wiki publisher to a text file, do the manual cleanup, and then paste the results into the wiki itself. I believe that the wiki publisher works fine for files containing text and perhaps some tables, but as soon as you add images, it can't cope. --Jean -- Unsubscribe instructions: E-mail to [email protected] Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
