Bug 139797 - Can't place a bar directly over phonetic symbols in Writer
Summary: Can't place a bar directly over phonetic symbols in Writer
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.0.2 rc
Hardware: x86-64 (AMD64) All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Font-Rendering
  Show dependency treegraph
 
Reported: 2021-01-21 03:41 UTC by Quintao
Modified: 2023-09-26 19:50 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
bars over symbols (6.54 KB, image/png)
2021-02-08 03:47 UTC, Quintao
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Quintao 2021-01-21 03:41:46 UTC
Description:
In my work I need to placed a bar over phonetic symbols.

The  symbol U+304 (named, combining macron) among the Combining diacritical marks, combines with normal letters as a bar above them, but with phonetic symbols as a true space modifier, sitting to the above-right position.

My question is, how can I put a bar over a phonetic symbol and have it shown directly over the character in Libre? It works in a text editor, but not in Libre as the mark is treated properly as a space modifier - so how might I turn off "detect space modifiers with phonetic symbols"?

Maybe it's just not possible. thanks


Steps to Reproduce:
1.Open special characters
2.Insert a phonetic vowel followed by the combining macron
3.

Actual Results:
the macron sits to top right (correct behaviour)

Expected Results:
I need a way to make the macron sit directly on top of the symbol


Reproducible: Always


User Profile Reset: No



Additional Info:
An option not to recognise phonetic symbols so that the combining characters do no act as combiners, even as they don't with normal characters.
Comment 1 Mike Kaganski 2021-01-21 05:54:19 UTC
It's unclear what is the use case. Maybe a better match would be using Asian phonetic guides (ruby)? or Math objects with bar operator?

Also please attach a sample document with text having current status, and some mockup of wanted result.
Comment 2 Quintao 2021-02-08 03:47:22 UTC
Created attachment 169565 [details]
bars over symbols

screengrab showing 2x phonetic symbol pairs with the 'bars' above offset to right, and a basic symbol pair with 'bars' directly above.
Comment 3 Quintao 2021-02-08 04:07:58 UTC
Sorry if anything not clear enough. I am writing text documents in Writer.

An important point I must add is my font: Liberation Serif

With another font, e.g Sans Serif, the problem resolves - the bars appear directly above.
which might indicate the font is to blame.
But if I copy a symbol sample into Gimp's Text tool, or any other application, with Liberation Serif font, the bars appear directly above.

So why is Liberation Serif treated differently in Libre?
I don't really have a suitable alternative to this font either.
thanks
Comment 4 Dieter 2022-02-08 06:55:26 UTC
Hello Quintao, a new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.

If it is still present, it would be helpful, if you could add sample document with some text in Sans Serif (where it works) and Liberation Serif (where is doesn't work). Thank you.
Comment 5 Mike Kaganski 2022-02-08 07:09:49 UTC
(In reply to Dieter from comment #4)

It's still the same with Version: 7.3.0.3 (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL

For a test, compare these two lines:

aU+0304
аU+0304

The first uses ASCII 'a', while the second uses Cyrillic 'а', which looks identically, but is a different character. Putting the cursor after U+0304, and pressing Alt+X, converts the code into the combining character, which is placed differently in these two cases.

But the same problem may sometimes be with Latin 'a' - I haven't identified the specifics, but maybe it's some different formatting attribute applied to 'a' compared to the following combining character.