> Not necessarily:
> if you are dealing with UTF8/UnicodeString and other codepages, it is
> quite likely, and preferred, that you have unit cwstring included.
> Michael.
Question about this: If I use cthreads, cwstring, and load my own memory
manager, what should the order in the uses clause be?
On Mon, 4 Apr 2016, Graeme Geldenhuys wrote:
On 2016-04-04 10:43, Michael Van Canneyt wrote:
No. It says 'typically'.
That doesn't necessarily mean it is so, but is mostly correct.
It is still a very vague assumption. As I mentioned in my previous
reply, that statement is false on my
On 2016-04-04 10:58, Jonas Maebe wrote:
> I have now updated the page to reflect this
> fact.
Thanks Jonas, that's an important point to note.
Regards,
- Graeme -
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
On 2016-04-04 10:43, Michael Van Canneyt wrote:
>
> No. It says 'typically'.
>
> That doesn't necessarily mean it is so, but is mostly correct.
It is still a very vague assumption. As I mentioned in my previous
reply, that statement is false on my FreeBSD system too. So I should
read the wiki
On 2016-04-04 10:39, tobiasgie...@gmail.com wrote:
> It says "On Linux and Mac OS X UTF-8 is typically the system codepage, so the
> RTL uses
> here by default CP_UTF8."
>
> Not on my Mac. DefaultSystemCodePage is 20127 before I set it to 65001.
Indeed, and on my FreeBSD system
On Mon, 4 Apr 2016, Jonas Maebe wrote:
Michael Van Canneyt wrote on Mon, 04 Apr 2016:
Don't be too hasty in changing things. Jonas (who created that page) is
usually very careful in such matters.
I did forget to mention that the Default*CodePage variables are only
initialised with the
Michael Van Canneyt wrote on Mon, 04 Apr 2016:
Don't be too hasty in changing things. Jonas (who created that page)
is usually very careful in such matters.
I did forget to mention that the Default*CodePage variables are only
initialised with the "real" values on *nix platforms if you
tobiasgiesen wrote on Mon, 04 Apr 2016:
Your question was not about Lazarus but maybe you should read this:
http://wiki.freepascal.org/Better_Unicode_Support_in_Lazarus
Very interesting, but apparently there is some wrong info.
It says "On Linux and Mac OS X UTF-8 is typically the system
On Mon, 4 Apr 2016, tobiasgie...@gmail.com wrote:
On Mon, 4 Apr 2016, tobiasgie...@gmail.com wrote:
Your question was not about Lazarus but maybe you should read this:
http://wiki.freepascal.org/Better_Unicode_Support_in_Lazarus
Very interesting, but apparently there is some wrong
On Mon, 4 Apr 2016 11:35:53 +0200 (CEST)
Michael Van Canneyt wrote:
>[...]
> >> Then no conversions will be done for all ansistrings that contain UTF8.
> >
> > And this really means AnsiString, not AnsiString(something).
>
> The latter cannot contain UTF8 unless you do
>
>
> On Mon, 4 Apr 2016, tobiasgie...@gmail.com wrote:
>
> >> Your question was not about Lazarus but maybe you should read this:
> >> http://wiki.freepascal.org/Better_Unicode_Support_in_Lazarus
> >
> > Very interesting, but apparently there is some wrong info.
> >
> > It says "On Linux and
On Mon, 4 Apr 2016, tobiasgie...@gmail.com wrote:
Your question was not about Lazarus but maybe you should read this:
http://wiki.freepascal.org/Better_Unicode_Support_in_Lazarus
Very interesting, but apparently there is some wrong info.
It says "On Linux and Mac OS X UTF-8 is typically
> Your question was not about Lazarus but maybe you should read this:
> http://wiki.freepascal.org/Better_Unicode_Support_in_Lazarus
Very interesting, but apparently there is some wrong info.
It says "On Linux and Mac OS X UTF-8 is typically the system codepage, so the
RTL uses
here by
On Mon, 4 Apr 2016, Mattias Gaertner wrote:
On Mon, 4 Apr 2016 10:32:58 +0200 (CEST)
Michael Van Canneyt wrote:
[...]
You cannot, but you can set DefaultSystemCodePage to CP_UTF8.
I think it is important to note how to do this properly:
On Mon, 4 Apr 2016 10:32:58 +0200 (CEST)
Michael Van Canneyt wrote:
>[...]
> You cannot, but you can set DefaultSystemCodePage to CP_UTF8.
I think it is important to note how to do this properly:
SetMultiByteConversionCodePage(CP_UTF8);
On Mon, Apr 4, 2016 at 11:36 AM, wrote:
> Sorry, I was not able to come to that conclusion from the existing docs.
Your question was not about Lazarus but maybe you should read this:
http://wiki.freepascal.org/Better_Unicode_Support_in_Lazarus
It works also without
> You cannot, but you can set DefaultSystemCodePage to CP_UTF8.
> Then no conversions will be done for all ansistrings that contain UTF8.
Fantastic. Many thanks. That fixes my problem entirely (I think).
Sorry, I was not able to come to that conclusion from the existing docs.
Cheers,
Tobias
On Mon, 4 Apr 2016, Tobias Giesen wrote:
Hello,
my application uses the AnsiString type to store UTF-8 data. That was
totally fine. Now in FPC 3, automatic conversions cause data loss. I
get question marks replacing Chinese characters, for example.
I do not fully understand at which points
Hello,
my application uses the AnsiString type to store UTF-8 data. That was
totally fine. Now in FPC 3, automatic conversions cause data loss. I
get question marks replacing Chinese characters, for example.
I do not fully understand at which points these conversions are done.
The FPC 3 Unicode
19 matches
Mail list logo