[OpenAFS-win32-devel] New Feature: "Ability to Store Filenames in AFS using ANSI Code Pages instead of OEM Code Pages for

[Matthew Cocker]

We have just run into a problem migrating users from the university run 
windows file storage into AFS in that it seems AFS does
not handle filenames with characters from an asian character set.

We have tried from both linux and windows clients. Am I correct in guess 
ing that there is no work arounds except renaming files or zipping them up.

Cheers

Matt


Jeffrey Altman wrote:
> In the latest daily builds (pre-1.3.75) there is a new feature which 
> allows OpenAFS for Windows to store filenames into AFS using ANSI Code 
> Pages instead of OEM Code Pages.  The Windows ANSI Code Pages are 
> supersets of the ISO Latin character sets whereas the OEM Code Pages are 
>  highly incompatible.  If you are a user (or site) which uses non-US 
> ASCII characters (aka Western Europe) and you desire the ability to 
> access the files both from Windows and Unix, you may want to use this 
> feature.
> 
> When OEM Code Page 437/850 is used (United States or Western European
> locales), the following characters when used in filenames cause the 
> files to becoming inaccessible from Unix:
> 
>      [Ç]  128  08/00  200  80  C cedilla
>      [ü]  129  08/01  201  81  u diaeresis
>      [é]  130  08/02  202  82  e acute
>      [â]  131  08/03  203  83  a circumflex
>      [ä]  132  08/04  204  84  a diaeresis
>      [à]  133  08/05  205  85  a grave
>      [å]  134  08/06  206  86  a ring
>      [ç]  135  08/07  207  87  c cedilla
>      [ê]  136  08/08  210  88  e circumflex
>      [ë]  137  08/09  211  89  e diaeresis
>      [è]  138  08/10  212  8A  e grave
>      [ï]  139  08/11  213  8B  i diaeresis
>      [î]  140  08/12  214  8C  i circumflex
>      [ì]  141  08/13  215  8D  i grave
>      [Ä]  142  08/14  216  8E  A diaeresis
>      [Å]  143  08/15  217  8F  A ring
>      [É]  144  09/00  220  90  E acute
>      [æ]  145  09/01  221  91  ae diphthong
>      [Æ]  146  09/02  222  92  AE diphthong
>      [ô]  147  09/03  223  93  o circumflex
>      [ö]  148  09/04  224  94  o diaeresis
>      [ò]  149  09/05  225  95  o grave
>      [û]  150  09/06  226  96  u circumflex
>      [ù]  151  09/07  227  97  u grave
>      [ÿ]  152  09/08  230  98  y diaeresis
>      [Ö]  153  09/09  231  99  O diaeresis
>      [Ü]  154  09/10  232  9A  U diaeresis
>      [ø]  155  09/11  233  9B  o slash
>      [£]  156  09/12  234  9C  Pound sterling sign
>      [Ø]  157  09/13  235  9D  O slash
>      [×]  158  09/14  236  9E  Multiplication sign
>      [ƒ]  159  09/15  237  9F  Florin sign
> 
> In the new builds, a new registry value, HKLM\SOFTWARE\OpenAFS\Client
> "StoreAnsiFilenames" can be set to instruct OpenAFS for Windows to store
> filenames using the ANSI Code Page instead of the OEM Code Page.  The 
> ANSI Code Page is a compatible superset of Latin-1.
> 
> The one negative associated with this change is that if you have already 
> created filenames using these characters from Windows, by activating 
> this feature the previously created files will become inaccessible from 
> all platforms.
> 
> Therefore, I have not made this change a default behavior.
> 
> Jeffrey Altman
> 
>