Thanks for clarification. The fix looks good to me.
On 24.02.2015 18:07, Roman Kennke wrote:
We usually don't have fontconfig on AIX and it would be nice if AWT
would still work even without fontconfig. There are also other ancient
operating systems without fontconfig like for example HP UX whic
> > We usually don't have fontconfig on AIX and it would be nice if AWT
> > would still work even without fontconfig. There are also other ancient
> > operating systems without fontconfig like for example HP UX which are
> > not currently supported by OpenJDK but by commercial licensees of the
> >
We usually don't have fontconfig on AIX and it would be nice if AWT
would still work even without fontconfig. There are also other ancient
operating systems without fontconfig like for example HP UX which are
not currently supported by OpenJDK but by commercial licensees of the
OpenJDK source base
Hi Roman,
thanks for the clarification.
Volker
On Fri, Feb 20, 2015 at 3:01 PM, Roman Kennke wrote:
> Hi Volker,
>
> The patch doesn't change anything for the default graphics that use
> X11FontManager. The internal error is only thrown on backends that explicitly
> use FcFontManage, and thus
Hi Volker,
The patch doesn't change anything for the default graphics that use
X11FontManager. The internal error is only thrown on backends that explicitly
use FcFontManage, and thus require fontconfig.
Regards, Roman
Am 20.02.2015 14:49 schrieb Volker Simonis :
>
> We usually don't have fontc
We usually don't have fontconfig on AIX and it would be nice if AWT
would still work even without fontconfig. There are also other ancient
operating systems without fontconfig like for example HP UX which are
not currently supported by OpenJDK but by commercial licensees of the
OpenJDK source base.
Am Donnerstag, den 05.02.2015 um 19:52 +0300 schrieb Sergey Bylokhov:
> Hello, Roman, Phil.
> The fix looks fine except an absent documentation in new class and
> InternalError + 80 chars per line.
I added a class comment. I added a small msg to the internal error
explaining why it happens (what
It should still be functional. Some day we are likely to remove it but
not yet.
In the event that we can't find fontconfig for some reason, this should
allow us to limp along moderately well as opposed to being in dire straits.
-phil.
On 2/5/15 8:52 AM, Sergey Bylokhov wrote:
Hello, Roman, Phi
Indeed, for quite some time now I believe we don't *really* need this
fallback. While we're refactoring this, it would be nice to see this gone
too.
I'm sure Phil has better knowledge here to know for sure though.
Cheers,
Mario
2015-02-05 17:52 GMT+01:00 Sergey Bylokhov :
> Hello, Roman, Phil
Hello, Roman, Phil.
The fix looks fine except an absent documentation in new class and
InternalError + 80 chars per line.
But I have a question: do we really need this failback?
527 /* Using the X11 font path to locate font files is now a fallback
528* useful only if fontconfig
> > http://mail.openjdk.java.net/pipermail/awt-dev/2015-January/008819.html
> >
> > I got no reply, so I'm sending it here, maybe it's a better fit? ;-)
>
> font related discussions should go to 2d-dev.
> The change looks OK. But test it as much as
> you can. The previous re-factoring in JDK7
> ha
On 01/20/2015 07:42 AM, Roman Kennke wrote:
I already sent that patch to awt-dev for review, a while ago:
http://mail.openjdk.java.net/pipermail/awt-dev/2015-January/008819.html
I got no reply, so I'm sending it here, maybe it's a better fit? ;-)
font related discussions should go to 2d-dev.
I already sent that patch to awt-dev for review, a while ago:
http://mail.openjdk.java.net/pipermail/awt-dev/2015-January/008819.html
I got no reply, so I'm sending it here, maybe it's a better fit? ;-)
Hello,
I am currently working on a port of AWT/Java2D to DirectFB (using
Caciocavallo [1] a
13 matches
Mail list logo
