From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Language identifiers
Date: Sun, 20 May 2012 09:48:28 -0400 [thread overview]
Message-ID: <86r4uf9d5f.fsf@mercure.progiciels-bpi.ca> (raw)
Hello, Org people.
Seeing again the (org) Languages node in the manual, I decided to check
all my #+BEGIN_SRC for language tags, which I too often improvise, for
normalizing them. I noticed a few things, and wonder if the manual
should be amended, or if I should change my habits instead.
- I was using lower case "c" and "r", while the manual suggests
upper case "C" and "R" instead. Both seem to work (in Emacs at
least). Should the manual be amended to say that case does not
matter? If then, should the manual stick uniformly to lower case?
- The identifier in the left column did not work, but if I change it to
the identifier in the right column, the content highlights (in
Emacs). The manual does not list it.
| config | conf |
| email | mail |
| make | makefile |
| postscript | ps |
- I was using "elisp" instead of "emacs-lisp" and "javascript" instead
of "js". Both seem to work (in Emacs at least). If there are many
alternate languages identifiers for a language, should the manual list
all acceptable identifiers?
- Tag "xml" seems to work nicely (within Emacs). The manual does not
list it.
I wonder what "are supported" really means, in the first sentence.
Maybe the fact that Emacs supports a language tag does not mean that Org
supports it? Maybe exporters would fail to render them nicely? Maybe a
few more words could be added to the page for explaining what users
should expect, or not expect. Currently, I do not know whether if the
list is missing a few identifiers, or if I'm not using them properly.
Other tiny details about the table at the beginning of this Info page.
It would be clearer if there was a separating line between the title
line and the table contents. A vertical line separating both halves
would be welcome too, one has to take a few seconds to understand that
this is a two column table, each column itself holding two columns.
Finally, the sorted entries are presented row wise in this two column
table; the table would be easier to consult if the sorted entries were
presented column wise instead.
François
next reply other threads:[~2012-05-20 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 13:48 François Pinard [this message]
2012-05-20 17:31 ` Language identifiers Thomas S. Dye
2012-05-20 18:23 ` François Pinard
2012-05-20 18:56 ` Nick Dokos
2012-05-21 14:22 ` François Pinard
2012-05-21 14:34 ` Nick Dokos
2012-05-21 15:17 ` François Pinard
2012-05-22 23:04 ` Bastien
2012-05-21 9:02 ` Sebastien Vauban
2012-05-21 12:54 ` Eric Schulte
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=86r4uf9d5f.fsf@mercure.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--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).