Created attachment 111070 [details] Comparison between Discover and store.kde.org: Description displayed inappropriately See attached screenshot. The first paragraph becomes the Comment, which is inappropriate for a variety of reasons: - It wasn't meant to be displayed this way - If it's long, it will get elided and look ugly - If there's only one paragraph, nothing is displayed in Discover's Description section, as shown in the screenshot
That happens because many resources don't fill in the short summary. We did get bug reports because it was empty and the delegate looked b0rked, so we added such fallback. See KNSResource::comment(). To me the solution is to get hold of the store.kde.org and make sure resources offer the text fields we need.
Is the short summary/comment field not mandatory for KNS items? If it isn't, we should consider making it mandatory, because otherwise clients like Discover are going to display ugly-mis-formatted content forever. Perhaps we should discuss this on https://phabricator.kde.org/project/view/70/?
Er, I mean https://phabricator.kde.org/T8137 Until that's changed (or if it's declined), perhaps we should simply omit the Comment field in Discover for resources that don't provide that information. Trying to synthesize it artificially leads to bad-looking results.
What I was trying to tell you is that we used to omit it, it also looked bad. At the moment, anything we do will look bad so I prefer not to spend time on it until it's not fixed in our main provider.
Hmm, it's hard for me to imagine that omitting the comment could possibly look worse than jamming the entire description into the comment, losing most of it because of eliding, and having no description at all. But I agree that the data source should be improved. Let's focus on that.