-
Notifications
You must be signed in to change notification settings - Fork 282
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
basicio: use fs::path in Impl #2800
base: main
Are you sure you want to change the base?
Conversation
b98ab16
to
74e640b
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2800 +/- ##
=======================================
Coverage 63.89% 63.89%
=======================================
Files 103 103
Lines 22361 22362 +1
Branches 10861 10861
=======================================
+ Hits 14288 14289 +1
Misses 5855 5855
Partials 2218 2218 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Exiv2 0.28 dropped the old `std::wstring` path and breaks non-ASCII path handling in Windows. While recent Windows supports using UTF-8 as locale, it might cause other issue. Before actual fix in <Exiv2/exiv2#2800> getting merged, we stick to exiv2 0.27 branch for Windows build.
Exiv2 0.28 dropped the old `std::wstring` path and breaks non-ASCII path handling in Windows. While recent Windows supports using UTF-8 as locale, it might cause other issue. Before actual fix in <Exiv2/exiv2#2800> getting merged, we stick to exiv2 0.27 branch for Windows build.
Exiv2 0.28 dropped the old `std::wstring` path and breaks non-ASCII path handling in Windows. While recent Windows supports using UTF-8 as locale, it might cause other issue. Before actual fix in <Exiv2/exiv2#2800> getting merged, we stick to exiv2 0.27 branch for Windows build.
Exiv2 0.28 dropped the old `std::wstring` path and breaks non-ASCII path handling in Windows. While recent Windows supports using UTF-8 as locale, it might cause other issue. Before actual fix in <Exiv2/exiv2#2800> getting merged, we stick to exiv2 0.27 branch for Windows build.
Exiv2 0.28 dropped the old `std::wstring` path and breaks non-ASCII path handling in Windows. While recent Windows supports using UTF-8 as locale, it might cause other issue. Before actual fix in <Exiv2/exiv2#2800> getting merged, we stick to exiv2 0.27 branch for Windows build.
Exiv2 0.28 dropped the old `std::wstring` path and breaks non-ASCII path handling in Windows. While recent Windows supports using UTF-8 as locale, it might cause other issue. Before actual fix in <Exiv2/exiv2#2800> getting merged, we stick to exiv2 0.27 branch for Windows build.
I guess we'll need to bump any future version/branch to 0.29 for this? |
this breaks API btw. const std::string& cannot be returned as fs::path is used. If I had to guess, it doesn't work without UTF8 either. |
I think this is no longer desired (on main) after #2951? Not sure what's to be done about 0.28.x though - either backport UTF-8 only from main to make that clear cut (and bump min Widows req), or someone has to restore wstring... |
No description provided.