Modify

Ticket #3290 (new defect)

Opened 2 years ago

Last modified 2 years ago

Make sure an XML parser fully supporting UTF-16 is used by JOSM

Reported by: Gubaer Owned by: team
Priority: major Component: Core
Version: Keywords:
Cc:

Description

See the discussion on dev and josm-dev:

  • there's a problem with XML parsers which don't handle  UTF-16 correctly. Apparently, they insert duplicates of surrogate code points in OSM keys or values while parsing. After a couple of IO operations even small OSM files/fragments can become very large. In OSM the problem was spotted because of  gothic code points in name:got-tags.

JOSM should either ship a compliant parser with it's distribution or check/enforce on startup that a known compliant parser is on the classpath.

Attachments

Change History

comment:1 Changed 2 years ago by Gubaer

Here the links to the two threads:

comment:2 Changed 2 years ago by stoecker

  • Priority changed from critical to major
View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will be changed from team. Next status will be 'new'
Next status will be 'needinfo'The owner will change to Gubaer
as duplicate The resolution will be set to duplicate. Next status will be 'closed'The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous. Next status will be 'assigned'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.