fixes issue #34 - put on hold

[ghost]

No description provided.

[ghost]

While it solves the creation of scripts issue it generates display issues of menu items.
On hold until solved.

[chcg]

@ClaudiaFrank Do you mean the issue from #20:

Could you add Unicode support to the menu?
Hebrew file-names are displayed as gibberish.

?

[chcg]

Should be possible to use the version OPENFILENAME, GetSaveFileName, CreateFile without the W extension as we are building with Unicode and in this case it is anyhow mapped to the W versions, see e.g. docu of https://msdn.microsoft.com/en-us/library/windows/desktop/ms646839(v=vs.85).aspx
at the end of the page in requirements

[ghost]

Kind of yes, it is a little bit strange, it does work under subdirectories and in main menu when using
Configuration tool (see script ÜberÄÖß.py)

but running it by clicking the item under subdirectory corrupts the
Run Previous Script menu item

and clicking the ÜberÄÖß.py under main menu does NOT corrupt the Run Previous Script menuitem
BUT does not execute the script at all.

[chcg]

Seems to be caused by:
void MenuManager::updatePreviousScript(const char *filename)

Need to be tested with e.g.
גלילת שורות.py
this is still not fixed.

[ghost]

I guess/assume I understood what the problem is.
PythonScript does, internally, char to wchar/wchar to char conversion by using utf-8.
I assume this is related to being pythons "native" encoding and consoles output encoding.
Now, windows uses, afaik, ucs-2 and acp internally - so an additional WcharMbcsConverter
like let's say acp2wchar and/or wchar2acp should do the trick (at least I hope so)

I will follow up on this and see if this is really the case.

[ghost]

This is still not perfect, even so menu issues should have been solved another issue raised
You cannot use console.writeError function together with python byte strings

Left, the white background = current situation (without unicode path support)
Right, black background = the new situation

In case that one wants to use the extended chars to be displayed as "error text" it is needed
to use unicode strings. I haven't found a suitable way to get rid of this.
Any ideas are very much appreciated.

[chcg]

See PR #60, so this one could be closed, as discussed offline