Created attachment 54652 [details]
sample docx file with an RTL paragraph
When generating a docx file with a RTL paragraph, the paragraph looks fine in LibreOffice.
But when opening the file in MS Word (2007 / 2010) the paragraph appears as LTR.
This commit is relevant for this bug http://cgit.freedesktop.org/libreoffice/core/commit/?id=e9911f12d1e124d1910ac2310c224e66ab365ed4
docx: fdo#43093 fdo#44029 fix the alignment when the paragraph are RTL
It that the latest build still has the problem
(tested using Build ID: cb14b1e56d2aab70d28afca8bf039a27f89671c8)
Hello Ophir Yoktan,
I've tested Faisal's patch and it works for me, can you check again please?
Created attachment 89714 [details]
RTL save bug (created with LO set to RTL locale)
I found one more problem, with LO set to RTL locale (so the default paragraph direction is RTL right aligned): if you open a new document, write some text and save to docx, it will open in MS Word as RTL *left* aligned. Opening the docx in LO still shows RTL right aligned, so it both opening & saving bug.
It's happening only at the beginning of a document, as changing direction\alignment to something else, and later changing back does open\save correctly.
Looks like it caused by the locale where the original document is created, because opening this document in LO set to LTR locale and saving to docx, also shows the bug.
Faisal M. Al-Otaibi committed a patch related to this issue.
It has been pushed to "master":
docx: fdo#44029 export the right alignment when locale are RTL.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
Thank you for all your efforts in fixing docx direction bugs. I really appreciate your patience!
I can confirm the fix with master build. But it's apply only when locale set to RTL. Problem is still there if you open & save using LO with LTR locale, a document previously created with RTL locale. (Isn't it easier to just force LO to always export the alignment regardless the default?) Also would be great if you could commit also to libreoffice-4-2 so all users could benefit your great work in the near future.
To not clutter this bug, I opened Bug 72560 for one more problem. It's unfortunate that after all my intensive tests with real world documents, there are still issues!
You might be also interested in Bug 72017. It's a document created using LO probably before your patches.
Thank you again!
(In reply to comment #6)
> Hi Faisal,
> Thank you for all your efforts in fixing docx direction bugs. I really
> appreciate your patience!
you are welcome :)
and thank you for your test and verified the patches.
> I can confirm the fix with master build. But it's apply only when locale set
> to RTL. Problem is still there if you open & save using LO with LTR locale,
> a document previously created with RTL locale. (Isn't it easier to just
> force LO to always export the alignment regardless the default?) Also would
> be great if you could commit also to libreoffice-4-2 so all users could
> benefit your great work in the near future.
hmmm i can't reproduce it with libreoffice
Build ID: 6e6d0ef0b8fd5b89aeb292700cca3096a03681bf
can you see if it is still there
if yes please upload a test file.
(In reply to comment #7)
> can you see if it is still there
> if yes please upload a test file.
It's reproducible with attachment 89714 [details]. Make sure to set LO to LTR locale. The result document will right aligned with LO, but left aligned with MS Word. Tested with Build ID: 4c539fac018dfd44cd8db52161a8cb930c627da7.
** 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 (4.4.1 or later)
*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)
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 your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
appears to be working on latest version : 22.214.171.124 (Windows)
WFM per comment 10.
I came across this issue and found it was fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=b524cab24b8f7c39104db7842e071599eb1d674f ( at least when attachment 89714 [details] is converted from commandline using --convert-to docx )