Skip to main content

OpenOffice.org on Mac OS X - Bullet point corruption fixed

One continuous gripe I have with OpenOffice.org on Mac OS X is the apparent failure to properly handle bullet points. It only affects MS Word .doc format, and looks something like this:


This is apparently caused by the .doc format itself. Saving a .doc file in Word or OpenOffice.org and opening it in OOo will result in this bug. It is caused by a complete encoding failure on the part of the Word document format for bullet point symbols, as it explicitly looks for a particular glyph in the Symbol font rather than looking for the Unicode code point for the character. So, on machines that don't have the Windows version of Symbol.ttf installed ... it simply displays a nonsense character. OS X has its own Symbol font with different glyphs.

Fortunately the workaround for this is very simple. You can use font substitution to make OOo look at a "Symbol compatible" font for the glyph - in this case, OpenSymbol. Open the preferences panel and navigate to the Fonts page. Then, enter a font substitution for Symbol to OpenSymbol, to be applied Always.


This will take effect immediately, so any documents you have open will magically get their bullet points back. Smashing! Here is the same document immediately after closing the preferences window:



Comments

  1. Thanks SO much for this article!
    This was driving me nuts.

    ReplyDelete

Post a Comment

Popular posts from this blog

Sheffield CAMRA 35th Steel City Beer Festival!

The first weekend of October has rolled around, so once again it is time for the Sheffield CAMRA Steel City Beer Festival. Now in its 35th year, the festival has seen a lot of change in the recent past. After the terrifying ordeal that was the Darnall Liberal Club, standing out in a field with beer seems like a much nicer proposition. Unfortunately, reviews of the 34th festival were tainted with dissatisfaction, both with the venue and the organisation as a whole. I didn't attend last year, but I attended this year with some trepidation. Thankfully, the whole event was better run than I had been led to believe, but not without its fair share of hiccups. Two marquees provided more indoor space, the place didn't smell like a donkey sanctuary, and the beer tasted great. There were around a hundred beers to try, and thirty ciders, so even more than some previous years. After a couple of false starts, our little troop of merry drinkers (myself, Emma and Chris) finally arrived at...

iPhone OS 3.0.1 fixes SMS hijack bug

A lot of Apple haters have been rubbing their tiny hands with glee recently after news reports of a security flaw in the iPhone OS 3.0 that could allow hackers to "Hijack every iPhone in the world" . Many were quick to point out how slow Apple were for not releasing a patch, and many simply made it a soap box for "iPhone sucks, use Android" rants. However, on July 31st, Apple released iPhone OS 3.0.1, with a patch for this SMS issue. It installs easily enough, job done. Of course, not being privy to such information as how to hack my own phone with this exploit, I can't check if it does the job. Either way, there it is. A fix. More detail on the OS 3.0.1 release notes .

Juniper Network Connect on Mac OS X Snow Leopard

Juniper Network Connect is a very popular VPN client for corporate networks. It bootstraps from a Java applet and has native versions for Windows, Linux and Mac, and works very well. Unfortunately, it seems that Mac OS X 10.5 Leopard and 10.6 Snow Leopard have some issues caused by a dodgy installation program. One common way to make it work is to enable the root user and log in with full admin privileges under OS X and install it that way. This is a sledgehammer approach to a fairly simple problem, opens up security issues, and didn't even work for me. I won't even bother exploring that route in this blog post. There are a couple of other things that can be done to make it work, though. If you upgraded from a previous version of OS X and already had the Network Connect client installed, you may just be suffering a simple permissions issue. These instructions are for Network Connect 6.2.0, but they might well work with other versions with a tweak. From Termin...