Any way to expedite the process of fixing this bug?

(In reply to Jack from comment #5)
> Any way to expedite the process of fixing this bug?

Money: https://www.documentfoundation.org/gethelp/developers/

(In reply to Jack from comment #5)
> Any way to expedite the process of fixing this bug?

With open source there are always 4 options:
1) Fix it yourself;
2) Find a friend, family member, colleague to fix it;
3) Pay for a fix -> almost always out of the reach for a single individual.....assume at least 1k generally (10 hours at about $100/hr) minimum
4) Wait for a volunteer to take interest, could be tomorrow, could be years from now

Unfortunately for that amount of money I can buy 10 licenses for Microsoft Office 2016 Professional Plus which has much better support for RTL languages, so it's simply not cost-effective. If I ever run a business that requires dozens or more Office users, I'll invest in improving LibreOffice.

(In reply to Joel Madero from comment #7)
> (In reply to Jack from comment #5)
> individual.....assume at least 1k generally (10 hours at about $100/hr)
> minimum

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice 
(5.2.7 or 5.3.3  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and 
your operating system, and any changes you see in the bug behavior
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20170522