From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Skipping unexec via a big .elc file Date: Sat, 25 Feb 2017 16:52:12 +0200 Message-ID: <83r32mqq5f.fsf@gnu.org> References: <8360ojpndr.fsf@gnu.org> <83shrnm0k1.fsf@gnu.org> <075B0922-F07A-4FBA-AE71-027E964A5ED4@raeburn.org> <54AAC13A-CF56-4393-A932-DC6CBBF51259@raeburn.org> <3CC6BB36-1794-4202-8243-132E0345B236@raeburn.org> <52BDCC33-546C-4F47-A230-00EBC813B038@raeburn.org> <15CF14CC-C7DE-44BA-AC7D-F0BF1F160979@raeburn.org> <9463F91F-DB82-48E1-BE01-1E2BC8DA0766@raeburn.org> <831swxzbw8.fsf@gnu.org> <83y3z2wphb.fsf@gnu.org> <83tw9bb42m.fsf@gnu.org> <349ED8B9-C34B-495B-9FB5-E72CE6EFCA38@raeburn.org> <87inpni6xa.fsf@linux-m68k.org> <8360lmesso.fsf@gnu.org> <3B044D64-7C94-42D7-BE1B-7A9CA76C5A67@raeburn.org> <83k29xc49v.fsf@gnu.org> <2C5C5C6E-9D73-4613-948B-C15B93968717@raeburn.org> <83poiy8cnv.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1488034396 18070 195.159.176.226 (25 Feb 2017 14:53:16 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 25 Feb 2017 14:53:16 +0000 (UTC) Cc: emacs-devel@gnu.org To: Ken Raeburn Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Feb 25 15:53:12 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1chdie-0003r6-Sq for ged-emacs-devel@m.gmane.org; Sat, 25 Feb 2017 15:53:08 +0100 Original-Received: from localhost ([::1]:42970 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1chdik-0008Cs-UG for ged-emacs-devel@m.gmane.org; Sat, 25 Feb 2017 09:53:14 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50378) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1chdiC-0008Cl-Tn for emacs-devel@gnu.org; Sat, 25 Feb 2017 09:52:41 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1chdi9-0006B5-3e for emacs-devel@gnu.org; Sat, 25 Feb 2017 09:52:41 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:55728) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1chdi9-0006B1-07; Sat, 25 Feb 2017 09:52:37 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4434 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1chdi8-00049W-69; Sat, 25 Feb 2017 09:52:36 -0500 In-reply-to: (message from Ken Raeburn on Sun, 5 Feb 2017 09:19:38 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:212596 Archived-At: > From: Ken Raeburn > Date: Sun, 5 Feb 2017 09:19:38 -0500 > Cc: Emacs developers > > I also tracked down my new ja-dic-cnv problem. It looks like SKK-JISYO.L was being mangled on read because the input sequences weren’t recognized as Unicode compatible; this caused the resulting buffer not to be considered UTF-8 compatible, so it prompted for a coding system to write with. Calling unify-charset on the various charsets seems to be needed. Is this part in the repository? Because I still get prompted for an encoding when producing ja-dic.el: GEN ../lisp/leim/ja-dic/ja-dic.el Reading file "d:/gnu/git/emacs/no-unexec/leim/SKK-DIC/SKK-JISYO.L" ... Processing OKURI-ARI entries ... Processing POSTFIX entries ... Processing PREFIX entries ... Collecting OKURI-NASI entries ... collected 26% ... collected 30% ... collected 40% ... collected 50% ... collected 60% ... collected 70% ... collected 80% ... collected 90% ... Processing OKURI-NASI entries ... processed 10% ... processed 20% ... processed 30% ... processed 40% ... processed 50% ... processed 60% ... processed 70% ... processed 80% ... processed 90% ... processed 100% ... Select coding system (default japanese-shift-jis): utf-8-unix I needed to type utf-8-unix by hand. Any ideas? Is it possible that this happens because my default encoding is not UTF-8? I also pushed a small Windows-specific change to the branch, to allow Windows users try building this branch. Thanks.