Hi all thank you for all the information.
I was out and just today i came back to the office.
So, i will write a resume of my working solution.
Font: OpenSans link:<a
href="http://www.google.com/fonts/specimen/Open+Sans"
target="_blank"
class="newlyinsertedlink">http://www.google.com/fonts/specimen/Open+Sans</a>
on the global css turned off the kerning:
global
{
kerning: off;
fontFamily: main;
fontSize: 11;
}
how the fonts are embebed:
@font-face
{
src: url("assets/fonts/OpenSans-Regular.ttf");
fontFamily: AppFont;
fontStyle: normal;
fontWeight: normal;
embedAsCFF: true;
}
@font-face
{
src: url("assets/fonts/OpenSans-Italic.ttf");
fontFamily: AppFont;
fontStyle: italic;
fontWeight: normal;
embedAsCFF: true;
}
...
@Alex: Thanks for the info about the playerglobal.
i tried with the version 10.2 when it worked well,but when i tried the
configuration above and the result was also good in the version 11.8 i choose
for the last version.
In this moment i will have to change components to spark like forms, datagrid,
images, spacers, etc...
And for the next release is +1 application on Apache Flex SDK 4.10!
Thanks for all that help and that maintain the community alive!
Best regards,
Miguel
> From: mihai.ch...@gmail.com
> Date: Fri, 4 Oct 2013 19:52:01 +0100
> Subject: Re: blurry fonts
> To: users@flex.apache.org
>
> The way I did it was to edit the font file directly using Type
> Light<http://www.cr8software.net/typelight.html>.
> I went into Font->Font Options..., deselected Kerning and saved it on top
> of the original font file. With this treatment, the font does not trigger
> the bug I mentioned, yet is still readable. I did not turn off kerning as
> suggested by Maurice. I'm not even sure it would have made a difference now
> that the font did not have this information to begin with.
>
> If you're using another OS, I'm sure there is another good font editor that
> you can use to make this change.
>
> Hope it helps.
>
>
> On 4 October 2013 18:43, Maurice Amsellem <maurice.amsel...@systar.com>wrote:
>
>> Ah, ok.
>>
>> -----Message d'origine-----
>> De : modjkl...@comcast.net [mailto:modjkl...@comcast.net]
>> Envoyé : vendredi 4 octobre 2013 19:42
>> À : users@flex.apache.org
>> Objet : Re: blurry fonts
>>
>> Thanks Maurice,
>>
>>
>> Mihai's post below states to remove kerning to avoid a bug:
>>
>>
>> However, if you're going to use it, make sure you remove the kerning
>> information inside it until we have a resolution for this bug<
>> https://issues.apache.org/jira/browse/FLEX-33779> .
>>
>>
>>
>> ----- Original Message -----
>> From: "Maurice Amsellem" <maurice.amsel...@systar.com>
>> To: users@flex.apache.org
>> Sent: Friday, October 4, 2013 10:29:42 AM
>> Subject: RE: blurry fonts
>>
>> global {
>> kerning: off;
>> }
>>
>> However, usually text is more readable when kerning is on, especially for
>> some letters combinations, eg AV and things like that.
>> So why would you turn it off?
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : modjkl...@comcast.net [mailto:modjkl...@comcast.net]
>> Envoyé : vendredi 4 octobre 2013 19:12
>> À : users@flex.apache.org
>> Objet : Re: blurry fonts
>>
>> I like peoples suggestions for embedded fonts that look nice.
>>
>>
>> Just curious though, how does one remove the kerning? Do you need special
>> font software to manipulate this? Or, is it done directly in the font file
>> somehow? Or, done using actionscript code? etc.
>>
>> ----- Original Message -----
>> From: "Mihai Chira" <mihai.ch...@gmail.com>
>> To: users@flex.apache.org
>> Sent: Friday, October 4, 2013 1:15:27 AM
>> Subject: Re: blurry fonts
>>
>> Hey Miguel,
>>
>>
>> we're using Myriad Web
>> Pro<http://www.azfonts.net/load_font/myriadwebpro.html>with the latest
>> version of the SDK and it looks just fine. We also make software meant for
>> many hours' use.
>>
>> However, if you're going to use it, make sure you remove the kerning
>> information inside it until we have a resolution for this bug<
>> https://issues.apache.org/jira/browse/FLEX-33779>
>> .
>>
>>
>> Best,
>> Mihai
>>
>>
>> On 4 October 2013 08:16, Miguel Ferreira <miguel.cd.ferre...@hotmail.com
>>>wrote:
>>
>>> The difference is really big.
>>> Even the colors of some item renders.
>>> But the question for me is, that will depend of the user player?
>>> For the older version is more redable but even so with the font opensans
>>> the difference is smaller.
>>> There is some font that the guy from the new renderer adivce?Because if
>>> they say that is better they should have some study cases were they can
>>> prove that.
>>> So maybe they can advice on good font for a flex enterprise
>>> application.Where the user work with it between 4 to 8 hours per day.
>>> Because with that blurry foggy fonts will be a nightmare.
>>> Thanks alex for be always available... almost 24/7
>>> Miguel
>>>> From: aha...@adobe.com
>>>> To: users@flex.apache.org
>>>> Date: Thu, 3 Oct 2013 23:40:44 -0700
>>>> Subject: Re: blurry fonts
>>>>
>>>> Did you try it with an older swf version?
>>>>
>>>> On 10/3/13 11:08 PM, "Miguel Ferreira" <miguel.cd.ferre...@hotmail.com
>>>
>>>> wrote:
>>>>
>>>>>Thank you all,
>>>>>I am trying with another font type to see if i can have a better
>>>>>results.Because of the "better" rendering was one of my key issues to
>>>>>update to the last version to try to keep up with the Apache
>> evolution,
>>>>>but after the project manager saw the result was really hard to
>> convince
>>>>>him that we are on the right path following the steps and evolution of
>>>>>Apache releases.
>>>>>I tried OpenSans and i have a better result but on the edges if we go
>> to
>>>>>detail we can see that is not perfect is still a little bit foggy!
>>>>>Another font suggestion is always welcome?
>>>>>@tom
>>>>>"- it took some experimenting with the various hinting options for
>>>>>>>the font, as well as embedding a few different fonts before we
>> found
>>> a
>>>>>>>combination that worked well."
>>>>>can you tell what combinations you did that worked out?
>>>>>Thanks,Miguel
>>>>>
>>>>>> From: aha...@adobe.com
>>>>>> To: users@flex.apache.org
>>>>>> Date: Thu, 3 Oct 2013 09:19:11 -0700
>>>>>> Subject: Re: blurry fonts
>>>>>>
>>>>>> I can't find the email thread, but the answer I got was that there
>> is
>>> no
>>>>>> equivalent of gridFitType because the new font rendering algorithm
>> is
>>>>>> "better". IIRC, it is "better" because it employs some anti-aliasing
>>>>>> algorithm on all edges, not just one ones that are unlucky enough to
>>> not
>>>>>> fall on pixel boundaries, and doesn't mess with inter-character
>>> spacing.
>>>>>>
>>>>>> That said, several folks are unhappy with this algorithm. One
>>>>>>experiment
>>>>>> for you to try now that we have more version flexibility in Apache
>>> Flex
>>>>>>is
>>>>>> to set your player/air versions back to whatever it was in 4.1 or
>> even
>>>>>> 4.0. That might cause the player to select an older rendering
>>>>>>algorithm.
>>>>>>
>>>>>> HTH,
>>>>>> -Alex
>>>>>>
>>>>>> On 10/3/13 7:24 AM, "modjkl...@comcast.net" <modjkl...@comcast.net>
>>>>>>wrote:
>>>>>>
>>>>>>>I've always had problems with embedded fonts in 4.5.1 SDK. I've
>> tried
>>>>>>so
>>>>>>>much to overcome it. Seems no matter which version of Arial or
>>>>>>Helvetica
>>>>>>>I embed, the spark text always looks shorter and fat (e.g. blurry),
>>> and
>>>>>>>the mx text looks tall and skinny. The hinting options, while
>> having
>>> an
>>>>>>>effect, don't seem to correct this. If anyone has settings that
>> make
>>> an
>>>>>>>embedded font (Arial or Helvetica) look normal, I'd really like to
>>> try
>>>>>>>them.
>>>>>>>
>>>>>>>----- Original Message -----
>>>>>>>From: "Tom Chiverton" <t...@extravision.com>
>>>>>>>To: users@flex.apache.org
>>>>>>>Sent: Thursday, October 3, 2013 6:59:30 AM
>>>>>>>Subject: Re: blurry fonts
>>>>>>>
>>>>>>>On 03/10/2013 14:54, Miguel Ferreira wrote:
>>>>>>>> I am finalizing a updated to my costumer from flex 4.1.0 to flex
>>>>>>4.10.0
>>>>>>>>and the fonts really look horrible.
>>>>>>>We had the same issue when migrating up from Adobe Flex 4.1 to
>> Apache
>>>>>>>4.x - it took some experimenting with the various hinting options
>> for
>>>>>>>the font, as well as embedding a few different fonts before we
>> found
>>> a
>>>>>>>combination that worked well.
>>>>>>>I'd start by stripping out any relevant styles, then add in a
>>> specific
>>>>>>>embeded font, then have a look at the various hinting options
>>>>>>available.
>>>>>>>
>>>>>>>Tom
>>>>>>
>>>>>
>>>>
>>>
>>>
>>
