Import from divmod. Added css. Original log message:

r1585 | casper | 2005-07-09 23:26:15 +0200 (Sat, 09 Jul 2005) | 3 lines

Last checkin before version 0.2





git-svn-id: svn://svn.code.sf.net/p/pyalsaaudio/code/trunk@12 ec2f30ec-7544-0410-870e-f70ca00c83f0

doc/src/Makefile

@@ -5,7 +5,7 @@
 #
 # You also need a working latex installation, and the latex2html
 # tool installed.
-PYTHONSOURCE = /usr/src/Python-2.3.4/
+PYTHONSOURCE = /usr/src/Python-2.4.1/
 
 # Shouldn't need to change anything below here!
 
@@ -13,3 +13,8 @@ MKHOWTO = $(PYTHONSOURCE)/Doc/tools/mkhowto
 
 all:
 	$(MKHOWTO) --dir .. --html pyalsaaudio.tex
+
+text:
+	$(MKHOWTO) --dir .. --text pyalsaaudio.tex
+
+

doc/src/libalsaaudio.tex

@@ -234,7 +234,7 @@ full. In this case, the data should be written at a later time.
 The most common reason for problems with playback of PCM audio, is that the people don't properly understand
 that writes to PCM devices must match \emph{exactly} the data rate of the device.
 
-If too little data is written to the device will an underrun, and  ugly clicking sounds will occur. Conversely,
+If too little data is written to the device, it will underrun, and  ugly clicking sounds will occur. Conversely,
 of too much data is written to the device, the write function will either block (PCM_NORMAL mode) or return zero
 (PCM_NONBLOCK mode).
 
@@ -394,4 +394,4 @@ and that which I do understand has come from a painful trial and error process.
 \subsection{ALSA Examples \label{pcm-example}}
 
 For now, the only examples available are the 'playbacktest.py' and the 'recordtest.py' programs included.
-This will change in a future version.
+This will change in a future version.

doc/src/pyalsaaudio.tex

@@ -2,7 +2,7 @@
 
 \title{PyAlsaAudio}
 
-\release{0.1}
+\release{0.2}
 
 % At minimum, give your name and an email address.  You can include a
 % snail-mail address if you like.