Changeset 19637 in josm for trunk/src/org/openstreetmap/josm/tools/bugreport/ReportedException.java

Timestamp:

2026-10-06T08:57:52+02:00 (5 days ago)

Author:

stoecker

Message:

detect the UTF-8 filename issue in non-UTF contexts, patch by wangi, fix #24940

File:

• trunk/src/org/openstreetmap/josm/tools/bugreport/ReportedException.java (modified) (3 diffs)

trunk/src/org/openstreetmap/josm/tools/bugreport/ReportedException.java

@@ -5 +5 @@
 import java.io.Serializable;
 import java.lang.reflect.InvocationTargetException;
+import java.nio.file.InvalidPathException;
 import java.util.ArrayList;
 import java.util.Arrays;
@@ -22 +23 @@
 import org.openstreetmap.josm.tools.Logging;
 import org.openstreetmap.josm.tools.StreamUtils;
+import org.openstreetmap.josm.tools.Utils;
 
 /**
@@ -279 +281 @@
 
     /**
+     * Check if this is caused by the name of a file which cannot be represented in the character set Java uses for
+     * file names. Java takes that character set from the locale, so this happens when JOSM runs in the C/POSIX locale,
+     * or with a locale which is not installed: file names are then ASCII only, and opening a folder which holds a
+     * non-ASCII name fails. See #14596.
+     * @return <code>true</code> if it is.
+     * @since 19637
+     */
+    public boolean isUnmappableFileName() {
+        return !"UTF-8".equalsIgnoreCase(Utils.getSystemProperty("sun.jnu.encoding"))
+                && StreamUtils.toStream(CauseTraceIterator::new).anyMatch(t -> t instanceof InvalidPathException
+                        && String.valueOf(((InvalidPathException) t).getReason()).contains("unmappable characters"));
+    }
+
+    /**
      * Iterates over the causes for this exception. Ignores cycles and aborts iteration then.
      * @author Michal Zangl