One of the available font effects is striking text with '/' or 'X' characters.
For Right-to-Left text - at least, Hebrew and Arabic - this effect works on-screen, but does not carry over to exported PDFs.
Steps to Reproduce:
1. Type some Hebrew text
2. On the Menus, choose File | Export as... | Export as PDF...
3. Accept the default export options
4. Complete the export to some file
5. Open the PDF file you've created in any PDF viewer
The lines with Latin text and with numbers, which have been struck over with slashes or Xes exhibit those strikes. The lines with Hebrew and Arabic text - do not.
All lines with struck-over text should appear struck over in the PDF as well
User Profile Reset: No
See attachments for an example.
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Created attachment 142457 [details]
Example text with various font effects
This file contains lines with Hebrew, Arabic, Latin and numbers (separately), with different font effects: None, strike-through, striking with / and striking with X. One column has the font set to Arial, the other has it set to David CLM (although David CLM doesn't cover Arabic, so you should get the default.
Created attachment 142458 [details]
Result of exporting the example document to PDF
This exhibits the bug.
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone
else confirms it.
(In reply to Xisco Faulí from comment #3)
> You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone
> else confirms it.
It's not my own bug, actually - it was discussed and confirmed at the link I mentioned. I understand you may not have been able to see that, since it's a conversation in Hebrew. It was confirmed by 4 different people (although 3 of them were not registered users).
Ok, thanks for the information!!
OS: Lubuntu 18.04.1 32 bit
Build ID: 1:6.1.1~rc2-0ubuntu0.18.04.1~lo3
CPU threads: 1; OS: Linux 4.15; UI render: default; VCL: gtk2;
Locale: he-IL (en_US.UTF-8); Calc: group threaded
Dear Eyal Rozenberg,
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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Bug still manifests with:
Build ID: 1:6.3.1-1
CPU threads: 4; OS: Linux 5.2; UI render: default; VCL: gtk3;
Locale: he-IL (en_IL); UI-Language: en-US
(Reproduced by exporting the example document to PDF.)