From mint-bounce@lists.fishpool.fi Mon Jun 7 16:27:40 2010 Message-ID: <1C234B03F25B48DBAE066177330CFDBC@mercatus.local> From: "Jo Even Skarstein" To: References: <0015d7ad.01a4363cb752@mail.gmx.net> In-Reply-To: Subject: Re: [MiNT] Daily builds Date: Mon, 7 Jun 2010 22:28:28 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: -------------------------------------------------- From: "m0n0" Sent: Monday, June 07, 2010 10:15 PM To: "Helmut Karlowski" Cc: Subject: Re: [MiNT] Daily builds >> I implemented some sort of compatibility for old programs, assuming that >> when it passes a pattern in all uppercase it is not able to handle >> lowercase, and so all is displayed. It does not happen when the >> fileselector is called from XaAES on ext2. > > Sorry to say that, but to me this does not sound like an good > compatibility enhancement. Because the old systems could not handle lower > case names, it interprets lower cases as uppercase. At least, that's what > the docs say. So, when I code an "open file selector" for old Ataris, I > would also pass lower case file ext, because I think: "that doesn't > matter". I assume many programs pass lower case, but mean upper case. This is true for minixfs, but not ext2. However, shouldn't this fix depend on the domain of the calling application? Compatibility on when the application is in TOS-domain, and off when in MINT-domain? Jo Even