This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13796 - [Applet30] \u escaped characters in grammar applets
Summary: [Applet30] \u escaped characters in grammar applets
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Grammar Test Applets (show other bugs)
Version: Working drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Michael Dyck
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
: 29568 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-16 19:24 UTC by Andrew Eisenberg
Modified: 2016-04-27 20:36 UTC (History)
2 users (show)

See Also:

Attachments

Description Andrew Eisenberg 2011-08-16 19:24:35 UTC 
When I parse the expression '\u0045' I see the following:

|START [1:0 - 1:8]
|   QueryList [1:0 - 1:8]
|      Module [1:0 - 1:8]
|         MainModule [1:0 - 1:8]
|            Prolog [1:0 - 0:0]
|            QueryBody [1:0 - 1:8]
|               Expr [1:0 - 1:8]
|                  StringLiteral 'E' [2:1 - 1:8]

I expected:

|                  StringLiteral '\u0045' [2:1 - 1:8]
Comment 1 Michael Dyck 2011-08-17 03:29:57 UTC 
The conversion of unicode escapes (\uHHHH) is happening in code that JavaCC generates. The odd thing is, we're explicitly telling JavaCC (via the JAVA_UNICODE_ESCAPE option) to generate that code. We've done so since 2005/03/25. It looks like this came about from confusion/conflation with the UNICODE_INPUT option (which controls whether the input stream object reads "Unicode files" or ASCII files).
Comment 2 Michael Dyck 2011-08-17 15:14:15 UTC 
Unfortunately, simply disabling the option causes some tests to fail, so this will take some investigation.
Comment 3 Andrew Eisenberg 2011-09-28 18:18:19 UTC 
This issue came to my attention due to test cases in our QT3 test suite. I've reported the bug there as Bug #14328.
Comment 4 Josh Spiegel 2016-04-15 20:39:32 UTC 
*** Bug 29568 has been marked as a duplicate of this bug. ***
Comment 5 Michael Dyck 2016-04-27 20:36:52 UTC 
I tried disabling the JAVA_UNICODE_ESCAPE option again today, and (to my surprise) the test-failures mentioned in comment #2 no longer occurred.

I'm surprised because the version of JavaCC I'm using hasn't changed since I wrote comment #2. However, the versions of Java and Ant that I'm using *have* changed, so perhaps the bug lay somewhere in there.

Anyhow, the applets now deliver the result that Andrew expected originally, so I'm marking this bug resolved-fixed.