Re: Unicode strings in GUI Editor

Julian Smart wrote:
> akusaya%40gmx.net">akusayagmx.net wrote:
>> However there are some problems:
>> - sometimes I check the new option checkbox but the effect is the opposite
>>
> Sorry, I've found that problem and will fix it in the next release (soon
> if it's proving a nuisance).

Thanks.

>;> - I still get messages about cannot convert to iso-8859-1 even when the
>>; new option is enabled.
>> - So I tried to change the encoding to utf-8, and save it again, but I
>>; got "Failed to convert file ... to Unicode" message, and the cpp file
>>; editor become empty. I was shocked but fortunately the original file was
>>; still intact.
>>
> If you still have Unicode in e.g. comments, then there may still be
> problems. I don't think the above is related to the new features, though
> I may be wrong. I assume there must have been some confusion when
> switching encodings - if you can reproduce it I'd be grateful.

Oh, I realized that previously I directly type unicode characters in
system encoding to compensate for the lack of the new option. I removed
that since I do not need them again, so my cpp file now only contains
<0x7f bytes. However I still get "cannot write to ... .tmp" error if the
encoding is set to iso-8859-1 (default). So I changed it to utf-8 and
that fixed the problem.

(However, unicode characters should not produce any problem when saved
in utf-8, because utf-8 can represent any character, right?)

Thanks, again!

•  2
  New Members

• Preventative maintenance software program
• Preventative maintenance program software
• Computer software program
• Help desk software program
• Scheduling program software

Hi,

akusaya%40gmx.net">akusayagmx.net wrote:
&gt;
> Oh, I realized that previously I directly type unicode characters in
> system encoding to compensate for the lack of the new option. I removed
> that since I do not need them again, so my cpp file now only contains
> <0x7f bytes. However I still get "cannot write to ... .tmp" error if the
> encoding is set to iso-8859-1 (default). So I changed it to utf-8 and
> that fixed the problem.
>
>; (However, unicode characters should not produce any problem when saved
> in utf-8, because utf-8 can represent any character, right?)
>
Yes, it should be OK assuming the compiler doesn't have a problem with
these characters.

Thanks,

Julian