Opened 17 years ago

Closed 17 years ago

Last modified 17 years ago

#139 closed defect (fixed)

Schemareport encoding problem with tilda's

Reported by: zspitzer Owned by:
Priority: medium Milestone: 1.2
Component: General Version: 1.2.0
Severity: major Keywords:
Cc: External ID: 938891, 936049


There is a problem with the schema report, when the xsl transformation is done, the tildas '~' used by king oracle FDO are decoded into '-x7e-' which then break the view data and view feature display.

They fail with 'The specified class was not found.' and a Null reference respectively.

Change History (4)

comment:1 by rexszeto, 17 years ago

External ID: 938891

comment:2 by rexszeto, 17 years ago

External ID: 938891938891, 936049

comment:3 by rexszeto, 17 years ago

Resolution: fixed
Status: newclosed

Main issue fixed with

Added UTF-8 Encoding Fixed in 1.2.x by submission Fixed in trunk by submission

comment:4 by rexszeto, 17 years ago

The following two submissions fix the schema report pages to function correctly with the character escaping re-introduced by rolling back the ticket#184:

Fixed by submission Fixed by submission

Note: See TracTickets for help on using tickets.