https://bugs.documentfoundation.org/show_bug.cgi?id=96416
--- Comment #2 from Luke Kendall <l...@zeta.org.au> --- Interesting that you couldn't reproduce it on Windows. I've done some more investigation, too. The UTF-8 character is in fact in the original .odt file! I don't know how it got in there, though. Do you have any idea how one might accidentally type it from the keyboard? But doesn't that make it especially strange that you couldn't reproduce the problem in the .docx conversion under Windows? I think the safest assumption is that it's possible to somehow generate the character accidentally. I suspect the way to generate it may be similar somehow to the Ctrl-Shift-<space> needed to generate a non breaking space. I suspect I've occasionally mis-keyed that sequence to produce the bad character. Is there any way in LO to find or report on such unusual characters? Or, better still, to make them visible (ideally, as some kind of "illegal character" box)? As thing stand, to find such erroneous characters in a novel produced using LO, you need to manually inspect the result in the Kindle previewer page by page, looking for illegal character indicators. That means the only way I know to find them in LO (if you don't know what may be there) is to arrow past them and notice that the cursor doesn't move. That's a completely impractical mechanism, though. May I suggest this bug, though, is changed from severity "Normal" to "enhancement"? I think it's fundamental cause is user error. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
