[Libreoffice-bugs] [Bug 151095] Writer bold rendering of Adobe OTF ex Linotype fonts fails, Linux font fallback issue

2023-02-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151095

--- Comment #9 from PeterSergej  ---
(In reply to خالد حسني from comment #8)
> No way to fix this without access to a test document and the affected fonts.

After six months of deafening silence, I must conclude that you (and everyone
else here) never had any intention of fixing this bug.  Generations of people
have been born and died in the time it took you to respond, and then, suddenly,
in two days, someone takes interest enough to close the 'ticket' to make it
seem like you guys actually do something every now and then?

I guess it's why Libre Office is a cobweb project.

Have a nice day.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151095] Writer bold rendering of Adobe OTF ex Linotype fonts fails, Linux font fallback issue

2023-02-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151095

خالد حسني  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

--- Comment #8 from خالد حسني  ---
No way to fix this without access to a test document and the affected fonts.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151095] Writer bold rendering of Adobe OTF ex Linotype fonts fails, Linux font fallback issue

2023-02-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151095

--- Comment #7 from PeterSergej  ---
(In reply to Buovjaga from comment #6)
> Can you attach an example file that shows the problem? Your attachment just
> has screenshots. Normal testers would be testing this without installing any
> of the mentioned commercial fonts.

Thank you for your interest.  However, I have long since rejected Libre Office
as a serious alternative to commercial office suites.  Quite apart from not
being able to render simple fonts, the number of other deficiencies when
compared to commercial contenders is too great, and a turnaround time of six
months in a bug reporting thread indicates no one at your end is serious about
developing a reliable and popular product.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151095] Writer bold rendering of Adobe OTF ex Linotype fonts fails, Linux font fallback issue

2023-02-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151095

Buovjaga  changed:

   What|Removed |Added

 CC||ilmari.lauhakangas@libreoff
   ||ice.org
 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #6 from Buovjaga  ---
Can you attach an example file that shows the problem? Your attachment just has
screenshots. Normal testers would be testing this without installing any of the
mentioned commercial fonts.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151095] Writer bold rendering of Adobe OTF ex Linotype fonts fails, Linux font fallback issue

2022-09-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151095

--- Comment #5 from PeterSergej  ---
(In reply to V Stuart Foote from comment #2)
> The text runs "render". 
> 
> But, whatever font gets selected by the font manager for fallback does not
> have coverage of the glyph--that is what the placeholder/missing glyphs (the
> X-boxes) on the "wrong" lines of bold text indicate.

Thank you for the clarification.  In my Libre Writer settings no font fallback
has been configured; does the program itself look for a fallback when
encountering a problem?  I assume that the 'rendering' of the font either did
not find the bold OTF file, or looked at the wrong glyphs.

I logged this as a bug because both GIMP and Scribus, running on the same Linux
system as the 'bug' in Libre Writer, did render the font as bold, and the
problem does not exist for Libre Office in Windows 10.  Have I erred?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151095] Writer bold rendering of Adobe OTF ex Linotype fonts fails, Linux font fallback issue

2022-09-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151095

--- Comment #4 from V Stuart Foote  ---
(In reply to Rafael Lima from comment #3)
> Maybe a duplicate of bug 103596 ?

No, those LT fonts are *not* modern OTF Variable fonts.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151095] Writer bold rendering of Adobe OTF ex Linotype fonts fails, Linux font fallback issue

2022-09-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151095

--- Comment #3 from Rafael Lima  ---
Maybe a duplicate of bug 103596 ?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 151095] Writer bold rendering of Adobe OTF ex Linotype fonts fails, Linux font fallback issue

2022-09-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151095

V Stuart Foote  changed:

   What|Removed |Added

 CC||vstuart.fo...@utsa.edu
Summary|Linux Libre Word bold   |Writer bold rendering of
   |rendering of Adobe OTF ex   |Adobe OTF ex Linotype fonts
   |Linotype fonts fails|fails, Linux font fallback
   ||issue

--- Comment #2 from V Stuart Foote  ---
The text runs "render". 

But, whatever font gets selected by the font manager for fallback does not have
coverage of the glyph--that is what the placeholder/missing glyphs (the
X-boxes) on the "wrong" lines of bold text indicate.

-- 
You are receiving this mail because:
You are the assignee for the bug.