<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Writer: SVG, TEXT, spacing, sorting, copying, displaying bugs galore"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108716">108716</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Writer: SVG, TEXT, spacing, sorting, copying, displaying bugs galore
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>Mac OS X (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Writer
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>deepflight5@mailinator.com
</td>
</tr></table>
<p>
<div>
<pre>BUG 1) LO Writer forgets how items are stacked upon another after reopening of
a document. It forgets the order of sorting if there are two or three SVGs
laying upon another (or a text frame on a SVG image) and are sorted by "send to
back" and "send to front". Sometimes when opening a documents it is OK,
oftentimes it is messed up. LO does not remember how they were put. This messes
up the design of a document and one cannot trust LO Writer. This bug happens
often, after inserting additional SVGs on other pages of the document, then
closing the document and open it again.
BUG 2) I write several Writer documents including SVG files. Then I put them
together by "manual page break", so they are in one document but separate from
each other. Sadly this is in LO Writer only theoretically. If I edit one
document in the middle of the put together document, and the text exceeds over
the end of that document, SVGs in the following documents disappear until I
reopen the whole document.
BUG 3) You have a main Writer document. When adding (by manual page break) a
second document that includes SVGs, those SVGs are not imported. You have to
manually place them from the second document to the main document. JPG images
are also not imported.
BUG 4) If you have a JPG image and use the context menu command to add a
description, it creates a frame around the picture, but the image doesn’t sit
exactly on top of the frame bit 1 millimetre below. The created text has huge
spacing, but using the paragraph command and make the line spacing 80 or 90 %
proportional messes up the placing of the image, some parts disappear.
BUG 5) When proportionally reducing "line width" of a paragraph (for example to
90 %) the first and second line move closer together than the others. If
further reducing line width this effect becomes more severe.
BUG 6) When I copy parts of a Writer document (text, image, SVG) by pressing
CMD-C (on OSX) Writer oftentimes (in three out of four cases) inserts at this
place a bookmark.
BUG 7) In full-screen mode it is possible to edit a Writer document, but it is
impossible to save it. CMD-S (on OSX) doesn’t work.
BUG 8) Moving selected text from a Writer document to the OSX desktop (called
Finder) deletes the text from the Writer document. Expected behaviour is simply
to place a Text-Clip on the desktop with the text in the Writer document
unaltered (as any text application in OSX does).
BUG 9) LO 5.3 seems to have changed the font-rendering. All fonts in sizes of
12 point or lower (the usual size for editing documents) have terrible spacing,
letters move/smear into another, spaces disappear. With this major bug I’m
stuck with LO 5.2.7.2. Designing a newsletter in WYSIWYG is now impossible.
Finally: I always have to triple check, if there are missing SVGs and messed up
designs, when I am opening a Writer document. I don’t do anything exotic, but
LO is quite buggy for serious use. Meanwhile I know how to work around all
those bugs, but it costs time.
LO 5.2.7.2 and older</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>