From: brian powell <briangpowellms@gmail.com>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org mode, minted, and non-ASCII
Date: Thu, 5 Jan 2012 10:17:09 -0500 [thread overview]
Message-ID: <CAFm0skE72d6qemzXG7s7RzOBA7QpPX+h+zpkU0t3vHUgfujk2w@mail.gmail.com> (raw)
In-Reply-To: <87vcoqdeoq.fsf@iro.umontreal.ca>
[-- Attachment #1: Type: text/plain, Size: 3165 bytes --]
* Firstly, thanks for sending this issue to the group: pygments & minted
are very interesting tools for OrgMode/LaTeX persons.
** Read this
http://ctan.mackichan.com/macros/latex/contrib/minted/minted.pdf
** And this: http://pygments.org/docs/unicode/
*** Seems that running the pygmetize from the command line has some
provisos.
*** Also, noticed this in bold type at
http://pygments.org/docs/unicodethat might help you:
"Since Pygments 0.6, all lexers use unicode strings internally. Because of
that you might encounter the occasional UnicodeDecodeError if you pass
strings with the wrong encoding.
...
The formatters now send Unicode objects to the stream if you don't set the
output encoding. You can do so by passing the formatters an encoding option:
from pygments.formatters import HtmlFormatter
f = HtmlFormatter(encoding='utf-8')
You will have to set this option if you have non-ASCII characters in the
source and the output stream does not accept Unicode written to it! This is
the case for all regular files and for terminals."
---------- Forwarded message ----------
From: François Pinard <pinard@iro.umontreal.ca>
Date: 2012/1/4
Subject: [O] Org mode, minted, and non-ASCII
To: emacs-orgmode@gnu.org
Hi, Org people.
Still experimenting around for this report, I installed *minted* so one
of the appendices might nicely display a bulky bit of Python code.
It works satisfactorily (and speedily enough) if I squash out all
diacriticized and other Unicode special symbols in the file. However,
no output is produced if I leave the tiniest non-ASCII character in the
file. OK, OK, don't kill me :-). Agreed that all non-ASCII characters
are neither tinier or bigger than one another in this context.
The Org document, the Python sources, and the default charset for this
machine are all UTF-8. I saw no Unicode problem between Unicode and
LaTeX when minted is not in the picture. pygmentize also appears to do
well with Unicode input.
So the problem likely lies either between Org mode and minted LaTex, or
within minted. Is that a known problem or limitation?
This problem is bit more hurtful here, as the Python code really uses
Unicode, and mangling out Unicode characters really changes the semantic
of the code as displayed in the report. If it was not for this problem,
the minted output is attractive, at least more than what I saw with the
listings package. On last resort and of course, I may still include an
unfontified Python source in the appendix, or produce it by other means;
not such a big deal, it's just that I would have liked to impress my
coworkers a bit more with Org mode integration and capabilities. :-).
To confuse me a little more, I'm getting random (I mean, unpredictable
by me) "org-mode fontification error" diagnostics while creating the PDF
output. Perusing org.el tells me that this is likely a mere
coincidence, as those fontification errors seem wholly unrelated to
LaTeX processing.
François
P.S. Who is a bit tired right now, and maybe missing something trivial?
Tomorrow, I'll surely revisit most of today's experiments.
[-- Attachment #2: Type: text/html, Size: 3993 bytes --]
next prev parent reply other threads:[~2012-01-05 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 3:40 Org mode, minted, and non-ASCII François Pinard
2012-01-05 15:17 ` brian powell [this message]
2012-01-05 19:47 ` Nick Dokos
2012-01-05 21:21 ` François Pinard
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=CAFm0skE72d6qemzXG7s7RzOBA7QpPX+h+zpkU0t3vHUgfujk2w@mail.gmail.com \
--to=briangpowellms@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/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).