From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,341ea6d4f1d28719 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!proxad.net!proxad.net!skynet.be!newspost001!tjb!not-for-mail Date: Tue, 01 Mar 2005 23:29:10 +0100 From: Adrien Plisson Reply-To: aplisson-news@stochastique.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: fr-be, fr, en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: need a little string hint... References: <1109606915.447479.184780@l41g2000cwc.googlegroups.com> <4223462d$0$30168$ba620e4c@news.skynet.be> <1109609391.989190.235510@f14g2000cwb.googlegroups.com> <422354fb$0$14965$ba620e4c@news.skynet.be> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <4224ec33$0$20669$ba620e4c@news.skynet.be> Organization: -= Belgacom Usenet Service =- NNTP-Posting-Host: e455e908.news.skynet.be X-Trace: 1109716019 news.skynet.be 20669 80.200.104.28:10015 X-Complaints-To: usenet-abuse@skynet.be Xref: g2news1.google.com comp.lang.ada:8579 Date: 2005-03-01T23:29:10+01:00 List-Id: Simon Wright wrote: > Of course you may not be talking about DNS -- but I'm pretty sure that > under DNS legal hostname characters are [a-z0-9.-] (case insensitive) > which doesn't include space. it depends: look at IDN (Internationalized Domain Names), it allows to have Unicode characters in domain names. it then depends if your configuration file should hold only the ASCII-compatible value, in which case my remark is invalid, or if it is allowed to hold the non-encoded Unicode value, in which case trimming spaces will certainly yield a different result from the actual hostname in the file. > A text-based config file format that includes significant whitespace > as you suggest and doesn't delimit it (eg, with quotes) is asking to > be derided. Just look at make(1). there is also a problem of incompatibility: if the configuration file is intended to be read by many (> 1) different softwares, they all have to handle spaces the same way. i don't think trimming spaces is a common operation on hostnames, so he had better no do it this way. -- rien