Anti-aliasing of device fonts in TextField is different in Flash 8 and Flash 10

We have noticed that when we display a TextField with a device font (Verdana), that the antialiasing is different (and subjectively worse) when
the app is compiled as a swf10 app than when it is compiled as a swf8 app.
Below is the TextField when compiled and run as a SWF 10 file,  displayed in the 10.1 player. The font size was set to 12 point, magnified, to show that it uses grayscale antialiasing
An below is the same code but compiled to a swf8 file (and run in the 10.1 player as well)
You can see that when the file is compiled as SWF8, the device font is rendered with color pixels, I guess as an LCD font.
Can anyone tell me why this is not being done for TextField when the app is compiled/run as SWF10 ??
The code to instantiate the text field looks like
        var tf:TextField = new TextField();
            tf1.antiAliasType = AntiAliasType.ADVANCED;
            tf1.autoSize = TextFieldAutoSize.LEFT;
            tf1.sharpness = 0;
            tf1.x = 100;
            tf1.y = 50;
            tf1.width=400;
            tf1.height=50;
            var fmt:TextFormat = new TextFormat();
            fmt.kerning = true;
            fmt.size = 12;
            fmt.font = 'Verdana';
            tf1.embedFonts = false;
            tf1.styleSheet = null;
            tf1.defaultTextFormat = fmt;
            var str = "Verdana";
            tf1.htmlText = str;

Actually our users are complaining that the Flash 10 grayscale antialiasing on device fonts does not look as good
as the Flash 8 style antialiasing.Virtually everyone uses LCD monitors now, and it seems like the Flash 8 color
dithering produce better results on these displays.
It is demonstrated that the Flash 10 player will render device fonts with
different algorithms when it is using AVM1 or AVM2, so what I would like to know is if there is any way to have programmatic control over this
choice in my Flash 10 application, so I can get the Flash 8 style antialiasing, or control other parameters on a device font,  like sharpness, etc.

