unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Michael Welsh Duggan <mwd@md5i.com>,
	Michael Albinus <michael.albinus@gmx.de>,
	Kenichi Handa <handa@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Encoding of etc/HELLO
Date: Sat, 19 May 2018 10:17:33 -0700	[thread overview]
Message-ID: <69662556-2fb0-356f-dad8-5b94d6833ce5@cs.ucla.edu> (raw)
In-Reply-To: <83k1rzhdoo.fsf@gnu.org>

Eli Zaretskii wrote:
> Thanks, I used this idea to extend Enriched mode with support of
> 'charset' properties, and then recoded HELLO in UTF-8 and placed it
> under Enriched mode.

Thanks for doing all that.

In looking at the new etc/HELLO, I see many uses of <x-charset><param> that seem 
to be unnecessary when Emacs is viewing the file. For example, the first few 
uses are:

<x-charset><param>latin-iso8859-1</param>¡Hola!, Grüß Gott, Hyvää päivää, Tere 
õhtust, Bon</x-charset><x-charset><param>latin-iso8859-3</param>ġu
           Cze</x-charset><x-charset><param>latin-iso8859-2</param>ść!, Dobrý 
den, </x-charset>

Can't the abovementioned formatting commands be removed without affecting what 
any Emacs user sees, because the corresponding character sets are not unified in 
Unicode? Would it be OK to simplify /etc/HELLO to remove unnecessary formatting 
commands, and to keep only the formatting commands that are plausibly needed in 
a Unicode text file? And if so, what heuristic should be used to remove the 
unnecessary formatting commands?

I assume that the formatting commands were done automatically, so perhaps I'm 
talking about potential changes to lisp/textmodes/enriched.el.



  reply	other threads:[~2018-05-19 17:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 13:25 Encoding of etc/HELLO Eli Zaretskii
2018-04-20 15:34 ` Michael Albinus
2018-04-20 16:00   ` Eli Zaretskii
2018-04-20 16:16     ` Stefan Monnier
2018-04-20 17:22       ` Eli Zaretskii
2018-04-20 20:42         ` Stefan Monnier
2018-04-20 21:02           ` Clément Pit-Claudel
2018-04-20 21:26           ` Paul Eggert
2018-04-21  7:07           ` Eli Zaretskii
2018-04-21 14:58             ` Michael Welsh Duggan
2018-05-19 15:23               ` Eli Zaretskii
2018-05-19 17:17                 ` Paul Eggert [this message]
2018-05-19 18:03                   ` Eli Zaretskii
2018-05-19 18:23                     ` Paul Eggert
2018-05-19 18:39                       ` Eli Zaretskii
2018-05-19 19:38                         ` Paul Eggert
2018-05-19 20:03                           ` Eli Zaretskii
2018-05-20  8:56                             ` Eli Zaretskii
2018-05-19 17:52                 ` Michael Albinus
2018-04-20 17:39     ` Michael Albinus
2018-04-21  7:10       ` Eli Zaretskii
2018-04-21 14:40         ` Clément Pit-Claudel
2018-04-21 15:43           ` Eli Zaretskii
2018-04-21 15:52           ` Paul Eggert
2018-04-23  2:53         ` Stefan Monnier
2018-04-23 15:07           ` Eli Zaretskii
2018-04-23 15:23             ` Stefan Monnier
2018-04-23 16:12               ` Eli Zaretskii
2018-04-20 16:56   ` Paul Eggert
2018-04-20 17:37     ` Michael Albinus
2018-04-21 20:31       ` Juri Linkov
2018-04-23 16:25         ` Eli Zaretskii
2018-04-23 20:05           ` Juri Linkov

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=69662556-2fb0-356f-dad8-5b94d6833ce5@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=mwd@md5i.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.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).