Short File names are to allow apps that can't support long file names
(LFN) to access a file. Long filename support includes wchar encoding.
If Firebird can't support  wchar filenames, then it should NOT convert a
short filename to its LFN equivalent (unless there is some other very
important reason it needs the LFN).

On 10/4/17 7:15 AM, DougC doug@... [firebird-support] wrote:
> Hamish-
>
> Windows short path names are decidedly NOT for apps that cannot handle
> Unicode. They were introduced far earlier than that and were intended
> for programs that could not handle anything but the short 8.3 limits
> for any given file or folder name. That they often help with avoiding
> unicode is a side effect.
>
> Sound like your misunderstanding of this may be contributing to your
> frustration.
>
> Doug C.
>
>
> ---- On Tue, 03 Oct 2017 23:25:23 -0400 *Hamish Moffatt
> hamish@... [firebird-support]
> <firebird-support@yahoogroups.com>* wrote ----
>
> On 03/10/17 19:59, Dimitry Sibiryakov sd@...
> <mailto:sd@...>
> [firebird-support] wrote:
> > 03.10.2017 2:25, Hamish Moffatt hamish@...
> <mailto:hamish@...> [firebird-support] wrote:
> >> Any ideas?
> > Give up. Firebird does not support unicode characters in
> database name and path. Only ANSI.
> >
> >
>
> Thanks for confirming what I figured from the source. But this is
> exactly what the Windows short path names are for - if your
> application
> can't handle Unicode filenames, use the short names. I tried it
> and it
> fails. Firebird explicitly converts the short path name back to a
> long
> name it can't use?!
>
> It seems to mostly work with UTF-8 on linux, or at least I had it
> working a couple of years back.
>
>
> Hamish
>

--
Richard Damon