• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
  • Bear Bibeault
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Piet Souris
  • salvin francis
  • Stephan van Hulst
Bartenders:
  • Frits Walraven
  • Carey Brown
  • Jj Roberts

Compound Documents and chapter titles

 
arch rival
Posts: 2813
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have been creating a large compound (or master) document with Star Office 5.2. It has about 230 pages and puts together about 30 separate sub documents. So far I have been very pleased with the way star office handles this. However I seem to have found a limitation in the way compound documents work with headers.
There seems to be no way to ensure that the Headers in the sub documents are reflected in the master document. Does anyone have any ideas on this.
On a more general (and creepily free book grasping) note, here are some of the excellent features of Star Office I have been taking advantage of.
Table of contents generation using the Outlining, multi column Alphabetical index generation, application and manipulation of styles, HTML export (not perfect but very acceptable) the VB like macros (Shfit F2 now imports and applys a particular style on my system) and most of all utter transparent use between the Linux and the Windoze version, which is useful as my Linux refuses to print.
By the way, this document is due to form the basis of a book so I was wondering if a book published from Star Office would be a first?

------------------
http://www.jchq.net Mock Exams, FAQ, Tutorial, Links, Book reviews
=================================================
Almost as good as JavaRanch
=================================================
 
Author
Posts: 377
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Marcus,
Floyd's the StarOffice Writer king, so he'll be riding out of the sunset any minute to answer your question about the limitations.
Floyd and I wrote our book in Frame. If you feel comfortable with Writer, well, we say more power to you! ;> You might be the first, though the benefits of such an accomplishment might be marginal.
The fact that everything except printing is the same across Linux, Solaris, and Windows is great. It's very odd that many SO books out there specify that their book is "for linux" or "for windows".
Sounds like you've got Writer by the tail. Good job!
Solveig

Originally posted by Marcus Green:
I have been creating a large compound (or master) document with Star Office 5.2. It has about 230 pages and puts together about 30 separate sub documents. So far I have been very pleased with the way star office handles this. However I seem to have found a limitation in the way compound documents work with headers.
There seems to be no way to ensure that the Headers in the sub documents are reflected in the master document. Does anyone have any ideas on this.
On a more general (and creepily free book grasping) note, here are some of the excellent features of Star Office I have been taking advantage of.
Table of contents generation using the Outlining, multi column Alphabetical index generation, application and manipulation of styles, HTML export (not perfect but very acceptable) the VB like macros (Shfit F2 now imports and applys a particular style on my system) and most of all utter transparent use between the Linux and the Windoze version, which is useful as my Linux refuses to print.
By the way, this document is due to form the basis of a book so I was wondering if a book published from Star Office would be a first?



------------------
author of:
StarOffice Companion
 
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Howdy, Marcus -
I burned the beans and had ta ride inta town for another can. Sorry about the pokey response.
When you talk about headers and footers not coming over, I assume there are special things in the headers/footers that aren't being maintained. The things that control headers and footers unique are the page styles they're attached to. For example, left pages can have unique headers and footers from right pages. In the master document, you can create separate page styles just like you can in individual documents. But if you're getting really tricky with multiple types of page styles (p.211 of the book), you may need to first create the page styles you want in the master document, then import them into your individual documents (p.221 of the book), and create the exact page flow you want in your individual documents, so that the master document reflects all the page styles/breaks.
There's a whole chapter in the book on dealing with books and longer documents. This chapter shows you how to keep things simple and get the maximum flexibility you can, such as using running heads in the header or footer that display the current heading in a section.

------------------
author of:
StarOffice Companion
Standard CYA*******************************
All responses to questions posed in this News Group are given on an
"as is" basis. We believe the solutions or explanations given here are
correct, but do not guaranty that responses will be complete, without
error and/or work for all platforms and system configurations.
 
