Archive for November, 2005

Gnubuntu

Sunday, November 27th, 2005

Mark Shuttleworth mentioned a few days ago on the Ubuntu mailing list that the Ubuntu folks were interested in developing a version of Ubuntu that contains only software deemed by the Free Software Foundation to be “free.” Shuttleworth mentions that they might collaborate with Ututo, an Argentinian Linux distribution that includes only free software (English description of project).

I was curious about how much non-free software was included in Ubuntu, so I installed the virtual Richard M. Stallman, or vrms (which sounds like a joke, but is not):

sudo apt-get install vrms

vrms took the liberty of not only installing, but also adding itself as a monthly cron job– reminds me of the real RMS: irritating but right.

It turns out that my Ubuntu server is pure– free software only– but my desktop machine has the Sun JDK, Opera, RAR, and XMame. The first three I don’t actually use, but with regards to XMame, I will confess that I like Zaxxon. In my defense, by the time I was old enough to have quarters, Zaxxon had been replaced by NBA Jams, or some other irritating business.

I suspect that vrms is not as particular as the real RMS, as I have installed the w32 codecs and the gstreamer mp3 decoder on my desktop machine. I *thought* those are both non-free. Maybe the iPodLinux people will get ogg working on generation 4 ipods soon. It’s believed to be possible, as the gen 4 has the faster PortalPlayer 5020 processor.

Microsoft plans to submit Office 12 formats to ECMA

Monday, November 21st, 2005

According to a report at PC World, Microsoft is planning to submit the XML formats it will use in Office 12 to the European Computer Manufacturer’s Association (ECMA) for approval. PCWorld mentions tha Massachusetts ODF controversy and quotes Alan Yates of Microsoft: “We have a few barriers [with government contracts],” says Alan Yates, general manager for Microsoft Office. “It will give governments more long-term confidence.” Yates was the man who wrote Microsoft’s initial response to Massachusetts’ new policy.

The Financial Times has an article that frames the move as a response to a “concern raised by the European Union executive body.” The article, by Maija Palmer, does not cite any sources for its information.

Microsoft now has a press release up.

Andy Updegrove has a quick summary and brief analysis up at Consortiuminfo.org. The interesting question that he asks is: “[I]f Microsoft is willing to open its formats and to come up with the necessary converters to allow old documents to be upgraded, why not just support ODF?”

I suspect that the answer is that Microsoft will not actually go all the way without adding a restriction that prevents programs like OpenOffice from using their formats. They have already said that they will release the formats under the same liberal license as their Office 2003 Reference Schema; they just don’t allow sublicensing of the royalty-free license that they grant, which excludes any GPL program from using the formats.

If nothing else, it will be entertaining to see how they pull this off. As Andy Updegrove points out, both Microsoft and the ODF folks are claiming the support of Apple and Intel now.

Nothing from the Between The Lines blog at ZDNet yet.

Writely supporting OpenDocument

Monday, November 21st, 2005

Writely announced today that has added support for ODF. Writely is an AJAX word processor, i.e. a program like Microsoft Word that you use through your web browser.

That means that there are now several different programs supporting ODF:

  • OpenOffice / StarOffice
  • KOffice
  • Writely

Abiword and Textmaker can open ODF, and they’re both working on saving in the format.

Curtis Chong, OpenDocument, accessibility, and web standards

Sunday, November 20th, 2005

David Berlind at ZDNet has been exchanging email with Curtis Chong, the president of the National Federation of the Blind in Computer Science, on the topic of the OpenDocument policy in Massachusetts. Chong’s concern is that Massachusetts discontinuing the use of Microsoft Office will result in screen readers failing to work for people with disabilities. Berlind thinks that moving to an open standard will mean that once screen readers are fixed to work with the standard, they will work forever.

