V16.2.0.3 Bug: conversion can trailing space on filename

[chrisjj]

1 Convert an WMA having a trailing space one the filename to Apple Lossless, using:

Output To
Source Drive:\[REPLACE]For Windows,For Macintosh,Source Path[]\Source Filename

Expected: filename preserved
Observed: trailing space lost e.g. https://i.imgur.com/XqXi3QE.png

Note: the List & Rename Files dialog at this button https://i.imgur.com/Y94UufR.png shows the source filename in a way that doesn't make it possible to see whether there is a trailing space e.g. https://i.imgur.com/uLZjcfd.png

[Spoon]

Re: V16.2.0.3 Bug: conversion can trailing space on filename

The filename is passed through our routines which regulate the length and remove illegal characters, even if Source Filename is used. You could argue that on certain filesystems (non-network), non-flash disc, ie HFS this should be preserved, however it is removed to maintain compatibility across all filesystems OS X can encounter.

[chrisjj]

Re: V16.2.0.3 Bug: conversion can trailing space on filename

You could argue that on certain filesystems (non-network), non-flash disc, ie HFS this should be preserved, however it is removed to maintain compatibility across all filesystems OS X can encounter.

I wouldn't need to argue it. I'm going from one filesystem to the same filesystem, so the program has no excuse for Source Filename not doing what it says.

Where can I find the specification of the filename format for which Source Filename does actually provide the source filename?