[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [patch][org-entities] More symbols
From: |
Rasmus |
Subject: |
Re: [O] [patch][org-entities] More symbols |
Date: |
Wed, 28 Aug 2013 13:38:38 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
Hi Nicolsa,
Sorry about the late reply.
Nicolas Goaziou <address@hidden> 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 =" 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" "ɸ ")
>
> Why is there a space in UTF-8 code?
Bug.
>> + ("preccurlyeq" "\\preccurlyeq" t "≼" "[precedes or equal]"
>> "[precedes or equal]" "≼")
>
> 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]" "≽")
>
> Ditto. Also, the LaTeX code looks wrong.
True.
>> + ("nexist" "\\exists" t "∃" "[there does not exists]" "[there
>> does not exists]" "∄")
>> + ("nexists" "\\exists" t "∃" "[there does not exists]"
>> "[there does not exists]" "∄")
>
> Didn't you forget a "\not" in LaTeX entry?
Yup. This is getting embarrassing.
>> ("lArr" "\\Leftarrow" t "⇐" "<=" "<=" "⇐")
>> ("Leftarrow" "\\Leftarrow" t "⇐" "<=" "<=" "⇐")
>> + ("impliedby" "\\impliedby" t "⇐" "<=" "<=" "⇐")
>
> 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.
–Rasmus
--
Don't panic!!!