It seems not - std::string handles only single byte characters, am I right?
If so, is it possible to somehow change the source code to make it support unicode labels?
From a storage point of view, std::string can be used to handle any null terminated string of characters
regardless the number of non null bytes encoding a character;
std::string class can then be used to store any UTF8 char strings.
Because of many other interesting properties of UTF8 char strings (lexicographic sort, byte oriented string search…)
there is no problem to store UTF8 char strings into std::string objects and because any unicode character can be
UTF8 encoded, there is no special need to handle unicode char strings in Tulip.
Hope this helps.
This is very helpful indeed.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.