[Lazarus] Lazarus (UTF8) and Windows: SysToUTF8, UTF8ToSys... Is there a better solution?

[Marcos Douglas]

On Fri, Dec 20, 2013 at 8:44 PM, Mattias Gaertner
<nc-gaertnma at netcologne.de> wrote:
> On Fri, 20 Dec 2013 17:55:48 -0200
> Marcos Douglas <md at delfire.net> wrote:
>
>> On Fri, Dec 20, 2013 at 3:19 AM, Jürgen Hestermann
>> <juergen.hestermann at gmx.de> wrote:
>> > Am 2013-12-19 23:04, schrieb Marcos Douglas:
>> >
>> >> Well, the same problem...
>> >> If there is no solution (for now), I prefer using SysToUTF8/ UTF8ToSys
>> >> because is more simpler than use WideString API and conversion to
>> >> UnicodeString, UTF8Decode, etc. Don't you think?
>> >
>> > As Bart already mentions, the ANSI (SYS) interface does *not* support
>> > Unicode.
>> > Also, you are not be able to access long paths (longer than 255 characters)
>> > when using ANSI API functions.
>> > Therefore the [W]ide (unicode) character API functions are a must.
>>
>> So, these limitations exist in Lazarus too, right?
>
> The file functions with UTF8 in name use internally the W functions
> under Windows.

I didn't know, thanks.

Marcos Douglas