If you can figure out some apps for which there is source and provide
those tweaks
that might help understand the differences but I am not sure it will be
as straightforward as you hope.
-phil..
On 6/15/15 1:52 PM, Felix Bembrick wrote:
The thing is that the way DirectWrite is utilised now by JavaFX either
through which hints are applied by default or by some other way, the
result is text which does not render exactly the same way as (almost)
every native Windows application that also utilises DirectWrite.
Wouldn't a simpler solution (or at least a first step) be just to
tweak the hints and options until JavaFX font rendering on Windows
matches the way native apps do it? I believe at the moment all the
default options are selected so perhaps experimenting with some of the
non-default options or examining actual code of some native apps to
see which options/hints they are setting would arrive at a "best
match" configuration that could replace the "all defaults"
configuration we have now?
Then, later down the track, these hints/options could potentially be
made user-configurable.
On 16 June 2015 at 06:05, Phil Race <philip.r...@oracle.com
<mailto:philip.r...@oracle.com>> wrote:
I would have to look at it starting more or less from scratch
and I do not know that it would be as simple as providing a
way to tweak DirectWrite rendering. The
differences seem to be quite small differences in sub-pixel
intensity and sub-pixel accumulation of the total advance.
I do not know what API or client produced the 'native' rendering.
And what if someone else wants something different again ?
So I am not sure when we will get to looking into this and
deciding if it makes sense.
-phil.
On 06/14/2015 02:31 PM, Felix Bembrick wrote:
Has anyone had a look at this, done some work on it or can
provide some
details as to its progress?
Thanks,
Felix
On 11 June 2015 at 13:50, Felix Bembrick
<felix.bembr...@gmail.com <mailto:felix.bembr...@gmail.com>>
wrote:
I am following this one closely and hoping that some
progress has been
made and that a fix is planned but it's difficult to
determine from the
JIRA issue.
Does anyone have any additional info on where this issue
is at?
Thanks,
Felix
