Problem with formatted text

I have been using paragraph styles in specific and many of the styles in the Styles and Formatting Window. So much so that I dock this window at the left side of Writer. This goes back to OOo 1.02 as I was writing the Getting Started with Base Chapter in the Getting Started Guide. I extensively use list styles along with the associated paragraph styles. I have even modified the list styles to make them do what I want.
      Recently, I have been using Calibre to convert my writings to the ePUB format. The latter uses a style sheet for its formatting. Because the conversion from ODF to ePUB is not perfect, my experiences with styles permits me to make the changes I need in the ePUB style sheet.
      I also agree with a previous poster: templates are very important when using styles. I have 16 templates many of which that I have created and use. Each one contains its own set of styles (paragraph, character, lists, and page). A couple of them are for resumes that are suppose to be quite professional. I seem to remember a law firm had created its own template for their legal briefs to make sure its structure was exactly what was expected.
       Obviously, templates can take time to create. But once created, they can be real time savers. The only way I know to teach the importance of templates and styles is to have the students create a template with a complex layout using styles. Then have them create two papers with this layout without the use of styles. Then have them make two papers with this layout using the template. Let them determine which takes the least amount of time. Finally have them make a change in one of these papers by changing a style and then by changing things manually. See if they can even make all of the changes manually.
      Just some thoughts.

--Dan

I'll admit to not using styles, but not so much because I don't want to. I've been using the various word processing programs since PCs were first produced, before the concept of styles. They came out shortly after, of course, but they got little or no attention in the limited technical press that I followed at the time. By the time they were in widespread use, I was pretty well entrenched in my ways.

I've tried reading the documentation on them, but (a) I never have the time to sit down and actually learn them and (b) the documentation isn't all it could be -- this goes for MS as well as OO/LO. The biggest problem I've had, and I still don't know the answer, is how to actually save the styles so they're available for any document. I don't like any of the defaults, but don't see the point of creating a style that is usable only in one document, so I just do all the hard-formatting I need (which may take up more disk space, but it's also a lot more flexible as far as I can tell).

I'm slowly catching on, but it's going to be a while.

Great responses so far from everyone!

Dan, I like your idea of giving the students a project of doing a complex document with and without styles.

Virgil

Where styles will really shine is to give the students a project of doing a complex document with and without styles and then ask them to change certain aspects to attain some consistent characteristic. Change all headings to XXX, indentation and font on all paragraphs to yyy, outline numbering to ZZZ and you will see the advantages.
Steve

Have you read chapter 3, Using Styles and Templates, of the Getting Started Guide? It was written using a template containing all the styles that were needed. I use the same template to write several chapters of the Base Guide. It also contains what I need even though the topics are vastly different.

--Dan

Just ran across it recently. I've skimmed the whole thing but haven't had the time to read it in detail and apply the knowledge (I'm a tax professional, but the season doesn't end exactly on 15 April!). Hope to find some time soon to devote to it.

Dave

This whole business about forcing people to use "styles" reminds me of the "Green Belt" program that was introduced into
my business about 12 years ago. It required at least a week's work to just try and make a plan for the simplest project,
which, when the project was undertaken, would wind up scrapped anyway, since no-one can foresee everything. I don't
know what eventually became of this--it's one of the reasons I took retirement when I did. The green-belt Nazis and your
style Nazis should get along well with each other!

--doug

Dave and Doug,

I appreciate, Dave, hearing your perspective as a true end user. Your sentiments are those I've heard from my employees. They just need to get a brief done and filed, and they don't have time to learn the styles.

Doug, obviously, nobody's trying to "force" styles on anyone. What I'm trying to do is find an effective way of persuading people that their lives would be so much better if they took the time to learn them.

It pains me to watch people mouse around a document going from paragraph to paragraph trying to get formatting consistent when all they need to do is make one change to a paragraph style and "voila", every paragraph having that style is automatically changed. Just today, one of my students was stunned to watch that work. "You mean I don't have to make the same change to every paragraph?" she asked.

It also pained me in my law office to see documents presented with no formatting consistency with paragraphs that are supposed to be the same looking haphazardly different.

There is a better way, and since a university pays me to teach students how to take advantage of modern technology, I feel it my duty to at least give it a college try to find a way to explain it to them.

Don't want to use it? Then, don't. Nobody here's going to "force" you to do it. If you want to take twice as long to create documents as it takes me (and have results that are not as good), go right ahead.

Virgil

Virgil, I think it is great that you are trying to show your students
a better way. I don't understand why there was an accusation (using
'Nazi' no less — that post seemed full of bitterness) that anyone was
trying to force anyone to use styles.

Styles are a better way, but some people are resistant to change,
preferring to use a word processor as if it were merely an electronic
typewriter. As the saying goes, 'you can lead a horse to water ....'

Hi :slight_smile:
I am a bit bitter about this sort of thing too.  Even back when i was in school i could see teachers clearly trying to help people.  Unfortunately general attitudes of the kids in the classroom meant that even those of us that were interested in learning the skill had a tough time.  It didn't improve at Uni.

