From: Ihor Radchenko <yantar92@posteo.net>
To: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Unicode problem with export of literal contents
Date: Fri, 17 Feb 2023 11:02:30 +0000 [thread overview]
Message-ID: <87cz68d06x.fsf@localhost> (raw)
In-Reply-To: <87zg9dx4yl.fsf@wi.uni-muenster.de>
Jens Lechtenboerger <lechten@wi.uni-muenster.de> writes:
> With Org 9.6.1 from Emacs master, I get the following warning, and I
> am asked to select a coding system:
>
>> These default coding systems were tried to encode the following
>> problematic characters in the buffer ‘ *temp*’:
>> ...
>
> With previous Org versions, this did not happen, export would just
> work. Note that I insert contents literally because I do not want
> ‘find-file-hook’, automatic uncompression, etc. (which are avoided
> according to the doc string of insert-file-contents-literally).
This warning appears upon Org calling `secure-hash'.
Org is doing nothing wrong here - your file does not have proper encoding.
You did not see this error in the past by chance.
Not a bug. You need to fix your files with improper encoding.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-02-17 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 10:46 Unicode problem with export of literal contents Jens Lechtenboerger
2023-02-17 5:51 ` Bruno Barbier
2023-02-17 7:48 ` Jens Lechtenboerger
2023-02-17 17:30 ` Bruno Barbier
2023-02-17 11:02 ` Ihor Radchenko [this message]
2023-02-17 16:56 ` Jens Lechtenboerger
2023-02-17 17:23 ` Bruno Barbier
2023-02-20 9:18 ` Jens Lechtenboerger
2023-02-20 9:40 ` Bruno Barbier
2023-02-20 10:16 ` Jens Lechtenboerger
2023-02-20 19:00 ` Bruno Barbier
2023-02-21 8:30 ` Jens Lechtenboerger
2023-02-17 18:22 ` Ihor Radchenko
2023-02-20 9:28 ` Jens Lechtenboerger
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=87cz68d06x.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=lechten@wi.uni-muenster.de \
/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.