Unicode plugin name

[Alextp]

Ghisler
Why not to name unicode plugins Name.Un.wlx instead of Name.uwlx.

[m^2]

Why to name unicode plugins Name.Un.wlx instead of Name.uwlx?

[Alextp]

2m^2
'wlx' extension will be the same.

[m^2]

But what benefit does it bring?

I can't think about any use for such plugins w/out updating programs to support them anyway.
It can only cause poorly written programs that use them to crash or the better ones to show error messages, which would cause user confusion. The latter applies to older TC versions too.

[Lefteous]

As there always has to be an ANSI version your suggestion would break the TC's auto-detection mechanism for Unicode plugin versions.

[m^2]

TC could change the mechanism easily.

[Lefteous]

Why should Ghisler do that?

[m^2]

I'm curious too.
But I guess there is some reason for this request.

[Alextp]

2m^2
the benefit: 'wlx' extensions is known to older tools. 'Uwlx' is not. No need (less need) to update tools for TC75.

2Lefteous
No break in detection, as Ghisler may change it (for new name).

[Lefteous]

Well but w?x is not the same as uw?x. That's why there is a new extention. Name different things diffrently.
From a plugin management point of view there is still just w?x. It doesn't matter if there is also a uw?x file. Are you sure you already understood the concept?

[ghisler(Author)]

The idea is that users don't take the Unicode wlx file when selecting the plugin manually because it has a different extension, so it's not listed in the open dialog.

To create a Unicode only plugin, you can simply create a dummy wlx plugin which just exports the basic functions which return error or not supported.

[Hacker]

Christian,
Unix? Unicode?

Roman

[ghisler(Author)]

Of course, corrected it.

[djk]

Unix, Unix... What does Christian think about? Should we expect any surprise?