Hi! TL;DR:
- Properties are handled as byte sequences and are not converted to the command line encoding. - Bug or feature? Yesterday, while scripting, I stumbled upon a strange phenomenon with the CLI-tool svn.exe. File names and log entries are properly converted to encoding of command line or repository (Codepage 437 / 850, ANSI, UTF8 <=> UTF8). However, input and output of the commands svn prop* seems not. If I pass a string encoded in Codepage 850 or ANSI, it appears exactly as that in e.g. svn:externals. This behaviour is disastrous for file names containing umlauts or other characters beyond code point 127 (h7F). Then a "Überraschung" turns into a surprise… This behaviour seems only effecting svn.exe. Loading these strings into the TortoiseSVN property dialogue converts the every encoding and the issue don't comes up. Is it simple this an intended behaviour of the svn prop* commands (thus poorly documented) or simply a bug? Merci for a short reply. Cheers ToraxMalu --- Ich hoffe, das hilft dir! Wenn du noch weitere Fragen hast oder Unterstützung benötigst, stehe ich dir gerne zur Verfügung. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/tortoisesvn-dev/db1b2af6-59a7-4511-8355-77494e5ac240n%40googlegroups.com.
