relpipe-data/classic-example.xml
branchv_0
changeset 151 5697a01db388
parent 146 8c2e2dbee5cc
child 166 d8be473e0d86
equal deleted inserted replaced
150:7d7d4e1f293f 151:5697a01db388
   114 			or add some quotes/apostrophes (which still requires escaping, because what if we have e.g. name field containing an apostrophe?).
   114 			or add some quotes/apostrophes (which still requires escaping, because what if we have e.g. name field containing an apostrophe?).
   115 			And parsing such inputs by classic tools and regular expressions is not easy and sometimes even not possible.
   115 			And parsing such inputs by classic tools and regular expressions is not easy and sometimes even not possible.
   116 		</p>
   116 		</p>
   117 		
   117 		
   118 		<p>
   118 		<p>
   119 			There are also other problems like character encoding, missing meta-data (e.g. field names and types), joining multiple files (Is there always a new-line character at the end of the file? Or is there a BOM at the beginning of the file?)
   119 			There are also other problems like character encoding, missing meta-data (e.g. field names and types), joining multiple files (Is there always a new-line character at the end of the file? Or is there some nasty BOM at the beginning of the file?)
   120 			or passing several types of data in a single stream (we have list of animals and we can have e.g. also a list of foods or list of our staff where each list has different fields).
   120 			or passing several types of data in a single stream (we have list of animals and we can have e.g. also a list of foods or list of our staff where each list has different fields).
   121 		</p>
   121 		</p>
   122 
   122 
   123 	</text>
   123 	</text>
   124 
   124