Problem with formatted text

users
#52

Hi :slight_smile:
In MS Office styles are an excessive waste of time. You just have to accept
that documents will have changing fonts, bullet-point sizes, misnumbering

> in lists and even changes in language used by spell checkers.

Are you saying the styles area a waste of time, or Office? LOL

When I first got started with Office, and got into styles, the program was a total mess. Often I couldn't even save a doc without Word crashing, and way too many times, I would lose half of a document. Sometimes, I even had to start over.

Then a new version came out, and things worked pretty good, and once I got a handle on styles and formatting there, I can't say I had any problems. I'm talking about writing various in house plans. It was also an Office only environment.

LO, on the other hand, baffles me more than Word ever did. I have to own up to not working very hard with styles and formatting yet. Have no reason to learn it, and haven't taken the time to just sit down with it.

But, just last night, found an issue with outlines in the current version. And it's a situation that should never have happened, and should have been fixed long ago. I've seen enough of these recurring things that I've started looking at alternatives, including commercial suites.

As I noted in private email, LO still has not assigned two bugs I filed to anyone yet. They are classified a low priority. As I mentioned, the issues are *not* low priority to me, so if they don't want to fix them, I'll pay for a program where the developers do care to fix the low priority issues.

In LibreOffice just start by using the default ones. Don't even set-up new ones. Instantly

> you see a rise in quality and productivity. Then show how changing the defaults ripples
> through the whole document but keeps it looking very high quality.>

The problem is that people have become so accustomed to the poor quality of documents

> that anyone insisting on higher quality is seen as a fuddy-duddy, someone to ignore and
> ridicule even if that person is in authority.

+1

<snip>

#53

Hi :slight_smile:
At my work place they have just run a 3 month training course in MS Office

> 2010. We are 2 months in and people still don't know how to select a printer
> or turn the machine on or off. The tutor has to do all that. I was also
> expecting a few to teach me how to place images to get the flexibility that
> LibreOffice gives me but they don't know how to get an imagine in let alone
> how to set it up or move it around.

This sounds to me like you have a class of students who need to be taught computer basics before being sent to an Office class.

One of my other personal gripes about today's computer users and some employers.

<snip>

#54

Hi,

I use styles as much as I can, just to achieve consistent formatting, to say nothing of time saving.

I find that most people I know who use word processors as a (barely glorified) typewriter are those who are most resistant to using styles.

Andrew

#55

IMO, this is a long time marketting motto which I try to fight: IT is *not* easy and IT is *not* intuitive. Unfortunately, for more than 30 years, the powers-that-be believe marketters.

#56

Hi,

I find that most people I know who use word processors as a (barely
glorified) typewriter are those who are most resistant to using
styles.

They are not resistant: they have never been seriously told about styles and their bosses believe software marketting (IT is supposed to be easy and intuitive, which it is *not*).

#57

Dear Ken,

could you please post numbers of these bugs here? The topic sounds to be interesting
Thanks
Milos

Dňa 05.05.2013 00:32, Ken Springer wrote / napísal(a):

#58

This is how open source works.
There are some companies (in LO: mainly RedHat and Novell) that hire full-time
developers. They work on anything that helps reaching companies goals.
Also, there is bunch of guys who just hack in their spare time. They work on
anything they find interesting or solve their own problems.

If your issues does not fall to interest of any of above groups, there is
still chance to get it solved: hire a freelance developer who will get thing
done.

Because LO is open source, you are not on the mercy of some company. You can
take matters into your own hands and do something.

Or you can buy some other software. You don't have to use LibreOffice.

#59

Hello Jean-Francois,

I didn't know that you know the same people I know.

#60

Hello Adrew,

I didn't know that you know the same people I know.

Typewriter users are still alive and well. This is just because *noone* (myself to begin with) never told them in time that a computer is no typewriter. The secret is well kept and trainers' first job should be to reveal it.

#61

