unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Modular texlive and xelatex
Date: Sun, 19 Jun 2022 21:29:06 +0200	[thread overview]
Message-ID: <Yq95Ak3g73NE52Op@jurong> (raw)
In-Reply-To: <87letvdryk.fsf@elephly.net>

Am Fri, Jun 17, 2022 at 09:06:06PM +0200 schrieb Ricardo Wurmus:
> The tlpdb says that this file is provided by the xunicode package –
> which we don’t have yet.
> 
> [time passes]

Not much actually!

> We now have texlive-xunicode as of commit
> 793ce82c9d5ead8457da9cec8d1d8afc12704f10.

Thanks a lot! I used "guix import texlive floatflt" to add this package.
Congratulations for a nice importer! (Although I stumbled over needing to
add #:trivial? #t, which becomes obvious only when comparing with
neighbouring packages.)

The result for my file still is not quite like the monolithic texlive.
First, babel complains as follows:
Package babel Warning: No hyphenation patterns were preloaded for
(babel)                the language `German (trad. orthography)' into the format.
(babel)                Please, configure your TeX system to add them and
(babel)                rebuild the format. Now I will use the patterns
(babel)                preloaded for \language=0 instead on input line 62.
I have installed texlive-generic-babel-german and texlive-hyphen-german;
have you got an idea what I am missing?

Second, the font (Linux Libertine O) looks ragged, and a "--" is typeset
as two dashes instead of an ndash. Suggestions are also welcome!

Andreas



  reply	other threads:[~2022-06-19 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 14:42 Modular texlive and xelatex Andreas Enge
2022-06-17 14:54 ` zimoun
2022-06-17 15:38   ` Andreas Enge
2022-06-17 19:06 ` Ricardo Wurmus
2022-06-19 19:29   ` Andreas Enge [this message]
2022-06-22  3:27     ` Maxim Cournoyer
2022-07-09 16:21       ` Andreas Enge

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=Yq95Ak3g73NE52Op@jurong \
    --to=andreas@enge.fr \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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).