gen-docheck is a useful tool for the gentoo italian translation team. gen-dockeck compares the version number of english document and italian translation.

In this way you can watch the status of one or more guides, keeping the translations updated.

Features:

• mail notification support (straight to guide’s translator or to a specified address)
• filter guides using regular expressions

Requirements:

gen-dockeck requires:

• perl
• perl module LWP::Simple (under debian is provided by libwww-perl)
• perl module Net::SMTP
• perl module Getopt::Long (usually available by default with all perl installation)
• perl module Pod::Usage (usually available by default with all perl installation)

Synopsis:

gen-docheck syntax: gen-docheck [--help] [--man] [--config configuration file] for more informations read the man page: gen-docheck --manan

Configuration file:

gen-docheck support also configuration files.

This is an example:

#mail sender
sender = gentoo_doccheck@gentoo.orgThis email address is being protected from spam bots, you need Javascript enabled to view it  
#check only guides mathing these names (use "." to match all, "," to separate names)
checkonly = diskless,macos
#checkonly = .  
#send mail notify to translator
mailnotify = 0  
#send all mail notify to this address
force_mail_destination = flavio.castelli@gmail.com  
# smtp server
smtp = smtp.tiscali.it  
# debug smtp commands
smtpdebug = 0

Usage:

You can automate gen-docheck adding it to cron.

Here’s an example:

0 10 * * 0 /home/micron/gen\-docheck/gen\-docheck.pl --config /home/micron/gen\-docheck/gen\-docheck.conff

In this way you’ll run gen-docheck every sunday at 10:00 AM

Download

The code can be found inside of this git repository.

Goal

id3medit is a simple script for tagging all mp3/ogg files present in a directory.

Requirements:

id3medit relies on id3v2, a command-line tool for editing id3v2 tags file names must be in format: ’## - trackname.ext’. Where ## is track’s number, and ext is file’s extension (mp3 or ogg in case insensitive format)

Synopsis:

id3medit syntax is: id3medit artist album year(*) genre(*) Where * denotes optional arguments You can obtain genre identification number in this way: id3v2 -L | grep -i genre

Example

id3v2 -L | grep -i rock

   1: Classic Rock
  17: Rock
  40: Alt. Rock
  47: Instrum. Rock
  56: Southern Rock
  78: Rock & Roll
  79: Hard Rock
  81: Folk/Rock
  91: Gothic Rock
  92: Progress. Rock
  93: Psychadel. Rock
  94: Symphonic Rock 
  95: Slow Rock
 121: Punk Rock
 141: Christian Rock

Code

{% gist 2469919 %}

So Firefox 1.5 is out, sporting a new canvas tag. Hopefully we will see all kinds of sweet innovative stuff using it. Here is my contribution:

Update: I also changed my little bugzilla greasemonkey script to work with Firefox 1.5. You can get that at the usual place, here.

We're in the last stages of preparation for the launch of the opensuse.org wiki in three more languages: german, spanish, and french.

To keep us busy, we have more languages already in the queue for the next batch of wiki instances. I'm confident that these won't need as much time and effort as the first 3. And a big thank you to you translators out there for all your help!

Also, the famous SUSE Linux support database will reincarnate as a part of the wiki Real Soon Now. Watch the announcement list for details!

If you have ever used the Novell Bugzilla you no doubt noticed that it likes to log you out after a short while. Usually for me it’s at least two additional clicks after clicking on a bug link before I can actually see the bug. It annoyed me enough tonight that I wrote a greasemonkey script to ease the pain. You can get it here. Just log in once manually after loading the script so it can store your user/pass, and it should do it for you after that.

Update: I just put a newer version of the script up. It will log you in even if the page you’re trying to view is not locked out to anonymous users. Also added some lame feedback so you know what it’s doing.

One more package update, one more bug to comment on, one bugfix to prepare for inclusion. One release party to survive ;-) and then - Crete, here I come.

I really need a vacation. There will be no network, and I won't take a camera. See you all in 2.5 weeks.

Add classes and concerts, tunes and songs, long session nights, old friends and little sleep. Stir and simmer for three days. Enjoy without distractions from the world beyond the castle walls.

There is a new motivation campaign for Germany. Or germans. I am not sure I understand its purpose, but at least they built the website with OpenCMS, which is of course always commendable in anything done by the government. On the downside, they managed to screw up browser detection so that the site stays completely blank in Firefox. Oh well.

Managed to run two rounds in the park near my place (to the locals: shut up, I know it's a small park, but I have to start somewhere). Lesson learned today: don't listen to Irish flute music while running, it completely confuses my breathing - probably because it's a wind instrument, or because I play the stuff myself. I'll take some electronic music next time, guaranteed without human breath in it.

Many fallen leaves and acorns on the ground, which were definitely not there last week.

Went to the airport yesterday, spotting planes and especially: watching them not crash, one after the other. I'll fly again in two weeks - this time on vacation, no booths, no customers ;-) - and don't like my own nervousness. I just want to enjoy the view.

So tomorrow I'll leave town to go to my first Novell BrainShare in Barcelona and present the openSUSE project to Novell customers there. It's a rather expensive event for visitors, and I have no idea what kind of people will be there with what kind of questions, and if they want to hear about that hacker-community-freak project at all ;-)

The discussions on the openSUSE list gain momentum as the more difficult questions get asked - how will we manage to create a truly open project when we have to control the distribution rather tightly to keep the quality? Do we have to keep that control everywhere? Do we need only one distribution, or maybe three trees as Debian has, or a completely different model? How much work can we expect from people who want a feature in the distribution which we just won't accept? Is it ok to say - hey, build your own packages, create your own CDs, here's how we can help you?

What can a linux distributor _really_ give back to the community if not the knowledge how to make distributions? (Employing hackers, sure. We do, too.)

At the same time 10.0 needs time for the final polishing, so nobody here really had the time to fully participate in these discussions, but they are necessary, keep them coming. And if you're not yet on the opensuse mailing list, hop on now.