Comments on: [Series] Open Software, Open Content, Open Translation Part I

By: El Oso, El Moreno, and El Abogado » Blog Archive » Open Software, Open Content, Open Translation Part IV

Fri, 21 Dec 2007 17:28:19 +0000

[...] parts one, two, and three, I tried to explain 1.) just what is open source software, 2.) what is open content and 3.) why both are in search of better translation tools. Now [...]

By: myke

myke — Thu, 20 Dec 2007 03:46:46 +0000

A tiny bit of advice … If you’re using Ubuntu … trying it out as it were … I’d strongly suggest installing the K desktop environment (KDE) along side of Gnome which is the standard that Ubuntu begins with. I’ve found over a 2 year period after seriously putting both desktop environments to a tough comparison that KDE is simply better. It’s much much more customizable, more elegant, and is easier to do those customizations that you mention that is the foundation of what opensource software is all about. Take in mind, though, that the coding language that Gnome is built upon (GTK) and the coding language KDE is built upon (QT) … both open source … are compatible no matter what desktop environment you primarily use under Linux. This is one of the primary benefits of Linux but also creates confusion with the average computer user because they do work differently. And … their are other desktop environments … KDE and Gnome are simply the main two battleing it out for supremacy. I use KDE as my main desktop and have finally (mainly to make room on my drive) completely removed Gnome. But the beauty of using either is that they are both layered on top of the Linux kernel itself so GTK and QT based programs generally will work in either desktop environment.

For Office … both have OpenOffice.org as the best office suite by far.

For CD/DVD burning, writing, etc. … the QT based K3b.

Watching DVDs, mpegs, etc. … Kaffeine … which also, btw, will allow you to take screenshots while watching a DVD. Really clear ones too.

Multi-protocol instant messenger … Pidgin … every protocol I can think of combined in to one program. Simple GTK based program that simply works.

Other free, though proprietary programs are also available for Linux such as Skype, Google Earth, and Picasa.

Firefox .. definitely the most superior browser even over the KDE included Konquerer (which … btw … is what Apple based the initial Safari on).

Amarok … best digital jukebox … QT/KDE based … completely compatible with ipods and lots of other mp3 players. Also workable for podcasts and internet radio (including shoutcast).

I could go on … but I’m digressing again. I need to talk Ubuntu with you some time ….

By: Malag@sy Miray | Lost in translation

Malag@sy Miray | Lost in translation — Fri, 14 Dec 2007 17:03:22 +0000

[...] ( le seront-ils-jamais ?). L’importance d’optimiser la traduction automatique est un débat qui a mobilisé un grand nombre d’experts et qui pose aussi des questions complexes auxquelles je ne peux répondre. Alors je voudrais saluer [...]

By: El Oso, El Moreno, and El Abogado » Blog Archive » Open Software, Open Content, Open Translation Part III

Thu, 13 Dec 2007 20:44:35 +0000

[...] that we’ve gone over the basics of open source software and open content, let’s take a closer look at what brought all of the participants together [...]

By: Zulma Aguiar

Zulma Aguiar — Mon, 10 Dec 2007 01:55:32 +0000

I’m glad u mentioned VLC, because you’re right, I recently upgraded my Mac OS as well and I found myself trying to take screen shots of my own DVD’s for campaign materials, well of course, i quickly learned this was not possible. I didn’t have time to figure it out, so i went to my old small compressed quicktime movie files of the same movie to get the video still exports, but it was definitely a lucky and only by chance workaround. thanks i’ll use VLC from now on.
z

By: jer

jer — Fri, 07 Dec 2007 23:15:31 +0000

Great Summary David,

One correction just for the sake of historical accuracy, Boris and I almost always use the plugin API that is part of WordPress to extend Global Voices, rather than editing the source code itself. It might seem picky but it’s an important distinction, as programs like Firefox use also use Plugin APIs to allow control rather than direct source editing. One effect of this is that programs that are not open source can in many ways be just as extensible as open source ones as long as they have a robust well-documented api (Movable Type is one example, though there are a lot less plugins than for wordpress). So that’s another kind of open-ness that can improve the quality of software, but doesn’t necessarily require GPL or open source code.

However, in practice it seems like Open source software tends to have better APIs than non-open software, which rarely offers plugin systems. Maybe it’s because there are more programmers that want it when the software is open source, or maybe it’s just that people can use API’s better when they can look at the original code and use it in their plugins (or have their plugins informed by information only available in the source). I know that even though I almost never make changes to the WordPress source code (because it would make it hard to upgrade later). I look through the source code to learn things on an almost daily basis.

Also, good luck with the linux switch on slow-mode. i’ve been doign it for two years now. So hard with mac laptops compared to dells and stuff, but there are a few awesome Dock replacement applications for Linux that I think will make it a lot easier in the near future.