Bug 143056 - [EMF+] StringFormat Tracking is not supported
Summary: [EMF+] StringFormat Tracking is not supported
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
(earliest affected)
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: EMF-WMF
  Show dependency treegraph
Reported: 2021-06-25 01:36 UTC by Valek Filippov
Modified: 2023-07-15 03:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

EMF sample with StringFormat tracking set to 1.5 (916 bytes, image/x-emf)
2021-06-25 01:37 UTC, Valek Filippov
Screenshot of the sample opened in LO7.3alpha and MS Paint (5.42 KB, image/png)
2021-06-25 01:38 UTC, Valek Filippov

Note You need to log in before you can comment on or make changes to this bug.
Description Valek Filippov 2021-06-25 01:36:22 UTC
LO seems to ignore tracking value of StringFormat

Steps to Reproduce:
Open attached EMF sample.

Actual Results:
LO shows three lines of text with normal spreading of the characters.

Expected Results:
These lines should have wide spaces between characters to almost touch thin vertical red lines.

Reproducible: Always

User Profile Reset: No

Additional Info:
Looks like the actual extent of the text block includes a space after the last character. Because of that  "HRVT" string has a gap on the right.
Comment 1 Valek Filippov 2021-06-25 01:37:15 UTC
Created attachment 173184 [details]
EMF sample with StringFormat tracking set to 1.5
Comment 2 Valek Filippov 2021-06-25 01:38:48 UTC
Created attachment 173185 [details]
Screenshot of the sample opened in LO7.3alpha and MS Paint
Comment 3 QA Administrators 2023-07-15 03:13:18 UTC
Dear Valek Filippov,

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