Re: [Alephmodular-devel] Autotools patch
Status: Pre-Alpha
Brought to you by:
brefin
From: Alexander S. <fe...@it...> - 2003-01-05 18:43:22
|
On Sunday, January 5, 2003, at 12:11 PM, Br'fin wrote: > > On Saturday, January 4, 2003, at 08:20 PM, Alexander Strange wrote: > >> >> It also might barf on InfoPlist.strings, but the conflict stuff can >> be fixed easily. >> > I finally figured out why it might be barfing on InfoPlist.strings. > The file is encoded in unicode-16. > > So if I put the whole file properly into unicode-16, then ./configure > can no longer substitute its values. > > On the other hand, Project Builder seems to be reasonably happy if I > change the file's encoding to unicode-8. (And this makes ./configure > happy too) > > Happen to know if there's anyway to tell configure and its tools to > treat the file as unicode-16? I'm ok with changing the encoding to > unicode-8 myself. But it possible I'd rather leave it in PB's > originally suggested encoding. > > -Jeremy Parsons I don't think configure is very good at Unicode; the substituting is probably done with sed, if you want to take a look at it. -- Alexander Strange "Is God willing to prevent evil, but not able? Then he is not omnipotent. Is he able, but not willing? Then he is malevolent. Is he both able and willing? Then whence cometh evil? Is he neither able nor willing? When why call him god?" -- anonymous, Boethius' Consolation of Philosophy |