Bug 116134 - Misalignment & wrong direction of Arabic contents in output EPUB when export from office to EPUB
Summary: Misalignment & wrong direction of Arabic contents in output EPUB when export ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.2.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: EPUB-Export
  Show dependency treegraph
 
Reported: 2018-03-01 20:23 UTC by yousifjkadom
Modified: 2024-08-26 03:15 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
arabic document (4.38 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2018-03-01 20:24 UTC, yousifjkadom
Details
output EPUB (2.46 KB, application/epub+zip)
2018-03-01 20:25 UTC, yousifjkadom
Details

Note You need to log in before you can comment on or make changes to this bug.
Description yousifjkadom 2018-03-01 20:23:35 UTC
Hi. I tried "export to EPUB" new functionality on office document in Arabic language. 

Frankly speaking, I was expecting a rubbish symbols of unknown meaning .....

But, output EPUB file was beyond my imagination: Arabic contents displayed correctly BUT with only one defect: alignment & direction of sentances is to the left (from left to right).

Please notice when I said direction is from left to right I do not mean that words rearrange inversely. But, I mean that character like "!" at the end of the line will appear in EPUB at the beginning of the line.

Please compare attached files (original office & EPUB)
Comment 1 yousifjkadom 2018-03-01 20:24:58 UTC
Created attachment 140275 [details]
arabic document
Comment 2 yousifjkadom 2018-03-01 20:25:55 UTC
Created attachment 140276 [details]
output EPUB
Comment 3 Aron Budea 2018-03-06 02:42:26 UTC
Hi, thanks for the bug report!
Confirmed using LO 6.1 master build (bc6f3c0fe95f9162fb14dc540fa2b4bc81af32bf) / Windows 7.
Comment 4 yousifjkadom 2018-11-09 04:24:11 UTC
Hi. I test bug on version 6.1.3.2 LO as AppImage. It is still existing without any improvement.
Comment 5 lbartolome 2018-11-16 19:17:27 UTC
Confirmed in Versión: 6.2.0.0.alpha1 (x64)
Id. de compilación: ff46ad24d1d3cbcea45895520483ed1fd4ff488b
Subprocs. CPU: 2; SO: Windows 10.0; Repres. IU: predet.; VCL: win; 
Configuración regional: es-ES (es_ES); Calc: threaded

Looks like it is related with the styles/language export I mentioned in bug 121449.

I'm comparing again outputs from both filters for additional information.

LO6.2 
<body class="body0" xmlns:epub="http://www.idpf.org/2007/ops">
<p class="para0"><span class="span0">تحية طيبة !</span></p>
<p class="para0"><span class="span0">احي فريق تطوير برنامج ليبري اوفس لجهودهم الجبارة في تطوير هذا البرنامج المجاني المفتوح المصدر واتمنى لهم التوفيق في جهودهم الجبارة لما فيه فائدة </span><span class="span0">&#160;</span><span class="span0">المجتمع.</span></p>
</body>

Style sheet from L 6.2 native epub filter
.para0 {
  line-height: 150.0000%;
  margin:  0px 0px 0px 0px;
  text-align: justify;
}

.span0 {
  font-family: 'Arial';
  font-size: 16.0000pt;
}

.body0 {
  -epub-writing-mode: horizontal-tb;
  -webkit-writing-mode: horizontal-tb;
  direction: ltr;
  writing-mode: horizontal-tb;
}



Writer2html 1.6.1 (it has it's own bugs like the style sheet not formatting properly contrary to the native epub)
  <body dir="rtl">
    <p class="Standard" dir="rtl" style="text-align:justify">تحية طيبة !</p>
    <p class="Standard" dir="rtl" style="text-align:justify">احي فريق تطوير برنامج ليبري اوفس لجهودهم الجبارة في تطوير هذا البرنامج المجاني المفتوح المصدر واتمنى لهم التوفيق في جهودهم الجبارة لما فيه فائدة &#160;المجتمع.</p>
</body>


I'm copying Mark and Miklos, which I understand are involved in epub filter.
Comment 6 QA Administrators 2019-11-17 03:32:04 UTC Comment hidden (obsolete)
Comment 7 yousifjkadom 2019-11-17 08:41:05 UTC
I tested this issue on last available AppImage fresh version & it is still existing !
Comment 8 Aron Budea 2019-11-17 15:15:23 UTC
(In reply to yousifjkadom from comment #7)
> I tested this issue on last available AppImage fresh version & it is still
> existing !
Thanks for rechecking! Please also add version information from Help -> About, so the version can be known without having to look up which AppImage was current at the time.
Comment 9 yousifjkadom 2019-11-18 06:39:01 UTC
Last available fresh standard AppImage is version 6.3.3.2
Comment 10 yousifjkadom 2020-08-24 14:03:16 UTC
I tested the issue with version 7.0.0.3 from FlatHub & still existing.
Comment 11 QA Administrators 2022-08-25 03:43:12 UTC Comment hidden (obsolete)
Comment 12 yousifjkadom 2022-08-26 10:23:35 UTC
Hello. I tested this issue on LibreOffice version 7.4.0.3 (flatpak version from FlatHub). 

Unfortunately, it is still existing without any fix or improvement!

I will change the version in this issue from 6.0.2.1 into 7.4.0.3.
Comment 13 Michael Warner 2022-08-26 14:21:18 UTC
(In reply to yousifjkadom from comment #12)
> Hello. I tested this issue on LibreOffice version 7.4.0.3 (flatpak version
> from FlatHub). 
> 
> Unfortunately, it is still existing without any fix or improvement!

I'm sorry to say, there are not many developers on this project relative to its size and complexity.

> 
> I will change the version in this issue from 6.0.2.1 into 7.4.0.3.

The version field is for the earliest known version in which the issue is present, NOT the most recent known version. We don't need the most recent known version because if the Status is NEW then the bug is presumed to be still be present in every version since the one it was discovered in. 

You can find descriptions for every Bug Field here:
https://bugs.documentfoundation.org/page.cgi?id=fields.html

I have reset the version field to 6.0.2.1.
Comment 14 QA Administrators 2024-08-26 03:15:38 UTC
Dear yousifjkadom,

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 with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug