unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: emacs-devel@gnu.org
Subject: Re: Coding systems vietnamese-vscii and vietnamese-tcvn
Date: Fri, 21 Jul 2023 15:34:57 +0300	[thread overview]
Message-ID: <83zg3pzbm6.fsf@gnu.org> (raw)
In-Reply-To: <u5y6djyk5@gentoo.org> (message from Ulrich Mueller on Fri, 21 Jul 2023 13:26:02 +0200)

> From: Ulrich Mueller <ulm@gentoo.org>
> Date: Fri, 21 Jul 2023 13:26:02 +0200
> 
> language/vietnamese.el defines coding systems vietnamese-vscii
> (with charset vscii) and vietnamese-tcvn (with charset tcvn-5712).
> However, mule-conf.el defines the two charsets as aliases [1]:
> 
>    (define-charset-alias 'tcvn-5712 'vscii)
> 
> Indeed, a file containing bytes 0x00 to 0xff decodes to the same buffer
> contents, regardless if its coding is specified as vscii or as tcvn.
> 
> Wikipedia also seems to say that these are only different names for
> the same encoding: https://en.wikipedia.org/wiki/VSCII
> 
> Should coding system vietnamese-tcvn be an alias for vietnamese-vscii
> (or the other way around)?

Why is the fact that we have two separate coding systems a problem in
this case?



  reply	other threads:[~2023-07-21 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 11:26 Coding systems vietnamese-vscii and vietnamese-tcvn Ulrich Mueller
2023-07-21 12:34 ` Eli Zaretskii [this message]
2023-07-21 12:52   ` Ulrich Mueller
2023-07-21 13:06     ` Eli Zaretskii
2023-07-28 18:03       ` Ulrich Mueller
2023-07-28 18:53         ` Eli Zaretskii
2023-07-29  5:19           ` Ulrich Müller

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=83zg3pzbm6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ulm@gentoo.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
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).