1 May 2006 18:05
Re: Problem with downloaded filenames
Carsten Laekamp <carsten-bnr <at> laekamp.org>
2006-05-01 16:05:44 GMT
2006-05-01 16:05:44 GMT
Jeff Snavely wrote: >> I've asked for that a long time ago. However, although "special" >> chars aren't a problem in file names, they still are in directory >> names (not on the linux side but within BNR). Therefore, I'm not so >> sure anymore that changing the defaults would be such a great idea. > > However, the release builds of BNR are configured to use > ANSI string functions instead of UNICODE string functions, so if you > were to find articles containing Chinese, Japanese, or other UNICODE > characters in their filenames that are not part of the ANSI character > set, then the filenames will show up on the screen as illegible > gibberish and save to with that same filename instead of the correct > characters because showing the correct characters is impossible > without either UNICODE or switching locales. That will always be a problem because posters don't all use the same charset anyway. But what I was referring to was that BNR2 (the linux version at least) doesn't combine parts if it creates a directory the name of which contains non-ANSI chars. Sorry for not specifying this last time. Important Addresses: Post message: bnr1 <at> yahoogroups.com Group owner: bnr1-owner <at> yahoogroups.com BNR homepage: http://www.bnr2.org/ Yahoo! Groups Links <*> To visit your group on the web, go to:(Continue reading)
RSS Feed