Hi, > I had already thought about it, but so far I haven't provided codepages for > Windows because I hadn't thought about someone in need for them. Now, I have > a reason to go ahead. ;-)
I like to hear that ;-)) > By the way, Alain, Windows makes use of DOS OEM codepages for the filenames. > You could easily verify that. > Open a Windows 9x DOS Box, go to your "Meus documentos" folder and type DIR. > You'll notice that the accented letters you find on the filenames in Windows > Explorer are the same you find at the DOS Box. Yes, I just tested it. > Anyway, I'll still provide the codepages. > That will still be useful when it comes to the file contents. This is now a far more complicated problem. If Windows uses diferent codepages for filenames and file contents (two cases I often find: text files edited in windows, and .dbf files), how could we satisfy both of them? This probably asks for 2 codepages switchable with a hot-key, but this is overcomplicated :( > This will add 9 codepages to the Full Codepage Pack and they won't be done > in a snap. I believe the standard codepage that windows calls ansi is used in much more countries than any dos codepage, so maybe this could be a first try... > I'll need some time. Be at ease Cheers, Alain ---------- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
