This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Mon Jun 3 22:45:08 2024 Received: from lml.valinux.com (postfix@lml.varesearch.com [209.81.8.228]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id TAA22620 for ; Sun, 12 Dec 1999 19:30:53 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by lml.valinux.com (Postfix) with ESMTP id 39F4659A21; Sun, 12 Dec 1999 16:30:00 -0800 (PST) Received: by vger.rutgers.edu via listexpand id ; Sun, 12 Dec 1999 19:24:43 -0500 Received: by vger.rutgers.edu id ; Sun, 12 Dec 1999 19:24:22 -0500 Received: from serenity.mcc.ac.uk ([130.88.200.93]:1788 "EHLO serenity.mcc.ac.uk") by vger.rutgers.edu with ESMTP id convert rfc822-to-8bit; Sun, 12 Dec 1999 19:24:07 -0500 Received: from ps.cus.umist.ac.uk ([192.84.78.160]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 11xJHM-000GiX-00; Mon, 13 Dec 1999 00:23:52 +0000 Received: from localhost (rhw@localhost) by ps.cus.umist.ac.uk (8.8.7/8.8.7) with ESMTP id AAA28387; Mon, 13 Dec 1999 00:23:11 GMT X-Authentication-Warning: ps.cus.umist.ac.uk: rhw owned process doing -bs Date: Mon, 13 Dec 1999 00:23:11 +0000 (GMT) From: Riley Williams X-Sender: rhw@ps.cus.umist.ac.uk To: "Jeff V. Merkey" Cc: Alan Cox , Linux Kernel Subject: Re: Supporting Macintosh FinderInfo/Resource Fork in Linux NWFS 2.0 In-Reply-To: <385421F6.35F0565E@timpanogas.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig Hi Jeff. >> The second issue is charset translation. I think you can simply >> use the code from fs/hfs/trans.c for this. > I am already handling the char set traslation for English names > in NWCREATE.C for MAC clients, so this is probably ok, but I'll > check this out to make sure I am doing it the same way hfs does. > Also, on a side note, I used the ACS_* characters for the > ncurses stuff, but for some reason, the display is still > striping the 8th bit during output. > Here's a code fragment that doesn't seem to output chars above > 127 on my bash shell (???). I'd love to know what's wrong here. > Any ideas? > #include > #include > #include > #include "termios.h" > #include "sys/ioctl.h" > > char buf[10] = { 201, 187, 200, 188, 204, 185, 186, 205, 0x1E, 0x1F }; > > int main(int argc, char *argv[]) > { > register int i; > struct termios term; > > ioctl(1, TCGETS, &term); > term.c_iflag &= ~ISTRIP; > term.c_cflag |= CS8; > ioctl(1, TCGETS, &term); > > for (i=0; i < 10; i++) > printf("[%c]\n", buf[i]); > > return 0; > > } I just used cut-and-paste to transfer that code into a text file called x.c and then compiled it with `gcc -Wall -o x x.c` where it compiled without any errors or warnings. Since I also run under bash, I then ran the resultant program and saw as output a column with the following in square brackets on each line, described using standard ASCII rather than the actual characters: E acute >> E grave 1/4 I grave Superscript 1 Underlined superscript O I acute [] [] The last two had nothing inside them... For reference, here's the result of `./x > xx` and telling pine to insert xx in this message: ===8<=== CUT ===>8=== [É] [»] [È] [¼] [Ì] [¹] [º] [Í] [] [] ===8<=== CUT ===>8=== The last two show up slightly differently here than they did on the screen though... Best wishes from Riley. * Copyright (C) 1999, Memory Alpha Systems. * All rights and wrongs reserved. +----------------------------------------------------------------------+ | There is something frustrating about the quality and speed of Linux | | development, ie., the quality is too high and the speed is too high, | | in other words, I can implement this XXXX feature, but I bet someone | | else has already done so and is just about to release their patch. | +----------------------------------------------------------------------+ * http://www.memalpha.cx/Linux/Kernel/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/