[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fossil-users
Subject:    Re: [fossil-users] UTF-8 and Binary Files
From:       David Botham <dbotham () infoblox ! com>
Date:       2014-08-27 21:29:17
Message-ID: 5F7265B990650F43AADC5B2135E420F21D060D9D () x2008mb2 ! infoblox ! com
[Download RAW message or body]

> -----Original Message-----
> From: fossil-users-bounces@lists.fossil-scm.org [mailto:fossil-users-
> bounces@lists.fossil-scm.org] On Behalf Of Joel Bruick
> Sent: Monday, August 25, 2014 8:43 PM
> To: Fossil SCM user's discussion
> Subject: Re: [fossil-users] UTF-8 and Binary Files
> 
> Hi David,
> 
> David Botham wrote:
> 
> 	Yes, I am editing in Komodo 8.5.3 on a Windows 7 workstation.
> 
> 	I will peek at the files in a hex editor and see what I can see...
> 
> 
> I use Komodo on Windows 7 quite a bit and have never had this problem.
> Does Komodo recognize the file as UTF-8 in the status bar? By default,
> it uses the system encoding (CP-1252 on my computer)  for new files. If
> it's showing some other encoding, change it to UTF-8 and re-save the
> file.
> 
> Also, if you go into the Komodo preferences, under the
> Internationalization category, the first option is "Use encoding defined
> in environment: [...]". I recommend unchecking this if you haven't
> already and setting the "Custom encoding" option to UTF-8. This should
> help avoid problems with files you create in the future (assuming your
> problems aren't due to a bug in Fossil's invalid UTF-8 detection, of
> course).

I set both of these settings.  

I am not getting the warnings, so, hopefully this fixed the problem.

Thanks for the great tips!

David 


> 
> Hope this helps in some way...


[prev in list] [next in list] [prev in thread] [next in thread]