all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Taiju HIGASHI <higashi@taiju.info>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
	53536@debbugs.gnu.org
Cc: me@tobias.gr, leo@famulari.name, marius@gnu.org
Subject: [bug#53536] [PATCH 0/1] Add poppler-with-data.
Date: Thu, 27 Jan 2022 09:55:27 +0900	[thread overview]
Message-ID: <87y232yp34.fsf@taiju.info> (raw)
In-Reply-To: <9e9597b58d81b8ff9ff5c3bff20d0818db39a9ee.camel@ist.tugraz.at> (Liliana Marie Prikler's message of "Wed, 26 Jan 2022 15:16:45 +0100")

Hi,

You're absolutely right.
This patch can only alleviate the pain, it cannot eliminate it.

This was a painstaking effort to accommodate users who do not use CJK,
but if you would consider making poppler-with-data a replacement for
poppler, that would be better.

> Unlike Nix, we don't have feature options (not until Ludo pushes the
> code to add them, at least, but that too appears to be at least one
> core-updates cycle away), so it's either the all-or-nothing approach
> of having or not having it as input to poppler, or the environment
> variable.  Looking at the output of `guix size', poppler takes up
> 138.1 MiB on a disk with 7.3 MiB being poppler itself, whereas
> poppler-data takes up 12.4 MiB.  I personally think that tradeoff to
> be worth it as in "let's include poppler-data in poppler so as to not
> discriminate against our Non-Latin script users".  It's an increase of
> less than 10% to support clearly more than 10% of the world's
> population (though how many of them use PDFs is an uncertain number).

I'm on the minority side, so I can't speak strongly, but I'd be very
happy if you would consider bundling poppler-data with poppler by
default.

I had a strong desire to use Guix, so I solved small problems on my own.
However, people who are just trying out Guix may decide that Guix is
useless just because it cannot display Japanese PDFs.

Displaying and outputting PDFs in Japanese is a very basic task, so
struggling with this is not impressive.

It's much better now, but in the past, We often encountered problems
specific to the Japanese environment in GNU/Linux.

In light of this, it is usually best to use a distribution with many
Japanese users.

If they are using Guix and run into such problems, they will think, "I
knew it".

I want more Japanese users to use this wonderful Guix, but I think it
would be a shame if these experiences affect them and they leave.

The above is my opinion as a Japanese, but other non-Latin script users
may have the same opinion.

Thanks




  reply	other threads:[~2022-01-27  0:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 23:59 [bug#53536] [PATCH 0/1] Add poppler-with-data Taiju HIGASHI
2022-01-26  0:20 ` [bug#53536] [PATCH 1/1] gnu: " Taiju HIGASHI
2022-01-26  7:37 ` [bug#53536] [PATCH 0/1] " Liliana Marie Prikler
2022-01-26 13:38   ` Taiju HIGASHI
2022-01-26 14:16     ` Liliana Marie Prikler
2022-01-27  0:55       ` Taiju HIGASHI [this message]
2022-01-26 13:42   ` Taiju HIGASHI
2022-02-02  3:48 ` [bug#53536] [PATCH v2] gnu: Include poppler-data with poppler Taiju HIGASHI
2022-02-02  7:27   ` Liliana Marie Prikler
2022-02-02 13:35     ` Taiju HIGASHI
2022-02-02 14:16       ` Liliana Marie Prikler
2022-02-02 15:47         ` Taiju HIGASHI
2022-02-03  6:54           ` Liliana Marie Prikler
2022-02-03  7:23             ` Taiju HIGASHI
2022-02-02  3:58 ` [bug#53536] [PATCH 0/1] Add poppler-with-data Taiju HIGASHI
2022-02-02  6:22 ` [bug#53536] [PATCH v2] gnu: Include poppler-data with poppler Taiju HIGASHI
2022-02-03  6:23 ` [bug#53536] [PATCH v3 1/2] gnu: poppler: Add poppler-data Taiju HIGASHI
2022-02-03  6:23   ` [bug#53536] [PATCH v3 2/2] gnu: pdf2djvu: Remove poppler-data Taiju HIGASHI
2022-02-03  6:28     ` Taiju HIGASHI
2022-02-06  0:00   ` bug#53536: [PATCH v3 1/2] gnu: poppler: Add poppler-data Liliana Marie Prikler

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

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

  git send-email \
    --in-reply-to=87y232yp34.fsf@taiju.info \
    --to=higashi@taiju.info \
    --cc=53536@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=liliana.prikler@ist.tugraz.at \
    --cc=marius@gnu.org \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.