From: <msk...@en...> - 2006-03-29 05:58:16
|
> On Tuesday 28 March 2006 13:15, Robert W. Kuhn wrote: > > Jeroen van der Zijp: > > > > >> If I want to use umlauts in the text of a FXMessageBox (or somethi= ng like > > >> that) I do not see the =C3=B6=C3=A4=C3=BC's but a white box. > > >> > > >> Do I have to use a macro (_T"=C3=A4=C3=A4"); ? Or what do i have t= o do? > > >> > > >> Tschau - Robert > > >> > > > > > > Try: > > > > > > > > > fromAscii("....\uXXXX...") > > > > > > which you can use to embed any unicode character in regular string = [it interprets > > > the \uXXXX and replaces it with the utf-8 character]. > > > > I have to do it in such a difficult way? I believe it is up to the co= ntrol > > to parse my ascii-char and replace all char>127 with the utf-unicode > > character. > > The control actually likes you to feed it utf-8 encoded unicode. Howev= er, the > new FXString constructors can also accept 16- and 32-bit wide character= s, so > if you want to input as a wide-character string, you can do this, too. > > Yes, this means you can use your favorite T() macro to embed constant w= ide-character > strings into your code, and as long as you're inside the "Basic Multila= ngual Plane" > then the fact that Unix wide-characters are wider than Windows wide-cha= racters shouldn't > be an issue at all. > > A third possibility is to make use of FXString's compose() API which ca= n perform > the standard "combining character" tricks to compose a" into =C3=A4. > > > I believe this is not a good solution. And I do not have always a con= st > > char*. Sometimes I have a FXString with umlauts. Same problems. > > Well, tell me what you'd like to see; we may be able to provide additio= nal > facilities beyond the ones we have now. > > - Jeroen There is very simple solution - just save all source files in UTF-8 and f= orget about the problem. Or use _T() macro or any else to call a function which= converts text in your codepage to UTF-8. That way you can also easy make your app = multilingual. Regards Micha=C5=82 |