![]() Mozilla/5.0 (compatible Windows NT 10.0 U WOW64 IA64 en) AppleWebKit/599.0+ (KHTML, like Gecko) Maxthon/4. Mozilla/5.0 (compatible Windows NT 6.1 U WOW64 IA64 en) AppleWebKit/599.0+ (KHTML, like Gecko) Maxthon/4. Mozilla/5.0 (compatible Windows NT 10.0 U WOW64 IA64 en) AppleWebKit/599.0+ (KHTML, like Gecko) Maxthon/5. Mozilla/5.0 (compatible Windows NT 6.1 U WOW64 IA64 en) AppleWebKit/599.0+ (KHTML, like Gecko) Maxthon/5. If the bug was not present in 3.Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) QupZilla/7.0.8 Chrome/.140 Safari/537.36 If the bug was present with 3.3 - set version to 'inherited from OOo' Ĥb. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from Ĥa. If you want to do more to help you can test to see if your issue is a REGRESSION. Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not Reply via email (please reply directly on the bug tracker) If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. Test to see if the bug is still present with the latest version of LibreOffice from If you have time, please do the following: We'd really appreciate your help in getting confirmation that the bug is still present. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. There have been thousands of bug fixes and commits since anyone checked on this bug report. To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. ![]() Saving As RTF may lose some formatting (in this case, there's no change in page style after p.1), but page break should have been retained, and the header text of p.2 at least put at the top of p.2 - but since opening the original showed a header change correctly, perhaps a page style change should have been forced? ![]() Header text from p.2 is in footnote on p.1īetter handling. On re-opening the saved file, the distortions are seen. After opening the sample RTF, which is correctly rendered, if the file is saved s RTF (I used a new filename in testing), the page break is lost (see Bug 116753) and the header text from p.2 is put in a footnote on p.1. ![]()
0 Comments
Leave a Reply. |