12.23.11
Posted in Camino, Life, Open Source
at 2:26 am
by Smokey
Matt Mullenweg:
Scripting is the new literacy. A hundred years ago, the dividing line was the ability to read and write. Today, it’s between people who can code simple things, and those who can’t. It’s so liberating to have an idea and be able to bend the computer to your will. I’ve found that of the most rewarding experiences in life is to create something that provides a useful function for other people. There’s an intrinsic goodness in it, like how I imagine what a true craftsman would put into a chair, table or door. You build it for the ages.
While I disagree strongly with the beginning of the quoted passage, and somewhat with the end, the middle rings true with me. I enjoy being able to write simple things to help me accomplish a task, and sometimes those pieces of “software” are even useful to others. Like many before me, I started finding my way around the Camino codebase and attempting to pick up Objective-C and Cocoa in part to fix things that bugged me, to bend Camino to my will (to paraphrase Matt).1 And although I’ve gotten great satisfaction out of fixing some bugs that have bothered me or have required some persistent debugging to fix, the most rewarding fixes—then and now—have been ones that have helped out others. It certainly isn’t saving the world, but if some code I write solves a problem someone else is having and makes their life just a little bit better or easier, it’s time well-spent.
Wishing you all the best this holiday season.
1 The other part of my reason for attempting to pick up coding was to provide more manpower and help keep development moving—something with which nearly all small open-source projects could use a hand. ↩
Permalink
10.29.09
Posted in Camino, Open Source
at 2:17 am
by Smokey
Taking another break from working on tasks for the Camino 2 release, I wanted to write a little bit about our amazing team of localizers tonight. As if someone was reading my mind, Christopher Henderson showed us this tweet he came across tonight.
Camino 2 is likely going to ship in English and 13 other languages (attentive readers will note that this is down by two from the number of languages in Camino 1.6.10, but still three more than shipped in the initial Camino 1.6 release), all translated by our volunteer localizers from the caminol10n project. New to Camino 2 will be Danish (which last appeared in the Camino 1.0 series) and Turkish, making its debut as a Camino localization.
The story of Danish in Camino 2 is particularly worth telling. At the end of September, about two weeks after we released Camino 2.0 Beta 4, Danish Camino user Allan Nyholm Nielsen posted a message in the Camino discussion forum asking why Camino 1.6 was localized in Swedish and Norwegian but not Danish, and whether Camino 2 would include a Danish translation. A member of the Camino development team replied that our localizations are all produced by volunteers and that while there had been a Danish localization in Camino 1.0.x and some work had been done for Camino 1.5, the leader of that team disappeared and the translation for 1.5 was never finished. We also pointed Allan to the caminol10n project (and to another Danish Camino user on the forum, David Munch, who could possibly help) and urged him to think about reviving the Danish translation.
The very next day, Allan had posted to the caminol10n mailing list (and back in the Camino discussion forum) stating that he had signed up and had gotten started. Two weeks after that, Allan posted a message stating that he had essentially completed the translation of Camino 2 into Danish, and, after a week of polishing the translation, he reported he had the complete translation ready.
In three weeks, we went from having no Danish translation and only an interested user who had never done any Mac OS X application localization to having a complete, peer-reviewed Danish localization for Camino 2.0! Congratulations to Allan and David on this achievement.
If you would like to see Camino in your language, you too can make it a reality. While not every language has a localization of an older version of Camino available to jump-start the process (there are a dozen languages that have shipped in past Camino versions that will not be in Camino 2.0, however), and while some teams take longer to complete a translation than others, you can still get started today and perhaps be ready to include your language in Camino 2.0.1 or 2.0.2. There are a few, relatively simple, specialized tools to learn, but for the most part all you need to know is English and your own language. There might even be other speakers of your language already interested in helping, and the existing Camino translators are knowledgeable and can help you get started with the tools.
The Danish experience is not an isolated case, either; during the Camino 1.6.x series, we added three new languages, and one of them was complete in a matter of weeks (one took a month or so, and the third we learned about only when it was already complete).
If your language is already included in Camino, be sure to thank the members of your language’s translation team and ask them if there is any way you can help; existing teams are usually looking for new members, too, to help spread the workload.
Finally, it is with sadness that I report that Catalan, Czech, Polish, and Portuguese (pt-BR) will be missing from Camino 2.0, so if you are a Camino user who speaks one of those languages, now is the time for you to get involved. Register with the caminol10n project, join the mailing list, and bring your language back to Camino.
Permalink
04.22.08
Posted in Links, Open Source, Software
at 2:37 am
by Smokey
Marc “uwog” Maurer, a leading AbiWord developer, on AbiWord’s 2008 Google Summer of Code projects:
Interestingly, we did receive quite a few applications about improving OOXML support, while we got zero OpenDocument related proposals. Apparently the support for the OpenDocument ISO standard isn’t strong enough in the F/OSS community to actually make an effort to improve support for it. Even when paid. Food for thought.
Both sad and disturbing for advocates of truly free and open standards for document formats (of which I am one).
Permalink
03.23.08
Posted in Open Source, Software
at 8:54 pm
by Smokey
Last Monday NeoOffice.org (aka Patrick and Ed, with bits of help from the rest of us) released the latest NeoOffice milestone, 2.2.3. Although this version is still using the OpenOffice.org 2.2 codebase, 2.2.3 is packed full of new Mac goodies you won’t find in other open source office suites for the Mac.
We’ve long been “spoiled” on the Mac by having things “just work”—often through the hard work of Apple engineers designing APIs and “for free” features of standard objects, but also through the hard work of application developers themselves. When porting an application from another platform, many of these things that “just work” in born-on-the-Mac apps don’t work. Because of our high standards as Mac users, it’s hard to build a good Mac app, and even harder to build a good Mac version of a cross-platform app.
NeoOffice began its life as an application that was hard to call even Mac-like (in comparison to OpenOffice.org, which only ran under X11, it was a gem; in comparison to Microsoft Office X, not so much), and development tackled the important tasks of stability and functionality (printing! native fonts!) first, gradually adding more characteristics of a standard Mac application and culminating in the “fully Aqua” NeoOffice 2.1 release last April. Of course there’s always more to do—another non-Mac-like bit to polish, another new Apple feature to include—and over the last year more standard Mac features were added (though at a slower pace, as feature size increased).
With NeoOffice 2.2.3, Ed added support for Mac OS X 10.5’s grammar checker to the existing support for the Mac OS X spell-checker (the support is fully pluggable, if anyone knows of any other grammar-checking backends). Patrick finally got the pop-up file hierarchy working in document titlebars (one of those “you don’t miss it until you go to use it and it’s not there” features). The lack of application menus when no documents were open became a thing of the past; your File menu and recent documents are always a click away now. The team ripped out OpenOffice.org’s arcane and crippled scanner support and replaced it with native Image Capture support for importing images from scanners and cameras. Our dedicated team of icon artists replaced a few dozen more ugly platform-generic icons with new Akua versions, bringing NeoOffice that much closer to the 7K+ figure required for a complete icon set.
By far the largest feature in 2.2.3, however, is support for embedded video playback. QuickTime is one of those ubiquitous Mac technologies that everyone expects to “just work” in every program; it’s in your web browser, your jukebox, and your presentations (don’t ask me why; maybe you want to spin around a model of a molecule or fly through a room in your building design?). Now it’s in your open source office suite, too, playing any non-protected QuickTime-supported format on Mac OS X 10.4 and above (and spinning your molecule models until your battery runs out), just like all of those other Mac apps you love.
What’s to come in the future? The OpenOffice.org 3.0 codebase, that much is for sure. Beyond that, we’ll have to see what other tricks Patrick and Ed have up their sleeves (Ed likes to tease everyone with screenshots of his machinations), but the OOo 3.0 upgrade will be huge in itself, thanks to the work of Sun’s OpenOffice.org and Novell’s ooo-build engineers.
One final note: if you’re a NeoOffice user who will be near Milan in late May, FreeSMUG.org will be hosting a NeoOffice event with Patrick and Ed. See the NeoWiki for more information.
Permalink
10.21.07
Posted in Life, Open Source
at 12:43 am
by Smokey
Not too long ago, someone emailed me looking for a Mac OS X version of the excellent libwpd tools for converting WordPerfect documents. Said correspondant had found my email and a now-404ed URL from a message in a mailing list archive, but couldn’t find a live version of the tools. After that, I told myself I needed to do a better job of blogging about libwpd and our releases, so that there would be fresher hits and valid URLs in search engines.
To that end, we released libwpd-0.8.12 earlier this month (it’s been a busy one for me, hence the delay). The main addition in this version is Fridrich’s fine work in bringing support for tabs and text alignment in WordPerfect 5 and WordPerfect for Mac 2.x and 3.x documents. Tabs and text alignment are probably the last common, “daily-use” features that were not converted in these document formats, and they are now supported more-or-less on par with WordPerfect 6/7/8/9/10/11/12 documents. This release is great news for Mac users who formerly used WordPerfect, as document fidelity should be much improved. In addition, for the first time ever, the Mac OS X versions of the tools are Universal Binaries.
Meanwhile, Fridrich is pushing forward on support for converting text and image boxes for the 0.9 series. Great things are in store for the future.
In the meantime, you can download the libwpd command-line tools (and an AppleScript wrapper for wpd2sxw) for Mac OS X from the project site and go convert documents with tabs until you’re blue in the face. Enjoy!
Permalink
07.29.07
Posted in Camino, Open Source
at 12:20 pm
by Smokey
In the beginning, there was email. It was open, it was interoperable, and all was well.
Then came the web, and, for a while, it, too was open and interoperable, and all was well.
Then came “online services,” walled gardens that kept their users from the web and interoperable email. They were closed, proprietary ecosystems; interoperability was a late, shoehorned addition. All was not well for users locked inside these gardens.
Then came the days of the lawless, “Wild West Web,” where interoperability was bleeding on the main street outside the saloon after the duel with browser vendors determined to make the web something that only worked in their browser. Users, citizens of this internet junction, were suffering.
Then a new sheriff rode into town, on a fire-breathing red lizard. It was Mozilla, determined to make the internet, all of it (as witnessed by its flagship product, an all-in-one suite of internet applications), open and interoperable again. Lawlessness was at an all-time high, but slowly the sheriff gathered a set of deputies, chief among them Chimera and Phoenix, and later Thunderbird, to help reign in lawlessness and make the internet open and interoperable again and to promote the public benefit. Citizens rejoiced.
Now we are seeing a rise of new walled gardens, the last refuges of those who would partition the internet into tiny fiefdoms where they might lord over their users like serfs. These walled gardens are not open or interoperable; one cannot be in one walled garden and talk to someone in another. They merely leverage the hard-won openness of the web to erect their redoubts and then lock their massive gates. Citizens are beginning to feel the burden of rushing from one walled garden to another in order to communicate with each other.
Who will lead the fight against these new walled gardens, to ensure we do not face another dark era of lawlessness on the internet where communication becomes an impossible or arduous task? The outcome of the Great Thunderbird War will tell.
We must hope the noble and just will win, or we face a dark, uncertain future of walled gardens looming over the open web, and open communication will be only a faint, fond memory.
Permalink
06.30.07
Posted in History, Open Source, Software
at 2:07 am
by Smokey
A long, long time ago, in a galaxy, er, back in the late 80s and early 90s, WordPerfect was the dominant word processor, ubiquitous (try finding commercial software today available on that many platforms) and powerful. The Mac version was Mac-like, a good citizen, easy to use and uncluttered yet still powerful (in fact, in 2007, the last released version, 3.5, dating to 1995—with a small but not insignificant update to 3.5e in 1997—does everything I’ve ever wanted to do with a word processor, save Unicode, and I’ve wanted to do some above-average things).
If you’ve been using computers since the late 80s or early 90s, or perhaps went to school in the mid/late 90s at an institution with a Novell network, chances are you have a collection of old WordPerfect documents. Fortunately (if you have any need of the data in those documents), some fine folks have created a very good file format translator (libwpd) for WordPerfect documents, which is available stand-alone and is also incorporated into open-source programs such as AbiWord, KWord, NeoOffice, and OpenOffice.org, and commercial products such as Nisus Writer Express. Currently libwpd supports most features of most common WordPerfect file formats, but the big missing piece was images. After all, everyone has some sort of images in their documents: logos in company letterhead, figures in reports or papers, clip art in family newsletters.
Last summer, the file format translator (libwpg) for the WordPerfect image format really took off, thanks to Ariya, but there was still no way to get a WordPerfect document with an image to open in any of those other applications and include the image. So close, but so far away….
This week Fridrich has been working on finally bringing libwpd and libwpg together, so that WordPerfect documents with images can be opened by other applications and retain their images—and the result looks good! Things are still rough, and and some images still won’t be converted properly, but you can see it with your own eyes; a new hope for old WordPerfect documents with images.
Thanks, Fridrich, Ariya, and all the other libwpd and libwpg hackers; this is indeed an exciting day!
Permalink
04.25.07
Posted in Open Source
at 12:13 am
by Smokey
If you’ve ever been tired of hearing “Unfortunately, the current scope of the NeoOffice project is limited by resources to keeping a native version of OpenOffice.org running on Mac OS X” (goodness knows I’ve been tired of saying it, and I imagine Patrick, Ed, and the other members of the NeoOffice community have as well), today is an exciting day.
Patrick has just announced the NeoOffice New Features Program, wherein users can donate funds towards implementing a specific new feature. If you want a feature implemented, donate, and if enough of your fellow users also want this feature and donate, Patrick and Ed will implement the feature.
Right now there are two features available for donations—they’re feature requests that have been fairly common and would improve the level of Mac OS X integration in NeoOffice—use of the native spellchecker (where available) and integration of the Mac OS X Address Book as a native data source (right now if you want to use data from Address Book, this less-than-ideal process is required). Patrick and Ed have analyzed and scoped these features and have determined an approximate cost of implementing each feature; if the amount of money required is raised before the deadline (all funds collected for features that don’t meet the required amount will be refunded; PayPal sets a deadline on refunds), the feature will be implemented.
If the costs of the features seem prohibitive, please remember that 1) Patrick and Ed live in California, a place that has a ridiculously high cost of living, and 2) Ed has a full-time job, and Patrick must balance NeoOffice work with consulting work to keep his family fed and housed. Developing software, especially software as popular as NeoOffice, is not cheap. Historically, a number of major feature additions, like drag-and-drop support, have been funded by significant donations; for the first time, the average user has a chance to fund a feature even if he or she doesn’t have deep pockets.
What if your favorite feature isn’t on the list? Don’t despair; other features will be added for funding in the future, once Patrick and Ed have had time to scope them out and estimate the cost. A popular request since Patrick first announced his intent to begin this program is support for video (e.g., whatever QuickTime can decode), especially in Impress, and some interest has been expressed in supporting PDF as an embeddable image format (e.g., not editable, but similar to how EPS files are currently handled). If you have another idea you’d like to propose for future consideration, please start a new thread in the New Features Program forum (if no one else has started a thread on the subject already); one idea per thread, please.
If you have other questions about the New Features Program (not answered on the New Features Program page), please check out the thread on trinity explaining the program.
Update 2007-05-21: Showing some additional menus even when all windows are closed is also on the list now, another improvement to take more of Windows out of NeoOffice. 
Permalink
04.22.07
Posted in Links, Open Source
at 9:40 pm
by Smokey
The developer(s) of Handbrake (an open-source application for converting DVD content to MPEG-4, e.g., for iPod Video or AppleTV) have written up a nice guide for end-users as to what open-source software is and isn’t.
By and large, the post is an appropriate characterization of every open-source project in existence, and it certainly is completely correct for 95% of all open-source projects out there (most of which are small single-programmer affairs). There are a few well-known software projects to which the entire post does not apply completely (corporate-sponsored OSS projects that are open-source in order to harness the “community” to improve the product and the bottom line, and projects that fall a little closer towards some manner of “cater[ing] to the needs, whims, or desires of end-users”), but even in these cases, the formula set out by the Handbrake developer(s) is still largely correct from an end-user perspective. If you’re not up for reading the entire post, the two bulleted lists provide a good summary and a quick read.
Since I stumbled upon the post today with some surprise at not having seen it before, and since I liked it so much, I wanted to make a quick post and “do my part” to give it some more exposure. (Who am I kidding? Only Sam reads this —and only to catch my typos.)
Thanks to the Handbrake guys for coming up with this great guide; it’s a must-read, and I wish I had known about it a month ago. If you are someone who uses open-source software, please consider reading it to be your homework assignment for the week.
Permalink
04.20.07
Posted in Open Source
at 6:33 pm
by Smokey
I began this post on 27 March, but due to some interruptions and, well, the month of April 
, finishing it sort-of dragged out.
Today [27 March], NeoOffice turns 2, or specifically, 2.1. It’s actually the third final release of NeoOffice (NeoOffice/J 1.1, NeoOffice 1.2, and now 2.1) but only the second major release. Over a year in development, this is the biggest and best NeoOffice ever, not compromising on its legendary stability while adding a number of the features most requested by NeoOffice users. The release is based on the latest stable OpenOffice.org codebase, 2.1 (which explains what happened to NeoOffice 2.0 “final;” when OpenOffice.org started giving their bug-fix releases new minor-version numbers, we synced the NeoOffice version number so that people don’t get confused about what version of OOo code is being used) and has all of the latest OOo bugfixes. 2.1 also includes code from the ooo-build and the odf-converter project, providing support for Word 2007 import, the only ongoing solution for using Excel VBA macros on the Mac, and some nifty Calc tools like Solver.
More importantly, though, NeoOffice 2.1 is much, much more pleasing to the eye. There are the new file and Akua toolbar icons, Patrick’s Cocoa Open and Save dialogues, and Ed’s amazing Aqua widget work. NeoOffice 2.1 arrives with the NeoWiki in five languages, so that tips, hints, and troubleshooting info is available in English, French, German, Italian, and Spanish. There is a great community, both at the NeoWiki and in the Trinity forums, that answer questions, write documentation, and generally ensure that anyone who arrives at the forum gets a welcome and helpful advice.
This release is made possible by the hard and creative coding of Patrick and Ed, all of the support, documentation, translation, and artwork from the community members, and the financial support from Early Access Program members and the major anonymous donor. Thanks to all of you for your efforts (especially those of you who had to put up with me at some point during the process ) and congratulations. NeoOffice turns 2(.1), and I’m sure there are more great things ahead.
Permalink
