Bug 1083520
| Summary: | Some special chars in Headings appear not correctly in the index | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joachim Backes <joachim.backes> | ||||||
| Component: | libreoffice | Assignee: | Caolan McNamara <caolanm> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 22 | CC: | caolanm, dtardon, erack, jgrulich, mstahl, sbergman | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-07-19 11:16:50 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 881750 [details]
the libreoffice document showing the descibed effect
Addendum: The special char is an "Open Symbol" char. The Navigator shows a wrong character too. 0xE47A is in the private use area so its going to appear differently depending on the font, and seeing as it wasn't in the index font an arbitrary font is used that does contain the glyph. I'm not sure if there's a good solution to this (MS Word has the same issue FWIW) Now at least I know it picks "AR PL UMing HK" over "OpenSymbol" because OpenSymbol is considered by fontconfig to not provide any language support, the text is German, and "AR PL UMing HK" supports German. Maybe: "When creating an index from headings, scan them for usage of symbol fonts and strip the language info from those ranges" which would make it do the right thing in this case or maybe go further and just "When creating an index from headings, scan them for usage of symbol fonts and do not over-ride the font name for those ranges" (In reply to Caolan McNamara from comment #6) just "When creating an > index from headings, scan them for usage of symbol fonts and do not > over-ride the font name for those ranges" Hi Caolan, Sorry, but I don't understand exactly what you mean :-( How to scan and how to perform this "non overriding font name"? Kind regards Joachim Backes Sorry, these are notes to myself as to a plausible technical solution I could implement This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Checking with libreoffice-4.4.3.2-5.fc22.x86_64: same (bad) results Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. (In reply to Joachim Backes from comment #0) > Created attachment 881749 [details] > Index containing the wrong line (1.2.2...) > > Description of problem: > Having some special chars in some heading of level 3. If I generate the > index, then the special chars are not presented correctly: See the attached > file with the heading "1.2.2 Das Kommando DRPROTOKOLL". In the index, the > heading looks as: "1.2.2 Das Kommando xxx DRPROTOKOLL" where xxx shows some > chinese chars (See attachments). > > > > Version-Release number of selected component (if applicable): > libreoffice-4.2.2.1-8.fc20.x86_64 > > How reproducible: > always in the attached document > > Steps to Reproduce: > 1. See description > 2. > 3. > > Actual results: > Index incorrect > > Expected results: > correct index > > Additional info: By re-generating the index of the doc, I see that the described effect has been fixed. This is at least true for libreoffice-5.1.5.1-1.fc24.x86_64. . |
Created attachment 881749 [details] Index containing the wrong line (1.2.2...) Description of problem: Having some special chars in some heading of level 3. If I generate the index, then the special chars are not presented correctly: See the attached file with the heading "1.2.2 Das Kommando DRPROTOKOLL". In the index, the heading looks as: "1.2.2 Das Kommando xxx DRPROTOKOLL" where xxx shows some chinese chars (See attachments). Version-Release number of selected component (if applicable): libreoffice-4.2.2.1-8.fc20.x86_64 How reproducible: always in the attached document Steps to Reproduce: 1. See description 2. 3. Actual results: Index incorrect Expected results: correct index Additional info: