On Linux I can do
fpc -oTestäあProg MyProg.pas
On Windows the Japanese char does not seem to be possible?
Mailing lists / fpc-devel / 2021-03
Fpc on Windows, how to specify foreign chars in -oExeName commandline
5 messages · 3 people ·
- Marco van de Voort 2
- Martin Frb 2
- Martin 1
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Op 2021-03-27 om 18:38 schreef Martin via fpc-devel:
Show quoted text 5 lines
On Linux I can do
fpc -oTestäあProg MyProg.pas
On Windows the Japanese char does not seem to be possible?
Did you select a 1-byte Japanese encoding on Windows?
Marco van de Voort wrote 8 lines
Op 2021-03-27 om 18:38 schreef Martin via fpc-devel:
> On Linux I can do
> fpc -oTestäあProg MyProg.pas
>
> On Windows the Japanese char does not seem to be possible?
>
Did you select a 1-byte Japanese encoding on Windows?
Probably not. I try to have my German ä and the Japanese char, both in the name at the same time. (And maybe add some Arabic too).
I know that "GetCommandLineW" does support it. I can write my own app using GetCommandLineW, and it will receive the data. (cmd.exe does not support it, but other shells do)
Op 2021-03-27 om 19:11 schreef Martin Frb via fpc-devel:
Show quoted text 13 lines
On 27/03/2021 18:55, Marco van de Voort via fpc-devel wrote:
>
> Op 2021-03-27 om 18:38 schreef Martin via fpc-devel:
>> On Linux I can do
>> fpc -oTestäあProg MyProg.pas
>>
>> On Windows the Japanese char does not seem to be possible?
>>
> Did you select a 1-byte Japanese encoding on Windows?
Probably not. I try to have my German ä and the Japanese char, both in
the name at the same time. (And maybe add some Arabic too).
So then you don't just want Japanese chars, you want full unicode, and preferably as one byte system. Do you know lazarus ? ( :-) ). Try to build the compiler in lazarus with the default utf8 code set in the resources screen, and then rebuild in a "cmd /w" prompt.
Disclaimer: all from theory, I never tried. Requires Win10 1905+
Marco van de Voort wrote 21 lines
Op 2021-03-27 om 19:11 schreef Martin Frb via fpc-devel:
> On 27/03/2021 18:55, Marco van de Voort via fpc-devel wrote:
>>
>> Op 2021-03-27 om 18:38 schreef Martin via fpc-devel:
>>> On Linux I can do
>>> fpc -oTestäあProg MyProg.pas
>>>
>>> On Windows the Japanese char does not seem to be possible?
>>>
>> Did you select a 1-byte Japanese encoding on Windows?
>
> Probably not. I try to have my German ä and the Japanese char, both
> in the name at the same time. (And maybe add some Arabic too).
>
So then you don't just want Japanese chars, you want full unicode, and
preferably as one byte system. Do you know lazarus ? ( :-) ). Try to
build the compiler in lazarus with the default utf8 code set in the
resources screen, and then rebuild in a "cmd /w" prompt.
Disclaimer: all from theory, I never tried. Requires Win10 1905+
1) not important, see 2 => so there is no flag/define to be given to the make command?
2) So by default the compiler only handles the ANSI encoding on Windows? Which also solves my problem.
I am trying to find out which of the gdb that I have supports what chars in the exe name. But If an exe of that name can not be compiled, it becomes less important. (Yes the user could still rename after build...)