I've got one similar setup that's working without problems and the only thing I see right away that's different is that it doesn't include any fonts configuration at all. Just to verify, try commenting out the entire <font>...</font> section of from the plugin configuration and see what happens. If that at least compiles, it probably means something is either wrong w/ the configuration or there's a bug in the 3.2 handling of it. I verified the local project here on 3.2.0 and 3.3-SNAPSHOT to show that both worked and it did, but 3.3-SNAPSHOT is definitely handling default font config differently judging from the compiler output.
--David On Mon, Aug 17, 2009 at 11:14 AM, Kelly Davis <[email protected]> wrote: > > I just tried it and got the same result. > > On Mon, Aug 17, 2009 at 11:00 AM, Marvin Froeder<[email protected]> wrote: > >> Here is the stylesheets (styles.css): > >> > >> @font-face { > >> src: url("../resources/arial.ttf"); > >> fontFamily: arial; > >> } > >> > >> I have tried a number of variations of the url for the font with the > >> same results. The only thing that does work is if I embed a local font > >> instead of referring directly to the font file. > > > > Did you try to put your fonts on src/main/resources and usr url like > > "/myfont.ttf" ? > > > > VELO > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
