Modify ↓
#14724 closed defect (worksforme)
Tag values not readed correctly from .osm file (decoding problem?)
Reported by: | sommerluk | Owned by: | team |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core | Version: | |
Keywords: | template_report javabug | Cc: |
Description
What steps will reproduce the problem?
- Open the attached file.
- Select the (only) node of the file and look at the value of the “name” key (in the right panel of JOSM).
What is the expected result?
The value is “𠀐𠀑”.
What happens instead?
The value is “𠀐𠀐𠀑”.
Comment
Maybe an decoding problem that occures with characters outside the first 65536 characters of Unicode?
Please provide any additional information below. Attach a screenshot if possible.
URL:http://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2017-04-02 01:45:00 +0200 (Sun, 02 Apr 2017) Build-Date:2017-04-02 01:34:50 Revision:11826 Relative:URL: ^/trunk Identification: JOSM/1.5 (11826 de) Linux openSUSE Leap 42.1 (x86_64) Memory Usage: 388 MB / 910 MB (71 MB allocated, but free) Java version: 1.8.0_60-b27, Oracle Corporation, OpenJDK 64-Bit Server VM Screen: :0.0 1366x687 Maximum Screen Size: 1366x687 Java package: java-1_8_0-openjdk:x86_64-1.8.0.60 Dataset consistency test: No problems found Plugins: + DirectUpload (33182) + editgpx (33004) Last errors/warnings: - W: Erweiterungen aktualisieren - org.openstreetmap.josm.plugins.PluginHandler$UpdatePluginsMessagePanel[,0,0,0x0,invalid,layout=java.awt.GridBagLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=9,maximumSize=,minimumSize=,preferredSize=]
Attachments (1)
Change History (6)
by , 8 years ago
comment:3 by , 8 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Me neither. Please upgrade your version of Java. 8u60 was released in August 2015, current version is 8u131.
comment:4 by , 8 years ago
It works with the new Java version!
I’ve updated to 1.8.0.121-25.1 (the currently newest version in the standard openSuse update repository) and indeed the problem is gone. So it seems this was a Java bug.
Thanks!
comment:5 by , 8 years ago
Keywords: | javabug added |
---|
Note:
See TracTickets
for help on using tickets.
bug.osm