Hi, Mario, Phil.
I would like to clarify how the test is intended to work on windows and macOS.
This fix changed encoding used in the FcFontConfiguration from UTF_8 to
ISO_8859_1.
The test also expected the text in the ISO_8859_1 encoding.
Is it expected that the postscript file will be create
riday, December 19, 2014 7:34:06 PM GMT +04:00 Abu Dhabi / Muscat
> Subject: Re: [OpenJDK 2D-Dev] Printing to Postscript doesn't support dieresis
>
> On Fri, 2014-12-12 at 11:06 -0800, Phil Race wrote:
>> Correct. jtreg doesn't like System.exit() but I also understand that
Hello Mario,
the change looks fine to me.
Thanks,
Andrew
- Original Message -
From: neug...@redhat.com
To: philip.r...@oracle.com
Cc: 2d-dev@openjdk.java.net
Sent: Friday, December 19, 2014 7:34:06 PM GMT +04:00 Abu Dhabi / Muscat
Subject: Re: [OpenJDK 2D-Dev] Printing to Postscript
On Fri, 2014-12-12 at 11:06 -0800, Phil Race wrote:
> Correct. jtreg doesn't like System.exit() but I also understand that shell
> tests are now highly frowned upon.
> So either
> 1) Run using "othervm" where calling System.exit() should be fine - I
> think !?
> 2) Don't worry about it, assuming j
Correct. jtreg doesn't like System.exit() but I also understand that shell
tests are now highly frowned upon.
So either
1) Run using "othervm" where calling System.exit() should be fine - I
think !?
2) Don't worry about it, assuming jtreg can clean up if needed. If it can't
halt the test threads
On Fri, 2014-12-12 at 10:11 -0800, Phil Race wrote:
> Hi Mario,
>
> I don't understand why your test needs a shell script to compile it ?
>
> Once we've resolved that question, and you get a 2nd review, feel
> free to push.
Sure, on my system the test randomly hangs if I don't call
System.exit
Hi Mario,
I don't understand why your test needs a shell script to compile it ?
Once we've resolved that question, and you get a 2nd review, feel
free to push.
-phil.
On 12/12/14 10:00 AM, Mario Torre wrote:
On Wed, 2014-12-10 at 15:36 -0800, Phil Race wrote:
the character is encoded as (
On Wed, 2014-12-10 at 15:36 -0800, Phil Race wrote:
> > the character is encoded as (which is correct ihmo)
> > but then mapped to ISOLatin1Encoding.
>
> \u00e4 (Umlaut) encoded as 8859 should just be "e4".
> What you have above is UTF-8, whereas the PS printing path is
> definitely expecting 885
the character is encoded as (which is correct ihmo)
but then mapped to ISOLatin1Encoding.
\u00e4 (Umlaut) encoded as 8859 should just be "e4".
What you have above is UTF-8, whereas the PS printing path is
definitely expecting 8859-1. I looked and found that when I reviewed this change
I comment
On Fri, 2014-11-07 at 17:36 +0100, Mario Torre wrote:
> Hi all,
>
> I've been working on a strange issue recently, this seems to affect all
> recent version of OpenJDK as well as Oracle JDK.
>
> The issue appears to be related to this change:
>
> http://hg.openjdk.java.net/jdk7u/jdk7u/jdk/rev/fb
Hi all,
I've been working on a strange issue recently, this seems to affect all
recent version of OpenJDK as well as Oracle JDK.
The issue appears to be related to this change:
http://hg.openjdk.java.net/jdk7u/jdk7u/jdk/rev/fbe9320339ea
The issue as I could find by debugging OpenJDK is a mix of
11 matches
Mail list logo