Marcus Green
arch rival
Posts: 2813
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When you talk about headers and footers not coming over, I assume there are special things in the headers/footers that aren't being maintained. The things that control headers and footers unique are the page styles they're attached to. For example, left pages can have unique headers and footers from right pages. In the master document, you can create separate page styles just like you can in individual documents. But if you're getting really tricky with multiple types of page styles (p.211 of the book), you may need to first create the page styles you want in the master document, then import them into your individual documents (p.221 of the book), and create the exact page flow you want in your individual documents, so that the master document reflects all the page styles/breaks.
That sounds like the area I was thinking about. What I want to happen is that in my sub-documents I want to put in a header in each document such as "Make money fast" or "Loose money faster". Then when I load up the master documents, the pages that contain those sub-documents will have the header in the master document.
There's a whole chapter in the book on dealing with books and longer documents. This chapter shows you how to keep things simple and get the maximum flexibility you can, such as using running heads in the header or footer that display the current heading in a section.

Woah, I can see why the word dummy or idiot was not in the book title
With reference to why I decided to the advantages of Star Office to put together an entire book ....
Word only runs on Windows and I see a very bright future for Linux. Also one of it's greatest proponents Woody Leonard says that its management of compound documents leaves a lot to be desired.
As the book is not graphics intensive I didn't feel I needed the fine grained control of DTP (I assume Frame that Solveig refers to is Frame Maker?).
I toyed with using LaTex and/Or Lyx but it just looked too hard. I even bought a copy of WordPerfect Office 2000 for Linux. Strange, I spend the equivalent of $USD200 on software and then end up using the stuff that cost $USD 0. WordPerfect would not do a sensible import of HTML which used the pre tag. Also I ended up with just the linux (wine) version and no windows version.
Star office is not perfect, but it seems better than any other paid for or free alternative.
I believe that software success is more about standards than technology. The free availablility of both binary and source for Star Office will mean it will be a no brain choice in the parts of the world with tightest budgets and reluctance to pay licence fees.
I printed out my book the other night and instantly spotted yet more errors. Now if they can just automate the proof reading in StarOffice
Marcus

------------------
http://www.jchq.net Mock Exams, FAQ, Tutorial, Links, Book reviews
=================================================
Almost as good as JavaRanch
=================================================
 
Floyd Jones
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Marcus Green:
Woah, I can see why the word dummy or idiot was not in the book title


I probably should have included in my sections of the book, "Written BY a dummy, not FOR dummies." Naw, we assumed SOME level of previous Office-type experience as a starting point for our instructions. However, since SO is new to most people, we DO do some good handholding, especially through some of the trickier stuff.

With reference to why I decided to the advantages of Star Office to put together an entire book ....
Word only runs on Windows and I see a very bright future for Linux. Also one of it's greatest proponents Woody Leonard says that its management of compound documents leaves a lot to be desired.
As the book is not graphics intensive I didn't feel I needed the fine grained control of DTP (I assume Frame that Solveig refers to is Frame Maker?).
Star office is not perfect, but it seems better than any other paid for or free alternative.


Just a dirty little secret: We wrote the book using FrameMaker, not Writer. I DO feel that Writer handles book-building better more gracefully than Word does. But for long books, nothing can touch FrameMaker. If we had done the book in Writer, I felt I could have worked around and tweaked some of the master document stuff. But one of the most important things Writer lacks is the ability to cross-reference across files (like, "see 'Predicting Earthquakes With Sheep's Bladders' on p. 253"). Much documentation I've read says you're supposed to be able to do it, but that dog just don't hunt. We wanted to use a lot of cross-references in the book, so that wouldn't work for us.
As far as the "Running heads" concept, I'd go into it more here, but it's just way too long for the space we have here. I will, however, quote from the beginning of the section that explains how to set up this functionality: "This feature is one of the most confusing and non-intuitive in StarOffice; and if it didn't play such an important part inhow other features in StarOffice work, you'd be wise to ignore it altogether."
------------------
author of:
StarOffice Companion
Standard CYA*******************************
All responses to questions posed in this News Group are given on an
"as is" basis. We believe the solutions or explanations given here are
correct, but do not guaranty that responses will be complete, without
error and/or work for all platforms and system configurations.
[This message has been edited by Floyd Jones (edited December 21, 2000).]
 
To avoid criticism do nothing, say nothing, be nothing. -Elbert Hubbard. Please critique this tiny ad:
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic