Re: Problem with non-ascii filenames on a non utf-8 locale

[John Darrington]

Right.  I think I'm beginning to understand.   I bet this problem only 
manifests itself on the VM.  I think a native windows running version will
work fine.

Can you put your printf dump before the call to any_reader_may_open ?

What kind of filesystem is /home/michel mounted on?

J'

On Sat, May 15, 2010 at 08:37:44AM -0300, Michel Boaventura wrote:
> Well, I've fixed my VM. Here is what I've found about this bug:
>
> Pspp really thinks the .sav file is a syntax because any_reader_may_open  
> returns false.
> It returns false because try_detect and fn_open also return false.
> Finally, fn_open returns false because the fopen call (file-name.c:225)  
> returns NULL.
>
> To test this, I've put a printf before the fopen, which prints each char  
> of the filename as
> a integer. Then I try to open the same file using both File -> Open and  
> the terminal. This
> is what I get:
>
> wrong: 92 104 111 109 101 92 109 105  99 104 101 108 92 110 195 163 111  
> 46 115 97 118
> right: 92 104 111 109 101 92 109 105  99 104 101 108 92 110 227     111  
> 46 115 97 118
> means:  \   h   o   m   e  \   m   i   c   h   e   l  \   n  atilde   o   
> .   s  a   v
>
> The two strings only differs on the non-ascii char. Notice that on the  
> wrong string
> two bytes are used to represent the atilde. This happens on Unicode. The  
> right string
> only uses one, which happens on ISO8859-1. So pspp is trying to open the  
> file using a
> utf8 string when it shouldn't.
>
> Regards,
>
> Michel
>
> _______________________________________________
> pspp-dev mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/pspp-dev

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://pgp.mit.edu or any PGP keyserver for public key.

signature.asc
Description: Digital signature