all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emmanuel Beffara <manu@beffara.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Josselin Poiret <dev@jpoiret.xyz>,
	help-guix@gnu.org, 56556@debbugs.gnu.org,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: bug#56556: texlive-babel-dutch with and without texlive-hyphen-dutch: No hyphenation patterns were preloaded
Date: Fri, 7 Apr 2023 12:47:21 +0200	[thread overview]
Message-ID: <20230407124721.GQ1554@beffara.org> (raw)
In-Reply-To: <87h6tsf0ca.fsf_-_@gnu.org>

Hi,

De Ludovic Courtès le 07/04/2023 à 12:33:
> > I don't really know how we could fix this: maybe build the formats with
> > all the hyphenation packages enabled?
> 
> The intertubes suggest running ‘fmtutil --all’ to get hyphenations
> packages straight.  Is this something we should do in the TeX Live
> profile hook for example?
> 
> Emmanuel, is this what you had in mind when you wrote about compilation
> of hyphenation patterns above?

Indeed !

Doing that is the job of fmtutil and it should be used for building
environments that include parts of TeXlive.

-- 
Emmanuel


  reply	other threads:[~2023-04-07 10:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 19:30 TeXlive packaging issues Emmanuel Beffara
2023-03-29 18:48 ` bug#56556: " Josselin Poiret
2023-04-07 10:33   ` bug#56556: texlive-babel-dutch with and without texlive-hyphen-dutch: No hyphenation patterns were preloaded Ludovic Courtès
2023-04-07 10:47     ` Emmanuel Beffara [this message]
2023-05-19 15:22       ` Simon Tournier
2024-08-31 23:20         ` Nicolas Goaziou via Bug reports for GNU Guix
  -- strict thread matches above, loose matches on Subject: below --
2022-07-14 14:13 Remco van 't Veer
2022-08-09 14:05 ` bug#56556: Wicki Gabriel (wicg)

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=20230407124721.GQ1554@beffara.org \
    --to=manu@beffara.org \
    --cc=56556@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.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 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.