The tough part of the question is deciding when to adopt a new, open standard over a dominant, proprietary standard. As far as I know, nobody makes the argument that proprietary standards are better for the person using the standard. I suspect that even a Microsoft zealot would love to erase their history of changing file formats with new releases of Word, if they could maintain the same features and market share they have today.

Software users want open standards, not because they’re interested in open standards, but because they’re *not* interested in standards at all. Standards are boring. As someone who has actually read IEC 60950 (Information Technology Equipment– Safety), I can verify that standards are not interesting. Converting documents from Word 97 format to .rtf to get rid of macro viruses is also no fun. I did a lot of it a few weeks ago– it is boring.

On the other hand, sometimes your just trying to get your job done so you can go home and play with your kids, or whatever it is that people who don’t like computers do. Sometimes, the shackles of a proprietary standard are comfortable, particularly in the short term. On a day to day basis, the incentive to disrupt your work on behalf of “standards compliance” is very low.

In the long term, it’s quite high. As Curtis Chong writes in his first letter to David Berlind: “[W]henever Microsoft decides to come out with a new version of Office or Windows, screen access technology developers and the blind community must race to keep up.” If the screen readers don’t keep up with Microsoft’s ever-changing standards, they are screwed.

The role of government, (for example, the state government of Massachusetts, where I live), should be to make sure that we take the long view. They should do this to minimize the total amount of pain that we go through. This is the same issue we face with the environment. We want the efficiency of the free market to maximize profits, but we have no reason to think that the free market will maximize, say, air quality. As a result, we allow the government to restrict the market to protect important shared resources through, for example, automobile emissions controls.

What does the long view tell us about file formats? By now, it is predictable that Microsoft will continue to change formats and force upgrades on their customers. It has been happening for approximately 20 years– I first used Microsoft Word 1985; I suffered; and I stopped using it regularly in 2001. If nobody forces us to switch to an open standard, it is very likely that the pain will continue. I suspect that Microsoft actually *needs* to change standards to stay competitive. Given that most people would be reasonably satisfied with the functionality of Word 97, if Microsoft loses the battle against OpenDocument, and there are free alternatives that reach the level of Word 97, they’re hosed.

Is it time to switch to OpenDocument? I use OpenDocument on a daily basis for spreadsheets and text documents. It works. The Massachusetts policy allows that accessibility will trump format, i.e. nobody will be forced to use OpenDocument if it means they can’t read it. Given that escape clause, OpenDocument’s maturity, and the strong incentive for all of Microsoft’s competitors to make OpenDocument work for everyone, mandating the use of OpenDocument is exactly what the Massachusetts government should be doing.

Editing files remotely over SSH using Bluefish

Saturday, November 19th, 2005

Every now and then, I think of a good idea for a software feature, and when I look where I think it should live, it’s already there. I was using everyone’s favorite closed source command line text editor, pico, to edit an XML file on a remote server, and I was missing syntax highlighting, which makes it easier for me to pick up my markup violations. I thought: there should be a GPL’d text editor that I can run locally that will manage the opening, updating, and closing of a source file on a remote server in the background. I tried Gedit, but no luck. It’s designed to be lightweight, which is good for a default editor. Then I tried Bluefish and hit the jackpot.

In Bluefish 1.0.1, I used File > Open URL and typed in my URL. The file opened, but when I tried to save, it wouldn’t let me. In despair, I selected File > Open, and I was surprised to be prompted for my password on the remote machine. I entered the password, and then I could edit and save without a problem. I’m not sure why I wasn’t prompted for the password when I tried to save, but the important point is that all the tedium of text editing in pico just dropped out of life, likely forever.

Time to submit the bug to the Bluefish folks.

Wordpress plugin for Google Analytics

Monday, November 14th, 2005

I wrote a Wordpress plug-in for the Google Analytics script. After I wrote it, I found that someone else had written a better one a few hours earlier.

Anyway, here’s mine. Cut and paste it into a file in your plugins directory with some name that ends in .php. Sign up for an account with Google, and paste your account string where indicated below. Then go to the plugins admin page and click “activate.”


