The problem with Unicode filenames is that Notepad++ is designed to run under non Unicode (eg Windows 98) OS'es as well. This means a lot of work has to be done in order to make the application work reliable in both environments (ANSI and Unicode).
If you want to change Notepad++ behavior with file loading, check out Notepad_plus.cpp and Parameters.cpp. First file does the actual loading, the second is more concerned with sessions and history. Theres also all the controls that display the filename or make use of the filename so it goes pretty deep. You also have to keep compatibility with plugins, they expect filenames to be ANSI.
-Harry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hey, I'm just thinking about to implement this feature(plus a easy use codepage converter plugin, i'll try and read the Win32 API docs in the feature, that might not be a hard to implement feature but very useful) but i need some help in reading the source code. hopefully the author can give me some hints.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No matter how powerful/useful a software is, if it can't open a file it's useless to the user. In this case it's a common problem face by most of the open source software eg. the popular firefox which can't open a HTML with unicoded filename. It's a shame as people in South East Asia are using unicode for filename.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is support for unicode filename in the plan?
The problem with Unicode filenames is that Notepad++ is designed to run under non Unicode (eg Windows 98) OS'es as well. This means a lot of work has to be done in order to make the application work reliable in both environments (ANSI and Unicode).
If you want to change Notepad++ behavior with file loading, check out Notepad_plus.cpp and Parameters.cpp. First file does the actual loading, the second is more concerned with sessions and history. Theres also all the controls that display the filename or make use of the filename so it goes pretty deep. You also have to keep compatibility with plugins, they expect filenames to be ANSI.
-Harry
Did you perhaps search for any messages on the forum about that?
hey, I'm just thinking about to implement this feature(plus a easy use codepage converter plugin, i'll try and read the Win32 API docs in the feature, that might not be a hard to implement feature but very useful) but i need some help in reading the source code. hopefully the author can give me some hints.
No matter how powerful/useful a software is, if it can't open a file it's useless to the user. In this case it's a common problem face by most of the open source software eg. the popular firefox which can't open a HTML with unicoded filename. It's a shame as people in South East Asia are using unicode for filename.