On Wed, 29 May 2019, Tomas Hajny wrote:
On 2019-05-29 12:19, Michael Van Canneyt wrote:
On Wed, 29 May 2019, Michael Van Canneyt wrote:
On Wed, 29 May 2019, AlexeyT wrote:
FPC generally uses system library functions for the conversion, so
it
does not depend on the FPC version.
But FPC ha
On 2019-05-29 12:19, Michael Van Canneyt wrote:
On Wed, 29 May 2019, Michael Van Canneyt wrote:
On Wed, 29 May 2019, AlexeyT wrote:
FPC generally uses system library functions for the conversion, so
it
does not depend on the FPC version.
But FPC has such files. Are they used in SetCodePage c
On Wed, 29 May 2019, Michael Van Canneyt wrote:
On Wed, 29 May 2019, AlexeyT wrote:
FPC generally uses system library functions for the conversion, so it
does not depend on the FPC version.
But FPC has such files. Are they used in SetCodePage code?
user@PC:~/fpcupdeluxe/fpcsrc/packages/
On Wed, 29 May 2019, AlexeyT wrote:
FPC generally uses system library functions for the conversion, so it
does not depend on the FPC version.
But FPC has such files. Are they used in SetCodePage code?
user@PC:~/fpcupdeluxe/fpcsrc/packages/rtl-unicode/src/inc$ ls cp*
cp895.pas cp932.pas cp
> FPC generally uses system library functions for the conversion, so it
does not depend on the FPC version.
But FPC has such files. Are they used in SetCodePage code?
user@PC:~/fpcupdeluxe/fpcsrc/packages/rtl-unicode/src/inc$ ls cp*
cp895.pas cp932.pas cp936.pas cp949.pas cp950.pas cpbuildu
On 2019-05-29 00:58, Alexey Tor. wrote:
I am making small unit https://github.com/alexey-t/aencoding
so I need to know:
a) will it work on FPC 3.0.4? do I need to use {$ifdef}?
It will probably (not) work the same under FPC 3.0.4 and trunk. No
guarantees though.
b) my trick to set CP_UTF8
I am making small unit https://github.com/alexey-t/aencoding
so I need to know:
a) will it work on FPC 3.0.4? do I need to use {$ifdef}?
b) my trick to set CP_UTF8 at the end of FromTo function is ok?
c) what encoding numbers (e.g. 936, 950) exist in FPC 3.3 but didn't
exist in FPC 3.0.4?
