Hi Rob, I agree with you on the source vs shared distinction of a logo and that is precisely why PNG is good for sharing and why SVG, after changing from font text to path [polygons] is also good. One good SVG, as graphic, covers many PNG files for others to use to get top quality results in their work - IMO
//drew On Fri, Sep 27, 2013 at 11:57 AM, Rob Weir <robw...@apache.org> wrote: > On Fri, Sep 27, 2013 at 11:51 AM, Alexandro Colorado <j...@oooes.org> > wrote: > > On Fri, Sep 27, 2013 at 10: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. > >> > > > > I think you are confusing the render on the browser with using this as a > > web design element. SVG have been around for ages, the fact that this > user > > asked for a vectorized version (to use for whatever reason) and he happen > > to notice an issue on the browser, doesnt mean his intentions is to put > it > > on the page. > > > > It is a reasonable assumption that the mention of the rendering on the > browser was not unrelated. > > > That said, I strongly think we should switch to SVG, natively, is much > > smaller, and more open. > > > > PNG = ISO/IEC 15948. So it is an open standard as well. As for > encouraging the propagation of our logo in an easily reusable vector > format, I don't agree with that. I think we should keep the source to > the logo rather controlled and make raster versions of it available > for approved purposes. > > -Rob > > > There are also many fallback libraries like svg.js and modernizr for > older > > browser. IE6 > 1% of the market. I think we have bigger issues that are > not > > working on the site than 1% of the visits. > > > > > > > > > > >> > >> -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 > >
