On Mon, 22 May 2017 09:57:31 +0200 Peter Kovacs <[email protected]> wrote:
> Thanks for the sum up. > > Still I think we should find a solution. > So i adf backup at the start of editing session to the list. > > Is there a bug for this? There certainly ought be, but I cannot point to one. I think Hagar has remarked on Forum of one instance of spellcheck or file corruption on his (work) Windows system, and with great respect, that might be due to a freak close down on his part. In this sort of fault finding the user reports of their actions are "unreliable", as they often feel they are being trapped into an admission of improper computer use. In ten years of heavy use of StarOffice/OO (last years on linux) I have experienced file corruption or spellcheck problems on very few occasions, caused by unexpected power cuts in storms. My computer experience goes back to 1965 (Fortran II on an IBM 1640), so I am aware of the need for system in their use, Rory > > > Am 22. Mai 2017 09:43:52 MESZ schrieb Rory O'Farrell <[email protected]>: > >On Mon, 22 May 2017 08:23:54 +0200 > >Peter Kovacs <[email protected]> wrote: > > > >> So we have 3 ) critical bugs? > >> > >> 1) # issue > >> 2) spell checker > >> 3) I don't have in mind but Hagar mentioned it in his bugzilla > >thread. > > > > > >The # issue seems caused usually by overhasty close down of the > >computer, after space has been allocated in the zip archive but before > >the data has been written to that space, which on inspection is usually > >00 (zeroes). > > > >The spellchecker problem seems highly user related. In almost all > >cases it is cured by deletion or renaming of the OO user profile. Why > >it sometimes occurs after installation or upgrade of OO I do not know - > >I would guess that this may be caused by "finger trouble" - the user > >using some non-standard method of installation. > > > >Instances of faulty spellchecking on a previously good installation > >seem to arise from partial corruption of registrymodiifications.xcu, > >which may be attributed to over hasty close down of the computer before > >the software/hardware write buffers have flushed to disk (remember that > >modern hard disk drives also have internal data buffering). > > > >Most of these instances of file corruption/faulty spellcheck occur on > >Windows. > > > >Long time computer users, who honour the correct power off procedures, > >do not seem to have these problems. > > > >A major requirement is that the original file should be backed up at > >the start of an editing session, so that in the event of a file > >corruption, only the current edit changes are lost. > > > >Rory > > > >> > >> :( I whish I could start immediately to find solution for them. > >> > >> Am 21. Mai 2017 22:17:02 MESZ schrieb Dave Fisher > ><[email protected]>: > >> >For what it's worth > >> > > >> >Sent from my iPhone > >> > > >> >Begin forwarded message: > >> > > >> >> From: Hugo Costa <[email protected]> > >> >> Date: May 21, 2017 at 1:36:19 PM EDT > >> >> To: "[email protected]" <[email protected]> > >> >> Cc: Rory O'Farrell <[email protected]>, Martin Groenescheij > >> ><[email protected]>, Brian Barker <[email protected]> > >> >> Subject: Re: Problem with Open Office before and after installing > >new > >> >update > >> >> Reply-To: [email protected] > >> >> Reply-To: Hugo Costa <[email protected]> > >> >> > >> >> I begin the campaign : DO NOT UPGRADE the OPEN OFFICE UNLESS > >the > >> >SPELL CHECK IS GOING TO WORK .. I don know who decides when to > >> >upgrade it, but how many of us have a problem with the spell check > >> >after it. > >> >> The solution given, solution at end, made with respect, is > >> >Neanderthal Time !!! > >> >> > >> >> I saw it the same answer before in this "chat"Spell check is an > >> >aptitude old as word editors. Do not touch it. > >> >> > >> >> Letś stand on it : I vote DO NOT UPGRADE the OPEN OFFICE UNLESS > >> >the SPELL CHECK IS GOING TO WORK > >> >> > >> >> > >> >> On Thursday, May 18, 2017 3:52 AM, Rory O'Farrell > >> ><[email protected]> wrote: > >> >> > >> >> > >> >> On Thu, 18 May 2017 01:58:06 +0000 (UTC) > >> >> Matt Wiser <[email protected]> wrote: > >> >> > >> >>> Hi. Matt Wiser here, and I have been a longtime user of > >OpenOffice > >> >since the Win98 days on a desktop, and now on my laptop. Today, I > >> >encountered a problem, and a forum search didn't help. I opened a > >> >document that I had created and saved two years ago, and it had wavy > >> >lines beneath all of the text, something that has never happened > >> >before. I downloaded and installed the update to the new version > >just > >> >released, and the same thing happens! Only by disabling the > >automatic > >> >spell check does the wavy line disappear. Language has been set to > >> >English (USA) as the default setting. What's going on here? > >> >>> Thanks in advance for your assistance, and can someone tell me > >> >what's going on here? I am a casual user of my computer-probably > >with a > >> >Capital C, so, any help is appreciated. > >> >> > >> >> Start by renaming your OpenOffice user profile. > >> >> > >> >> As you are using Windows close OpenOffice and the Quickstarter. > >Open > >> >File > >> >> Explorer. Copy and paste %appdata%\OpenOffice\4 in the File > >Explorer > >> >(sometimes called Windows Explorer) > >> >> Address Bar and press Enter. Rename the "user" folder - "user.old" > >is > >> >a > >> >> good choice. Start OpenOffice. > >> >> > >> >> This cures most spellcheck problems. > >> >> > >> >> -- > >> >> Rory O'Farrell <[email protected]> > >> >> > >> >> > >--------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: [email protected] > >> >> For additional commands, e-mail: [email protected] > >> >> > >> >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > -- Rory O'Farrell <[email protected]> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
