Ah, those appear to have been desired to be "tab" characters then.
[EDIT] Correction, the "tree" command creates a nifty ASCII-art file directory. So the different characters are the classic menu-drawing ASCII, and whitespace.
[EDIT2] Furthermore, piping it to a text file on Windows results in those bad characters instead of the ASCII-art menus.
[EDIT3]
³ = │ = Extended ASCII 179 = 0xB3
À = └ = Extended ASCII 192 = 0xC0
 = ┬ = Extended ASCII 194 = 0xC2
à = ├ = Extended ASCII 195 = 0xC3
Ä = ─ = Extended ASCII 196 = 0xC4
etc.
[EDIT4]
http://stackoverflow.com/questions/138576/sav … unicode-support
Anyhow, this isn't the board conversion's fault. Dunno if we should fix this...
There's more of this output from other utilities, example for Qbix:
https://www.google.com/search?q=%22%C3%82%C2% … iw=1429&bih=585
"I see a little silhouette-o of a man, Scaramouche, Scaramouche, will you
do the Fandango!" - Queen
Stiletto