tracker issue : CFB-4130079

select a category, or use search below
(searches all categories and all time range)

Data Loss Due to File Encoding Issue in Blizzard Beta1

| View in Tracker

Status/Resolution/Reason: Closed/Deferred/

Reporter/Name(from Bugbase): Travis Walters / Travis Walters (Travis Walters)

Created: 03/18/2016

Components: Preferences

Versions: 2016

Failure Type: Unspecified

Found In Build/Fixed In Build: Beta1_v31 /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Win All

Vote Count: 0

Problem Description:

When I create a new project, it does not give an option to set any base file encoding as it assumes the file encoding for the project is UTF-8 even though most of the documents have ISO-8859-1 encoding in this scenario.

If I have the File Navigator open on the left with a file selected and then go to Window -> Preferences -> Workspace and set the encoding to ISO-8859-1, it still has the UTF-8 encoding and neglects to change the encoding to ISO-8859-1. 

This thread discusses the problem and related issues:{E7CAEBDE-A8F5-4F52-B22D-E94600B746E8}&topid={3E201D69-1FFA-42F4-A96E-7905DB3D0C1E}

I am working as a developer on a project that originated in Europe so for whatever reason the original developers editor must have used ISO-8859-1 encoding.

I am attaching one of those files for reference that uses the ISO-8859-1 encoding.

Also note that if I save the file once opened that the original encoding would be lost and invalid characters would show as a diamond with a question mark in the middle of the diamond - not sure what to call this. Regardless, data loss occurs with this.
Steps to Reproduce:

Create a project in Blizzard that has a folder and the meta.cfm attached file within that folder. Try to change the encoding in the Window -> Preferences -> Workspace to ISO-8859-1. Open the file and see that characters are still encoded as UTF-8.

Actual Result:

File still UTF-8 encoded.

Expected Result:

ISO-8859-1 File Encoding.

Any Workarounds:

If I use File Navigator, right click the project, click properties, click resources, and change the text file encoding to ISO-8859-1, and submit, then any files underneath the project that inherit the encoding type from the parent will then use the ISO-8859-1 file encoding.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4130079

External Customer Info:
External Company:  
External Customer Name: Travis Walters
External Customer Email: TWALTERS84@HOTMAIL.COM
External Test Config:  

Bug File Paths:
\\\Prereleasebugfiles\ColdFusion Builder\3.1\Beta1_v31\4099674\meta.cfm



Added By:prk Note Added: This is a valid scenario, we will take this up in the next version, Thanks! Date Added :2015-12-16 15:23:22.0 Added By: PreRelease User User Name:Travis Walters Note Added: Entered Bug. Date Added :2015-12-14 10:09:26.0
Comment by CFwatson U.
26539 | March 18, 2016 05:26:11 AM GMT