unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: luhux <luhux@outlook.com>
Cc: 43592-done@debbugs.gnu.org
Subject: bug#43592: luit does not work
Date: Mon, 11 Jul 2022 15:09:39 -0400	[thread overview]
Message-ID: <87v8s3bh58.fsf@gmail.com> (raw)
In-Reply-To: <PSXP216MB02146967E1CAF39D077906E8A0390@PSXP216MB0214.KORP216.PROD.OUTLOOK.COM> (luhux@outlook.com's message of "Thu, 24 Sep 2020 20:24:50 +0800")

Hi,

luhux <luhux@outlook.com> writes:

> I use luit to convert the encoding of MUD games, but I failed
>
> It uses the wrong path to find the data
>
> dev@tencent ~$ luit -encoding gbk
> /gnu/store/a4knixgswikbb4r7cw9srh07w0f9n0jw-luit-1.1.1/share/X11/locale/locale.alias:
> No such file or directory
> Warning: couldn't find charset data for locale gbk; using ISO 8859-1.

'gbk' doesn't appear to be a known alias, at least for the locale.alias
file provided by our libx11 package.

I believe the missing locale.alias file has now been fixed with:

modified   gnu/packages/xorg.scm
@@ -1548,8 +1548,14 @@ (define-public luit
        ;; should become obsolete with the next release.
        (patches (search-patches "luit-posix.patch"))))
     (build-system gnu-build-system)
+    (arguments
+     (list
+      #:configure-flags
+      #~(list (string-append "--with-localealiasfile="
+                             (search-input-file
+                              %build-inputs "share/X11/locale/locale.alias")))))
     (inputs
-     (list libfontenc))
+     (list libfontenc libx11))
     (native-inputs
      (list pkg-config))
     (home-page "https://www.x.org/wiki/")

Closing.

Thanks for the report!

Maxim




      reply	other threads:[~2022-07-11 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 12:24 bug#43592: luit does not work luhux
2022-07-11 19:09 ` Maxim Cournoyer [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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87v8s3bh58.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=43592-done@debbugs.gnu.org \
    --cc=luhux@outlook.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/guix.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).