> How does the RTL support using unicode filenames (e.g. file names that > cannot be represented by the ansi char set)?
As said on IRC, afaik decisions about this have been continuously postponed. There are some problems: - If the border condition that w9x must remain supported persists, this becomes a magnitude more work. A way to deal with this has to be found (two win32 FPC releeases, one advocated as D2..D2006 compat + w9x, one as NT + Unicode/Tiburon?) - Also I have some doubts that using two different encodings is a good thing for a portable compiler, so a decision has to be made about that too (e.g. always support UTF-8 and allow overloading with utf16 if the platform defaults to it) - Do we have a non com widestring on Windows? - Tiburon compability. It doesn't make sense to roll our own slightly incompatible schema. At least we should have a look at it, before we decide if we support it (if it can folded in the multiplatform vision and it is sane from a native perspective) What are the exact plans of Lazarus in this? Is there some wiki page with how Lazarus plans to tackle this with all multi-platform concerns? Btw I saw that Cygwin is giving up 9x support in the next release. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
