Here’s the deal:

- A .pages file is produced by one of the applications in Apple’s iWorks office productivity suite.
- A .pages file is actually a zip file with a few files in it.
- If you rename the file from .pages to .zip, then open the zip you will see some files and folders.
- Inside one of the folders you will find a PDF file preview (and JPEG)
- View and print this PDF.

And you’re done!

Sure, sometimes you need to edit the file, the right way to do this would be to get the sender to export the file from Apple iWorks to a format that a Windows user would be able to use, such as Rich Text Format (.rtf) or Microsoft Word (.doc).

Get used to receiving these files, Apple computers are everywhere…

The biggest fix, is that our site now works properly in current versions of Google Chrome. Our web based system for generating highly printable bingo cards is great… but once in a while we run into compatibility issues. For now, it’s fixed. We’ve tested in current Firefox, Internet Explorer, Google Chrome, and Apple Safari web browsers. Ironically, part of the programming fix was related to a compatibility tweak for Mozilla browser from years back. Mozilla users, if you actually still exist, you will need to use a different browser to use print-bingo.com now.

At the same time, we made live a feature that we wrote for a custom bingo job a few months back. All bingo cards within a single run are now guaranteed to be unique. Previously, it was entirely random if a card was duplicated in a run – but it was highly, highly, unlikely. In fact, we programmed an email notification if the dupe-tester actually catches a dupe.

We had to hard-code a duplicate entry to actually make sure the dupe tester and the email notifier worked. The odds of duplicate cards that are randomly generated is extremely low – you can’t generalize exact odds, since every custom bingo card design is different.

The site has probably generated 1,000 card runs since the new code went live… and we haven’t been notified of a duplicate card yet. If we ever catch a dupe, we’ll be sure to post about it.

More code changes are on the way. It’s summer, traffic to print-bingo.com is lower than normal.

A company bought a  license to our unique Excel to SQL INSERT Commands tool for their internal, confidential, use.  Cool! We never expected tools.perceptus.ca to be a revenue generator… but it does have unique features.  After all, we wrote them because we couldn’t find another website that could do the task for us!

In the interest of delivering a nice package to our new licensee, we  noticed that many of the text mangling features did not work in Google  Chrome.  Chrome web browser was stripping line breaks and consolidating sequential “spaces”.  We then realized that the site was not working in Internet Explorer either. Whoops.  Well, it is a  site primarily for our own internal uses, after all.

We had discovered a browser compatibility issue that probably affects very few people. We want a textarea without any wrapping, because some features are based on copy and pasting large amounts of data from Excel – automatic text wrapping makes hard to read.

Our original, Firefox functional, Chrome and Internet Explorer non-functional, TEXTAREA used the following:

• CSS: white-space: nowrap;
• TEXTAREA attribute: WRAP=”OFF”

In Firefox, we got a nice blob of text that you can scroll horizontally displayed.  In IE7 and IE8?  All kinds of crazy.  ”Enter” keys got replaced by some sort of special inline character, lines and spaces got trimmed or cut out.  Google Chrome stripped out line breaks and leading spaces, and other oddities.

Upon research, we learned that the “WRAP” attribute is not W3C approved.  Technically, it is not deprecated, but that’s because it never existed in the specifications. So we removed it and tried to use only CSS. We tried a few combinations of the overflow, white-space, and display CSS properties.  They didn’t work.

What did work?

No CSS at all.

If you view the source of the tools.perceptus.ca site and the corresponding CSS file, you will only see this:

<TEXTAREA NAME=”thetext” ROWS=”20” COLS=”100” WRAP=”OFF“>

This works as we wanted in all three web browsers.  It is officially non-standard.  But it works.

If someone would like to submit a CSS that will actually work, I’d love to see it.  But for now, I’m just going to keep complaining about how much web programming still stinks. Maybe the moral of the story is that thanks to Apple’s Safari and Google Chrome, every web site should be tested against at least one of the Webkit based browsers in addition to Firefox and Internet Explorer.