From: Marcin Borkowski <mbork@mbork.pl>
To: Myles English <mylesenglish@gmail.com>,
Steven Arntson <steven@stevenarntson.com>,
emacs-orgmode@gnu.org
Subject: Re: allow italic quote marks? org-emphasis-regexp-components
Date: Thu, 18 Jun 2015 20:29:27 +0200 [thread overview]
Message-ID: <877fr03m60.fsf@mbork.pl> (raw)
In-Reply-To: <CAFyQvY23nYCePNscCarcXiT7vk8Cb7YS5CNBDFE-miARdbUxqw@mail.gmail.com>
On 2015-06-18, at 18:02, Kaushal <kaushal.modi@gmail.com> wrote:
> A quick google search comes up this these:
>
> http://tex.stackexchange.com/questions/83440/inputenc-error-unicode-char-u8-not-set-up-for-use-with-latex
> http://tex.stackexchange.com/questions/4268/inputenc-error-unicode-char-u8-error-while-trying-to-write-a-degree-symbol
>
> Based on those solutions, may be you can add
>
> \DeclareUnicodeCharacter{200b}{}
>
> I haven't tried it, so cannot guarantee if that will work.
Thanks, I'll check it in my Spare Time™.
> I regularly generate pdfs and almost all of my org documents would be using
> 0x200b somewhere. If a pdf generates fine without any visible artifacts and
> with all content as expected, I do not look into the tex compilation logs.
I hate when TeX gives me *any* errors. (So does AUCTeX.)
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-06-18 18:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 10:12 allow italic quote marks? org-emphasis-regexp-components Myles English
2015-06-18 2:46 ` Steven Arntson
2015-06-18 3:19 ` Kaushal
2015-06-18 3:23 ` Kaushal
2015-06-18 7:53 ` Marcin Borkowski
2015-06-18 14:29 ` Kaushal
2015-06-18 15:50 ` Myles English
2015-06-18 16:02 ` Kaushal
2015-06-18 17:04 ` Steven Arntson
2015-06-18 18:29 ` Marcin Borkowski [this message]
2015-06-18 18:58 ` Rasmus
2015-06-19 12:51 ` Myles English
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fr03m60.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=mylesenglish@gmail.com \
--cc=steven@stevenarntson.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.