I was testing the MOX-conversion with the new version 7.5 in writer. Chapeau! What unbelievable progress has been made! Only, there are very few documents that convert still bad. I remember, in the olden days, firefox had functionality to report websites that didn't render correctly. I think that was smart. The average user doesn't make a bug-rapport. And imho one couldn't ask him to do so. But perhaps they would submit their documents in this way. That could be of use to the developers. Just a thought.
This functionality could perhaps ask the user to specify the component of the LO-suite, give a short discription of what went wrong and submit the file.
Hi Pieter, (In reply to pieter kristensen from comment #0) > I was testing the MOX-conversion with the new version 7.5 in writer. > Chapeau! > What unbelievable progress has been made! Thanks - and I think you are right :) > Only, there are very few documents that convert still bad. > I remember, in the olden days, firefox had functionality to report websites > that didn't render correctly. I think that was smart. The average user > doesn't make a bug-rapport. And imho one couldn't ask him to do so. I agree that filing a proper bug report is not easy for many users. Luckily, there are also many with more understanding of the office suite and the files they use. > But perhaps they would submit their documents in this way. That could be of > use to the developers. If a document is provided with the message "it does not show correct", then someone needs to find out what. We - the community as a whole - try to prevent that developers need to do too much of that work. So we ask a description of "what does not correct" - thus how it should be. Screen prints.. And then people helping with CA - volunteers and staff - will ask questions, do some tests, to find more specific what the problem is. Maybe the bug is already reported, maybe it is new information to an existing bug. So I understand and respect that you ask for an easy way to .. but in practice it is often some work, with difficult elements. And if users (reporters) try to work together with the more active members in the CA-community, that works best. Thus: reporting of bugs is handled by the QA-community in TDF. There is information on the wiki: https://wiki.documentfoundation.org/QA/ https://wiki.documentfoundation.org/QA/BugReport To get an idea of e.g. reports around DOCX, pick some from this query: https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=Writer&f1=short_desc&f2=short_desc&j_top=OR&keywords=docx&keywords_type=allwords&list_id=1558883&product=LibreOffice&query_format=advanced And sorry that I was busy and didn't yet respond to the discussion on the Dutch mailing list. Will do know. Your suggestion does not really belong here - so I close the 'bug' as invalid :) But let's talk more at another place! Cheers - Cor
And, under Help you'll find Send Feedback, leading to e.g. this page https://www.libreoffice.org/get-help/feedback/?LOversion=7.6.0.0.alpha0&LOlocale=en-US&LOmodule=StartModule where Create a Bug report is mentioned clearly. Maybe the QA team can think about if that website can hint more specific at reporting rendering bugs? Maybe a link to a wiki, where say three links are provided that are for rendering bugs in Writer, Calc, Impress? OTHO, for filing a bug you need to have an account, and .. So all in all, I doubt if that will make it really easier for 'the broader QA-community' to get the important stuff visible and clearly reported.
Thank you Cor. So, I didn't ever notice or payed attention to the entry under Help. That could also be due to the fact that "Send Feedback" is almost impossible to translate in Dutch. Google translate suggests "Stuur Feedback"... I wouldn't call that an elegant translation but imho it is more informative than "Reactie zenden". Personally I would even find "Contact" more to the point...