Hi Phil,
Could you look at the two suggested ways of the multi-resolution
image support API implementation?
Thanks,
Alexandr.
On 8/20/2014 8:10 PM, Alexander Scherbatiy wrote:
Hi Phil,
I have prepared the fix where resolution variants are added directly
to the Image:
htt
Hello.
Please review the fix for jdk 9/8u40.
Device transformation "fDevTx ", which was added in [1] and fFontTx
contains different "directions".
Both of them are used in calculation of advances, because of that in
some cases we get incorrect/opposite text rotation.
Note that I am not sure that
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
Do we need to split it to AWT, Swing and 2D?
The email is to 3 lists and its not clear who would pick up reviewing it.
Also please use "client" forest this is our repo for pre-integration
testing all together with Client SQE we are following to avoid
regression cases.
Victor
On 10.12.2014 3:
On 12/10/2014 10:20 PM, Victor D'yakov wrote:
Do we need to split it to AWT, Swing and 2D?
I would not find that helpful.
The email is to 3 lists and its not clear who would pick up reviewing it.
I assume the people in each are would review their piece of the change.
Also please use "cli
