No Korean Character in latest JOSM on Ubuntu 18.04

[geofictician]

I have used JOSM on Ubuntu desktop for years. I recently built a new Ubuntu desktop, using 18.04, and installed the latest stable JOSM (14824).

For the first time, I have a strange problem - perhaps OS related as opposed to JOSM, but I can't solve it.

JOSM won't display Korean characters. Pure tofu. Some other unicode areas I've tested work fine (including Chinese and Amharic). So I don't get what's going on. I have CJK configured and working fine on every other aspect of this new desktop. Only JOSM is missing Korean characters.

[josm@…]

Screenshot JOSM 14824 / Ubuntu 18.04

[Don-vip]

Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.

Please add all needed information according to this list:

• The required parts of the Status Report from your JOSM.
  • Please, use Report Bug from Help menu and copy & paste.
• Describe what behaviour you expected.
• Describe what did happen instead.
• Describe if and how the issue is reproducible.
• Add any relevant information like error messages or screenshots.

To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help → Report Bug.

Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!

[josm@…]

The required parts of the Status Report from your JOSM.

Is this the "status report"?

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-03-03 00:16:03 +0100 (Sun, 03 Mar 2019)
Build-Date:2019-03-02 23:16:53
Revision:14824
Relative:URL: ^/trunk

Identification: JOSM/1.5 (14824 en) Linux Ubuntu 18.04.2 LTS
Memory Usage: 821 MB / 3538 MB (616 MB allocated, but free)
Java version: 1.8.0_201-b09, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
VM arguments: [-Djosm.restart=true, -Djava.net.useSystemProxies=true]

Plugins:
+ FastDraw (34867)
+ PicLayer (34867)
+ apache-commons (34506)
+ continuosDownload (82)
+ ejml (34389)
+ geotools (34513)
+ jaxb (34678)
+ jts (34524)
+ log4j (34527)
+ measurement (34867)
+ opendata (34911)
+ reverter (34917)
+ utilsplugin2 (34915)

Last errors/warnings:
- W: Cannot lock cache directory. Will not use disk cache
- W: No configuration settings found.  Using hardcoded default values for all pools.

OSM API: https://opengeofiction.net/api

Describe what behaviour you expected.

I wanted to see Korean characters.

Describe what did happen instead.

I did not see Korean characters, I saw "tofu" (boxes for missing unicode).

Describe if and how the issue is reproducible.

I think this might be hard to reproduce. I built a new Ubuntu 18.04 desktop, with CJK enabled (because I often work in Korean). I have done this before, many times. I installed JOSM. In the past, I never had problem with seeing Korean characters in JOSM on Ubuntu, but previous desktops of Ubuntu were 16.04 or lower. This time I did have a problem. So some recent change to JOSM, or some recent change to Ubuntu, has caused difficulty in seeing Korean characters.

Add any relevant information like error messages or screenshots.

Screenshot was attached before. Was that missed?

[josm@…]

I will add some additional screenshots.

Japanese works fine! (First two screenshots).

Korean doesn't work. (Second two screenshots).

[josm@…]

Japanese works fine

[josm@…]

Japanese works fine

[josm@…]

Korean does not work

[josm@…]

Korean does not work

[Don-vip]

Thanks. The status report is mandatory for defects otherwise we have no idea about your environment.

[Don-vip]

What happens if you run JOSM with openjdk-11-jre package (currently openjdk 10.0.2+13-1ubuntu0.18.04.4)?

[josm@…]

Here is new environment:

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-03-03 00:16:03 +0100 (Sun, 03 Mar 2019)
Revision:14824
Build-Date:2019-03-02 23:16:53
URL:https://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (14824 ko) Linux Ubuntu 18.04.2 LTS
Memory Usage: 436 MB / 3980 MB (296 MB allocated, but free)
Java version: 10.0.2+13-Ubuntu-1ubuntu0.18.04.4, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
Java package: openjdk-11-jre:amd64-10.0.2+13-1ubuntu0.18.04.4
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-20ubuntu0.1
VM arguments: [-Djosm.restart=true, -Djava.net.useSystemProxies=true]

