On Thu, Dec 25, 2014 at 11:15 PM, Alex Harui <aha...@adobe.com> wrote:
> > > On 12/25/14, 10:51 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > > >I think the same would apply to using the fonts in the iOS and Android > >skins, right? > > Yes. Although I am wondering why these skins and themes “require” font > embedding. What would happen if we took out the @font-face directives and > left the decision to embed to the developer? > > Then it won't be seamless to the user. I was trying to avoid having the user jumping through hoops to use the new skins. I think it would be fine on the device, because they are the default fonts would be available anyways. On the AIR simulator, things would look quite bad (especially on Windows which uses Times New Roman as the default) I am open to discussing removing the font embedding, but we want to see if there is an easier way of getting the font to the user, i.e downloading it via the Installer, etc. > Also, I looked at the defaults.css in MobileTheme and the @font-face usage > for Roboto is (to me) unusual. The common pattern is to use the same > fontFamily name for both normal and bold and simply change the font-weight > for bold. FlatSpark seems to be following the common pattern. > I've gotten into a habit of naming fontfamilies more explicitly. Do you want me to change it? Thanks, Om > > -Alex > >
