Hi,
fpcres fails on Windows with paths containing non ASCII characters. The compiler itself happily compiles units. FPC 3.0.0 and 3.1.1.
Is that a regression?
Mattias
Mailing lists / fpc-pascal / 2015-12
Unicode file names
5 messages · 3 people · –
- Mattias Gaertner 3
- Jonas Maebe 1
- Michael Van Canneyt 1
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Mattias Gaertner wrote 6 lines
Hi,
fpcres fails on Windows with paths containing non ASCII characters. The
compiler itself happily compiles units. FPC 3.0.0 and 3.1.1.
Is that a regression?
I don't think so, since that has probably never worked correctly.
Michael.
Show quoted text 12 lines
On Sat, 5 Dec 2015, Mattias Gaertner wrote:
> Hi,
>
> fpcres fails on Windows with paths containing non ASCII characters. The
> compiler itself happily compiles units. FPC 3.0.0 and 3.1.1.
>
> Is that a regression?
I don't think so, since that has probably never worked correctly.
Is there any FPC tool that supports Unicode file names on Windows?
Mattias
Mattias Gaertner wrote 13 lines
On Sat, 5 Dec 2015 12:55:42 +0100 (CET)
Michael Van Canneyt wrote:
> On Sat, 5 Dec 2015, Mattias Gaertner wrote:
>
>> fpcres fails on Windows with paths containing non ASCII characters. The
>> compiler itself happily compiles units. FPC 3.0.0 and 3.1.1.
>>
>> Is that a regression?
>
> I don't think so, since that has probably never worked correctly.
Is there any FPC tool that supports Unicode file names on Windows?
The title of the message and your latest questions talks about unicode "Unicode", but in your original text you talk about "non-ASCII". Did you mean "non-ANSI"?
No FPC tools contain any platform-specific file handling, nor do they change any of the Default.*CodePage settings. They all use either ansistrings or shortstrings.
Jonas
Show quoted text 18 lines
On 05/12/15 13:36, Mattias Gaertner wrote:
> On Sat, 5 Dec 2015 12:55:42 +0100 (CET)
> Michael Van Canneyt wrote:
>
>> On Sat, 5 Dec 2015, Mattias Gaertner wrote:
>>
>>> fpcres fails on Windows with paths containing non ASCII characters. The
>>> compiler itself happily compiles units. FPC 3.0.0 and 3.1.1.
>>>
>>> Is that a regression?
>>
>> I don't think so, since that has probably never worked correctly.
>
> Is there any FPC tool that supports Unicode file names on Windows?
The title of the message and your latest questions talks about unicode
"Unicode", but in your original text you talk about "non-ASCII". Did you
mean "non-ANSI"?
Sorry for the confusion.
The compiler itself seems to support the Windows console codepage (file names and output), which I guess is ANSI, so more than ASCII (#32-#126), but not Unicode.
fpcres seems to only support ASCII, which surprises me. Either my tests are wrong or fpcres is more limited than the compiler.
No FPC tools contain any platform-specific file handling, nor do they change any of the Default.*CodePage settings. They all use either ansistrings or shortstrings.
Thanks, that answers my second question.
Mattias