https://bugs.kde.org/show_bug.cgi?id=412516
--- Comment #2 from David C. Bryant <davidbry...@gvtc.com> --- (In reply to Christoph Cullmann from comment #1) > Hmm, can not really reproduce that here. > Is there a chance that you could update your KDE Frameworks version? Probably not. I'm not ready to try compiling something as complex as that from source. I'm basically a user who depends on pre-compiled binary packages, who *used* to be a programmer (IBM mainframes, in assembly language, mainly -- I'm old), and who is willing to help write KDE documentation. I have observed this bug on three different Linux platforms, all of which are installed on the same PC (Dell XPS 8930). Neon 5.16.4 (Plasma 5.16.5 Frameworks 5.62.0 Qt 5.13.1) SUSE LEAP 15.1 (Plasma 5.12.8 Frameworks 5.55.0 Qt 5.9.7) Debian 10.0 (Plasma 5.14.5 Frameworks 5.54.0 Qt 5.11.3) Kate / Kwrite version is 18.12.3 on SUSE, 18.08.0 on Debian. I don't have either Kate or KWrite installed on the Neon system any longer. That is where I first noticed the problem (in late August). I eventually moved my KAddressBook documentation project to the SUSE platform, and only used Neon for "arcanist", to upload stuff to Phabricator. I uninstalled Kate / KWrite because there were already enough updates to apply every time I booted into Neon. As a former programmer, I understand that this is the worst kind of bug, because it doesn't happen very often, and it's almost impossible to reproduce. I don't suppose it will get resolved unless a lot of other people also report it. Not to worry ... I haven't had the problem with gedit, and Kate / Kwrite works fine when I'm editing smaller documents. So I can patch around the problem. I didn't report this as a bug for about two months after I first noticed it. I knew Neon was buggy because there are a lot of new packages going in regularly. I finally decided to file this bug after it bit me on three different platforms. It generally happened with very large documents (2,000 lines of text, or so). I am certain it did in fact occur many times -- I would copy a small snippet of XML text (or straight data, like half of a sentence) and paste it in exactly one place (^C and ^V -- I rarely use the edit menu -- force of habit, I suppose), but when I ran "checkXML5" (a syntax checking program for .docbook files written in XML), it would report four or five errors, which were usually about CDATA (text appearing in areas between XML tags that ought not contain anything except white space) or breaking the DTD rules (XML tags appearing somewhere where the syntax rules said "No way, José"). When I tracked the errors down, they were all exactly the same "CDATA" or XML code sprinkled around the document in locations far away from the place where my cursor had been when I hit ^V. And I always recognized the errant character string as a bit of text I had copied from one spot to another during my previous editing session. Thanks for looking into it, Christoph! -- You are receiving this mail because: You are watching all bug changes.
