Opened 17 years ago
Closed 16 years ago
#23 closed defect (wontfix)
Problem importing unicode character references using GAST
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | v2.1 beta 2 |
Component: | GAST | Version: | |
Keywords: | metadata, unicode | Cc: |
Description
Using the GAST import functionality with Postgres, it seems impossible to insert XML with unicode character references into the database.
For instance, when trying to add metadata, with a word like "mañana" encode like this "mañana", then using the GAST import functionality, this is what happens:
1. "mañana" is imported like this "mañana" (interpreted) 2. "mañana" is imported like this "mañana" (nothing happens) 3. "mañana" is imported like this "mañana" (& is replaced by & not &) 4. "mañana" is imported like this "mañana" (stays the same)
The first and last one seem OK, if it wasn't for bug #19 (editing special character getting messed up).
In general: the GAST import tool should "never" interpret any unicode character reference before inserting metadata in the database. If users want to define their metadata in codes like, "mañana" it should let them do so. Now this seems not to be possible.
It may have been fixed, but the ticket is removed because of its age.