-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC4_dev] Use Win32 Unicode APIs and expect all strings to be UTF-8 (fixes #1765) #1839
Conversation
- Move content of legacy apply_gridshift.cpp and apply_vgridshift.cpp in grids.cpp - Rename nad_ functions to pj_hgrid_ - Rename internal proj_hgrid_/proj_vgrid_ functions to pj_
…nitialized variables
…o#1765) For backward compatibility, if PROJ_LIB content is found to be not UTF-8 or pointing to a non existing directory, then an attempt at interpretating it in the ANSI page encoding is done. proj_context_set_search_paths() now assumes strings to be in UTF-8, and functions returning paths will also return values in UTF-8.
d73a749
to
b8b6f74
Compare
a754945
to
929f37b
Compare
…exclusive of new option +grids
7ae37ee
to
81a6585
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bulk of this PR is the unicode stuff which isn't something I feel comfortable reviewing. I hope someone else can review this.
I appreciate that a replacement for the proj_api.h
fileAPI has been added to proj.h
. On a functional level I am also happy to see unicode support added!
It is largely inspired from what is used in GDAL: UTF-8 <--> widechar conversions and use of Win32 Widechar File APIs |
@hobu Want to give that a review ? |
Unless someone has further comments, I'll merge that tomorrow |
Not completely RFC4 specific but proper unicode support for Windows is now really needed given all the file manipulations we do.
continuation of PR #1826, starting with commit f6c4241