Plugins:
+ FastDraw (34867)
+ PicLayer (34867)
+ apache-commons (34506)
+ continuosDownload (82)
+ ejml (34389)
+ geotools (34513)
+ jaxb (34678)
+ jts (34524)
+ log4j (34527)
+ measurement (34867)
+ opendata (34911)
+ reverter (34917)
+ utilsplugin2 (34915)

Last errors/warnings:
- W: No configuration settings found.  Using hardcoded default values for all pools.

OSM API: https://opengeofiction.net/api

Exact same result. Identical screenshots - not sure you need them.

[anonymous]

As a point of comparison, I went to an old virtual machine I have running Ubuntu 16.04.

Here is the environment:

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-02-02 21:01:18 +0100 (Sat, 02 Feb 2019)
Build-Date:2019-02-04 21:50:11
Revision:14760
Relative:URL: ^/trunk

Identification: JOSM/1.5 (14760 ko) Linux Ubuntu 16.04.6 LTS
Memory Usage: 357 MB / 875 MB (57 MB allocated, but free)
Java version: 1.8.0_191-8u191-b12-2ubuntu0.16.04.1-b12, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
Java package: openjdk-8-jre:amd64-8u191-b12-2ubuntu0.16.04.1
VM arguments: [-Djosm.restart=true, -Djava.net.useSystemProxies=true]

Plugins:
+ FastDraw (34867)
+ continuosDownload (82)
+ measurement (34867)

Last errors/warnings:
- W: No configuration settings found.  Using hardcoded default values for all pools.
- W: Region [WMS_BLOCK_v2] Resetting cache
- W: Region [WMTS_BLOCK_v2] Resetting cache

OSM API: https://api.opengeofiction.net/api

Attached is screenshot in Korean. Works without problem.

[josm@…]

Attachment showing Korean Language JOSM working without problem on Ubuntu 16.04

[mdk]

I have no problems with Ubuntu 19.10. every thing looks fine for me:

Identification: JOSM/1.5 (15951 ko) Linux Ubuntu 19.10
Memory Usage: 337 MB / 1980 MB (122 MB allocated, but free)
Java version: 11.0.6+10-post-Ubuntu-1ubuntu119.10.1, Ubuntu, OpenJDK 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
Java package: openjdk-11-jre:amd64-11.0.6+10-1ubuntu1~19.10.1
Java ATK Wrapper package: libatk-wrapper-java:all-0.35.0-3
libcommons-compress-java: libcommons-compress-java:all-1.18-3
libcommons-logging-java: libcommons-logging-java:all-1.2-2
fonts-noto: fonts-noto:-
VM arguments: [-Djosm.restart=true, -Djosm.dir.name=JOSM-latest, -Djava.net.useSystemProxies=true]

[simon04]

Are you using the package from Ubuntu's official repository? ​https://packages.ubuntu.com/search?suite=bionic&searchon=names&keywords=josm If so, you might need to install josm-l10n.

Also notice that you're running a very outdated version. You might want to follow those instruction steps Download#LinuxRepositories.

[geofictician]

Observations to the above comments. I am the original poster - but I can't figure out what I was logging in as at that time - it appears I created some kind of alias prefixed with "josm@" but this site is proving difficult to interpret as far as recovering a lost username.

In fact, this problem "fixed itself" some time ago. I didn't notice that it had fixed itself, however, because I didn't do any mapping in Korean for an extended period, and thus didn't need the functionality.

I believe the problem was more on the Ubuntu side than on the JOSM side. I expect one of the periodic upgrades resolved the issue.

To the person who commented "notice that you're running a very outdated version." - that's a silly comment. The problem was reported over a year ago. The screenshots are from over a year ago. At THAT time, it wasn't outdated.

[skyper]

How about a font problem ? Have a look at fonts-noto and when it was installed (/var/log/apt/ or /var/log/dpkg.log*).