Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fix a small rdoc markup mistake.

  • Loading branch information...
commit 5f357be31be24a713fa12070348aed1a423de34e 1 parent 8a8afd5
Manfred Stienstra authored

Showing 1 changed file with 2 additions and 2 deletions. Show diff stats Hide diff stats

  1. 4  README.rdoc
4  README.rdoc
Source Rendered
@@ -13,9 +13,9 @@ To ensure that our internal encoding is always at least valid we can choose to
13 13
 do one of two things.
14 14
 
15 15
 1. Throw an exception when we receive invalid character data. (ie. Our internal
16  
-encoding is UTF-8 and we receive Latin-1 data or invalid UTF-8)
  16
+   encoding is UTF-8 and we receive Latin-1 data or invalid UTF-8)
17 17
 2. Accept whatever we get and try to mold it in such a way that it becomes
18  
-usable in our application.
  18
+   usable in our application.
19 19
 
20 20
 It is generally accepted to go for the second option, most of the times the
21 21
 end-user has no way of solving these problems because a vendor made a mistake.

0 notes on commit 5f357be

Please sign in to comment.
Something went wrong with that request. Please try again.