There have been some excellent suggestions in this list.  Perhaps set a mini-competition half the class using 1 technique. Perhaps ask for hands up if they can't cope with using styles, in order to play to the machismo of some.  When the results are in ask who can change the formatting of their document fastest.

Another idea is to get a horribly mangled paragraph and challenge them to insert it into their document to fit the style of their own work.

I frequently have to do this for my company's newsletter and at first found it took hours to try to fix people's messes in Word.  In LibreOffice i just pasted as unformatted and then applied styles taking just a couple of minutes at most.

However i still think it's easier to teach people things they want to learn.  Trying to trick them into wanting to learn about something else is a tough challenge.

Regards from

Tom :slight_smile:

I no longer need to write in any "required style or page format. SO, I never got into using styles. But you have a valid point in needing students to learn how to use it. The fact that writing "style" requirements change every so often. I went to 4 colleges and received 3 degrees. The problem I had was that every time I went back to college, the "standards" for foot notes, indexing, bibilography, and many other things I learn in one college English/Writing course changed. I ended up taking English and Writing courses several time to learn the new standards that the colleges were teaching and required for any paper to be turned into the professors. Then there are those classes that require specific formatting and styles for their paperwork.

If you create a set of styles, one per class/course/teacher, then you can write the documents and then apply the styles needed by the professor, or even the business reader.

I myself have run across times where using styles would work for me, but I never really learned how to use them correctly. Never took the time.

Tom's and other postings about getting students to "compete" in how fast it would be to format a "mangled" text to a predefined style and the others doing it the "hard way". Then having the students "compete" in a race to see who can create a style from scratch for the document. I bet there would be different version created that do the same end results.

The only problem I see with styles is some people may go and make a document so complex with styles for "everything" that it creates problems for an new user to edit/modify the document with new information or reorganize the flow of the document. I had to do that a few months ago and it was not easy. It seemed that every possible portion of the document, i.e. paragraph text and titles, columns and frames, images and headlines, were all defined in such a way that when moving text and images around the document, the styles setup would try to define the wrong text or document element. The editing and moving of text and images broke the very complex styling of the document.

The point is, styles are great in concepts, but some people can get carried away with their complexity. I have a book editor friend that I email back and forth with. She has some real horror stories trying to edit manuscripts that the author wrote using a complex set of styles. So if you teach and/or use styles, kept them simple enough that it does not get in the way of the next person needing to modify the document.

Hi :slight_smile:
I think you are thinking of Word rather than Writer.  Also you are talking about "House Styles" for different companies, different institutions, different professors.  Language and fashions do evolve too as you were also saying.

In Word Styles do tend to get very messy very quickly and it's overly complicated.  Plus you can never be sure that a style's definition will hold all the way through a document.

By contrast LibreOffice Styles "Cascade" (a bit like Css but different) so it's easy to change (for example the font of) one level of headings and find that change ripples out to other relevant styles.  KISS for internally consistent documents.

Regards from

Tom :slight_smile:

I first learned about styles and templates with Microsoft Word, and I think it is clear that this is something that all word processors do, for a very good reason. Back in the 1990s I developed a course for our degree completion students (basically people in their 40s who had started on a bachelors degree but never finished it). They needed to demonstrate proficiency with office software programs to graduate, and if they could not pass a test they could take my course and pass it. What almost always happened was that they put it off until the last possible time either because they thought they already knew it all, or because they thought they couldn't learn computer stuff and were afraid. By the time I was done with them, they almost always complained that they should have been given the course at the beginning because it would have saved them so much time. So people can learn this, and people can see the benefit of learning this.

I now do training sessions at placed like Ohio LinuxFest, and they are very well received. I just did another this past weekend at Penguicon, and had very enthusiastic participation. These are all people who chose to be there, so there is no possible implication of force involved. These are tools, and every tool works best if you learn how to do it properly. If you pick up the wrong saw and use it the wrong way, you may eventually cut the piece of wood, but it will look bad and take a lot more effort than it should.

Regards,

Same experience here;
           the rules keep changing, so I stick with the Keep It Simple
system :wink:

One additional thought: those who have learnt HTML and CSS should find
using styles quite natural — it is the same separation of content from
presentation (styles).

NO
it was a Writer file from the 3.4.x days.

The file needed a lot of work and additions to reflect the changes from 3.6.x to 4.0.x. I was not the one who created the document, but I had it for over a year and finally had some time to work on that documentation. I almost gave up. The person must have done a lot of "experimentation" with every style option in the document, even where it was not needed. I even found a sentence that has just a few words in it with their own style that was not used anywhere else. I ended up going back to an exported unformatted .txt file and starting over from there.

I hope the guy did not write the LO document in Word, but he could of, since he still has Word 2007, if I remember correctly. I use to use both Word 2003 and LO in the early days on a Win XP system, since I had to give others Word documents, so I made sure the LO .doc file looked correctly in Word. Sometimes it was easier to just do the editing in Word when I was using my laptop at their home or office. Now I just use 4.0.x on all my Windows systems, since it is better at dealing with the .doc/.docx files I am getting via email. I never went beyond MSO '03.

The KISS standard is something many "experimenters" do not use many times. They want to be to "creative" for my tastes.

