bernhard: thuban/Doc/technotes coding_guidelines.txt,1.2,1.3

[cvs@intevation.de]

Author: bernhard

Update of /thubanrepository/thuban/Doc/technotes
In directory doto:/tmp/cvs-serv29643/Doc/technotes

Modified Files:
	coding_guidelines.txt 
Log Message:
	* Doc/technotes/coding_guidelines.txt: easy typo fixed. 

	* Extensions/svgexport/test/test_svgmapwriter.py:
	Removed test_drawbezier in favour of new test_drawspline3 and 
	test_drawspline4 within new class TestDrawSplines(TestVirtualDC).
	All only to test DrawSpline.

	* Extensions/svgexport/svgmapwriter.py(DrawSpline):
	New implementation now really using the strange algorithm of
	xfig 3.1's approximated splines and its conversion to postscript
	with one twist: SVG can do quadratic beziers, so skipped translation
	to cubic beziers.
	(TestWithDC): Typo in comment fixed.


Index: coding_guidelines.txt
===================================================================
RCS file: /thubanrepository/thuban/Doc/technotes/coding_guidelines.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- coding_guidelines.txt	10 Aug 2004 00:23:36 -0000	1.2
+++ coding_guidelines.txt	11 Dec 2004 02:03:47 -0000	1.3
@@ -104,7 +104,7 @@
       testsuite*.  Yes, all of it.  Even if you think your change won't
       break anything.
 
-    - All commits should be described in the ChangeLog file.  The esiest
+    - All commits should be described in the ChangeLog file.  The easiest
       way to do that is to write the ChangeLog entry first and use that
       as the commit message.