Why does Path Finder force use of 'smart quotes' in file/folder names? This is a problem!

When you create/re-name a file or folder in Path Finder using the normal mechanism (clicking on the item so the name becomes highlighted and editable) then in any text that you type Path Finder converts regular single and double quotes into extended UFT-* 'smart quotes'.

For example, the single quote is ascii 0x27 but when types in Path Finder in a file/foler name it gets encoded as UFT-8 code e2 80 99. Same for double quotes; 0x27 -> e2 80 9d.

While this may perhaps look more aesthetically pleasing it can cause all sorts of unexpected issues and in some cases actual problems.

Since Finder does not do this I do not think that Path Finder should do it either, or at least it should be an option which has to be explicitly enabled. I haven't been able to d=find such an option anywhere...

Does anyone know of an option to disable this undesired behaviour? If not then I would suggest that this is a bug...

After more investigation it seems that Path Finder is respecting a system level setting (see attachment). However since Finder explicitly overrides this setting and smart quotes in file/folder names are generally not such a great idea maybe Path Finder should do the same, at least by default?

Thank you for your emails and for investigating the issue thus far. Your suggestion makes sense, I have forwarded your email to our developers. It may take some time for us to react, the developer is extremely busy with Path Finder 8 release which we expect to roll out this Fall.