On Fri, Sep 27, 2013 at 11:53 AM, Alexandro Colorado <j...@oooes.org> wrote: > On Fri, Sep 27, 2013 at 10:51 AM, Rob Weir <robw...@apache.org> wrote: > >> On Fri, Sep 27, 2013 at 11:48 AM, Rob Weir <robw...@apache.org> wrote: >> > On Fri, Sep 27, 2013 at 11:46 AM, Rob Weir <robw...@apache.org> wrote: >> >> On Fri, Sep 27, 2013 at 11:38 AM, Armin Le Grand <armin.le.gr...@me.com> >> wrote: >> >>> Hi Rob, >> >>> >> >>> >> >>> On 27.09.2013 14:50, Rob Weir wrote: >> >>>> >> >>>> On Fri, Sep 27, 2013 at 6:04 AM, Alexandro Colorado <j...@oooes.org> >> wrote: >> >>>>> >> >>>>> My guess is that the TM are not converted to path. Font diven logos >> could >> >>>>> be unstable across different renders engine. >> >>>>> -- >> >>>> >> >>>> >> >>>> And we still get many visitors using older browsers, even I.E. 6. So >> >>>> I'd recommend using a rasterized version of the logo on the website or >> >>>> anywhere else we expect random users to visit. There are ways of >> >>>> having both SVG and raster images, but if we're not seeing consistent >> >>>> SVG rendering then it would be safer to just render via Inkscape and >> >>>> use that. >> >>> >> >>> >> >>> There is a way to have a uncritical SVG version - just convert all >> text to >> >>> polygons first (and use absolute polygon paths, e.g. in inkscape). That >> >>> version would be safe since it would not use any font references, only >> >>> graphics (polygons). Relying on font rendering in SVG does simply not >> work >> >>> for multiple different systems, versions of these and even evtl. >> different >> >>> languages and installed fonts. >> >>> >> >> >> >> That might fix this one issue, but what about older browsers like I.E. >> >> 6? Will the logo render perfectly everywhere? We have challenges >> >> getting even HTML and Javascript to work right everywhere. I don't >> >> think we want to risk having our brand image rendering poorly. We've >> >> gone 12 years with a raster logo on the website. It works. >> >> >> > >> > And I should mention that we get 200K+ visits/month from mobile phones >> > and tablets as well. >> > >> >> And finally, converting to polygons in advance prevents the TrueType >> engines from doing its best job at rendering the font hinting at >> various scales. Compare it yourself. Take 12-point text, convert to >> polygons and then scale up (or down) the polygons. Then try again >> with an actual font reference. It might vary by font, but a >> well-designed font will render much better if you do not convert to >> polygons first. >> > > Umm.. I havent heard this before but AFAIK most fonts are developed on SVG > now. Fontforge uses as a core filetype to quote an example. >
See: http://en.wikipedia.org/wiki/Font_hinting Whether the font was designed in SVG is not relevant. Font hinting occurs at another level. It is the extra instructions that tell the font renderer that a 8pt font, a 24 pt font and a 80 pt font are not linear scalings of each other. -Rob > > >> >> -Rob >> >> > >> >> -Rob >> >> >> >> >> >>> Sincerely, >> >>> Armin >> >>> >> >>> >> >>>> >> >>>> -Rob >> >>>> >> >>>> >> >>>>> Sent from my Nokia N900 >> >>>>> >> >>>>> On Fri Sep 27 04:11:33 2013 David Gerard <dger...@gmail.com> wrote: >> >>>>>> >> >>>>>> On 27 September 2013 09:23, Jörg Schmidt <joe...@j-m-schmidt.de> >> wrote: >> >>>>>> >> >>>>>>> But a note: >> >>>>>>> The "M" in "TM" is shown cut off and the representation of "TM" is >> >>>>>>> different in Internet Explorer and Firefox, once serifs, once >> without >> >>>>>>> serifs, at an official logo should not be. >> >>>>>> >> >>>>>> >> >>>>>> >> >>>>>> Display artifact in Firefox. It's fine in Inkscape or on Wikimedia >> >>>>>> Commons: >> >>>>>> >> >>>>>> http://en.wikipedia.org/wiki/File:Aoo4-main-tm-logo-rgb.svg >> >>>>>> >> >>>>>> >> >>>>>> - d. >> >>>>>> >> >>>>>> >> --------------------------------------------------------------------- >> >>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> >>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >>>>>> >> >>>> --------------------------------------------------------------------- >> >>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> >>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >>>> >> >>> >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> > > > -- > Alexandro Colorado > Apache OpenOffice Contributor > http://www.openoffice.org > 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
