From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: Bruno Barbier <brubar.cs@gmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>, <emacs-orgmode@gnu.org>
Subject: Re: Unicode problem with export of literal contents
Date: Mon, 20 Feb 2023 10:18:41 +0100 [thread overview]
Message-ID: <87cz64u232.fsf@wi.uni-muenster.de> (raw)
In-Reply-To: <63efb80e.7b0a0220.bb35b.4ae2@mx.google.com> (Bruno Barbier's message of "Fri, 17 Feb 2023 18:23:25 +0100")
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On 2023-02-17, Bruno Barbier wrote:
> Here is a way to reproduce that doesn't use org, in case it might help
> to manully fix your encoding issue:
>
> (with-temp-buffer
> (insert "Lechtenb\303\266rger")
> (let ((buffer-file-name (make-temp-file "mailtest")))
> (save-buffer)))
>
> Does it work with your old config (with your old org) ?
This also asks for an encoding.
> What kind of failure do you get elsewhere if you let Emacs use the
> correct encoding (i.e. if you use `insert-file-contents') ?
I want to be sure to use the file contents in unchanged form, as
promised by insert-file-contents-literally. For now, I copied part
of the code from insert-file-contents-literally to avoid
after-insert processing and file handlers. I still do not
understand what is happening differently in my case, though...
Best wishes
Jens
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 6187 bytes --]
next prev parent reply other threads:[~2023-02-20 9:31 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
2023-02-17 16:56 ` Jens Lechtenboerger
2023-02-17 17:23 ` Bruno Barbier
2023-02-20 9:18 ` Jens Lechtenboerger [this message]
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
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=87cz64u232.fsf@wi.uni-muenster.de \
--to=lechten@wi.uni-muenster.de \
--cc=brubar.cs@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).