> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, March 28, 2007 11:09 AM
> 
> Hi Kirill,
> 
> On 03/27/07 17:43, Kirill S. Palagin wrote:
> 
> > Also the problem greatly affects scientific and academic 
> environments 
> > - they need to follow certain rules and just can't 
> introduce paragraph 
> > breaks on a whim of word processor. Academic environments are very 
> > important as they basically set person's habits for good 
> part of life 
> > and we want to be in there.
> 
> I still don't understand that requirement. What academic 
> environment does not allow the use of paragraph breaks? How 
> can one distinguish a paragraph break from a manual line break?
> 
> As OS already pointed out in his comment to i17171, this is 
> *not* easy to resolve. In Writer, we would either have to 
> extend the length of the currently used string type to 4 
> bytes or switch to rtl::OUString. In both case we would have 
> to check each and every code involving text that the string 
> index variables working on that text are adapted to 4 bytes 
> as well. Beside this, *very* long paragraphs tend to decrease 
> the performance of text editing, this has to be taken care 
> for as well.
> 
> Best regards,
> 
> Frank

Frank,
Thanks for the response.

I actually have two requirements - 
1. Fix the code in a way that would allow reasonably unlimited paragraph
sizes. I understand that the amount of code to be reviewed is
non-trivial, but this limitation seems to affect considerable number of
our customers (just see how many dups and votes we have). As far as
performance goes, slower machines will be replaced long before we fix
the problem (or so it seems).
Also recently we have published the document "Comparison of
OpenOffice.org 2 and MS-Office 2007" at
http://www.openoffice.org/product/more.html . The document contains
assertion that we are particularly good at handling long documents -
"OpenOffice.org software strength is in handling long documents.", yet
we have this embarassing problem.

2. If fixing the code is absolutely not an option in next several years
please at least stop user from shooting himself in the foot and disallow
removing autogenerated paragraph break - see comments by 

"allsorts46 Tue Oct 4 20:19:06 +0000 2005 
This is still a serious issue, as it causes loss of data which cannot be
recovered (by 'undo' or other means, except entirely reloading the
document,
assuming you are fortunate enough to have noticed before you saved,
overwriting
the original).

Please read http://www.openoffice.org/issues/show_bug.cgi?id=55464.

At the very least, Writer should not allow any actions that would cause
this to
happen, and present an error and explanation to the user. Simply
'losing' the
text is unnaceptable".

Thanks a lot for yout attention.
WBR,
K. Palagin.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  • [sw-discussion... Kirill S. Palagin
    • Re: [sw-d... Frank Meies - Sun Germany - Development - Software Engineer
    • RE: [sw-d... Kirill S. Palagin
      • Re: [... Frank Meies - Sun Germany - Development - Software Engineer
        • R... Matthias B.
          • ... Frank Meies - Sun Germany - Development - Software Engineer
          • ... Mathias Bauer
      • Re: [... Cor Nouws
    • RE: [sw-d... Kirill S. Palagin
      • Re: [... Frank Meies - Sun Germany - Development - Software Engineer

Reply via email to