Rimgaudas Laucius wrote

Hi. Is it posible to make fpc to support unicode source (principle)?

Yes. We are working on this; But there is no date set for this.

Michael.

Hi.

Is it posible to make fpc to support unicode source (principle)?

you wrote

Hi. Is it posible to make fpc to support unicode source (principle)?

Of course it is, and it shouldn't be that hard.

But would be the use of it? The only thing I could imagine are comments or constant strings.
But I guess people who need this use MBCS instead of unicode, no?

Furthermore, the 1.1 compiler contains codepage support for the input source, so you can specify how constant characters are converted to unicode when doing a wide string conversion for a constant string. Of course, this is only useful for languages with <=256 characters, it doesn't help users with very large character sets. Furthermore, the current implementation doesn't support dynamic loading of code pages and only the common (for me common :) )
code pages (850,437 and iso 8xxx-1) are compiled in.

Yes it is true. But i am interesting about support of other than basic latin simbols in idetificators (a.e. variables) also and about problems related with it (a.e. one of problems windows dlls do not support unicode identificators of exported routines).

The problem is the linker and assembler that only support normal ascii symbols.

Peter

Are there any windows dll which use really chars > 127?

latin

>>simbols in idetificators (a.e. variables) also and about problems

related

I do not know what you mean saying "normal ascii simbols". Ascii is standart for 7 bit characters but many of people use it talking about 8 bit standarts.
The linker and assembler supports 8 bit characters (i tayed it under windows).

Are there any windows dll which use really chars > 127?

I do not know. But it is posible to use them. I tryed. It is useless if dll is written for public use. But it is usable for closed projects.

Why i am speeking about internationalization of fpc? The most important reason is that we use Pascal translator for teaching algorithms in the schools. Programs written in the native language are more comprehensible and readable for pupils.

02-11-15 08.39, skrev Rimgaudas Laucius följande:

As I see it, they do only support a subset of 7-bit ascii, namely those constituting valid identifiers. At least in the general case, but of course it differs between different assemblers and linkers. E g PPCAsm for MacOS supports only symbols which is consided valid identifier (as in C or Pascal). That is they must be in the range _,A..Z,a..z,0..9 and not start with a digit.

To make FreePascal true cross-platform and to avoid problems, identifiers should be valid pascal of C identifiers, IMO.

But, as I can see, the problem could be solved if unicode names is encoded to names with chars in the above range. When symbols are parsed by the compiler, they could be converted, and stored as such internally. Error messages bounced back to the user is translated back to Unicode.

I dont know which encoding scheme could be used. Can UTF-8 or UTF-7 be used, do they translate a valid unicode identifier to a valid ascii identifier. ?

//Olle Raab

----- Original Message -----