Actions
Bug #1009
closedProblem with non-ascii characters
Start date:
03/11/2003
Due date:
% Done:
0%
Estimated time:
Bugzilla-Id:
1009
Description
One of the students entering data added a bounding geographic lat/long value as
deg/minutes/seconds, using the special PC character for degrees. This is not the
format described for lat/long (one should use fractional degrees), but the use
of the special degree character (which has a character code above 127) results
in a UTF-8 error of 'illegal one character unicode character' when the saved
data is parsed.
It is not clear just where the problem occurs. The degree symbol is in the data
that is successfully submitted to metacat, but problems occur later when
editing. (Maybe the problem is with Xalan?)
Related issues
Actions