Support for additional file encoding

Comments: 12

• 30 Jul, '21
  Pitty

  I have a lot of code in Delphi XE2 and if I merge any conflicted file in GitKraken, or even use the Beyond Compare called from GitKraken, the files are converted to UTF-8. Delphi doesn't work fine with UTF-8. It's very very annoying. Why GitKraken cannot simply maintain the encoding?

• 19 Aug, '21
  Alexander Samsig

  On a project at work, some files are using ISO-8859-1, and it makes it almost impossible for me to be productive while using GitKraken, as I'll regularly rewrite files into UTF-8 without noticing until I open a pull request, and then I have to go back and fix it up, which is very demotivating.
  This is also the first con I bring up when talking about GitKraken, other than this GitKraken is by far the most productive Git client I've used, and I'd love to be able to strike this con off the list.

• 17 Sep, '21
  Joey Kelroy Admin

  "Support json files" (suggested by Paul on 2021-09-16), including upvotes (1) and comments (0), was merged into this suggestion.

• 14 Dec, '21
  Cédric

  As a French speaking developer, I have a lot of code using special characters that are encoded in ISO-8859-1.
  I have to admit that it is a pain to have to rewrite often the whole translations file or comments in the code to make it still usable. Some message displayed for the user are defined in the code in French directly.
  Some dev doesn't want to work with GitKraken due to this only, and I have a hard time to say something against that.

• 30 Dec, '21
  Pedro Nascimento

  Several legacy projects I work on are ISO-8859-1, so I can't merge using gitkraken without breaking the code where there are special characters

• 02 Feb
  Ghani

  same probleme with Pedro Nascimento

• 03 Mar
  Sebastian

  Please support other encodings than UTF-8. For now I have to rely on Sourcetree which seems to be the only app that support this.

• 05 May
  DM

  Working with SQL files with encoding Win-1252 gives me a hard time and productivity is slowed down. It might even be that the team will not use GitKraken as these issues are avoidable in 2022. So please support different encodings.

• 23 May
  Jin

  I would like you to support Gitkraken to be compatible with non-utf-8 files.
  Our user are using files that shouldn't be encoded. So they are uncomfortable at this time.
  They can't stand the inconvenience and use other clients.

• 07 Jun
  Patrick

  Nearly all the files i'm working with are in Windows-1252
  This is the one big thing that keeps me from suggesting to my team-lead that all my teammates should use GitKraken too

• 10 Jun
  Patrick

  I want to add something to my previous comment:
  
  I would not mind if gk-client only displays the encoding in a wrong way, that's acceptable.
  The real problem is, that it saves the files in UTF-8 when they are changed within gk-client.
  
  As an example i created a new file in codepage 1252 with content: `äöüéèê` (The file contains bytes: E4 F6 FC E9 E8 EA)
  Then, within gk-client, i choose `Edit this file` on that file, add a `d` at the end and save it.
  
  Now the bytes are: EF BF BD EF BF BD EF BF BD EF BF BD EF BF BD EF BF BD 64
  
  That means gk-client changed every single char to EF BF BD, or in other words to the UTF-8 replacement character.
  That happens too when discarding any hunk. The file is completely rewritten.
  
  If the gk-client at least would only write the changed parts and doesn't change the rest of the file, that would be great already.
  
  With this behavior I will have to be very carefull what actions I'm executing with gk-client and for which I'm forced to use other tools.

• 05 Sep
  Kévin

  Hello,
  
  My team uses Delphi 5 which doesn't support UTF-8.
  So it's very problematic when GitKraken make bad conversions to UTF-8 from encoding like windows-2252, iso-8859-1.
  Characters like accents (éèà) and € are lost.
  
  GitKraken make conversion when merging, hunk discard, line staging...
  
  We have 5 license for the moment and we are 10 persons in the team.
  
  When will the fix be planned?
  
  If the fix doesn't arrive fast enough, we are considering leaving GitKraken for another Git client that handles these encodings like TortoiseGit.
  
  Have a nice day