-expect, however, was the nVidia binary driver. It did not support RandR until\r
-mid 2012, even though nVidia had announced that it will support RandR\r
-previously. What does missing RandR support mean for you? First of all, you are\r
-stuck with TwinView and cannot use <tt>xrandr</tt>. While this ruins the user\r
-experience, the more grave problem is that the nVidia driver not only does not\r
-support dynamic configuration using RandR, it also does not expose correct\r
-multi-monitor information via the RandR API. So, in some setups, i3 will not\r
-find any screens; in others, it will find one large screen which actually\r
-contains both of your physical screens (but it will not know that these are two\r
-screens).</p></div>\r
+expect, however, was the nVidia binary driver. It still does not support RandR\r
+(as of March 2010), even though nVidia has announced that it will support RandR\r
+eventually. What does this mean for you, if you are stuck with the binary\r
+driver for some reason (say the free drivers don’t work with your card)? First\r
+of all, you are stuck with TwinView and cannot use <tt>xrandr</tt>. While this ruins\r
+the user experience, the more grave problem is that the nVidia driver not only\r
+does not support dynamic configuration using RandR, it also does not expose\r
+correct multi-monitor information via the RandR API. So, in some setups, i3\r
+will not find any screens; in others, it will find one large screen which\r
+actually contains both of your physical screens (but it will not know that\r
+these are two screens).</p></div>\r