>Does it means that the source of all current projects for Win32 should
>be reedited?
What is reediting?
Let's classify all problems of such changes:
1. Source problem (both national comments and string constants). It will be
possible to fix this with my patch only by including {&encoding=ANSI}in
* "Vasily I. Volchenko" <[EMAIL PROTECTED]> [Sat, 29 Dec 2007 21:42:35
+0300]:
Seems like that. May be it can be possible to use/write such a
translation functions, but at present - neither they are compatible in
the source using "high char" comments/strings nor in reading non-utf
texts.
I notice
Seems like that. May be it can be possible to use/write such a translation
functions, but at present - neither they are compatible in the source using
"high char" comments/strings nor in reading non-utf texts.
I noticed that this is not acceptable - the answer is that win32 will be moved
to UTF8
On Nov 24, 2007 5:49 PM, Vasily I. Volchenko <[EMAIL PROTECTED]> wrote:
> This is only about unicode text files. Can you imagine that BOM will be in a
> text file given to pascal compiler?
A source code is a text file.
Free Pascal is already prepared to handle source code including a BOM marker.
This is only about unicode text files. Can you imagine that BOM will be in a
text file given to pascal compiler?
_
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://ww
OK, I understand the problems of using utf8 on windows, but I am speaking about
other things. Why lazarus should save (and load) pascal (and only pascal, not
lfm/lrs, not po) files in the internal encoding? If gtk2 version supports utf8,
it forces user to save all files in utf8, when if windows
