|
Description
Emir Sarı
2013-11-18 09:50:33 UTC
Set to new I think? *** Bug 88783 has been marked as a duplicate of this bug. *** Issues associated with typography and handling of font features for CTL, CJK and use of advanced font foundries in LibreOffice. adding bug 95222 and bug 95648 Uniscribe mishandling layout of several Graphite fonts on Windows. And OpenGL compounds issues. added these for ease of tracking Bug 73691 - add unicode conversion shortcut like word (alt+x) Bug 81129 - Unicode Chars with 5-hex-digit Codes are Filtered Away in Pasting Bug 95209 - Broken font rendering of some characters in Opus Standard font (was ok in LO4.4.2) Bug 96142 - <Alt>+<x> does not work in any of LO 5.1.0.0beta1 modules any longer Bug 96266 - Combining Diacritics will not stack when open file (arial) Bug 96456 - Old version Linux Libertine G and Linux Biolinum G fonts in Window installer bug 95209 and bug 98349 -- for handling of Latin 1252 mapped "Symbol fonts" with mappings to PUA codepoints. added bug 98367 - Draw/Impress small caps broken, including with Text box in Writer and its dupe bug 99540 - in a text box when selecting format->character->effects->small capitals lost and becomes capitals when deselected adding bug 99677 - "Opentype ligatures and context alternatives no longer work" (at 5.1.1 on Windows 7, with or without OpenGL) Added bug 100223 - "underlining is miscalculated when fallback glyph substitution is present, U+25cf for example on Droid, Caladea or Gentium fonts" This meta should not block bug 88991-Kerning issues with certain fonts like Arial, moved it to Depends on list I’d like to have a meta bug that tracks text layout issues in VCL (and not the higher level issues in Writer and other components). This one seems the closes, since most bugs tracked here fit with this criteria. Would it be OK to re-purpose this meta bug for this and move the bugs that does not fit with the new criteria elsewhere, or would it be better to have a new meta bug? (In reply to Khaled Hosny from comment #11) > I’d like to have a meta bug that tracks text layout issues in VCL (and not > the higher level issues in Writer and other components). This one seems the > closes, since most bugs tracked here fit with this criteria. Would it be OK > to re-purpose this meta bug for this and move the bugs that does not fit > with the new criteria elsewhere, or would it be better to have a new meta > bug? I agree with you, but which title is suitable? (In reply to Khaled Hosny from comment #11) > I’d like to have a meta bug that tracks text layout issues in VCL (and not > the higher level issues in Writer and other components). This one seems the > closes, since most bugs tracked here fit with this criteria. Would it be OK > to re-purpose this meta bug for this and move the bugs that does not fit > with the new criteria elsewhere, or would it be better to have a new meta > bug? OK I created bug 104131. From https://somefoobar.wordpress.com/2016/08/24/gsoc-project-comes-to-an-end/, the status after introduction of HarfBuzz on all platforms: <quote> LibreOffice text rendering code has some major issues in itself, which were too large to be covered by this project. Some of them are: 1. Using floating point arithmetic in text rendering. LibreOffice currently expresses various glyph characteristics in integers. This leads to many obscure rendering bugs (jumping characters, difference in inter-character spacing etc) and poor rendering overall. 2. Interaction of layout code with Writer code. LibreOffice justification code is outdated and needs to be updated. For example, the justification code is responsible for incorrect rendering when using Awami Nastaliq Graphite font. 3. Vertical text. 4. No platform independent abstraction of font objects. LO has different classes representing a font object on different platforms. Once these bugs are fixed, the cognitive load of the rendering code will be much less. It will be cleaner and easier to maintain. And it goes without saying that the glyph rendering will be much better. <unquote> The above point 1 is bug 103322 For the point 2, "see also" bug 38159 comment 17 Adding bug 106111 "Display, PDF, print and print preview broken for all spreadsheets with line breaks, wrong scaling depending on zoom level (5.3 regression) (steps in comment 40)" |