Skip to content

Checks java file encoding on windows (PR #75)#76

Open
ab3dat wants to merge 2 commits intoSerCeMan:masterfrom
ab3dat:master
Open

Checks java file encoding on windows (PR #75)#76
ab3dat wants to merge 2 commits intoSerCeMan:masterfrom
ab3dat:master

Conversation

@ab3dat
Copy link
Copy Markdown

@ab3dat ab3dat commented Jul 9, 2019

This implementation checks whether the UTF-8 file encoding is set when working on windows. If the wrong file encoding is set mounting the drive works, but accessing and working on it doesn't work.

Details see pull request #75

This implementation checks whether the UTF-8 file encoding is set when working on windows. If the wrong file encoding is set mounting the drive works, but accessing and working on it doesn't work.

Details see pull request SerCeMan#75
String winFspPath = WinPathUtils.getWinFspPath();
if (!System.getProperty("file.encoding").equals("UTF-8"))
{
System.out.println("UTF-8 encoding required! Current encoding: " + System.getProperty("file.encoding"));
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if it's a good idea to print such errors into stdout. That way, we might mess with the stdout of an application which other apps might rely upon.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed it to

    if (!System.getProperty("file.encoding").equals("UTF-8"))
    {	
         throw new FuseException("UTF-8 encoding required! Current encoding: " + System.getProperty("file.encoding"));
     }

Guess that's the better solution. It stops immediately.

Not sure right now, do I have to close this PR and open a new one or are you able to access the new version?

Copy link
Copy Markdown
Owner

@SerCeMan SerCeMan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, @ab3dat! Thank you for your contribution! I don't think we should print the warning to stdout. I need to check whether jnr already uses any loggers. If not, maybe a runtime error would be a reasonable response since it's not going to work anyways.

Replace output to stdout and throw exception if file encoding is not UTF-8 if running on Windows

Details see pull request SerCeMan#75
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants