POV-Ray : Newsgroups : povray.general : Image map filenames with extended ASCII characters (PoseRay development) Server Time
4 Aug 2024 10:22:48 EDT (-0400)
  Image map filenames with extended ASCII characters (PoseRay development) (Message 21 to 22 of 22)  
<<< Previous 10 Messages Goto Initial 10 Messages
From: Thorsten Froehlich
Subject: Re: Image map filenames with extendedASCIIcharacters(PoseRaydevelopment)
Date: 28 Jul 2003 14:50:37
Message: <3f25707d$1@news.povray.org>
In article <l4t9ivcinr4ejp55k9cjiopnh1odfjbgqe@4ax.com> , ABX 
<abx### [at] abxartpl>  wrote:

>> Actually, I do know about the much more complex issue of true unicode.
>
> There isn't even such a thing like "true" unicode.
> http://www.unicode.org/faq/utf_bom.html#14

Well, it really depends on how you define "true" in this context ;-)  It
should also be noted that POV-Ray internally only handles strings in UCS-2
without surrogates.  The reasons for this "limitation" are even more complex
than why files are only supported with ASCII characters, but it does have
certain effects...

    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

From: Patrick Elliott
Subject: Re: Image map filenames withextendedASCIIcharacters(PoseRaydevelopment)
Date: 28 Jul 2003 17:54:18
Message: <MPG.198f4871873a8560989847@news.povray.org>
In article <3f2441f9$1@news.povray.org>, tho### [at] trfde says...
> In article <MPG.198dcefec22b76a9989846@news.povray.org> , Patrick Elliott 
> <sha### [at] hotmailcom>  wrote:
> 
> > I however have trouble imagining any modern systems actually suffering
> > from this issue so severely that the result is not a mere flipping around
> > or replacement of a few letters that would give the file a funny looking
> > name. But, you say it is a problem, so I'll shut up now. :(
> 
> No, you still got it all upside down.  Probably I didn't make clear enough
> that there is a huge different between what you as a user see and what a
> program will "see" (not really, but I can't explain it better without going
> into endless details).

Sigh.. Well I have run into something like this with file names from a 
unix system that I tried to unpack to a Windows machine. The fact that 
this particular program included make files and headers that where 
'supposed' to let it compile under windows didn't change the fact that 
most programs like WinZip are apparently not smart enough to know the 
limitations of the system they run on and offer to let you rename the 
damn things. I can imagine a similar situation for files in POV, so... :( 
Oh well... :p

-- 
void main () {

    call functional_code()
  else
    call crash_windows();
}


Post a reply to this message

<<< Previous 10 Messages Goto Initial 10 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.