MATLAB Answers

UTF-8 strings in MEX-files

9 views (last 30 days)
Cris Luengo
Cris Luengo on 26 Mar 2017
Answered: Cris Luengo on 26 Mar 2017
This question has been asked here before, but not with any satisfying answers. Since all those answers, a new documented function mxArrayToUTF8String has appeared. I'm hoping to find the function that does the reverse: make an mxArray from a UTF-8 encoded C or C++ string. I'm OK with an undocumented function, or using a bit of code from someone else. I'm not OK with linking some huge Unicode library, which I have no use for. All I need is convert UTF-8 to UTF-16 (which seems to be what MATLAB uses in their mxChar arrays).
Does anybody have any experience with UTF-8 encoded strings in MATLAB?
What does The MathWorks suggest we do if we want to work with UTF-8 encoded strings?

  0 Comments

Sign in to comment.

Accepted Answer

Cris Luengo
Cris Luengo on 26 Mar 2017
A solution when using C++11:
I found this answer on StackOverflow: http://stackoverflow.com/a/38383389 It turns out C++11 has built-in functions for converting between various Unicode encodings.
#include "mex.h"
#include <algorithm>
#include <string>
#include <locale>
#include <codecvt>
...
std::string u8str = u8"µm²";
std::u16string u16str = std::wstring_convert< std::codecvt_utf8_utf16< char16_t >, char16_t >{}.from_bytes( u8str );
mwSize sz[ 2 ] = { 1, u16str.size() + 1 }; // +1 to include terminating null character
mxArray* mxstr = mxCreateCharArray( 2, sz );
std::copy( u16str.begin(), u16str.end() + 1, mxGetChars( mxstr )); // again +1 for terminating null character

  0 Comments

Sign in to comment.

More Answers (2)

Walter Roberson
Walter Roberson on 26 Mar 2017
I am not all that familiar with those APIs, but how about if you mxCreateString to copy the char* into an mxArray, and then call into MATLAB to execute native2unicode() with 'UTF8' as the encoding?

  1 Comment

Cris Luengo
Cris Luengo on 26 Mar 2017
Walter,
Unfortunately mxCreateString destroys the non-ASCII code points. Any byte with a value above 127 is converted to 65535.
But maybe I can convert to UINT8 array and use that function? Interesting idea, I need to try this tonight!

Sign in to comment.


Jan
Jan on 26 Mar 2017
Edited: Jan on 26 Mar 2017
Not a solution, but a contribution to the discussion:
See this discussion: http://www.mathworks.com/matlabcentral/newsreader/view_thread/301249 . The most reliable method I've found is http://site.icu-project.org/, which exactly matchs your excluded "*not* OK with linking some huge Unicode library".
Matlab and most libraries for C or the OS-APIs have a stable Unicode support. It is a pitty, that many conversion functions of the MEX API are not documented.

  1 Comment

Cris Luengo
Cris Luengo on 26 Mar 2017
Jan, indeed, that is the library I was thinking of when I said I didn't want to link in some huge library... :)
UTF-8 to 16 should be pretty straightforward, there is no reason to know about Unicode at all, just about the two encodings. I would be able to write that translation myself, but don't want to reinvent the wheel.
Indeed, it would be easy to document some of those functions. You can't pretend the whole world uses UTF-16, especially when it's the worst way to encode Unicode IMO.

Sign in to comment.

Sign in to answer this question.