<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></a></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D'><o:p> </o:p></span></b></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p></div><div><p class=MsoNormal>Because, ultimately, it's not that simple and it's not that standard across themes. A themer has flexibility to define base fonts as well as inherited fonts for just about everything on the screen. How do you suggest that we account for all those permutation programatically? You can't just change a base font to achieve the result because other fonts may inherit from it and/or override the font size elsewhere in the theme (at least I believe this is how it works based on my limited understanding of the theme files). So how does the software account for all those options? And spending them time to build such a "tool" isn't very well served when the same thing is already possible with a text editor and some basic understanding of how the themes are constructed. As someone concerned about how their system looks, you seem to have a desire to devote at least a modicum of effort into learning the basics of themes, enough so that you could, within a short time, be able to change various pieces of your favorite theme to achieve the result *you* desire. I have done this with my own system to tweak a few things I don't like about my current theme. Not only does this type of change solve your problem but I would hope that those that go down this path may someday want to take the additional steps to create their own themes and contribute them back to the community once they see what can be done with them. On the flip side, it probably also has the effect of introducing those "on the sidelines" of theme development to appreciate how much work it actually takes to get a theme "just right".<o:p></o:p></p></div><div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I agree, to a point. Some kind of huge programmatic change would not be well served but maybe some sort of “standards” might. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:5.25pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If it’s “not that easy” currently then what would it take to make it “that easy”? Flexibility has it’s limitations.. if you bend too far.. you may just break. Maybe some sort of “standards” documentation where theme designers are completely free to design to their own standards, ideas, strategies and even graphical whims.. but if they want their theme to be part of the “standard” accepted group then they would agree to design within certain standards.. in this case, limited or standardized inheritance rules for font size?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:5.25pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:5.25pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I agree that taking the time to learn how themes work might lead someone down the path of taking the additional step to create their own theme, and contribute to the community.. however, if themes are to retain their current form it may also just propagate themes that have the same issues as all of the others that came before.. and not actually improve the overall experience or truly contribute something new or better. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:5.25pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:5.25pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal><br>2) A way to adapt a theme for different size screens<br>(16:9/4:3/Big/Small/etc)<o:p></o:p></p></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Highly unlikely given the reasons already discussed about this process when those exact settings were removed in favor of the current configuration.<o:p></o:p></p></div><div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I’m not suggesting the adoption of “those exact” settings at all, but a new set of settings that would add some dynamic “intelligence” to the new way of applying/creating/adapting themes. <o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></body></html>