Hello John, all,
Thanks for your information.
Below are some more details and further feedback.
> In my application I associate a file extension which works fine. Clicking
> > on the desktop opens the app and loads the file I clicked on.
> >
> > This works fine for Windows and Mac on its own.
> >
> > Assume a file named "Kostenschätzung.avax" is stored on MacOS and gets
> > opened afterwards on Windows it fails. The filename on Windows is shown
> > correctly but after clicking on it on Windows the following call
> Where is this file stored? On a shared NAS? With SMB?
>
I personally tried sharing it on a NAS and sending it via Email.
In my case I cannot reproduce the issue. It works fine in both cases.
The reporter of the problem used sending via Email.
Even if I get the attachment (the file) I see the problem locally.
> For some reason, the parameters provided via the command line don't seem
> to properly decode the second form (a + composing umlaut) but do
> understand the first form (precomposed a-umlaut). This could be JavaFX,
> but could be lower level as well. You could see what happens if you do
> this with a non-JavaFX program, and get the parameters directly from a
> `main` method.
>
That's a good point and I confirm it is not a JavaFX issue per se.
A simple launcher class reports the undesired character from the beginning
on.
public class Launcher {
public static void main(String[] args) {
System.out.println("Arguments: " + Arrays.toString(args));
// launching JavaFX ...
}
}
I reached out to the reporter but did not get any more feedback for now.
Thanks,
-- Daniel
>
> --John
>
