Showing posts with label command-line. Show all posts
Showing posts with label command-line. Show all posts

Saturday, February 7, 2009

Burning video DVDs

Burning a data DVD under Ubuntu: easy. Brasero has a relatively straightforward interface. Burning a data DVD under KDE3: easy. K3b's interface is probably even more straightforward. Burning a data DVD under KD4: less easy. K3b has not yet been ported to the KDE4 framework. K3b does currently work on this computer, but it meant installing KDE3 libs. Good luck doing that on, say, Fedora, which I'm told no longer makes KDE3 packages available in their repos.

Burning a video DVD under any version of Linux: hard. Neither Brasero nor K3b offers an obvious way of doing it. There is a menu option in K3b called "new video DVD project", but it isn't obvious to me that it does what I want it to do: convert miscellaneous types of video files into something that will play on a regular DVD player, and burn each individual video as a separate chapter on the DVD.

Fortunately there is a not-nearly-as-intimidating-as-it-looks guide to doing it all using command line tools. For bonus points, it lets you create a menu for the video DVD as well. It's the tovid suite of tools, and instructions for using them are available here.

HOWEVER, be warned. The tovid package for Ubuntu does not put the commands "makemenu", "makexml" and "makedvd" in locations that are in your $PATH (ie they will not be run if you type their names at the command line the way the linked instructions tell you to do). They are stored in the directory /usr/share/tovid/ instead. This was apparently done deliberately by the package maintainers. See post 8 on this thread at the Ubuntu forums:
This is not a bug.

These utilities were diverted because they're low-level utilities and most users aren't interested in them. Moreover, the names are too generic, resulting in namespace pollution. "makemenu"? "makexml"?

The result is slightly annoying, but not a showstopper once you understand the problem. You just have to remember to call the commands by their full path. For example, instead of typing "makemenu" you type "/usr/share/tovid/makemenu". The Ubuntu thread linked above has instructions about how to stop having to always do that if it gets too annoying.

Monday, February 2, 2009

Keyboard fixed

Well that was easy. I just had to change the keyboard layout from pc104 to pc102 (the international version), and now I'm typing apostrophes and "quotation marks" properly.

The command "kcmshell4 keyboard_layout" brought up a window to let me easily configure it: select "Enable Keyboard Layouts" and hit the "Apply button". I then switched from the "Generic 104-key pc" option that I apparently selected at start-up to "Generic 102-key (intl) PC". If I read it right then it configures the keyboard for all X sessions, not just when I'm running KDE.

The keyboard_layout module lists the command it's using at the bottom of the window, in a linebox appropriately named "Command". The actual command that I ran, called setxkbmap, is, I believe, the keyboard configuration utility for the X server. I basically used a graphical tool to run the terminal command "setxkbmap -model pc102 -layout us -variant". Crude, but effective. I'm sure the manpage will provide helpful details on what all those options actually do now that I know they exist.

Hmmm...the apostrophe key was previously letting me do stuff like type the letter o with an umlaut. I wonder where that functionality has gone now? I vaguely recall something about a "compose" key to allow input beyond what appears on a standard anglo keyboard. Which key is the compose key now that my apostrophe key is not?

Discovery: kcmshell4

I just discovered the command line tool kcmshell4. This would appear to be a configuration utility for KDE4 that goes beyond that provided by its ¨System Settings" graphical tool. Or perhaps the two are related somehow, I don´t know.

In any case, if you type ¨kcmshell 4 --list¨ at the command line, you get a quite extensive list of what look to be more advanced configuration options.

Hmm....¨kcmshell4 standard_actions" brought up the configuration window that appears by going to K->System Settings->Keyboard & Mouse->Standard Keyboard Shortcuts¨. I´m guessing kcmshell4 is the configuration utility and System Settings is the front-end.

I found this out because I was trying to use a utility called Kxkb, but it wasn´t coming up when I called it by name. The Kxkb help page said that you could access Kxkb using the command ¨kcmshell4 keyboard_layout¨ from the terminal, which did work for me, and led me to discover this useful-looking little tool.

Curious that there are configuration options that don´t (yet) appear in the graphical frontend to the configurator thingy. I wonder what all those other options do?

I also wonder if the Kxkb functionality will fix the problem I´m having with the apostrophe key. I don´t know for sure, but I think I´m on the right track (I´m assuming a Dell Inspiron 1525 doesn´t necessarily use the default 104-key pc keyboard layout. I also have a sneaking suspicion that the option to change the keyboard layout was more visible in GNOME than it was in KDE, but this exercise is about discovery, not taking the easy path).