From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [patch][org-entities] More symbols Date: Wed, 28 Aug 2013 13:38:38 +0200 Message-ID: <87vc2qqc3l.fsf@gmx.us> References: <87y57zouv5.fsf@gmx.us> <87pptat5zf.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40447) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEe5K-0001A1-FO for emacs-orgmode@gnu.org; Wed, 28 Aug 2013 07:38:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VEe5B-0008HI-L1 for emacs-orgmode@gnu.org; Wed, 28 Aug 2013 07:38:50 -0400 Received: from mout.gmx.net ([212.227.15.18]:51639) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEe5B-0008H4-BX for emacs-orgmode@gnu.org; Wed, 28 Aug 2013 07:38:41 -0400 Received: from pank ([87.57.37.13]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MCLcP-1VN8PR0Fn7-009BUV for ; Wed, 28 Aug 2013 13:38:40 +0200 In-Reply-To: <87pptat5zf.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 19 Aug 2013 10:55:16 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: n.goaziou@gmail.com Cc: emacs-orgmode@gnu.org Hi Nicolsa, Sorry about the late reply. Nicolas Goaziou writes: > Thanks for the patch. > >> This patch adds some general interest(?) symbols to org entities that >> otherwise lived in my init file. >> >> 1. I don't know how to easily check whether a glyph is supported by >> Latin 1, so Latin 1 entries correspond to the ASCII equivalent. > > Use "C-u C-x =3D" on the character and look at "preferred charset" > property. OK. >> 2. HTML symbols have been tested in Firefox. In a few cases I >> couldn't find a pretty name (like "π") in which case I've >> supplied the unicode number (like "&960;"). Is that OK? (E.g. can >> Org produce non-uft8 HTML?) > > I think it can: see `org-html-coding-system'. It may be wiser to avoid > these symbols altogether. OK. >> 3. In LaTeX the symbols are mostly defined in amsmath, except coloneqq >> and eqqcolon which requires something like mathtools or kpfonts or >> possibly unicode-math. Is that OK? > > Any additional package needed must be added to > `org-latex-default-packages-alist', which means that the package will be > loaded in every LaTeX export. So, this is clearly not OK for packages > like "kpfonts". OK. > As a rule of thumb, I think we should avoid requiring new packages for > org-entities. I agree. I'd wish we could cut down on some of these darn symbol packages! latexsymb should be fairly easy to get rid of. >> I also fixed some >> inconsistencies. E.g. loz was loaded diamond even though loz is >> defined in amssymb and "~" and "\tilde" produced different results >> (the latter produces the irritating "\~{}" often observed among >> (social science?) university professors...). > > Sounds good. > >> + ("varphi", "\\varphi" t "ϕ" "varphi" "varphi" "=C9=B8 ") > > Why is there a space in UTF-8 code? Bug. >> + ("preccurlyeq" "\\preccurlyeq" t "≼" "[precedes or equal]" >> "[precedes or equal]" "=E2=89=BC") > > This one is LaTeX specific, it may be more appropriate in > `org-entities-user'. We also have stuff like le and rarr, which is clearly HTML-specific. An important part of entities (IMO) is the unicode display in-buffer. >> + ("succcurlyeq" "\\succeq" t "≽" "[succeeds or equal]" >> "[succeeds or equal]" "=E2=89=BD") > > Ditto. Also, the LaTeX code looks wrong. True.=20 >> + ("nexist" "\\exists" t "∃" "[there does not exists]" "[there >> does not exists]" "=E2=88=84") >> + ("nexists" "\\exists" t "∃" "[there does not exists]" >> "[there does not exists]" "=E2=88=84") > > Didn't you forget a "\not" in LaTeX entry? Yup. This is getting embarrassing. >> ("lArr" "\\Leftarrow" t "⇐" "<=3D" "<=3D" "=E2=87=90") >> ("Leftarrow" "\\Leftarrow" t "⇐" "<=3D" "<=3D" "=E2=87=90") >> + ("impliedby" "\\impliedby" t "⇐" "<=3D" "<=3D" "=E2=87=90") > > Is is really needed? There are already two entities producing the same > code. impliedby, iff and implied are recommended since they use correct spacing. They are, however, defined in amsmath, which isn't loaded, although perhaps it should be. I'll prepare a reduced patch. =E2=80=93Rasmus --=20 Don't panic!!!