[iyonix-support] Re: Embedded spaces
- From: Steven Simpson <ss@xxxxxxxxxxxxxxxx>
- To: iyonix-support@xxxxxxxxxxxxx
- Date: Thu, 04 May 2006 10:34:53 +0100
Stefaan Claes wrote:
> On 12 Apr, Vincent Lefevre <vincent@xxxxxxxxxx> wrote:
>
>> On 2006-04-11 07:13:29 +0100, John Ballance wrote:
>>
>>> since the space (or softspace) (&20 or %20) character is a filing
>>> system delimiter, embedding it as such in a file name is NOT atall
>>> simple. RISC OS has the hardspace (&A0 or %A0) which displays as
>>> space and overcomes this issue.
>>>
>> Does this work even in UTF-8 environment?
>>
>
> Yes, it works: the right UTF-8 sequence is used (C2 A0).
>
It depends on all applications specifying and interpreting filenames in
the same way.
The *Filer*, as an application using the filing system, works - if you
tell it to create a new directory, and that includes a space (32/0x20 in
all charsets on RISC OS, right?), it understands that this must be
converted to two bytes C2 A0 if UTF-8 is in effect, or to just A0 in
other cases.
O2 seems not to work. Give it a 'file:' URL with %20 in it, and it maps
it to a filename with just A0 in it, and fails to find the file. Give
it a filename with a hard space in it, and it displays as something like
'%20 (i.e. preceded by some sort of quote, prime or apostrophe) in the
URL field.
---
To alter your preferences or leave the group,
visit //www.freelists.org/list/iyonix-support
Other info via //www.freelists.org/webpage/iyonix-support
Other related posts:
