I'm using a redhat 6 system with jdk 1.8u40 where the only font available
is "Liberation" in all its variants, bold, italic, mono, serif, sans-serif
etc.
/usr/share/fonts/liberation
/usr/share/fonts/liberation/LiberationSerif-Regular.ttf
/usr/share/fonts/liberation/LiberationMono-BoldItalic.ttf
/u
>
> this may mean, people who do this must work with a patched JDK in the
> future.
>
Right. But I think that's going to be more and more common in future. If
you rely on people installing proprietary stuff like JWS or applets then
it's a bleak future, as the way forward is clearly bundled JREs.
On Fri, Apr 24, 2015 at 1:16 PM, Mike Hearn wrote:
> this may mean, people who do this must work with a patched JDK in the
>> future.
>>
>
> Right. But I think that's going to be more and more common in future. If
> you rely on people installing proprietary stuff like JWS or applets then
> it's a
Did you read the reply from Phil in the other thread?
> There will be a -XX flag in JDK 9 that jigsaw provides to aid in the
> transition.
So you will not have to maintain a JDK9 build but only start with this
thread to still access private APIs and this is something you can
clearly control if
On Fri, Apr 24, 2015 at 2:19 PM, Tom Schindl
wrote:
> Did you read the reply from Phil in the other thread?
>
> > There will be a -XX flag in JDK 9 that jigsaw provides to aid in the
> transition.
> So you will not have to maintain a JDK9 build but only start with this
> thread to still access
Yes, but then read the rest of the thread. You really must not rely on
the theoretical possibility of an XX flag that magically kicks all your
problems down the road a year or two. The best time to get all this
nailed correctly is now. That flag is not likely to be as extensive and
durable a
I agree and we are hesitant. However, if that buys you three or more years
of time to either see if Oracle is making good decisions regarding things
we now build using private APIs as a last resort or if all (for us)
showstopping JFX bugs are fixed by then, this can be a valid option in the
real wo
On Fri, Apr 24, 2015 at 5:27 PM, Donald Smith
wrote:
> Yes, but then read the rest of the thread. You really must not rely on
> the theoretical possibility of an XX flag that magically kicks all your
> problems down the road a year or two. The best time to get all this nailed
> correctly is now
FX should just be asking fontconfig what your set up is.
What do you get if you run the fontconfig command line app ?
$ fc-match sans:regular:roman
Vera.ttf: "Bitstream Vera Sans" "Roman"
-phil.
On 4/24/15 1:30 AM, Adam Granger wrote:
I'm using a redhat 6 system with jdk 1.8u40 where the only
Hi,
I never proposed to rely on this feature forever but to relax the
concerns raised that JDK9 is the end for useing JavaFX in new not yet
explored ways and people stop using it today because it is already sure
today that you won't get the API you require in your app.
I've already outlined in ou
Reminder, Monday is our weekly sanity testing.
You can find your testing assignment at:
https://wiki.openjdk.java.net/display/OpenJFX/Sanity+Testing
Also please remember that the repo will be locked from 1am PDT until 1pm
PDT.
Happy testing!
Thanks,
Vadim
Ok, I've run into many problems in the past with diacritics, as there were
some JDK problems, but I supposed they were all fixed today. But perhaps
there's something I'm not understanding.
I've several files with diacritics in their name, let's say e.g. "La
Cathédrale Engloutie.m4a". A cata
12 matches
Mail list logo