A program is intuitive if it matches something in our previous experience. Before computers, business professionals used typewriters. If you want a computer to be intuitive, you need to make it work as much like a typewriter as possible. (I'm still amazed that, after 30+ years, the typewriter remains the model of the word processing user interface, even for those who have never touched a typewriter.)

But, by making it intuitive, you lose the power of the computer. To gain the power of the computer, old dogs need to learn new tricks, like paragraph styles, which isn't intuitive.

Virgil

#62

https://bugs.freedesktop.org/show_bug.cgi?id=44871
https://bugs.freedesktop.org/show_bug.cgi?id=46986

Will wonders never cease... The first one has been assigned to someone. <grin>

Maybe there's hope after all, as I've got a list from long ago that I never bothered to file as these were never addressed and assigned, so I never bothered.

#63

Hi, Mirosław,

Interspersed reply below.

As I noted in private email, LO still has not assigned two bugs I filed
to anyone yet. They are classified a low priority. As I mentioned, the
issues are not low priority to me, so if they don't want to fix them,
I'll pay for a program where the developers do care to fix the low
priority issues.

This is how open source works.
There are some companies (in LO: mainly RedHat and Novell) that hire full-time
developers. They work on anything that helps reaching companies goals.
Also, there is bunch of guys who just hack in their spare time. They work on
anything they find interesting or solve their own problems.

I've known that for a long time, but others reading this may not.

But the company's goals should be to meet the user's goals first. If you don't meet your users goals, your level of success will never reach the top. You'll have a group of people bad mouthing your product, regardless of the product. People saying the product doesn't do what you want is OK, but people saying your product is broken is not.

If your issues does not fall to interest of any of above groups, there is
still chance to get it solved: hire a freelance developer who will get thing
done.

Simply for the sake of discussion... We should be talking about the average user of LO, not the those users that are capable of programming the changes, or knowing how go about hiring someone to do the job. If LO or any product, open source, commercial, bucket making, is to increase the number of users, you've got to pay attention to the users that can not make the changes on their own.

Because LO is open source, you are not on the mercy of some company. You can
take matters into your own hands and do something.

And I'm one of those users that possesses neither the time, money, nor interest in creating a change. A change that may not be compatible with any other LO produced file.

Or you can buy some other software. You don't have to use LibreOffice.

Exactly. For open source, I could try Open Office and Lotus Symphony. And there are 3 commercial products I'm going to look at, one of which may possibly be a better match for me than LO. I did not know of this product when I started with LO.

I first started with 8-bit computers, and would buy every new word processor that came out until I finally found one that worked for me. I never said the others were "crap", just that they didn't do what I wanted to do. :slight_smile:

#64

I totally agree, especially for the technical side of things.

But it would be so much easier if people would just read the manual.

OH!! Wait! No one makes manuals for their products any more! LOL

LO is to be commended for bucking the trend in this area.

#65

I'm not so sure that by making it intuitive, you lose the power of the computer. And I will stipulate that what is intuitive to one user is not to another. My Mac drove me up the wall sometimes, in this area. Windows? Not a problem. But I've got a friend that is the exact opposite. OS X not a problem for her, but never did understand Windows.

What needs to be stressed/taught, is "try something". Be inquisitive about the computer. "What happens if I do X?"

I often try to mix features between Win and OS X, so it does what I wish and makes sense to me. Right now, I'm trying to get OS X's sidebar view in Finder to be similar to the Win Explorer's Navigation Pane. So far, with no success. :frowning: So, if anyone knows of a way... LOL

#66

Doug,

I may be wrong, but it would seem to me that all this fuss about styles
is made by people who are trying to do desktop publishing.

Styles are, obviously, a step towards DTP but, as you emphasize, a word processor is no DTP (as much as a word processor is no typewriter). Styles are a very powerful tool that makes ordinary users -- who do not intend to publish, just have correctly crafted documents -- gain time and energy. And, in the business, time is money.

But I can see what you're hinting: for those users who want to actually publish, such a tool like Scribus is the way to go. I share this thought, but DTP is a whole other beast that requires training on its own.

I'm not ashamed to say that I use
word processors as word processors, not as desktop publishers. I am very
happy to have this glorified typewriter

There's a very wide gap between a typewriter -- as glorified as it could be -- and a word processor. I'm always insisting to users forget the typewriter (even if they never really use any, or even touched any) and acquire the concepts of word processors.

BTW, do you know the hardware piece where the evil comes from? The keyboard. A typewriter kb and a computer one are not the same although they look alike. They just look too much alike and the trainer has to show they are different.

#67

From: Ken Springer [snowshed1@q.com]
Sent: Sunday, May 05, 2013 7:49 AM
To: users@global.libreoffice.org
Subject: [libreoffice-users] Re: Paragraph styles

https://bugs.freedesktop.org/show_bug.cgi?id=44871
https://bugs.freedesktop.org/show_bug.cgi?id=46986

Will wonders never cease... The first one has been assigned to someone.

Actually, FDO bug 44871 has been "assigned" since the date it was submitted during QA bug triage. But that means exactly squat since Cedric did not assign himself (indicating he accepted and was working on it).

Assignment is just not a tool that has a lot of meaning in the LibreOffice project (and most other FOSS) because, as has been mentioned, development and quashing of bugs is driven by the interests of the respective developers. Some developers will assign to themselves, some will not--personal choice.

Maybe there's hope after all, as I've got a list from long ago that I
never bothered to file as these were never addressed and assigned, so I
never bothered.

Can't help but notice that in the ensuing time you have moved from OSX 10.6.8 to your current 10.8.3 build, yet YOU have not filed additional updates or status regards either issue. Truth is issues with OSX builds require a lot of care and feeding given the rapid changes to Apples APIs. If you want things fixed you have to be engaged and nurture the issues you raise. Please take the time to research the FDO Bugzilla ( https://bugs.freedesktop.org/query.cgi?format=advanced&product=LibreOffice ) and if not already identified, submit as new issues items from your list.

You should have a look at the OSX issues meta bug https://bugs.freedesktop.org/show_bug.cgi?id=42082 and you'll get some idea.

Regarding fdo#44871, the labeling as Distribute Rows Equally is clearly wrong. Its function is documented as "Space Rows Equally" -- Adjusts the height of the selected rows to match the height of the tallest row in the selection, which it does. So what you were really asking for is an enhancement. Which as was pointed out in comments to 44871 would receive the best review on the UX-Advise list. Did you follow up there? Just looked and saw no record.

So, I've opened a new enhancement request in fdo#64242 and asked the UX-Advise list for discussion--essentially for handling Table columns and rows the UX is a bit muddled between Distribute and Equal Spacing actions.

Stuart

#68

I write letters--where I have a heading saved as a file that I can import--and I write occasionally for publication, in which case I write double-spaced,
extra space for paragraph, and no indent. I don't need any kind of "style" to do that--I can set the double space once per article--that is no more
trouble than finding and turning on a preset style, which I could only do if I knew how to create it in the first place. And I edit material sent for a
newsletter of some 1000 circulation, for which the publisher uses Pagemaker on a Mac to format it. I don't know, but I think any kind of style
setting would go bonkers seeing the formats that come in and trying to mold them into something consistent. I mold them fairly easily in a word
processor, by hand. And I save in MS .doc 1997~2003 format, because everybody in the world can read that. And I write emails, and all I need to
do is fix typos, which styles can't do!

I rest my case. --doug

#69

Hi :slight_smile:
I am not sure if people are aware but under Sun a lot of bugs just got ignored or left to rot because the aim at that time was stability.  If a bug is known about and still exists in a new version then that qualifies as being "stable".  Unstable is where you can't rely on long running bugs still being around.  If you are not sure whether something has been fixed or not then it really means the thing is unstable.  Companies using the program may have written work-around or patches that they applied each time to each new release but if a particular problem had been sorted out in a newer version then should such a company apply their patch or not!  So, Sun wanted "stability" so that companies could rely on all the problems being well known.

Hmm, does that sound a tad bitter?  I wasn't even around for that.  I used Go-oo without even knowing that it wasn't pure OOo for the last couple of years that OOo was under Sun.  Before that i was an MS fanboy.

Under TDF the main aim has been to declutter all the code, streamline it, remove old outdate comments and translate the remaining ones into English.  Also re-writting chunks done in weird languages, such as Java, in order to consolidate it into just 1 language throughout and generally de-spaghettfy it.  At the same time they have also managed to add in 'new' functionality to help bring the program out of the late 90's and well into this century.  They've also fixed quite a lot of bugs although mostly that has been to try to make it compatible with the latest changes in the MS formats.  I think they have done a remarkable job.

Now it should be easier to address individuals bugs.  Many of which have probably just dropped out due to the de-spaghettifying.

You could help by test-driving the latest beta-release each time and adding a comment to your bug-report to let people know that it still exists.  if you leave bug-reports until after release then less people will be looking into it.  Pre-release catches the attention of the most devs.

I don't think it's fair to blame TDF for the failures of Oracle or Sun and it's not fair to assume that just because your pet peeves haven't been sorted by Sun that they are not going to be sorted under TDF. 
Regards from
Tom :slight_smile:

#70

Hi, Stuart,

I hope my manual reformatting of your reply works out. Most of the time, there's a failure somewhere down the road. :frowning: You are the 2nd poster whose messages display correctly, but do not format correctly when using the Reply/Followup option in Thunderbird. I do not know where the fault lays.

From: Ken Springer [snowshed1@q.com]
Sent: Sunday, May 05, 2013 7:49 AM
To: users@global.libreoffice.org
Subject: [libreoffice-users] Re: Paragraph styles

https://bugs.freedesktop.org/show_bug.cgi?id=44871
https://bugs.freedesktop.org/show_bug.cgi?id=46986

Will wonders never cease... The first one has been assigned to someone.

Actually, FDO bug 44871 has been "assigned" since the date it was submitted

> during QA bug triage. But that means exactly squat since Cedric did not
> assign himself (indicating he accepted and was working on it).

Assignment is just not a tool that has a lot of meaning in the LibreOffice project

> (and most other FOSS) because, as has been mentioned, development and
> quashing of bugs is driven by the interests of the respective developers. Some
> developers will assign to themselves, some will not--personal choice.

I've noticed that in other FOSS software. :frowning:

IMO, that's not a professional approach, and has to change for any FOSS project to be considered for going head to head with good commercial software.

I seem to be one of the dwindling few that have not lowered their standards to get along with the rest of the world. As George Bernard Shaw said, "Reasonable people adapt themselves to the world. Unreasonable people attempt to adapt the world to themselves. All progress, therefore, depends on unreasonable people."

Maybe there's hope after all, as I've got a list from long ago that I
never bothered to file as these were never addressed and assigned, so I
never bothered.

Can't help but notice that in the ensuing time you have moved from OSX

> 10.6.8 to your current 10.8.3 build, yet YOU have not filed additional
> updates or status regards either issue. Truth is issues with OSX builds
> require a lot of care and feeding given the rapid changes to Apples APIs.
> If you want things fixed you have to be engaged and nurture the issues
> you raise. Please take the time to research the FDO Bugzilla
> ( https://bugs.freedesktop.org/query.cgi?format=advanced&product=LibreOffice )
> and if not already identified, submit as new issues items from your list.

That's because I quit checking on their status over a year ago, when I was still using 10.6.8. :slight_smile: The only reason I know now is because Milos wanted to know the Bugzilla numbers.

And because nothing was happening, I lost any interest in even reporting other issues I found. That's a two-way street. If my submissions aren't of any import to them, why should I help? I can simply go buy a program that works. :slight_smile:

You should have a look at the OSX issues meta bug

> https://bugs.freedesktop.org/show_bug.cgi?id=42082
> and you'll get some idea.

There's a lot of work to be done, but fixing the interface is eye candy if the features and functions don't perform. I originally started out with NeoOffice, and when I found issues there, I discovered I had to pay to post in the NeoOffice forum. Not going to happen. I pay my car mechanic to fix the problem, not tell him about the problem. I've not used NeoOffice since.

Regarding fdo#44871, the labeling as Distribute Rows Equally is clearly

> wrong. Its function is documented as "Space Rows Equally" -- Adjusts the
> height of the selected rows to match the height of the tallest row in the selection,
< which it does. So what you were really asking for is an enhancement. Which as
> was pointed out in comments to 44871 would receive the best review on the
> UX-Advise list. Did you follow up there? Just looked and saw no record.

"... is clearly wrong." Your words. :slight_smile: That means error, something needs to be fixed. I just checked, http://thesaurus.com/browse/enhancement?s=t and nowhere will you find the word fix or similar listed as a synonym for the word enhancement.

A bug is something that needs to be fixed, not made prettier, not something new added. <grin>

So, I've opened a new enhancement request in fdo#64242 and asked the UX-Advise list

> for discussion--essentially for handling Table columns and rows the UX is a bit
> muddled between Distribute and Equal Spacing actions.

I actually think both ideas would be valid.

#71

Hi :slight_smile:
+1
*  Text editor = plain text with no formatting

*  Word-processors allow you to add little bits of formatting as and when you want.  Results look a little different on each different machine but it's easy for people to edit and collaborate.  It's more about the process of writing than about the final result

*  Desktop publishing is all about the final result.  Consistent, well laid out.  The same on every machine and every printer.

LibreOffice seems to straddle both word-processing and, to some extent, desktop publishing.  It can be used just as a word-processor, like Word, but then you miss the opportunity of getting faster and better results.  The important thing, imo, is that it's your choice.  Many of us start using it just as a word-processor and then take advantage of the extra bits once we have worked out the style we want to aim for with the document.  Sometimes the document is already finished before we've even thought about layout and it looks fine.  You don't need to have any clue about how the final document will look when you start.  You can just jump in and figure it out as you go along.

LaTex, Inkscape(?), Scribus and others are almost purely about Desktop Publishing.  You kinda have to know what you are aiming for before you start.  You probably can "rough it" a bit but it's going to be awkward.

Just my thoughts from what people have written in this thread and from my own limited experiences.

Regards from

Tom :slight_smile: