Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Sat, 6 Sep 2008 09:05:01 +0200 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id m8674tho013857 for ; Sat, 6 Sep 2008 09:04:56 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id m8670Epd022761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 Sep 2008 09:00:14 +0200 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id m85M1JJK031843; Sat, 6 Sep 2008 09:00:13 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 19802 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 6 Sep 2008 09:00:10 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id m86704vm001435 for ; Sat, 6 Sep 2008 09:00:04 +0200 Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.248]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id m866xwqb009602 for ; Sat, 6 Sep 2008 09:00:02 +0200 Received: by rv-out-0708.google.com with SMTP id c5so652928rvf.10 for ; Fri, 05 Sep 2008 23:59:58 -0700 (PDT) Received: by 10.140.249.20 with SMTP id w20mr7231874rvh.21.1220684398221; Fri, 05 Sep 2008 23:59:58 -0700 (PDT) Received: from ?10.0.1.102? ( [219.90.177.78]) by mx.google.com with ESMTPS id f21sm2318612rvb.5.2008.09.05.23.59.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 05 Sep 2008 23:59:57 -0700 (PDT) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v928.1) References: <20080906063514.GA11840@irwin.vpn.uni-freiburg.de> X-Mailer: Apple Mail (2.928.1) X-Spam-Whitelist: Message-ID: <70D6670C-0571-454E-AB6D-5432205F8ECA@gmail.com> Date: Sat, 6 Sep 2008 16:29:51 +0930 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Will Robertson Subject: Re: Unicode for accent \b? To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <20080906063514.GA11840@irwin.vpn.uni-freiburg.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -2.599 () BAYES_00 X-Scanned-By: MIMEDefang 2.64 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 06 Sep 2008 07:05:01.0258 (UTC) FILETIME=[E141AAA0:01C90FEE] Status: R X-Status: X-Keywords: X-UID: 5214 (forwarded to Ross Moore in case he's not on this list) On 06/09/2008, at 4:05 PM, Heiko Oberdiek wrote: > what's the unicode code point for \b as accent? > > U+0331 COMBINING MACRON BELOW/NON-SPACING MACRON BELOW > + opposite of \= (U+0304 COMBINING MACRON/NON-SPACING MACRON) > - Unicode doesn't have a letter with this accent > > +U0332 COMBINING LOW LINE/NON-SPACING UNDERSCORE > + practical use for underlining (e.g. in bookmarks) > - it isn't a typical accent > > +U0320 COMBINING MINUS SIGN BELOW/NON-SPACING MINUS SIGN BELOW > - I don't see use cases, especially, there isn't a `plus sign below'. > > My guess would be `macron below', \b seems to be inherited > from math mode. I don't know heaps about this sort of stuff. Here're a few representative lines from Ross Moore's xunicode: \DeclareEncodedCompositeCharacter{\UTFencname}{\b}{0332}{005F} % Combining low line \DeclareUTFcomposite[\UTFencname]{x1E06}{\b}{B} \DeclareUTFcomposite[\UTFencname]{x1E07}{\b}{b} \DeclareUTFcomposite[\UTFencname]{x1E0E}{\b}{D} \DeclareUTFcomposite[\UTFencname]{x1E0F}{\b}{d} \DeclareUTFcomposite[\UTFencname]{x1E34}{\b}{K} \DeclareUTFcomposite[\UTFencname]{x1E35}{\b}{k} \DeclareUTFcomposite[\UTFencname]{x1E3A}{\b}{L} \DeclareUTFcomposite[\UTFencname]{x1E3B}{\b}{l} \DeclareUTFcomposite[\UTFencname]{x1E48}{\b}{N} \DeclareUTFcomposite[\UTFencname]{x1E49}{\b}{n} \DeclareUTFcomposite[\UTFencname]{x1E5E}{\b}{R} \DeclareUTFcomposite[\UTFencname]{x1E5F}{\b}{r} \DeclareUTFcomposite[\UTFencname]{x1E6E}{\b}{T} \DeclareUTFcomposite[\UTFencname]{x1E6F}{\b}{t} \DeclareUTFcomposite[\UTFencname]{x1E94}{\b}{Z} \DeclareUTFcomposite[\UTFencname]{x1E95}{\b}{z} \DeclareUTFcomposite[\UTFencname]{x1E96}{\b}{h} However, if I look up the decomposition for these composite characters (using the Mac OS X application UnicodeChecker), they all use the U +0331 glyph. E.g., U+1E0F -> 0064 0331 *** So xunicode uses u+0332 for \b, even for glyphs that should be combined with u+0331. I suspect this is a bug... Back to your original question, Heiko, I'd agree with your intuition that u+0331 would be the right glyph to use. Will