[Mono-bugs] [Bug 75679][Nor] Changed - sometimes SeekableStreamReader translates buffers into incorrect chars

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by rharinath at novell.com.

http://bugzilla.ximian.com/show_bug.cgi?id=75679

--- shadow/75679	2005-08-01 05:15:16.000000000 -0400
+++ shadow/75679.tmp.4823	2005-08-01 07:46:09.000000000 -0400
@@ -56,6 +56,16 @@
 Created an attachment (id=15517)
 the example code that does not compile. It's from http://www.geocities.co.jp/SiliconValley/5459/
 
 
 ------- Additional Comments From atsushi at ximian.com  2005-08-01 05:15 -------
 (btw, the attached example is under BSD license.)
+
+------- Additional Comments From rharinath at novell.com  2005-08-01 07:46 -------
+It appears that SeekableStreamReader always positions the pointer at a
+character boundary when manipulating the pointer in 'buffer'.
+
+It can possibly end up seeking to the middle of a multi-byte character
+if the requested position is outside the buffer.  Do we know if all
+callers of SeekableStreamReader.Position.set ensure the offset is at a
+character boundary?
+