Issue 10222 - Text box break between pages
Summary: Text box break between pages
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Linux, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-19 18:57 UTC by rblackeagle
Modified: 2013-07-19 20:54 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Example of inserted page offset destroying page count (11.84 KB, application/octet-stream)
2003-11-15 19:58 UTC, rblackeagle
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description rblackeagle 2002-12-19 18:57:29 UTC
At present, making a text box at a location that includes a page break puts the entire text box on the second page.  Further, a text box cannot exceed a page in size.  There are numerous occasions when it would be very useful to have a text box that spans pages.
Comment 1 h.ilter 2003-01-07 16:46:48 UTC
Reassigned to BH
Comment 2 eric.savary 2003-04-16 15:32:51 UTC
Set to "NEW"
Comment 3 rblackeagle 2003-08-17 04:34:14 UTC
Has anyone looked at this?  The problem seems to persist in RC3.
Comment 4 rblackeagle 2003-10-05 23:16:57 UTC
Set to "New", assigned to BH. Has anything else been done on this?  
It may be related to a number of other issues, so I'd like to know.  
I can't get to a computer using OOo, so I'd like to hear if anyone's 
tested it with 1.1.0.
Comment 5 rblackeagle 2003-11-15 19:58:53 UTC
Created attachment 11300 [details]
Example of inserted page offset destroying page count
Comment 6 rblackeagle 2004-03-05 20:28:56 UTC
1.1.1rc (linux): Yech!!! Worse than ever.  Text box overlaps blank space between
pages.  The best way to describe the printed text is that is "slops" over onto
the next page with no regard for pagination, margins or anything else.
Comment 7 ace_dent 2008-05-16 02:39:01 UTC
OpenOffice.org Issue Tracker - Feedback Request.

The Issue you raised has the status 'New' pending further action, but has not
been updated within the last 4 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version: http://download.openoffice.org/index.html
or consider trying the new OOo 3 BETA (still in testing):
http://download.openoffice.org/3.0beta/
 
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
http://www.openoffice.org/issues/query.cgi
 
Many thanks,
Andrew
 
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 8 bettina.haberer 2010-05-21 14:49:12 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements". 
Comment 9 cwscott 2013-07-19 20:54:17 UTC
The comment,

https://issues.apache.org/ooo/show_bug.cgi?id=10222#c7
Comment 7
ace_dent 2008-05-16 02:39:01 UTC

requests that somebody tests this problem with an updated version of OpenOffice.

That request was made in 2008. 5 years ago.

I recently came across exactly the same problem and decided to check the bug register. To my amazement this problem was first registered in 2002-11. Nearly 11 (ELEVEN) years ago!

I am using OO 3.4.1.

It looks really, really, bad when a bug as obvious as this stays unresolved for 11 years.


While I am about it let me explain why I found the bug, in the hopes that some other related bugs/feature requests can be directed to the correct place.

Where I live there is a need for a very simple data collection tool which it seems OO already has 95% (if not more) of the capability of providing.

Basically what is needed is a digital read-only question and answer (Q+A) document in which the answer fields are initially blank, editable, growable, text boxes into which respondents can type their answers. There could be a number of ways of saving this document/data: the whole document, read-only questions and respondent edited answers, could be saved together in a read+copy-only PDF (perhaps with a predefined filename derived in a systematic way with timestamps from the base Q+A filename); alternatively the answers alone could be saved in a structured format such as XML, which could subsequently be used to allow the data to be brought into a database or even, simply, into a table in an ODT document. Basically the result of the digital Q+A session should be simply and conveniently savable on a local disk in a non-editable form which can subsequently be emailed to an appropriate destination for analysis.

The creation of the base read-only Q+A document, edit protected with a password, and with unprotected editable response fields, is fully provided for by my current version of OO, 3.4.1 (except for the current bug, that is). What is obviously missing at the moment is any simple and obvious ways to save the respondents replies (there are workarounds, but they are very clumsy, and go completely against the idea of a tool for reliably collecting replies from respondents who are completely untutored in OO, and basically just know how to read the questions and type straightforward text replies).

Where within Bugzilla should I direct my ideas on this matter?

regards,

Chris Scott