unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Göktuğ Kayaalp" <self@gkayaalp.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Build failure caused by a .tit file
Date: Tue, 18 Apr 2017 16:16:12 +0300	[thread overview]
Message-ID: <871sspc0v7.fsf@gkayaalp.com> (raw)
In-Reply-To: <8760i1c2gm.fsf@gkayaalp.com> ("Göktuğ Kayaalp"'s message of "Tue, 18 Apr 2017 15:41:45 +0300")

On 2017-04-18 15:41 +0300, Göktuğ Kayaalp <self@gkayaalp.com> wrote:
> diff --git a/lisp/international/titdic-cnv.el b/lisp/international/titdic-cnv.el
> index 130bc74..6a593e2 100644
> --- a/lisp/international/titdic-cnv.el
> +++ b/lisp/international/titdic-cnv.el
> @@ -474,7 +474,6 @@ titdic-convert
>      (with-temp-file  (tit-make-quail-package-file-name filename dirname)
>        (let ((standard-output (current-buffer)))
>  	(with-temp-buffer
> -	  (set-buffer-multibyte nil)
>  	  ;; Here we must use `raw-text' instead of `no-conversion' to
>  	  ;; enable auto-decoding of eol format (CRLF->LF).
>  	  (let ((coding-system-for-read 'raw-text))

A better version of this one is as follows, which removes the
complementary set-buffer-multibyte call:

diff --git a/lisp/international/titdic-cnv.el b/lisp/international/titdic-cnv.el
index 130bc74..aa6e4f1 100644
--- a/lisp/international/titdic-cnv.el
+++ b/lisp/international/titdic-cnv.el
@@ -474,7 +474,6 @@ titdic-convert
     (with-temp-file  (tit-make-quail-package-file-name filename dirname)
       (let ((standard-output (current-buffer)))
 	(with-temp-buffer
-	  (set-buffer-multibyte nil)
 	  ;; Here we must use `raw-text' instead of `no-conversion' to
 	  ;; enable auto-decoding of eol format (CRLF->LF).
 	  (let ((coding-system-for-read 'raw-text))
@@ -504,7 +503,6 @@ titdic-convert
 		  (coding-system-change-eol-conversion coding-system 'unix))
 	    (remove-text-properties (point-min) (point-max) '(charset nil)))
 
-	  (set-buffer-multibyte t)
 	  ;; Set point the starting position of the body part.
 	  (goto-char (point-min))
 	  (if (not (search-forward "\nBEGIN" nil t))

BTW I did manage to successfully build with this patch applied.  Maybe
that second call should happen before the first call to the search
forward, i.e. just after the let form in the first hunk.

Now I get this weird warning, I can report that elsewhere if not
expected:

Error (initialization): Creation of the default fontsets failed: (error
Invalid script or charset name: old-italic)

This is from a build of master as of yesterday (edc63bf).  I don't get
this with 25.1.

--gk.



  reply	other threads:[~2017-04-18 13:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 14:03 Build failure caused by a .tit file Göktuğ Kayaalp
2017-04-17 14:41 ` 良ϖ
2017-04-17 15:57   ` Göktuğ Kayaalp
2017-04-17 14:45 ` Eli Zaretskii
2017-04-17 15:55   ` Göktuğ Kayaalp
2017-04-17 16:21     ` Eli Zaretskii
2017-04-17 23:08       ` Göktuğ Kayaalp
2017-04-18  2:43         ` Eli Zaretskii
2017-04-18 12:41           ` Göktuğ Kayaalp
2017-04-18 13:16             ` Göktuğ Kayaalp [this message]
2017-04-18 15:02               ` Eli Zaretskii
2017-04-18 14:56             ` Eli Zaretskii
2017-04-18 16:19               ` Göktuğ Kayaalp
2017-04-18 16:39                 ` Eli Zaretskii

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=871sspc0v7.fsf@gkayaalp.com \
    --to=self@gkayaalp.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).