> I would try to edit the dump file with a hexeditor and replace the > offending two bytes with two spaces (or the proper UTF-8 character > if you know what should be there and the UTF-8 sequence has the same > number of bytes).
Ok, lets take some hex editor and get rid of those bad sequences. > I hope the number of paths affected by this problem > is small enough to keep this solution practical. I'll hope so too - lets see how to split my dump to get hexedit solution running. > > > If none of the third-party dump manipulation tools can do that, > > ... then we should provide our users with a way of fixing it, > as we did for e.g. badly encoded revision properties. That would be a "nice-to-have" feature :). > Daniel, please keep in mind that this is the *users* list. Yes. > Maybe Torsten would like to try this, but I doubt that modifying > Subversion's code is the kind of advice he was looking for. You're right ;-) > And I really don't think that this suggestion is something that people > who are not familiar with Subversion's code base should attempt to do. > If people modify the code without understand it well the chances of > unintentionally breaking things are way too high. > I can try but as you said - i am not familiar with the code base and i'll bet, things are more worse after my modifications ;-). > It's bad enough that Torsten has to edit the dump file to fix this. But i will take this "red pill" to see where the journey ends :-D
smime.p7s
Description: S/MIME cryptographic signature
