emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Paul Schlesinger <phschlesinger@gmail.com>
Cc: Orgmode <emacs-orgmode@gnu.org>
Subject: Re: orgmode 9.6
Date: Sun, 18 Dec 2022 02:59:16 +0300	[thread overview]
Message-ID: <Y55X1O0YNwnxnupW@protected.localdomain> (raw)
In-Reply-To: <CAG8VtR2n7gdJLdXC4a4nn-CnbiZkjMfGCQeDapoWDv-JkRFwbA@mail.gmail.com>

* Paul Schlesinger <phschlesinger@gmail.com> [2022-12-17 00:31]:
> Just to remind you the encoding warning does not occur with the same files
> using the emacs 28.1 with orgmode 9.52 included.  The characters that
> trigger the warning are ones that are not found in UTF-8 and since I do a
> lot of editing of web documents and do not correct them until final
> output.  orgmode has ignored them in the past (BEFORE 9.6) and  I am happy
> with that as long as the files do not become corrupted.  Can one set the
> encoding in orgmode as not having to configure file in real time would be
> helpful.

I remember that I was solving those issues by other editor that
automatically recognized those wrong characters and offered me to
normalize it.

I believe that editor was the `mousepad'.

Here is what I suggest to you:

1. Make a copy of the file that has the errors.

2. Try opening it with the `mousepad' and see if it is offering you
correction.

3. Save it with the `mousepad'.

4. Open it with Emacs and see if it works at that point.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/


      reply	other threads:[~2022-12-18  0:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 23:02 orgmode 9.6 Paul Schlesinger
2022-12-16  6:06 ` Ihor Radchenko
2022-12-16  6:47 ` Jean Louis
2022-12-16 21:28   ` Paul Schlesinger
2022-12-17 23:59     ` Jean Louis [this message]

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=Y55X1O0YNwnxnupW@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=emacs-orgmode@gnu.org \
    --cc=phschlesinger@gmail.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 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).