Blogger's 3 year paragraph debacle - the case of universal line break conversion

(Post title revised to reflect updates.)

I'm increasingly running across old posts that I've not touched where paragraphs have now vanished.

Not content with ruining formatting on newer posts, Google (blogger) is is now blowing up older posts.

I need to find an alternative to Blogger.

Update: I ask at Blogger's help group, but, based on the questions there, I doubt it will get any attention. Here's a sample of the damage. I have hundreds to thousands of old posts like this ...

Update 10/29/10: This has been going on since 2007. Three years of screwing up.

Update 10/29/10b: I've figured out part of this, thanks to a hint in that 2007 article. Blogger has a feature in settings that turns out to have devastating side-efects:

I believe the default setting is "convert line breaks". I changed it to NO to see if non-conversion would help with Google Composer's longstanding paragraph and format mangling. It never occurred to me that I was changing a setting that would be applied to every post in my blog. I reversed this setting on tech.kateva.org and my old posts now have line feeds again.

On notes.kateva.org I'd never changed the setting, so it wasn't disrupted.

Incidentally, I have two new insights on what's wrong with Blogger's various editors. MarsEdit's HTML view illustrated the second bug:

1. Blogger's rich text editor paragraph controls get confused when a paragraph begins with bold text. Frequently, but not always, this triggers an extra line feed.
2. Blogger's editor sometimes inserts <div> tags when it should insert <p> tags. In the rich text editor these create paragraphs, but browser behavior is variable. To quote Jennifer Kyrnin: The <div> tag is not a replacement <p> tag. The <p> tag is for paragraphs, only, while the <div> tag defines more general divisions within a document. Others have been confused about this distinction.

Update 10/29/10c: It appears that the editor is inserting two <br> tags and a <div> tag instead of a <p> tag. Both the current standard editor and the draft editor do this, I think the old editor might have inserted a single BR tag and a DIV tag. This is a terrible practice. See this Stack Overflow discussion and this one.

Update 10/30/10: The MarsEdit forum has a 2008 post on Blogger's flailing about with paragraph breaks, there's a companion thread in the Blogger developer forum. The developer group is only moderately interesting, it's been invaded by desperate end users seeking support. There is a "new developer relations engineer", perhaps because his predecessor was last seen drinking heavily in an Alaskan bar.

I wonder if there's a fundamental flaw in Atom Pub 1.0 that somehow led to Blogger's twisted implementation of the paragraph.

Annals of irritating design: Apple's auto-linking of iPhone contacts

When a computer / smartphone syncs to multiple address services, you will end up with multiple entries for some people.

It's easy to imagine clever ways to address this problem (though most are probably patented -- even though they are trivial to reinvent). That's not what Apple did.

Instead Apple "links" (merges when viewed in iPhone) based on matching first and last names. That's a formula for high error rates if you have a large number of contacts. (Though I admit it probably works for most people who have smaller number of Contacts.)

This rule is "sensitive" (will favor merges) but not "specific" (high number of false positives).

I ran into it today, and I deleted information before I realized what was going on.

Now you're warned. If you see a screwy looking contact in the Contacts.app, first look for the "unlink" button. It will appear when iOS has done its automated "merging". Click it before you start deleting apparently nonsensical information.

