XML (and SGML before it) is a meta language. From that you derive a description language for the specific use. HTML meets the needs for an on-line presentation of information. HTML is not designed and does not work well for printed materials. DocBook is designed to be used for multiple ways of presenting information and has the features for books and other printed media.

To use a bad analogy, think of XML and C. You can write the "hello world" example in C, but it doesn't replace a database application written in C. C can be used for big or small applications. XML can be used for relatively simple description languages (such as HTML) or very rich description languages for large, complex documents (such as DocBook).

I've been using FVWM with multiple monitors for years. xrandr has simplified things considerably. I can drag from one monitor to another with no problem. Below is my current xorg.conf (note that I am running on Fedora 10). You can use a Radeon card by changing the driver to 'radeon'. Use 'lspci' to get the appropriate BusID for your card(s). There may be simpler solutions but this has worked well for me.

And for those saying to use a different window manager please note that FVWM has not stood still but is still true to the name it had when I began using it 15 years ago: the Frugal Virtual Window manager. It is frugal with regards to RAM and CPU use. I also like it because I can edit a file (gasp) to modify the configuration. For old farts like me that's a plus. YMMV.

Section "InputDevice"
# keyboard added by rhpxl
                Identifier "Generic Keyboard"
                Driver "kbd"
                Option "XkbModel" "pc105"
                Option "XkbLayout" "us"
EndSection

Section "Monitor"
                Identifier "DVI0"
                Option "Enable" "true"
                Option "DPMS"
EndSection

Section "Monitor"
                Identifier "DVI1"
                Option "LeftOf" "DVI0"
                Option "Enable" "true"
                Option "DPMS"
EndSection

Section "Device"
                Identifier "nVidia Corporation GeForce 8600 GT"
                Driver "nv"
                BusID "PCI:1:00:0"
                #Option "Monitor-DVI0" "DVI1"
EndSection

Section "Screen"
                Identifier "Default Screen"
                Device "nVidia Corporation GeForce 8600 GT"
                DefaultDepth 24
                SubSection "Display"
                                Depth 24
                                Virtual 3840 1200
                EndSubSection
EndSection

Section "ServerLayout"
                Identifier "Default Layout"
                Screen "Default Screen"
                InputDevice "Generic Keyboard"
EndSection

Two comments:

1. Comments are there to tell WHY the code is doing what it is doing, not necessarily what the code is doing. I deal with code all the time that has comments that tell me what I can easily learn by reading the code, but they don't tell me why so when it is broken I don't know if it is because there is a subtle problem with the code or that the developer didn't know what they were doing.

2. After literally getting headaches from reading code written by other people I came up with a simple metric: The complexity of the coding solution to a problem is inversely proportional to how well the developer understood the problem they were trying to solve. In other words, someone who understands the problem will have a simpler solution than someone who doesn't understand the problem as well. You can apply this metric to things other than code, too, but it is usually very apparent with software.