Bug 327058

Summary: ant editor does not respect XML file encoding
Product: [Eclipse Project] Platform Reporter: Hao Zhang <digizer0>
Component: AntAssignee: Platform-Ant-Inbox <platform-ant-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3    
Version: 4.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
problematic xml file in Shift_JIS encoding
none
problematic xml file in Windows-31j encoding none

Description Hao Zhang CLA 2010-10-05 23:52:56 EDT
Build Identifier: 20100917-0705

when open an ant build file(build.xml), the ant editor does not respect certain kinds of encoding specified in the XML header. To be specific, among all encoding I tested:UTF-8, EUC-JP, Shift_JIS, Windows-31j, the former 2 encodings were respected and the latter 2 were not processed properly.

Reproducible: Always

Steps to Reproduce:
1.create a normal Java project
2.create a xml file named build.xml
3.make sure the xml file is opened in Shift_JIS, Windows-31j encoding
4.open build.xml with ant editor
5.copy the following lines into the editor(change encoding accordingly)
<?xml version="1.0" encoding="Shift_JIS" ?>

<project name="proj" default="compile" basedir=".">

    <target name="compile" description="コンパイルします" />
	
    <target name="clean" description="antで作られたファイル等を削除します" >
        <delete dir="${build.dir}"/>
    </target>

</project>
Comment 1 Hao Zhang CLA 2010-10-05 23:55:02 EDT
Created attachment 180293 [details]
problematic xml file in Shift_JIS encoding
Comment 2 Hao Zhang CLA 2010-10-05 23:56:14 EDT
Created attachment 180294 [details]
problematic xml file in Windows-31j encoding
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:36:22 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.