2010/1/1 Johnny Rosenberg <[email protected]>: > 2010/1/1 NoOp <[email protected]>: >> On 12/31/2009 04:13 PM, Johnny Rosenberg wrote: >>> 2009/12/31 NoOp <snip>: >>>> On 12/31/2009 11:12 AM, NoOp wrote: >>>>> On 12/31/2009 10:27 AM, Johnny Rosenberg wrote: >>>>> ... >>>>>> >>>>>> I am on Ubuntu 8.10,by the way, I'm not sure I mentioned that⦠My >>>>>> other machine, which is running OpenOffice.org 3.1, has Ubuntu 9.10, >>>>>> and no issues with FreeSans or any other (I think) fonts. >>>>> >>>>> Then probably JJJ has a valid point: >>>>> https://launchpad.net/ubuntu/+source/ttf-freefont >>>>> Jaunty & Intrepid use ttf-freefont (20080323-3) >>>>> >>>>> Download & try the 2009 version & see if that fixes the problem: >>>>> http://packages.ubuntu.com/source/karmic/ttf-freefont >>>> Sorry, I gave you the link to the source, here is the deb: >>>> http://packages.ubuntu.com/karmic/ttf-freefont >>> >>> Okay, thanks. Seems like it was something wrong with the fonts after >>> all. After installing the new ones all characters are now visible. >>> >>> Thanks! >>> >>> Regards >>> >>> Johnny Rosenberg >> >> Actually you might want to thank John Jason Jordan (JJJ) as he's the one >> the suggested changing the font... I just led you to where it is :-) > > Well, I didn't express myself very clear, but my intention was to > thank everyone for contributing with ideas and testing, but of course > JJJ deserves an extra thank for solving my problem. Thanks again JJJ, > if you read this! > > Regards > > Johnny Rosenberg > > >> >> All the best & Happy New Year(s). >> >> Gary >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
Even this new version of FreeSans seems to be incomplete. Characters like musical symbols doesn't show up when Bold or Italic, but FreeSans Normal works fine. Those characters are, among others: πππβ―βπππ (Hopefully they display in this email). Well, it's not an OpenOffice.org issue, but rather an FreeFonts issue, I guess, so my problem is solved anyway, in the way that I now know why this happens. Regards Johnny Rosenberg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
