> a caveat in its implementation. StyledEdit uses BTextView to provide > the majority of the text editing functionality. The caveat is that > BTextView is set up to only handle UTF-8 text. UTF-8 is always used in BeOS, this was a design decision. It would not make sense to support all the different character sets etc. > properly with the BTextView. Also, I have come to the realization that > the original StyledEdit used the convert_to_utf8/convert_from_utf8 > solution. So, if we move to that we are still providing the same level > of functionality. I think this is the correct way. > Although this approach still has the drawback that files that are > loaded and re-saved may not be binary identical after no changes, I > think this is acceptible. This is acceptible because we still provide Yes, should be acceptable. You a not writing DiskProbe. Marcus