/*
Plugin Name: Google Analytics
Plugin URI: http://pingswept.org/index.php/wp_plugins
Description: Adds Javascript instrumentation to main page for Google Analytics
Version: 0.1
Author: Brandon Stafford
Author URI: http://pingswept.org
*/

function call_google_script() {
echo ‘
type=”text/javascript”>

_uacct = “PUT YOUR ACCOUNT STRING HERE”;
urchinTracker();
‘;
}

add_action(’wp_head’, ‘call_google_script’);

?>

NYTimes.com has devised a clever new form of marketing

Saturday, November 12th, 2005

I hear there is an article that explains why Times Select is worth the money. If I could read it, I’m sure I’d sign up for Times Select right quick!

Mac OS only on Apple’s x86’s?

Saturday, November 12th, 2005

Apple announced a few months ago that they are planning on switching from Motorola’s PowerPC processors to Intel’s x86 processors. Today, we have a demonstration from ZDNet of OS X running on a Toshiba laptop with an x86 processor.

Their article mentions that Apple’s intent is that the Mac OS will be “bound directly to the hardware by a special security chip,” says ZDNet. What I’m wondering is why Apple is adding the security chip when they know that it won’t work. Just as the DRM encumbering songs from the iTunes store is cracked rapidly and repeatedly, Apple must expect that their security chip will be quickly circumvented.

Why bother? The security chip cuts into their profits– is it supposed to act as a symbolic deterrent?

What is Microsoft up to?

Saturday, November 12th, 2005

Microsoft has claimed that their Open XML formats for Office 12 will be released under the same “open” license as their Office 2003 Reference Schemas, as I mentioned a few days ago. At the time, I couldn’t figure out why Microsoft would adopt such a liberal license without going all the way. All of their competitors in the proprietary software world (Corel with WordPerfect or Apple with iWork, for example) will finally be able to write import filters for Microsoft documents that aren’t reverse engineered. That will go a long way toward allowing people using different packages to collaborate.

At the same time that Microsoft is opening their formats, they’re including a restriction that prevents their use in GPL’d software. To me, the forbidding of sublicensing seems like a strange restriction– it prevents the sharing of code between parties writing software to read the format, but allows the writing of the code in the first place. In the framework of Stallman’s four freedoms, it allows the first three– the freedom to run, study, and redistribute the code– but it forbids the last, the freedom to improve the code. I wonder whether Microsoft is trying make itself look as much like a free and open collaborator as it can while still defending itself against the open source juggernaut.

Where is the AJAXy word processor that reads OpenDocument released under the GPL?

Friday, November 11th, 2005

The organization that I work for has been struggling to find a way to exchange editable text documents across platforms (Windows, OS X and Linux) without also exchanging viruses or relying on a server at the far end of our T1 line.

What I really want is an AJAX word processor like Writely, but released under the GPL. Writely looks decent, and I found a mention that they plan on supporting OpenDocument by Thanksgiving 2005. Unfortunately, I can’t run Writely on our local network, because the Writely folks, like most proprietary software companies, will not share their code. This means that if our rather shaky Internet connection were to go down, we’d lose access to all our documents, which is not acceptable. I also have some concerns about the security of our data on their servers, but given the lax security of our network, it’s not as much of a concern as network unreliability. Maybe it will turn out that Writely will let us run a precompiled local version on a server on our network– if we can afford it, that could be great.

FCKEditor, on the other hand, is released under the GPL and sports the AJAXy goodness, but doesn’t support OpenDocument yet. I haven’t seen any mention of FCK adding support for ODF, but I wouldn’t be surprised if it happened.

We’d also consider Microsoft’s new Office Live, when it’s released, but we’ve previously had trouble with Word files as a virus vector. Given that history and the price (I’m guessing around $50 per user, similar to the price we pay now for Office), I’m hesitant to stay with them.

Anyone else know about any competitors I’m missing?