Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341703 - Wrong encoding determined from content
Summary: Wrong encoding determined from content
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-02 14:37 EDT by Simão CLA
Modified: 2011-04-04 04:21 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simão CLA 2011-04-02 14:37:51 EDT 
Build Identifier: 20110301-1815

JSF fragments and text files created in eclipse windows plataform (default encoding is iso-8859-1) are determined as utf-8 files in eclipse linux plataform =(

Reproducible: Always

Steps to Reproduce:
1. Create a JSF fragment in windows (default encoding is iso-8859-1)
2. Copy projet to linux
3. Open fragment in linux (determine utf-8 enconding)
Comment 1 Dani Megert CLA 2011-04-04 04:21:31 EDT 
Some file types have a default encoding (e.g. 'UTF-8' for XML files) but most don't. In those cases the platform default is used. If you use the same files on different platforms then you should set the default encoding on the project so that the encoding is also shared via repository.