>I don't think this can go wrong, if Explorer uses the wide-character >API. As far as I know, it does, as file names with random Unicode >characters work just fine in Explorer, and get passed to applications >like WordPad or MS Office just fine.
>> 2 The text encoding guessed by OOo does not match the text encoding >> used by Explorer. >I doubt this is a question of guesswork, but the issue is that the >command line contains characters not representable in the system >codepage URI encoding seems to take place somewhere in Explorer however. evidence: try to navigate to a nonexisten file called æ.txt, Explorer's error message will be: --------------------------- Microsoft Internet Explorer --------------------------- file:///C:/%E6.txt blev ikke fundet. Kontroller, at stien eller Internetadressen er korrekt. --------------------------- OK --------------------------- Note also the Alert header of "Microsoft Internet Explorer". So there is one of the things they used the integration of the Shell namespace and their internet browser to achieve. Cheers, Bryan Rasmussen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
