Does SourceTree support international characters? I tried to open source files with Greek comments and instead of greek letters I get weird characters.
You currently have no plans to support other encodings? What kind of response is that? Developers work the world over, some working in different languages or on legacy projects where different encodings are found. At least providing a way to allow users to set the encoding used when displaying diffs would be preferred... Surely it cannot be that difficult to implement a pre-parser...
Nevermind...
Too much hassle for such a basic thing. Every other git/mercurial client I've used had no problem with greek letters. I will just go back to Tortoise then...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Apostolos,
SourceTree supports UTF-8/Latin-1 encodings which generally support the majority of required characters. If you use different encodings then you'll get unexpected characters. Perhaps try saving your files in one of these encodings provided they support the characters you need and it should work fine.
We don't currently have any plans to support other encodings, however.
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, The file I was refering to are source files from Delphi 7, in which case I cannot make a change the encoding of those files. And even if I could, this would be a tedious job, re-enconding all my source files every time I make a change.
I cannot see where ST supports that utf-8 you claim. Even opening plain text files, I get weird characters instead of greek letters.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Apostolos,
It would suggest that the file either isn't in that encoding or has mixed encodings within the file (this isn't uncommon). We definitely support UTF-8/Latin-1 character sets, otherwise most people wouldn't be able to read files. Additionally, we have support for Japanese which would require this of us.
Perhaps you could open up an issue on jira.atlassian.com with some example files that we could take a look into? This way I could load the files into SourceTree myself and take a look to see what's going on.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.