Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 325474

Summary:

[Backport] [content type] Platform doesn't recognize xml encoding attribute with additional whitespaces

Product:

[Eclipse Project] Platform

Reporter:

Gary Karasiuk <karasiuk>

Component:

Resources

Assignee:

Platform-Resources-Inbox <platform-resources-inbox>

Status:

RESOLVED FIXED

QA Contact:

Severity:

major

Priority:

CC:

nsand.dev, Szymon.Brandys

Version:

3.4.2

Target Milestone:

3.4.2+

Hardware:

OS:

Windows XP

Whiteboard:

Bug Depends on:

293773

Bug Blocks:

Attachments:

Description	Flags
Fix + test	none

Description Gary Karasiuk

2010-09-16 10:18:42 EDT

Steps to reproduce

1) create an XML file, and use encoding="gb2312" (or encoding="UTF-16")
2) Observe from the properties view that the encoding is gb2312
3) Add a blank before the equals sign, e.g. encoding ="gb2312"
4) Observe from the properties view that the encoding has been ignored, that the encoding is now the default UTF-8

This is a regression from 3.0.2. The customer that I'm working with, felt that this defect should be a "major" defect, since they have a lot of these files.

Comment 1 Nick Sandonato

2010-09-17 11:53:37 EDT

This looks like it has been resolved in later releases via Bug 293773.

Comment 2 John Arthorne

2010-09-17 15:14:49 EDT


*** This bug has been marked as a duplicate of bug 293773 ***

Comment 3 Nick Sandonato

2010-09-17 15:48:01 EDT

We would like this fixed in 3.4.2  if possible for an adopter product.

Comment 4 Szymon Brandys

2010-09-20 08:53:40 EDT

Created attachment 179241 [details]
Fix + test

Comment 5 Szymon Brandys

2010-09-20 09:20:46 EDT

The fix and test checked in to R3_4_maintenance.