Re: [MSEide-MSEgui-talk] Question about translated strings and utf8

On Saturday 18 June 2016 12:37:24 Julio Jiménez wrote: > 2016-06-18 11:59 GMT+02:00 Martin Schreiber : > > The character constants must be in # format, please try again with > > git master f2913bc8de8c26c1730324b2073808a1d8792939. > > > > Martin > > Hi Martin. > > Inside

Re: [MSEide-MSEgui-talk] Question about translated strings and utf8

On Saturday 18 June 2016 12:19:18 Julio Jiménez wrote: > I see... thanks. > > I also have noticed that now, convert to pascal string does the job > converting to hexadecimal instead of decimal. > > example: 'Sí' -> old way 'S'#0237 new way 'S'#$00ED > > In unit mseconsts_es you have

Re: [MSEide-MSEgui-talk] Question about translated strings and utf8

2016-06-18 11:59 GMT+02:00 Martin Schreiber : > > The character constants must be in # format, please try again with git > master f2913bc8de8c26c1730324b2073808a1d8792939. > > Martin > Hi Martin. Inside .mfm file I see it uses old decimal format (not using four digits):

Re: [MSEide-MSEgui-talk] Question about translated strings and utf8

I see... thanks. I also have noticed that now, convert to pascal string does the job converting to hexadecimal instead of decimal. example: 'Sí' -> old way 'S'#0237 new way 'S'#$00ED In unit mseconsts_es you have included directive: {$codepage utf8} this means you can type utf8 chars

Re: [MSEide-MSEgui-talk] Question about translated strings and utf8

On Saturday 18 June 2016 10:15:06 Julio Jiménez wrote: > Hi Martin > > Since -Fcutf8 translated string (like the ones in mseconsts_es) are not > working properly. Special chars are replaced by character '?'. Of course if > you don't use -Fcutf8 all is ok. This is because the unit contains pascal