iPhone HDR - why there are two pictures (and Apple's updated user guide)

I tried using the iPhone 4 HDR feature, but I couldn't understand why I got two pictures.

I expected one image made up of the merger of two images with different exposure levels.

Apple's web site explains ...

 Apple - iPhone 4 - About the 5-megapixel camera with LED flash

... After selecting HDR, just point iPhone 4 at your subject and shoot. iPhone 4 automatically captures three photos of the scene — each with different exposure levels. Then iPhone 4 layers the shots together to create a single photo that combines the best elements of each shot and more accurately represents the wide range of light in the scene. Both the regular shot and the HDR photo appear in the Camera Roll.

I assume the first picture is the standard exposure, the high and low are discarded, and the second is the merged image.

It would be "nice" to have some more documentation. There's nothing in my iOS4 user guide about HDR. However, it turns out, the Apple website has a different iOS4 user guide. It reads on page 121:

On iPhone 4, you can turn on HDR to take HDR (high dynamic range) photos. HDR blends the best parts of three separate exposures into a single photo. For best results, iPhone and the subject should be stationary.

Turn HDR on or off: Tap the HDR button at the top of the screen. The button indicates whether HDR is on or off. (HDR is off by default.)

Note: When HDR is on, the flash is turned off. With HDR, you can save both the normal-exposure version and the HDR version of a photo in the Camera Roll, or save just the HDR version. By default, both are saved.

Choose whether to save both the normal-exposure version and the HDR version of photos: In Settings, choose Photos, then turn Keep Normal Photo on or off. If the setting is turned off, only the HDR version of a photo is saved.

If you save both versions, [HDR icon] appears in the upper-left corner of the HDR photo when you view the photos in Camera Roll (if the controls are visible).

My June 23, 2010 iO4 user guide is 18MB and 243 pages, the one I just downloaded is 19.7 MB and 258 pages. The part numbers on the last pages are different

• original: 019-1838/2010-06-22
• latest: 019-1891/2010-09

So Apple updated the manual in September. The update included a new HDR section.

I wonder if I'm the only person who's ever noticed this.

Small discoveries in tech

Fragments of things ...

• Some corporations have stopped paying for remote employee business phones. Employees are signing up for Google Voice. They get much better service for "free", and they now own their business number. When they leave they take it with them. These corporations are outsourcing a business function to Google. There will be unintended consequences.
• In 10.6 QuickTime Player will trim video fragments. This is old news, but new to me. I hadn't noticed. It's a big help. Now I can take the 300MB videos Emily and the kids make and trim them in seconds to a fragment I can file in iPhoto. This is the kind of high speed video editing I can manage. AVI inputs are saved as QuickTime movie. One bug -- no date/time metadata! I need a utility that will change the file creation and modification time stamps to match the true video acquisition date. Metadata standards for video are a mess.
• Yesterday I wanted to conference in a remote speaker to a lecture. In under 10 minutes I plugged external speakers into a WiFi connected laptop and called his cell from Gmail's Talk/Phone capability. He gave the 10 minute presentation from his airplane seat. Everyone could hear him easily. It was all a bit supernatural.
• The latest version of iTunes does quite a good job simultaneously synchronizing multiple iOS devices. That's an improvement. It still has some problems when users accounts switch however.
• Google Voice quality to Canada nose dived a few weeks ago, but is very good now. The improvement corresponded with switching from using the dial-up method to establishing a connection using GV Mobile+ on my iPhone. Could be coincidence, but the call setup is different. This service has saved me about $2,500 -- and cost AT&T that much. I'm now seeing non-geeks using Google Voice. I wonder when this will impact AT&T.
• Apple killed the 5.25" floppy, the 3.25" diskette, the serial and parallel cable, and the CD (data and music). Now Apple is killing the DVD and the hard drive. I wonder if they're going to try to kill the unborn USB 3. Ruthless.
• The power, value, and significance of Apple's FairPlay DRM is grossly underestimated. In technology as in politics some of the most important discussions are completely invisible. In my 50s I am more intrigued by what is not said than what is said.
• Blogger's rich text editor paragraph/line spacing problems are getting worse, but maybe that's a sign of progress. At this point I'll take any straw.
• FaceTime for OS X is a big deal. The big fight now is whether a future carrier will allow it over a 4G network (WiFi only now). Sprint?
• Microsoft, Dell and HP are walking dead. That's shocking. Is Intel next?
• The MacBook Air 11", iPad, iPhone and iPod Touch all provide overlapping value. The iOS devices have much better Exchange/ActiveSync synchronization services, the Air runs other software I prefer. I have an iPhone and I'm a geek, so the Air is under serious consideration.
• OS X management of mounted drives on a WiFi network sucks.
• First family trip with each kid one iPhone equivalent. I don't like it -- much better to have the kids watch one DVD. More on this in another post I think.

FaceTime for Mac - just about perfect

The artistic sociopath alternates cruel sadism with lovely gifts.

That's Apple.

The gift this time is FaceTime for Mac. It's just about perfect. Best of all, unlike the long dead iChat app it replaces, it's not tied to an OS release - it works for 10.6 and beyond. I dare to hope Apple is decoupling app functionality from OS release, but that's because I've got Stockholm Syndrome.

Seriously, OS coupling made iChat worthless. If Apple doesn't want to repeat that mistake, they have to maintain FaceTime outside of OS cycles.

On the other hand, there's not that much to maintain. It's pretty good as is. I'd like to see bigger buttons, but it's the kind of simple UI an elderly person with good vision can work with. (Apple is paying attention to demographics.)

During initial setup you can use your MobileMe account [1] or start a new apple account. You then associate it with ANY email address you own. After initial setup you can assign multiple addresses; they're simply unique identifiers that Apple assigns to your Facetime account identifier. You can choose one of these to be your callback email.

I love that "that you can also start a call from Mac OS X via URLs like facetime://appleid or facetime://email@address or facetime://phone#".

I tried this by embedding this protocol into a Google sites page. !It worked!

This means I can create a web page for my mother with a large clickable link target. That's far more useable for her than Google Video Chat or OS X iChat.

That's cool.

[1] Please do not make my MobileMe renewal mistake!

How to replace a $150 MobileMe family renewal with an $83 MobileMe renewal

A new Mobileme Family Pack costs $83 on Amazon.com. I thought my renewal through Apple would cost $99. Wrong, it cost $150; $99 for me and $50 for the family pack "extension".

That's wicked.

It turns out I could have renewed by buying the $83 family pack.

I'm going to see if I can get a refund. Don't make my mistake!

Update 10/20/10: I had a very satisfactory response through Apple's Express Lane. I have 45 days after payment to cancel for a full refund. If I then reactivate with a family pack key I get all the family accounts and data back -- Apple keeps it for a time (forever?).

So I'll order the renewal package from Amazon. When I have they key ready I'll cancel for the full refund, then immediately renew using the Amazon family pack key.

Update 10/28/10: This worked, with only a few surprises. Here's how to do it.

1. Before you cancel, make sure you have every family members user name and password at hand.
2. Cancel the account for a full refund (within 30 days).
3. login again with the account owner un/pw. You get a note that the account has expired. Enter the MobileMe key you got from Amazon.
4. You will see your account, but nothing about family members!
5. Now add each family member back, one at at time. When the dialog comes up it will ask you if you want a new account or to migrate an existing account for a regular member. I chose the 2nd option. Enter the un/pw of the family member. It takes about 30 seconds for the accept button to appear if you've entered correctly. Errors get an immediate response.

As best as I can tell no data was lost. I could see all the synchronized contacts I expected to see.

iPhoto 11 and Aperture 3 - more bad news

Somewhere on the boring, insipid, new iPhoto 11 page is a link to an iPhoto to Aperture page with gems like ...

... While iPhoto is designed to work with one library at a time, Aperture lets you set up as many libraries as you want and switch between them instantly. And you can export a project — and all the related photos — as a new library. That makes it easy to do things like take a slideshow from your work computer to your home computer to finish it. Since the slideshow is a separate file, you can work with it directly — no need to import it into one of your home libraries. When you bring it back to your work computer, all the edits you made sync automatically...

I gave up two years ago on multi-library support in iPhoto, support that would let me edit my photos while I travel and then merge them into my home library. The iPhoto 11 non-event, this conversion page, and Apple's $50 price point for iLife should crush anyone's residual hope for a better version of iPhoto.

So why am I not happy to buy Aperture 3? I have Aperture 2. The upgrade price is reasonable.

Because (shocking!!) .... Apple lies.

The iPhoto to Aperture 3 conversion is not seamless. Large amounts of metadata, such as album and event comments, image tags, and book definitions and the like are lost. Apple doesn't tell you this. That's because Apple is made up of Satan-worshiping sadists...