handle internationalized strings on windows #176
Labels
Milestone
Comments
AddressXception
added
bug
AddressXception
added a commit
that referenced
this issue
Sep 10, 2021
replace the hardcoded manifest with one that is not affected by #176
AddressXception
added a commit
that referenced
this issue
Sep 13, 2021
* 🚧 Adjust to Single Project Shift project towards new csproj for C# project and away from Shared Setup. Remove the shared project setup and start with .net standard 2.0 and .net framework 4.8 with the goal of adding more pieces including .net core. Fix tests * 🙈 Ignore Test with Memory Address Issues * ✨ Create Release Workflow * ✨ Add links to README * ♻️ Update Make * 🚀 Add so, dylib, and dll to Release * respect configuration when loading binaries * use truncated manifest replace the hardcoded manifest with one that is not affected by #176 * update readme and build tasks * Remove msys package target * try run netstandard tests * only run netstandard tests on macos for now * dont run tests * 🧹 Update Test Project references * 🧹 Quick Cleanup Co-authored-by: Matt Wilhelm <[email protected]>
AddressXception
added a commit
that referenced
this issue
Sep 15, 2021
* 🚧 Adjust to Single Project Shift project towards new csproj for C# project and away from Shared Setup. Remove the shared project setup and start with .net standard 2.0 and .net framework 4.8 with the goal of adding more pieces including .net core. Fix tests * 🙈 Ignore Test with Memory Address Issues * ✨ Create Release Workflow * ✨ Add links to README * ♻️ Update Make * 🚀 Add so, dylib, and dll to Release * respect configuration when loading binaries * use truncated manifest replace the hardcoded manifest with one that is not affected by #176 * update readme and build tasks * Remove msys package target * try run netstandard tests * only run netstandard tests on macos for now * add chaum pedersen to C interface * Add C# chaum pedersen proofs * update version numbers Co-authored-by: Keith Fung <[email protected]> Co-authored-by: Keith Fung <[email protected]>
AddressXception
added a commit
that referenced
this issue
Sep 15, 2021
* 🚧 Adjust to Single Project Shift project towards new csproj for C# project and away from Shared Setup. Remove the shared project setup and start with .net standard 2.0 and .net framework 4.8 with the goal of adding more pieces including .net core. Fix tests * 🙈 Ignore Test with Memory Address Issues * ✨ Create Release Workflow * ✨ Add links to README * ♻️ Update Make * 🚀 Add so, dylib, and dll to Release * respect configuration when loading binaries * use truncated manifest replace the hardcoded manifest with one that is not affected by #176 * update readme and build tasks * Remove msys package target * try run netstandard tests * only run netstandard tests on macos for now * add chaum pedersen to C interface * Add C# chaum pedersen proofs * update version numbers * rename x86 file Co-authored-by: Keith Fung <[email protected]> Co-authored-by: Keith Fung <[email protected]>
AddressXception
added a commit
that referenced
this issue
Sep 15, 2021
* 🚧 Adjust to Single Project Shift project towards new csproj for C# project and away from Shared Setup. Remove the shared project setup and start with .net standard 2.0 and .net framework 4.8 with the goal of adding more pieces including .net core. Fix tests * 🙈 Ignore Test with Memory Address Issues * ✨ Create Release Workflow * ✨ Add links to README * ♻️ Update Make * 🚀 Add so, dylib, and dll to Release * respect configuration when loading binaries * use truncated manifest replace the hardcoded manifest with one that is not affected by #176 * update readme and build tasks * Remove msys package target * try run netstandard tests * only run netstandard tests on macos for now * add chaum pedersen to C interface * Add C# chaum pedersen proofs * update version numbers * rename x86 file * do not upload 32 bit * remove try Co-authored-by: Keith Fung <[email protected]> Co-authored-by: Keith Fung <[email protected]>
|
the dllimport calls probably need the charset explicitly set |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Expected Behavior
international character sets are handled in utf-16
Actual Behavior
when marshalling strings from c# to the native library, the character set is misinterpreted. likely due ot the use of wide string and converting to string.
steps to reproduce:
netframework ManifestGenerator uncomment one of the lines that includes spanish language.
set a break in the Manifest.h c++/cli wrapper constructor after
Utilities::MarshalString(json, _json);expected: the string is properly translated
actual: the string has extra characters
Environment
The text was updated successfully, but these errors were encountered: