| Summary: | RTL: DOC: closing parenthesis is displayed as LTR in embedded document | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Xisco Faulí <xiscofauli> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | aron.budea, ilmari.lauhakangas, marklh9, suokunlong, xiscofauli |
| Priority: | medium | ||
| Version: | Inherited From OOo | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=60533 https://bugs.documentfoundation.org/show_bug.cgi?id=89224 |
||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 43808 | ||
| Attachments: | comparison MSO 2010 and LibreOffice 6.2 | ||
|
Description
Xisco Faulí
2018-09-10 14:24:07 UTC
@Mark Hung, Since you fixed bug 60533, I thought you could be interested in this issue... The LibreOffice version is the image has seriously broken Arabic text; the spacing is incorrect, lots of letters overlap and even complete words are misplaced. Most probably something is seriously broken with layout of fallback fonts. (In reply to Khaled Hosny from comment #2) It doesn't look like that to me (In reply to Xisco Faulí from comment #0) The attachment is very weird, it seems to have a WMF object embedded in it. I'm not even sure it's LO that's rendering that text. Can you reproduce this bug with a simpler document? Confirmed. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: 36befb3aca96907a14e71e82497dbb8f03ead5ab CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); Calc: threaded Built on 3 October 2018 Dear Xisco Faulí, 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! Warm Regards, QA Team MassPing-UntouchedBug Still reproducible in Version: 6.4.0.0.alpha0+ Build ID: c9336bfb6bbf6d73d3f23c124262ade30133448d CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded @Mark Hung, I thought you might be interested in this issue... Bug finding is the best technique for making your non-running code into the running form. The code we write in https://aussiessayreviews.com/ is only runnable when you will be able to find the bug. Bug removing is the most important work which you can do. Bug finding is the best technique for making your non-running code into the running form. The code we write in https://aussiessayreviews.com/ is only runnable when you will be able to find the bug. Bug removing is the most important work which you can do. Bug finding is the best technique for making your non-running code into the running form. The code we write in https://aussiessayreviews.com/ is only runnable when you will be able to find the bug. Bug removing is the most important work which you can do. Bug finding is the best technique for making your non-running code into the running form. The code we write in https://aussiessayreviews.com/ is only runnable when you will be able to find the bug. Bug removing is the most important work which you can do. Bug finding is the best technique for making your non-running code into the running form. The code we write in https://aussiessayreviews.com/ is only runnable when you will be able to find the bug. Bug removing is the most important work which you can do. Bug finding is the best technique for making your non-running code into the running form. The code we write in https://aussiessayreviews.com/ is only runnable when you will be able to find the bug. Bug removing is the most important work which you can do. Dear Xisco Faulí, 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 Still reproducible in Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ebe151d919a454f98c36013245bca9eb41d92707 CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded @Kevin, I thought you might be interested in this issue |