Similar Messages

  • Font in SWF file different once inserted and previewed in Captivate 5

    I have inserted a SWF File as an animation into my captivate 5 movie. When I view the SWF file independently, thus, outside of Captivate, the font looks exactly as it should: in Arial. However, once I have inserted the SWF file into Captivate and preview the Animation, the font changes to something which looks like Times New Roman.
    A colleague tested the file on her computer also and experienced the same issue.
    Does anyone have an idea what could solve this? Does a setting need to be changed in Flash or in Captivate?
    Thank you so much!!

    OK.  Changing to a different font to test is a good strategy.  Stick with a standard Windows font, e.g. Verdana.
    There have been some issues with fonts getting corrupted that were reported several months ago when Cp5 first came out.  Caused some wierd behaviour including preventing Cp from opening at all: http://forums.adobe.com/message/3441458#3441458
    Hope yours turns out to be something much simpler.

  • Device Font Anti-aliasing on Windows

    Hi,
    I'm using a device font in a Flex 4.1 Preloader.
    I'm using the following textformat ...
    var percentLoadedFormat:TextFormat = new TextFormat( "_typewriter", 20, 0x333333, null, null, null, null, null, TextAlign.CENTER );
    ... to style a TextField using percentLoadedText.defaultTextFormat = percentLoadedFormat;
    I get a nice looking monospace/typewriter front in Mac browsers, but in windows (FFox/IE7/Chrome) the text is not Antialiased and looks awful.
    The text is not masked and is positioned at whole pixels.
    ( PC / FFox 3.6.8 at 200 % )
    ( Mac / FFox 3.6.8 at 200 % )

    Hi,
    So Anti-aliasing of device fonts is not cross-platform?
    Embed the font or try Courier
    I can't use an embedded font as it is a preloader. I would love to use Courier, only Macs tend to have Courier while PCs have Courier New and as far as I know there is no way to declare a font stack in Flash or is there?

  • Anti-Aliased Fonts : FF2 vs IE7

    I could have sworn Firefox was the first to come out with
    font
    anti-aliasing, for smoother text detail... then IE7 came out
    and followed
    suit, opening the door to fonts smaller than 10px looking
    smooth (for
    copyright notices and the like).
    However, as I compare both browsers today, I see IE7 has the
    anti-aliasing
    but FF2 doesn't. Yet my FF2 install is defaults-only, so I
    can't imagine I'd
    have turned anti-aliased fonts off.
    What happened? Did I imagine the whole thing, where FF came
    out with
    anti-aliased fonts first? Or did they try it and change their
    minds in a
    future update? Am I losing my mind?
    Thanks.

    "darrel" <[email protected]> wrote in message
    news:fcmoav$b5u$[email protected]..
    >> Darrel, anti-aliasing is not hacking. It's not a
    short-cut, a cheat, or a
    >> crutch. Those magazines you read that make millions
    of dollars and can
    >> afford the best printing equipment out there ALSO
    use anti-aliasing on
    >> their fonts. Time magazine, Entertainment Weekly,
    Rolling Stone... none
    >> of those fonts are anti-alias-free.
    >
    > Anti-aliasing is a screen concept. Nothing to do with
    printed type.
    I've printed both anti-aliased and non-anti-aliased fonts at
    300dpi, and I
    see a difference. In fact, there are several levels of
    anti-aliasing, from
    crisp to smooth.
    Why are we even having this discussion? It's quickly turning
    ugly.
    > And it's a hack to get around the inherit low resolution
    that is a
    > computer screen (compared to print).
    It's being used as such on screens, yes. But it's not its
    sole and only
    purpose.
    >> It is simply inconcievable to imaging a resolution
    SO HIGH that the human
    >> eye won't be able to distinguish between 2-tone and
    anti-aliased fonts.
    >
    > That's exactly what a basic laserprinter gives you.
    >
    >> I mean it would have to be a million dots per
    inches.
    >
    > Nah...anything above 300 dpi is fine.
    See above answer about being able to visually see the
    difference between
    anti-aliased and non-anti-aliased fonts at 300dpi.
    What you can say is that YOU don't see it, but please don't
    project that
    limitation on all of us. ;-)
    >>>> Not for a mere copyright notice or other
    fine print! (They call it that
    >>>> for a reason :-)
    >>>
    >>> If you are purposely making it illegible, than
    what's it matter if it's
    >>> smooth or not?
    >>
    >> Same reason it's small but smooth on print mediums.
    >
    > So it looks good under a magnifying glass? ;o)
    Please stop trolling me. :-P
    And on that note, I'll let you have the last reply. No
    offense intended
    whatsoever, but I've learned to spot a coming flamefest from
    a mile out, and
    I'm just too old for them now. ;-)

  • (Arial) Fonts turn into cyrillic with anti-aliasing 'none' (bug?)

    Hi, I've got this really strange problem here.
    When I'm typing 'ç' in a Photoshop I get a cyrillic 'H'. When I turn the anti-aliasing of the font into 'sharp' instead of 'none' for instance, it's back the ç again. This occurs with every key in the numeric row.
    I'm using an azerty keyboard and the ç is located on the 9-key,  This only happens with the default font 'Arial' (regular). I'm working with Photoshop CS3 (Master Collection) on a Mac OSX 1.5.6 (Leopard).

    You're welcome.   
    Undisclosed recipient wrote:
    Thrashing the preferences did the trick. I should make a habbit of this when things fall apart.
    Absolutely! It's the first thing I try when anything starts acting weird "suddenly".
    Undisclosed recipient wrote:
    I figured it was a russian H because the other letters on the numeric row were russian too (inverted R's and so on).
    Interesting.
    Incidentally, the я is not an inverted or flipped R but a uniquely Cyrillic letter which represents the diphthong YA, and its name in Russian is indeed "Ya".

  • No anti-aliasing?

    I have read that the Text Engine introduced with Flash Player 10 is supposed to provide anti-aliasing for devide fonts (i.e. non-embedded fonts).  This is essential for Web applications: without anti-aliasing text looks awful and Flex applications cannot compete with HTML applications.  But fonts that include East-Asian characters cannot be embedded because they take up too much space.  And I don't see how a Web application in 2009 can fail to support East-Asian characters.
    Today I tried Flash Builder 4, and created 3 Spark components, of types RichEditableText, RichText, and SimpleText, without embedding any fonts.  All three could be rotated, which I believe means they use the new Text Engine.  But none of them had anti-aliasing (which I checked by looking at how they rendered capital letter W).  Why is this?  Do I have to do something special to get anti-aliasing?  Or is anti-aliaing a feature that will be coming later?
    Thanks in advance,
    Francisco

    Hi Corey,
    Thanks for your message.  I've looked more carefully at the device font I'm using on the Mac (with an LCD display).  You are right, it's anti-aliased.  (I can't see any subpixel colorations with my magnifying glass as I can see them on Windows, but maybe they are just less obvious.) 
    So the reason the device font looks ugly on the Mac must just be the letter spacing.  Since you said it looks good to you, I checked the code and did some experimentation.  It turns out that I'm saying fontFamily="_sans" and, surprisingly, in Flex 3, this it not the same as not assigning a value to fontFamily.  (Out of curiosity I checked Flex 4, and it is the same there.)  Saying fontFamily="_sans" causes the letter spacing to be way off.  If I don't say anything the spacing it still a bit off, but not too much, and the font does not look bad, although it still does not look as good as an embedded font.
    I tried taking screen shots, but they come out a little blurry and it's hard to judge fonts on them.  But I'm attaching a simple mxml file that compares the embedded font, the device font with no assignment to fontFamily, and the device font with fontFamily="_sans".
    If you want to see the huge difference that fonts make on the application, the best thing is to look at the application itself, so I should say what it is.  It's Noflail Search, a search engine that you can find at noflail.com.  It starts out using an embedded font, but if it encounters an East-Asian character, or you specifiy an East-Asian language restriction, or you turn on an IME for an East-Asian language, it switches to fontFamily="_sans" (and lets you know that it does).  To go back to the embedded font you can remove what caused the switch and reload the page.  So it's easy to compare the effect of the two fonts.
    The switching to the device font was my clumsy attempt at coping with the East-Asian character problem.  Unfortunately the switching happens fairly often, because East-Asian characters pop-up in results when you least expect it, even if the query has nothing to do with East-Asia.  So I will remove the "feature" soon, and just use device fonts and hope that most Windows users have ClearType enabled.  But I'll leave it on all day Monday in case you want to check out the effect of the fonts on the application.
    When I said that Adobe should not rely on embedded fonts I was referring to the fact that the nice anti-aliasing and text rendering that you have in Flex 3, and the presumably nicer one in Flex 4, is only available for embedded fonts.
    Btw I've been comparing the subpixel anti-aliasing that I get with ClearType and a device font on Windows to the embedded font, and the embedded font looks definitely better.  The device font with ClearType looks purplish, and the anti-aliasing does not seem as good.  So let me emphasize that I'm not arguing that Adobe should use subpixel anti-aliasing.  I'm arguing that the grey-scale anti-aliasing and text rendering that you use for embedded fonts should be used for device fonts as well.  Is there any technical reason that makes this difficult?  Impossible?
    Thanks for listening
    Francisco

  • Having text anti aliased?

    Hi!
    We recently bought catalyst and at first it seemed like a nice software, but the more I use it the more I get the feeling that this version should really have been called ver. 0.2 BETA or something similar There are so many problems and restrictions.. Now I come to my latest prob. Can I get text anti aliased? My client thinks the text looks really bad and I have to agree.
    thanks!
    regards
    /Tobias

    It is just static text, I have tried different fonts, all of them standard fonts like arial, times, etc. I have tried the presentation on different work stations with different graphic cards and different flash versions. All I get is text without anti aliasing. I must be missing something, probably something really simple ..
    /Tobias

  • Possible bug in Illustrator CS4 text anti-aliasing in Save for Web and Devices

    Hello all,
    This could be a bug... if so, I'd be happy to add it to Wade's bug list a few messages down the stream.
    Here's what's happening: when I create small text using a very thin font (in this case, Helvetica Neue Light), the Pixel Preview gives a noticeably different anti-aliasing solution to the actual output from Save for Web & Devices. I'm attaching an original .AI file as well as a screenshots of what I'm getting in both situations.
    I'd really prefer the Save for Web and Devices output to look exactly like the Pixel Preview. The font looks great in Illustrator but loses a lot of its punch when I Save for Web.
    ---Peter

    In the Svae for Web and Device  under the image tab where it says art Optimize that is a drop down menu select Type Optimize as such
    htis is what it lloks like in AI and a browser when you choose Type Optimize
    This the difference between Art Optimized and Type Optimize
    That is what is happening to you you are selcting Art Optimize and that is the reason when you choose art optimize aqnd you rraster the image it looks right to you.

  • Why is getLineMetrics inaccurate when using device fonts* or immediately after resizing a TextField?

    1.  We need getLineMetrics to return correct values immediately after changing a TextField's width/height or any property that would affect the layout metrics, withouth having to alter other properties like setting the text to itself (p1.text = p1.text).  Currently, if you change the width of a text field to match the stage width for example, getLineMetrics will not return correct values until the next frame.... UNLESS you set the text property.
    2.  We also need some kind of "stage scaled" event in addition to the "stage resize" event (which only fires when stage scale mode is no_scale), because stage scaling affects the rendered size of device fonts so dramatically that we must call getLineMetrics again.  This is not the case for fonts antialiased for readability, since their size is relatively stable with scaling, as demonstrated by drawing a box around the first line once and then scaling the stage.
    So those are the problems.  The asterisk in the title of this post is there because it seem that TextField.getLineMetrics is accurate with device fonts, but I cannot take advantage of that accuracy without a way to detect when the player is scaled.  I can only confirm its accuracy at a 1:1 scale, since there is no way to recalculate the size of the line rectangle once the player is scaled, aside from setting a timer of some sort which is a real hack not to mention horribly inefficient with no way to detect when the stage has actually be scaled.
    I use device fonts because embedded fonts look terrible and blurred compared to device font rendering.  The "use device font" setting matches the appearance of text in web browsers exactly.  The only way to get embedded/advanced antialiased text in flash to approximate that of the device font look is to primarily set gridFitType to PIXEL instead of SUBPIXEL, and secondly set autokerning to true to fix problems caused by the PIXEL grid fit type.  That ensure strokes are fitted solidly to the nearest pixel, however it still lacks the "ClearType" rendering that device fonts use, which has notable color offset to improve appearance on LCD monitors, rather than the purely grayscale text that flash uses in its subpixel rendering.  Frankly, failure to use device fonts because of API issues, is the only reason why Flash sometimes doesn't look as good as HTML text and why people say text in Flash "looks blurry".  I'm tired of hearing it.  If the player simply dispatched an event when scaled and updated the metrics immediately when any property of the text field that would affect the metrics is changed, then we could all happily use device fonts and Flash text would look great.  As is stands, because of the two problems I mentioned in the opening paragraph, we're stuck dealing with these problems.
    If you create two text fields named "p1" and "p2" for paragraph 1 and 2, populate them with an identical line of text and set one to "use device fonts" and the other to "antialias for readability", then use this code to draw boxes around the first line of text in each of them:
    import flash.text.TextField;import flash.text.TextLineMetrics;graphics.clear();drawBoxAroundLine( p1, 0 );drawBoxAroundLine( p2, 0 );function drawBoxAroundLine( tf:TextField, line_index:int ):void{          var gutter:Number = 2;          var tlm:TextLineMetrics = tf.getLineMetrics( line_index );          graphics.lineStyle( 0, 0x0000ff );          graphics.drawRect( tf.x + gutter, tf.y + gutter, tlm.width, tlm.height );}
    The box surrounding the line of text in the "use device fonts" box is way off at first.  Scaling the player demonstrates that the text width of the device font field fluctuates wildly, while the "antialias for readability" field scales with the originally drawn rectangle perfectly.  That much is fine, but again to clarify the problems I mentioned at the top of this post:
    Since the text width fluctuates wildly upon player resize, assuming that getLineMetrics actually works on device fonts (and that's an assumption at this point), you'd have to detect the player resize and redraw the text.  Unfortunately, Flash does not fire the player resize event unless the stage scale mode is set to NO_SCALE.  That's problem #1.  And if that's by design, then they should definitely add a SCALE event, because changes in player scale dramatically affect device font layout, which requires recalculation of text metrics.  It's a real issue for fluid layouts.
    The second problem is that even when handling the resize event, and for example setting the text field width's to match the Stage.stageWidth property, when the text line wraps, it's not updated until the next frame.  In other words, at the exact resize event that causes a word to wrap, calling getLineMetrics in this handler reports the previous line length before the last word on the line wrapped.  So it's delayed a frame.  The only way to get the correct metrics immediately is basically to set the text property to itself like "p1.text = p1.text".  That seems to force an update of the metrics.  Otherwise, it's delayed, and useles.  I wrote about this in an answer over a year ago, showing how sensitive the text field property order is: http://stackoverflow.com/a/9558597/88409

    As I've noted several times, setting the text property to its own current value should not be necessary to update the metrics, and in some subclasses of text field, setting a property to its own value is ignored as the property is not actually changing and processing such a change would cause unnecessary work which could impact application performance.  Metrics should be current upon calling getLineMetrics.  They are not.  That's the problem.
    From a programming perspective, having to set the text property (really "htmlText" to preserve formatting) to itself to update metrics is almost unmanagable, and doesn't even make sense considering "htmlText" is just one of a dozen properties and methods on a TextField that could invalidate the layout metrics (alignment, setTextFormat, width, height, antiAliasMode, type, etc.), and I would have to override every one of those properties so that I could set htmlText = htmlText.  Using such a subclass isn't even possible if I want to use the Flash IDE to add text fields to the stage.  I would have to iterate over the display list and replace all existing fields with my subclass, which also isn't a good workaround because there's no way to update any and all variable references that may have been made to those instances.
    Frome what I've read, the invalide+render event system is unreliable.  My layout framework is similar to that of Windows Forms, and performs layout immediately, with dozens of docking modes and uses suspend and resume layout calls for efficiently resizing multiple child objects in a component.  Certain calculations cannot be aggregated for a render event, because some containers are semi-reflexive, meaning they can expand to fit the child contents while also contraining the child size, depending on whether the contain was resized or the child component was resized, so as a matter of correctness the resizing calcultation must occur immediately when the child resizes, otherwise a top-down pass on the display hierarchy for resizing will not be sufficient.
    As far as waiting until the next frame, no that is not possible, as it will cause one frame to be completely wrong.  If I was dragging the browser window to resize it, it would look terrible as virtually every single frame during the resizing operation would be incorrect.  Also, in the case where a user clicks the maximize or restore button of the web browser, the resizing event will occur exactly once, so if the metrics are not correct when that occurs, there is no recalculation occuring on the next frame, it will just be wrong and sit there looking wrong indefinitely.
    In case it's not obvious by now, this is a web application.  It uses the NO_SCALE stage scaling option, so notification of the event is not actually an issue for me personally.  I was just pointing out that for anyone not using the NO_SCALE option, there is no event in Flash to detect player scale.  What you're suggesting is using a JavaScript event and using the ExternalInterface bridge to send a message, which there is no guarantee whether it will be processed in a timely matter by the player and introduces possible platform inconsistancies, depending on whether the browser has actually resized the Flash interface at that point or what state Flash is in when it tries to recalculate the size of the text.  The browser may send that event to flash before the player is actually resized, so it will be processing incorrect sizes and then resized after the fact.  That's not a good solution.  Flash needs a scale event in addition to a resize event.  I'm really surprised it doesn't have one.  At the very least, the existing resize event should be dispatched reguardless of the stage scale mode, rather than occuring exclusively in the NO_SCALE mode.
    Bottom line is that getLineMetrics needs to return correct values every time it is called, without having to set the "text" property immediately before calling it.  If such a requirement exists, which seems to be the case, then that needs documented in the getLineMetrics method.

  • Font appears different in Muse (without smooth anti aliasing)

    I am using Google Font Roboto and noticed that it appears thicker when i type it in Muse than in Photoshop. When i have anti-aliasing on 'Strong' in photoshop it mirrors what is showing in Muse, but i prefer the default Smooth anti-aliasing. Is there a way to turn this on in Muse?

    Adobe Muse CC 2014 (font strong, bolder)
    https://db.tt/JMZhwPtT
    Photoshop CC 2014 (Correct version)
    https://db.tt/QLQtxYZL
    Whats interesting is the output in a web browser varies from browser to browser and computer to computer. I've tried it on many computers and browsers. It shows correctly on all macs in Safari but mostly incorrectly in Firefox and Chrome. However, i tried on a 2008 Lion Mac which works correctly in all browsers. On Windows computers it shows correctly nearly every time.

  • Flex without anti-aliased font in IDE

    Hi
    In Flex 3 running on Mac OSX 10.5.4 is it possible to make
    the font in the IDE more bitmap looking (ie without text
    smoothing/anti-aliasing)? Staring at small anti-aliased fonts all
    day seems to be harder on my eyes!
    Thanks in advance
    H

    i already do have anti-aliasing turned on. black text on a white background is anti-aliased as expected. i'm trying to use white on black and the difference, while subtle, is there. since i sit in front of a terminal and program all day, i want a font and display combination that is easier on my eyes than what i'm seeing now. i'll go back to black text on light background for now, but in the long run i prefer the opposite style.
    iMac Mac OS X (10.4.7)

  • AS window in leopard shows anti aliased font. Fix?

    I was using CS3 no problem, but when I upgraded to leopard on
    my mac, the cs3 actionscript window shows all anti aliased text.
    The standard text in morocco 10, which it is set to. I know that I
    can go into preferences in leopard and change the aliaseing to be
    turned off for 10 and bellow, but then most things are aliased.
    This problem didn't exist earlier.
    So is there a setting or something in Flash that I can set to
    make sure that the actionscript window keeps text aliased? I really
    don't want smooth text in my as window. Any help would be great.
    Cheers.
    -i

    i already do have anti-aliasing turned on. black text on a white background is anti-aliased as expected. i'm trying to use white on black and the difference, while subtle, is there. since i sit in front of a terminal and program all day, i want a font and display combination that is easier on my eyes than what i'm seeing now. i'll go back to black text on light background for now, but in the long run i prefer the opposite style.
    iMac Mac OS X (10.4.7)

  • JDeveloper Code Editor doesn't do ClearType font anti-aliasing

    I can't seem to get the Code Editor in JDeveloper (11.1.1.5.0) to do ClearType sub-pixel font anti-aliasing. Everything else in the IDE is doing proper sub-pixel anti-aliasing, it's only the Code Editor that's not doing it. It's doing "normal" pixel anti-aliasing which isn't nearly as good and still leaves the font looking quite jaggy.
    I've got the following lines in my jdev.conf:
    AddVMOption  -Dswing.aatext=true
    AddVMOption  -Dawt.useSystemAAFontSettings=lcd
    And I've checked "Enable Text Anti-Aliasing" in Preferences->Code Editor->Display.
    Is sub-pixel antialiasing in the JDeveloper code editor possible? If so, how? I'm running Windows 7 btw.

    No problem Timo.
    I don't think it's worth opening an SR for this. It looks like sub-pixel anti-aliasing isn't supported in the JDeveloper Code Editor, which is a shame, because that's the place where it's most needed.
    Michael.

  • Font Anti-Aliasing Issues in HTML/Ajax based Air Applications

    It seems that the font-renderer in HTML/Ajax based Air Applications is using some kind of sub-pixel font renderer that is overriding and vastly inferior to the standard Windows ClearType, or any Apple based option as well.  This problem is particularly noticable with light text on a dark background, and made worse the smaller the text is.  I've put together an example image explaining exactly what I mean at: http://regator.com/fontRendering.png   (it's a large image 1126 x 1500 px)
    My example shows two fonts at four different sizes rendered in an HTML Air App vs the default Windows Cleartype, as well as using Safari to show the Font style anti-aliasing.  In all cases the HTML Air App rendering is far more difficult to read, and in many cases severely distorts the color of the text in a way that other subpixel algorithms do not.  As far as I can find after literally hours of googling and searching there's no way to override this in HTML based applications.  Is there any solution to this, or a planned fix for the renderer?  Other than this rendering issue, the HTML interface for creating Air apps is absolutely brilliant, this is just making my finished product look significantly less polished than it otherwise would if the text were more readable.
    Thanks.

    Dear caturner81, dear Adobe,
    is there a solution to this problem? I'd really love to fix the aliasing thing in Air/HTML!

  • [SOLVED] How to turn on font hinting and font anti-aliasing?

    I wanted to configure hinting and anti-aliasing, although I've never used fontconfig before.
    I had been reading https://wiki.archlinux.org/index.php/font_configuration and I have found some contradictions.
    First it says "Configuration can be done globally through /etc/fonts/fonts.conf" and then immidiatelly after that it says "This file is replaced during fontconfig updates and shouldn't be edited".
    Then it says per-user path ~/.fonts.conf is deprecated in turn for $XDG_CONFIG_HOME/fontconfig/fonts.conf with no indication where should this "$XDG_CONFIG_HOME" actually be.
    I get that I am supposed to put my custom XML "somewhere":
    <match target="font">
    <edit name="hinting" mode="assign"><bool>true</bool></edit>
    <edit name="hintstyle" mode="assign"><const>hintfull</const></edit>
    <edit name="antialias" mode="assign"><bool>true</bool></edit>
    </match>
    But I have no idea where?
    Last edited by choosegoose (2015-02-02 23:22:56)

    Normally the $XDG_CONFIG_HOME variable points to .config in your /home/<user> directory.
    So the path that you would use would be: /home/<user>/.config/fontconfig
    Please note that it's DOT config. 
    HTH

Maybe you are looking for