It is fixed in trunk from this week. Note FPC usually only guarantees to supports ANSI and UTF16 and NOT UTF8, but methods for handling UTF8 correctly are now added in the FCL for TRegistry on other platforms than Windows and the Windows version now uses UTF16 internally. FPC will probably never support UTF8 directly.