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

Bug 343795

Summary:

DBCS4.1: XML Editor fails to handle CJK Extension B as an element name.

Product:

[Eclipse Project] PDE

Reporter:

Masaihko Maedera <maedera>

Component:

Assignee:

PDE-UI-Inbox <pde-ui-inbox>

Status:

RESOLVED INVALID

QA Contact:

Severity:

normal

Priority:

CC:

cgold, curtis.windatt.public, daniel_megert, pwebster, remy.suen

Version:

3.6

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
TOC_U20B9F.xml can be opened with Table of Contents Editor.	none

Description Masaihko Maedera

2011-04-26 01:34:18 EDT

Build Identifier: I20110419-2200

OS: Red Hat Linux 6
Eclipse SDK 4.1
JRE: IBM Java 1.6.0

XML Editor fails to handle a string with CJK Extension B as an element name.
It marks an error on the string.

Reproducible: Always

Steps to Reproduce:
1. Download and import TOC_U20B9F.xml, attached to this bug report.
2. Open it with "Table of Content Editor".
3. Click "Source" tab
4. Verify that an unexpected error is marked on <&#x20B9F; />,
   though the XML Standard allows CJK Extension B in element names.

Comment 1 Masaihko Maedera

2011-04-26 01:37:16 EDT

Created attachment 194035 [details]
TOC_U20B9F.xml can be opened with Table of Contents Editor.

Comment 2 Chris Goldthorpe

2011-04-29 13:55:30 EDT

Reassigning to the PDE team which owns this editor.

Comment 3 Curtis Windatt

2011-05-02 17:14:03 EDT

Dani, is a translation problem such as this a priority for the RC builds?

Comment 4 Dani Megert

2011-05-03 11:58:31 EDT

Sorry but the given snippet is not valid XML (try http://validator.w3.org/#validate_by_input):

# Warning Line 5, Column 2: character "<" is the first character of a delimiter but occurred as data

	<&#x20B9F; />

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.