After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 605565 - doxygen unable to work under path containing unicode character in Windows
doxygen unable to work under path containing unicode character in Windows
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: build
1.6.1
Other Windows
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks:
 
 
Reported: 2009-12-27 20:23 UTC by supercoolman
Modified: 2018-07-30 11:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description supercoolman 2009-12-27 20:23:17 UTC
I'm not sure if same problem exist for other OS, but under windows it's unable to support path containing Unicode or double-byte characters.

doxygen 1.6.1
E:\寫程式\doxygen1.6.1\doxygen.exe
E:\寫程式\project_1+3\main.c
E:\寫程式\project_1+3\interrupt.c
E:\寫程式\project_1+3\interrupt.h


first, doxygen is unable to generate default config file with command "E:\寫程式\doxygen1.6.1\doxygen.exe" -g "E:\寫程式\project_1+3\doxy\default.doxy"

second, if I made that config file myself and launch doxygen with that file, doxygen complaints that the file does not exist.

These two problems are resolved if I rename 寫程式 into "temp" or "programs". However, that broke all of my projects because I have eclipse projects and other projects created by other IDEs all with absolute path configuration in that directory.
Comment 1 Dimitri van Heesch 2009-12-28 09:30:16 UTC
Seems like a windows only issue indeed, as I cannot reproduce it on my Mac.
Comment 2 André Klapper 2018-07-30 11:01:16 UTC
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to 

   https://github.com/doxygen/doxygen/issues

All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github.

Hence I am closing this GNOME Bugzilla ticket.
Please use the corresponding ticket in Github instead. Thanks a lot!