From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: BUG: swapped utf-8 symbols in org-entities
Date: Tue, 28 Jun 2016 21:21:30 +0200 [thread overview]
Message-ID: <87por1azlx.fsf@gmx.us> (raw)
In-Reply-To: CAH+LVpk1TNqxUva7CC=k7b58iJ-jmgmxAgMWWH5GNpmCJaujYQ@mail.gmail.com
Konstantin Kliakhandler <kosta@slumpy.org> writes:
> Hello,
>
> The unicode letters for 'varphi' and for 'phi' are swapped.
>
> Here is a patch correcting this:
>
> diff --git a/lisp/org-entities.el b/lisp/org-entities.el
> index 4044432..6f6d054 100644
> --- a/lisp/org-entities.el
> +++ b/lisp/org-entities.el
> @@ -204,9 +204,8 @@ packages to be loaded, add these packages to
> `org-latex-packages-alist'."
> ("upsih" "\\Upsilon" t "ϒ" "upsilon" "upsilon" "ϒ")
> ("upsilon" "\\upsilon" t "υ" "upsilon" "upsilon" "υ")
> ("Phi" "\\Phi" t "Φ" "Phi" "Phi" "Φ")
> - ("phi" "\\phi" t "φ" "phi" "phi" "φ")
> - ("varphi" "\\varphi" t "ϕ" "varphi" "varphi" "ɸ")
> + ("phi" "\\phi" t "φ" "phi" "phi" "ɸ")
> + ("varphi" "\\varphi" t "ϕ" "varphi" "varphi" "φ")
It's not straight forward.
The behavior is "correct" with reference to (La)TeX. E.g.
M-x set-input-method RET TeX RET
Then,
\phi → φ
\varphi → ϕ
Your suggestion is correct with reference to HTML.
I’d tend to favor the TeX interpretation even if it’s technically wrong.
Rasmus
--
May contains speling mistake
next prev parent reply other threads:[~2016-06-28 19:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 8:15 BUG: swapped utf-8 symbols in org-entities Konstantin Kliakhandler
2016-06-28 14:49 ` Nicolas Goaziou
2016-06-30 14:33 ` Konstantin Kliakhandler
2016-07-01 7:24 ` Nicolas Goaziou
2016-07-03 11:47 ` Konstantin Kliakhandler
2016-07-05 19:13 ` Nicolas Goaziou
2016-08-29 12:26 ` Konstantin Kliakhandler
2016-08-30 9:54 ` Nicolas Goaziou
2016-07-06 11:18 ` Rasmus
2016-07-06 13:10 ` Nicolas Goaziou
2016-06-28 19:21 ` Rasmus [this message]
2016-06-28 19:58 ` Nicolas Goaziou
2016-06-28 20:30 ` Rasmus
2016-06-28 20:10 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87por1azlx.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).