To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=26519
User hdu changed the following:
What |Old value |New value
================================================================================
CC|'cedricbosdo,fme,maxweber,|'cedricbosdo,fme,hdu,maxwe
|pjanik,thb' |ber,pjanik,thb'
--------------------------------------------------------------------------------
Assigned to|hdu |od
--------------------------------------------------------------------------------
Status|STARTED |NEW
--------------------------------------------------------------------------------
OS/Version|Linux |All
--------------------------------------------------------------------------------
Summary|Wrong kernings with differ|Attribute change in text b
|ent colors |reaks kerning
--------------------------------------------------------------------------------
------- Additional comments from h...@openoffice.org Thu Sep 3 14:06:18 +0000
2009 -------
Adjusted the summary line to the root cause. The real problem is that
Writer-/Edit-Engine feed vcl
what to do using their portion concept one portion at a time. A portion is a
sequence of unicodes
sharing the same text attributes such as font face, font size, justification
method, BiDi attributes, font
color, background color, underline color, portion position, etc.
Since vcl currently only gets to see the exact portion and nothing of the
attributes of its neighboring
portions it only could take wild guesses of its own. Assuming that text
attributes like font face, font
size or any other text attributes would probably not change across a portion
boundary will certainly
introduce new problems, because the assumption is certainly wrong as the
portion boundary is there
exactly because there was such an attribute change. The proposed patch works by
assuming that the
font face, font size and the pair-kerning attribute keep unchanged.
@od: The best short-term fix is for Writer-/Edit-Engine to adjust the portion
positions when the
kerning attribute is valid across portion boundaries. They know the position
adjustment which is
needed for this e.g. by calling GetKerningPairs() or by measuring the layout of
multiple joined portions
of kerned/unkerned text.
There is a better fix in best long term fix though: doing most of the layout
near the shaping engines by
providing all the details to fully layout a line of text to vcl at once instead
of this piecewise feeding. This
could also solve such problems as i88539, where Writer tries to do an
adjustment between reference
device and target device, which has always been an approach that has resulted
in highly criticized text
layout. VCL currently cannot do anything about this because it cannot
distinguish whether awkward
positioning is intential (e.g. from tab-spacing) or from a bad adjustment to
the reference device.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@gsl.openoffice.org
For additional commands, e-mail: issues-h...@gsl.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
