Logging files names that contain Norwegian letters in the file name in Unix OS using a Jar executabl-CodePudding

The

In the end the logs.log file should look like this:

2022-10-25 14:27:02 INFO Logger:99 - File: 'DN_Oppmålings.pdf' 2022-10-25 14:27:02 INFO Logger:99 - File: 'Salg_av_gærden.pdf'

However, this is how it ends up in the log file, all Norwegian letters are represented with a square.

I can't seem to figure out why it happens. It probably has something to do with the encodings. Because when I run it on windows locally, everything runs as expected and I get the result I need. But when I build the project as an executable jar and run on the server it gets wrong.

Here is the code I am using.

public static void renameFiles3(File[] files) throws IOException { for (File filename : files) { if (filename.isDirectory()) { renameFiles3(filename.listFiles()); } else { String fileNameString = filename.getName(); if (fileNameString.contains("å") || fileNameString.contains("ø") || fileNameString.contains("æ")){ logger.info("File: '" filename.getName()); } } } } public static void main(String[] args) { File[] files = new File(path).listFiles(); try { renamer.renameFiles3(files); } catch catch(IOException ex){ logger.error(ex.toString()); } }

Someone pointed out that the encoding should be specified, but I am not sure how that is done. If I run "locale" command on the Unix server this is what I get as output.

[e1111111@ilt repository]$ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=

I use Putty to run the jar file. Here are the configs.

Stacktrace of the error I get when running the jar:

java.nio.file.NoSuchFileException: ./documentRepository/DN_Oppm�lings.pdf at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116) at java.base/sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:430) at java.base/sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:267) at java.base/java.nio.file.Files.move(Files.java:1422) at com.example.fixfilenamesonfileserver.Renamer.renameFiles2(Renamer.java:105) at com.example.fixfilenamesonfileserver.Renamer.renameFiles2(Renamer.java:89) at com.example.fixfilenamesonfileserver.Renamer.renameFiles2(Renamer.java:89) at com.example.fixfilenamesonfileserver.Renamer.renameFiles2(Renamer.java:89) at com.example.fixfilenamesonfileserver.Renamer.renameFiles2(Renamer.java:89) at com.example.fixfilenamesonfileserver.Renamer.renameFiles2(Renamer.java:89) at com.example.fixfilenamesonfileserver.Renamer.renameFiles2(Renamer.java:89) at com.example.fixfilenamesonfileserver.Renamer.main(Renamer.java:154)

What makes it even more strange, is that I can create for instance a folder with mkdir containing Norwegian letters in the name and it would be displayed correctly and also logged correctly if I create a file with Norwegian letters.

CodePudding user response：

Some time ago I wrote an answer for a very similar problem.

As stated in the aforementioned solution, the problem could be related with the use of different charsets in your local Windows laptop (probably, cp-1252 or some variant) and your server.

As suggested, please, consider review the charset which is in place in the JVM in every environment, and review and adapt if necessary the value of the file.encoding system property on your laptop and the server environment, maybe it will help you solve the problem.

Probably running your jar with a proper value for the file.encoding JVM property may do the application work properly:

java -Dfile.encoding=UTF-8 -jar your_app.jar

CodePudding user response：

I suspect there is no problem with your Java nor your file.

The problem is likely with the app you use to view that text. That app is using a font that lacks a glyph for those characters.

Edit your Question to note the app and OS if you want further assistance.