Difference between revisions of "AEncoding"

From Lazarus wiki
Jump to navigationJump to search
m (Improving language and grammar)
Line 1: Line 1:
 
=About=
 
=About=
This is small unit which partly replaces LazUtils.LConvEncoding. It gives few functions to convert strings from/to some encoding:
+
'''AEncoding''' is a small unit, which partly replaces LazUtils.LConvEncoding. It provides few functions converting strings from/to some encoding schemes:
  
 
<syntaxhighlight>
 
<syntaxhighlight>
Line 18: Line 18:
 
Why "partly replaces"?
 
Why "partly replaces"?
  
* It uses FPC 3.x SetCodePage, which requires OS support for many encodings. While LConvEncoding doesn't require OS support. For common encodings (CP1250...CP1258, CP437, CP866 etc) OS support should work, on Windows and Unix'es.
+
* It uses FPC 3.x SetCodePage, which requires OS support for many encodings, whereas LConvEncoding doesn't require OS support. For common encodings (CP1250...CP1258, CP437, CP866 etc) OS support should work, on Windows and Unix'es.
 
* FPC SetCodePage doesn't raise exceptions, while LConvEncoding can do it (when global variable is set in LConvEncoding unit).
 
* FPC SetCodePage doesn't raise exceptions, while LConvEncoding can do it (when global variable is set in LConvEncoding unit).
  

Revision as of 12:12, 2 June 2019

About

AEncoding is a small unit, which partly replaces LazUtils.LConvEncoding. It provides few functions converting strings from/to some encoding schemes:

function AEncodingConvertFromUTF8(const AInput: RawByteString; out AOutput: RawByteString;
  AEnc: TSystemCodePage): boolean; inline;

function AEncodingConvertToUTF8(const AInput: RawByteString; out AOutput: RawByteString;
  AEnc: TSystemCodePage): boolean; inline;

function AEncodingConvertFromTo(const AInput: RawByteString; out AOutput: RawByteString;
  AEncInput, AEncOutput: TSystemCodePage): boolean;

To use functions with "string" var, do this:

 AEncoding....(RawByteString(S), ....);

Why "partly replaces"?

  • It uses FPC 3.x SetCodePage, which requires OS support for many encodings, whereas LConvEncoding doesn't require OS support. For common encodings (CP1250...CP1258, CP437, CP866 etc) OS support should work, on Windows and Unix'es.
  • FPC SetCodePage doesn't raise exceptions, while LConvEncoding can do it (when global variable is set in LConvEncoding unit).

It also gives few integer constants aeid_NNNN for common encodings.

  • Author: Alexey Torgashin.
  • License: MPL 2.0 or LGPL.

Download

GitHub: https://github.com/Alexey-T/AEncoding