BUT
as for the original posting. . . .
I really like the idea of teaching people to use LO in the higher education environments. The younger crowd would be easier to teach since they were not so "frozen" onto the MSO mentality and concepts. Making learning fun and people of all ages might learn more in a faster time and enjoy the learning process more than I found in most of my college courses, and in the high school courses I had to teach as a substitute teacher.

Templates vs. Styles is a whole different discussion with pros and cons with each. For the business world, templates might be easier to deal with for the user, since they do not need to remember which styles go with which document[s] they are required to make. Then you do not need to see if the "master document" creator's work with styles gets to work with all of the user's individual desk systems. I really do not know how to import a number style from computer to another so they can be used on different documents. The same problem might come up with one writer including a font in their document that the next person using it does not have that font installed. The document states/displays the correct font in the font drop-down window, but Writer tries to use a different installed font as a substitute.

Hi :slight_smile:

I think that is called "a teaching moment" and they are extremely rare.  In 20 years of teaching one can expect about 4 of those.

Regards from

Tom :slight_smile:

Do you use styles?

The point with OO/LO is that unfortunately, like Word, its style concept
does not allow to work in the "structure markup" way.

So, even if you tried to use styles consistently, you wouldn't be able
to benefit from it the way you can with e.g. LyX/LaTeX or document
processors like Wordperfect or Framemaker (or any other document
processing application that I know of - except LO/OO and Word).

Just look at the official documentation (which would be supposed
to be a showcase of how to work with LO) and try to work with it. For
example, to make the documents actually readable, try something as
simple as replacing the body text typeface with one actually made
for readable text.

In any document processing application with a well-implemented style
concept, this would require the change of one single definition in
one style. With LO/OO, just like with Word, you're in for a whole day of
work. Because you'll have to modify each and every style individually
and besides, due to invisible (and incorrectible) "bugs" in the
formatting parts of the documents will still require manual
re-formatting. And once you're done with that, besides a seriously
strained wrist, you still have an unstructured spaghetti document.

This is why I wouldn't use LO to teach what structure markup (e.g.
"styles") is about in the first place. And why I don't use it for
*writing* documents. Only for generating them from databases.

Sincerely,

Wolfgang

Comments inline:

Do you use styles?

The point with OO/LO is that unfortunately, like Word, its style concept
does not allow to work in the "structure markup" way.

      What do you mean by a "structured markup" way? Please be specific.

So, even if you tried to use styles consistently, you wouldn't be able
to benefit from it the way you can with e.g. LyX/LaTeX or document
processors like Wordperfect or Framemaker (or any other document
processing application that I know of - except LO/OO and Word).

Just look at the official documentation (which would be supposed
to be a showcase of how to work with LO) and try to work with it. For
example, to make the documents actually readable, try something as
simple as replacing the body text typeface with one actually made
for readable text.

       How about some specific answers instead of aaccusations? What font is unreadable? (I have been able to read them easily for more than a decade.) Why is it unreadable? What font would you prefer were used instead. What chapter and Guide are you referring to as official documentation? What version of LibreOffice was used to produce it? (This is found below the Copyright.) What paragraph style was used by LO to define the fount that was used? Why can't a person change the font from what it is to what you would prefer?
       I actually work with styles beginning first in OOo 1.0.2 and continuing up to today. What is it that I have been doing could have been done easier and quicker?

In any document processing application with a well-implemented style
concept, this would require the change of one single definition in
one style. With LO/OO, just like with Word, you're in for a whole day of
work. Because you'll have to modify each and every style individually
and besides, due to invisible (and incorrectible) "bugs" in the
formatting parts of the documents will still require manual
re-formatting. And once you're done with that, besides a seriously
strained wrist, you still have an unstructured spaghetti document.

      Please give us a specific example of what you are talking about. What bugs? Why are they causing problems. What has to be manually re-formatted? How about an example of a structured document and an unstructured spaghetti document?

--Dan

I no longer need to write in any "required style or page format. SO, I
never got into using styles. But you have a valid point in needing
students to learn how to use it. The fact that writing "style"
requirements change every so often. I went to 4 colleges and received 3
degrees. The problem I had was that every time I went back to college,
the "standards" for foot notes, indexing, bibilography, and many other
things I learn in one college English/Writing course changed. I ended
up taking English and Writing courses several time to learn the new
standards that the colleges were teaching and required for any paper to
be turned into the professors. Then there are those classes that
require specific formatting and styles for their paperwork.

This clearly shows that, unless the word processing learning is part of the course, the teachers/professors/whatelse should provide a template for the paperwork they are requesting.

The only problem I see with styles is some people may go and make a
document so complex with styles for "everything" that it creates
problems for an new user to edit/modify the document with new
information or reorganize the flow of the document.

Yes, sure.

Any template should come with a manual and/or a refcard describing the workflow and the styles usage. The tool is the software *and* the template.

The point is, styles are great in concepts, but some people can get
carried away with their complexity.

Sure, too.

People having to *write* shouldn't be bothered with any conceptual complexity (the template manufactoring). This should be taken care elsewhere by someone else.