[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 07:46:09.000000000 -0400
+++ shadow/75679.tmp.5734	2005-08-01 09:21:19.000000000 -0400
@@ -66,6 +66,15 @@
 
 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?
 
+
+------- Additional Comments From rharinath at novell.com  2005-08-01 09:21 -------
+Hmm...  It appears there's no problem with the offsets -- at least I
+couldn't find any.
+
+What is puzzling is that changing the size of the buffer doesn't seem
+to alter the behaviour either, even if the buffer is large enough to
+contain the whole file.
+