Sorry, these two letters were accidentally sent personally. To Felipe Monteiro de Carvalho:
> > probably Windows will become totally utf16 (not really unicode, but > > at least utf16) really soon (at least in newer versions in a way > > incompatible with current ones). > > A small correction, utf16 is a type of unicode. Uh, Unicode is a big standard with lotsa features. UTF.. is "Unicode transformation format". So, utf16 is a type of representing unicode characters. And, as I think, basic utf16 support does not include support for representing symbols by several utf16 units (unicode is to be about 1000000 symbols, neither much more, nor significantly less). Also, support for ligatures and other features is weird to non specialized programmers too. I don't think that Windows will support all unicode features in their implementation of utf16 in filenames. But Windows, MS Office, MS Internet Explorer and some more M$ products are listed on unicode page as programs supporting unicode. To FlАvio Etrusco: > copy of the string) you should access it as a PChar. > > as 'const' and 'var', and maybe using PChar in some few places, or can > > Cheers, > Fl vio PChar type is no less ugly for pascal than dynamic array. I have null characters in my strings sometimes. If a char may have zero code, string should be able to contain it at any place. _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
