emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: Bruno Barbier <brubar.cs@gmail.com>
Cc: <emacs-orgmode@gnu.org>
Subject: Re: Unicode problem with export of literal contents
Date: Fri, 17 Feb 2023 08:48:26 +0100	[thread overview]
Message-ID: <87fsb4u3zp.fsf@wi.uni-muenster.de> (raw)
In-Reply-To: <63ef15e9.df0a0220.8edda.8c58@mx.google.com> (Bruno Barbier's message of "Fri, 17 Feb 2023 06:51:35 +0100")

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

Hi Bruno,

On 2023-02-17, Bruno Barbier wrote:

> Hi Jens,
>
> Jens Lechtenboerger <lechten@wi.uni-muenster.de> writes:
>
>> ...
>> 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).
>>
>> Could the old behavior be restored?
>
> By using `insert-file-contents-literally' (as opposed to
> `insert-file-contents'), you're also forbidding Emacs to decode the
> binary content of your file into text.
>
> My guess is that it was working by chance in previous versions.

in any case, this will introduce failures elsewhere.

> In case somebody might help you, here is a simple way to trigger the
> encoding question with a recent version of org (mine is Org mode version 9.6.1).
>
>    (with-temp-buffer
>       (insert "Lechtenb\303\266rger")
>       (org-mode))

Thank you for the simpler recipe.  This indeed fails now.

So, maybe my question is: Must text be decoded for Org mode from now on?

Best wishes
Jens

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 6187 bytes --]

next prev parent reply	other threads:[~2023-02-17  7:49 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 [this message]
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
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=87fsb4u3zp.fsf@wi.uni-muenster.de \
    --to=lechten@wi.uni-muenster.de \
    --cc=brubar.cs@gmail.com \
    --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

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).