On Thursday 24 September 2015 09:28:28 Jonas Maebe wrote:
>
> There are several more, including lack of support for non-ansi encoded
> file names and most classes that (still) exist only in ansistring form.
> You can of course create replacements for all of that, but then again,
> you could also implement a replacement for resourcestrings in that case.
>
Do you think it is possible without compiler magic other than parsing the
sources?
> I'm not suggesting that this is what you should do, nor that FPC
> shouldn't support resourcestrings in arbitrary encodings or at least
> with a deducible encoding for external tools (since apparently external
> tools are supposed to be able to work with these generated files), but I
> don't think there's a fundamental difference between these cases.
> Standard Pascal IO routines are as much part of the language as
> resourcestrings are.
>
> > Should I make a bug report?
>
> There is already a (very old) bug report for that.
>
Can you give a link please?
> > Another question, it looks to me that -Fcutf8 does not work like
> > {$codepage utf8} for string constants. Is this intend?
>
> I think they should have the same effect.
>
Another bug?
Martin
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
