`Export to PDF` of the writer doc in which there are Cyrillic glyphs combined with combining accent (U+0301) may produce unexpected space after such combined glyphs in the PDF output (but not in the source ODT). PDF type (1-A or not) does not matter.
However, if the glyph in question is highlighted, the unexpected space does not appear in PDF output.
This happens at least for the XITS font face version 1.105 (latest). I didn't find another font face triggering this effect yet.
Attached simple source ODT and resulting PDF, as produced here.
Created attachment 112116 [details]
simple deo doc
Created attachment 112117 [details]
pdf output from simple demo doc
(In reply to Yury from comment #0)
> `Export to PDF` of the writer doc in which there are Cyrillic glyphs
> combined with combining accent (U+0301) may produce unexpected space after
> such combined glyphs in the PDF output (but not in the source ODT). PDF type
> (1-A or not) does not matter.
> However, if the glyph in question is highlighted, the unexpected space does
> not appear in PDF output.
> This happens at least for the XITS font face version 1.105 (latest). I
> didn't find another font face triggering this effect yet.
Sounds like we'd need the XITS font for repro. Where can one get that?
Status -> NEEDINFO
> Attached simple source ODT and resulting PDF, as produced here.
Here, in the `releases` secion (and the issue is there with the latest 1.108 release):
4.3.3 and 4.5 PDF exports produce extra space with xits2 example.
3.3.0 PDF export produces extra space with xits1 and xits2 examples.
Ubuntu 14.10 64-bit Version: 126.96.36.199.alpha0+
Build ID: 7201fa0dddd7dd0352f69fd2b2b64efcb361ccad
TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2015-01-11_23:28:55
Build ID: 430m0(Build:2)
** 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.1.5 or 5.2.1 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)
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!
Issue still there in:
Build ID: 31dd62db80d4e60af04904455ec9c9219178d620
CPU Threads: 2; OS Version: Linux 4.4; UI Render: default;
Locale: ru-RU (en_GB.UTF-8); Calc: group
*** This bug has been marked as a duplicate of bug 89246 ***
Thank you for reporting the bug. This issue has previously been reported, so this bug will be resolved as a duplicate of the earlier report. You will automatically be added to the CC list of the other bug.
(In reply to Xisco Faulí from comment #9)
> Hello Yury,
> Thank you for reporting the bug. This issue has previously been reported, so
> this bug will be resolved as a duplicate of the earlier report. You will
> automatically be added to the CC list of the other bug.
Thanks all involved. Actually, my report came in earlier, but never mind. ))