Thorsten Froehlich wrote:
> You cannot load files with names outside the ASCII character range.  Unicode
> is supported for text, not filenames.  There is no workaround in a portable
> program like POV-Ray.  You have to rename your files.

Shouldn't unicode be portable?  I know *NIX supports unicode, thus so
would OSX, and Win2k+ supports it, therefore there is no reason to say
unicode isn't portable.

-- 
Tim Cook
http://home.bellsouth.net/p/PWP-empyrean

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

> Shouldn't unicode be portable?  I know *NIX supports unicode, thus so
> would OSX, and Win2k+ supports it, therefore there is no reason to say
> unicode isn't portable.

Unicode implementations are still kind of tricky under many platforms, and
not compiled-in by default on lots of others. Not to mention that Unicode is
not generally used for filenames on *NIX (AFAIK), only for text and
interfaces.

Post a reply to this message

Roberto A. wrote:
> Unicode implementations are still kind of tricky under many platforms, and
> not compiled-in by default on lots of others. Not to mention that Unicode is
> not generally used for filenames on *NIX (AFAIK), only for text and
> interfaces.

*sniffle*  But Unicode is the best thing since sliced bread! T_T
Sucks that a lot of Windows software doesn't support it yet...

-- 
Tim Cook
http://home.bellsouth.net/p/PWP-empyrean

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

In article <3f213bda@news.povray.org> , Tim Cook <z99### [at] bellsouthnet>  
wrote:

> Shouldn't unicode be portable?

It has nothing to do with Unicode.  It has to do with the filesystem and how
it is accessed.  there is no portable way to access files with Unicode names
because you cannot pass Unicode strings.  That is all.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <3f21823b$1@news.povray.org>, tho### [at] trfde says...
> In article <3f213bda@news.povray.org> , Tim Cook <z99### [at] bellsouthnet>  
> wrote:
> 
> > Shouldn't unicode be portable?
> 
> It has nothing to do with Unicode.  It has to do with the filesystem and how
> it is accessed.  there is no portable way to access files with Unicode names
> because you cannot pass Unicode strings.  That is all.
> 
>     Thorsten
> 
I doubt this is a unicode file name. File systems don't use it. In fact 
the file name is likely using a perfectly valid OEM file name, which 
allows for anything from character 32 to 255, with the exception of a few 
like ',', '*', '?', etc. The problem is, using the usual complete lack of 
common sense, MS decided that the file system itself should 'allow' 
characters beyond 127, but that some standard methods for opening, 
closing, etc. the same files should only use the main ASCII range. 
Obviously POV-Ray falls pray to this same stupidity by either enforcing a 
nonexistent restriction or by calling the file handler in a way that 
results in it rejecting perfectly valid names. This is ironically a left 
over for the days of DOS, when only programs the bypassed the standard 
DOS access methods could save or read such a file.

In any case, if POV-Ray won't read them, then it is because it is not 
asking the file system to use the name properly, not because the name is 
invalid. And it literally "can't" be a unicode name, since he obviously 

are NULL + Letter and you can't 'ever' have a NULL value in a file name.

Something is going wrong here, but it is not the fault of the underlying 
filesystem, though it might be something in between the two.

-- 
void main () {

    call functional_code()
  else
    call crash_windows();
}

Post a reply to this message

> *sniffle*  But Unicode is the best thing since sliced bread! T_T
> Sucks that a lot of Windows software doesn't support it yet...

I'm with you, but any such process takes time. Let's hope it doesn't require
as much time as IPv6... :-)

Post a reply to this message

> void main () {

>     call functional_code()
>   else
>     call crash_windows();
> }

I love your .sig. Is it the source code for "Windows for quantic computers"?
:-D

Post a reply to this message

In article <MPG.198b4d77e17bd15e989842@news.povray.org> , Patrick Elliott 
<sha### [at] hotmailcom>  wrote:

>> It has nothing to do with Unicode.  It has to do with the filesystem and how
>> it is accessed.  there is no portable way to access files with Unicode names
>> because you cannot pass Unicode strings.  That is all.
>
> I doubt this is a unicode file name. File systems don't use it. In fact
> the file name is likely using a perfectly valid OEM file name, which
> allows for anything from character 32 to 255, with the exception of a few
> like ',', '*', '?', etc. The problem is, using the usual complete lack of
> common sense, MS decided that the file system itself should 'allow'
> characters beyond 127, but that some standard methods for opening,
> closing, etc. the same files should only use the main ASCII range.
> Obviously POV-Ray falls pray to this same stupidity by either enforcing a
> nonexistent restriction or by calling the file handler in a way that
> results in it rejecting perfectly valid names. This is ironically a left
> over for the days of DOS, when only programs the bypassed the standard
> DOS access methods could save or read such a file.

Obviously you have no clue what you are talking about.  You either don't
seem to even have read this thread or you don't know what "portable" means.
It has nothing to do with Mircosoft.  It has nothing to do with "POV-Ray
fall[ing] pray to this same stupidity" because this, too, has absolutely
nothing to do with not making Unicode filenames possible.  Your whole
response is just completely on the wrong track and has absolutely nothing to
do with anything discussed in this thread.  Sorry!

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <MPG.198b4d77e17bd15e989842@news.povray.org> , Patrick Elliott 
<sha### [at] hotmailcom>  wrote:

> In any case, if POV-Ray won't read them, then it is because it is not
> asking the file system to use the name properly, not because the name is
> invalid. And it literally "can't" be a unicode name, since he obviously

> are NULL + Letter and you can't 'ever' have a NULL value in a file name.

I am still undecided whether I should recommend some sleep or you are on
drugs.  There is neither head nor tail to what you are writing.  I don't
even know how to respond to this in a meaningful way!?! :-(

> Something is going wrong here, but it is not the fault of the underlying
> filesystem, though it might be something in between the two.

Nothing is wrong outside your head.  Note that I am not saying anything
about the inside of your head, I don't think I would want to look in there
;-)

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Tim Cook wrote:

> *sniffle*  But Unicode is the best thing since sliced bread! T_T
> Sucks that a lot of Windows software doesn't support it yet...

It is more an issue of platform specific file management systems than
it is the visualization of text. If you can grasp the concept of that
then you will understand the imposition of the limitations.

-- 
Ken Tyler

Post a reply to this message