Ray Gardener wrote:
> Analysis of the code in pov_util.cpp indicates heavy reliance on 8-bit 
> C-string functions when processing filenames, which would need 
> nontrivial recoding to support non-ASCII filenames.
> 
> The core problem is that filenames/pathspecs are considered strings, 
> when they should be promoted to their own datatype of which the string 
> aspect is an implementation and/or interface detail. Code that does
> 
>   char* filename = Parse_C_string(true); // true indicates "is filename"

Actually, that line is not he problem, but the fix. POV-Ray is perfectly 
capable of parsing UTF-8, but the remaining file handling code cannot always 
deal with UTF-8 strings, and on non-recent-Unix systems it is not even 
supposed to. As inspecting the code for UTF-8 would have been overkill for 
3.6, the design decision was to disable it, which is why the line you quoted 
above enforces an ASCII string.

Either way, it is not a bug and the design is not going to be changed for 
3.6 either.

	Thorsten, POV-Team

Post a reply to this message