unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
* bug#35780: [PATCH] attempt to fix polyglossia
       [not found]   ` <87y334ctfu.fsf@elephly.net>
@ 2019-06-21 15:40     ` Josh Holland
  2022-05-14  5:22       ` bug#35780: texlive-latex-polyglossia package empty Maxim Cournoyer
  0 siblings, 1 reply; 2+ messages in thread
From: Josh Holland @ 2019-06-21 15:40 UTC (permalink / raw)
  To: Ricardo Wurmus; +Cc: guix-devel, 35780

Hi,

(CCing guix-devel because I'm confused about this and more eyes can't
hurt)

On Sat, May 18, 2019 at 05:50:13AM +0200, Ricardo Wurmus wrote:
> Thanks for giving it a try.  The build system works on “ins” files by
> default.  I guess it should try “dtx” files as well.

Should this be a patch to the build-system?  Although maybe it's not
that simple: https://ctan.org/texarchive/macros/xetex/latex/polyglossia
lists four files, incuding an "ins" file.

> We can patch the dtx file in a build phase and replace “../README” with
> just “README”.

I tried patching the README path as Ricardo suggested.  This got
somewhere, complaining of missing fonts, so I added texlive-fonts-cm
to native-inputs.  With both these changes, the build now fails while
trying to build example-thai.tex, and the errors appear to indicate
trying to build a LaTeX file with plain TeX:

Processing file polyglossia.dtx (example-thai.tex) -> example-thai.tex
File polyglossia.dtx ended by \endinput.
Lines  processed: 11224
Comments removed: 1600
Comments  passed: 215
Codelines passed: 9209

! Undefined control sequence.
l.209 \documentclass
                  [11pt]{ltxdoc}
! Undefined control sequence.
l.210 \usepackage
               {color}
! Undefined control sequence.
l.211 \usepackage
               {xspace,fancyvrb}
! Undefined control sequence.
l.212 \usepackage
               [neverdecrease]{paralist}
! Undefined control sequence.
l.213 \definecolor
                {myblue}{rgb}{0.02,0.04,0.48}
! Undefined control sequence.
l.214 \definecolor
                {lightblue}{rgb}{0.61,.8,.8}
! Undefined control sequence.
l.215 \definecolor
                {myred}{rgb}{0.65,0.04,0.07}
! Undefined control sequence.

(and more...)

I'm not that familiar with the intricacies of properly building TeXLive
from source, but the difference between the file list on CTAN and what
comes from the Subversion repo via texlive-ref smells fishy to me.  If I
manually run any permutation of  `{xe,lua}tex polyglossia.{ins,dtx}`
it mostly seems to build OK, but to my surprise no polyglossia.sty
is produced!  There's no actual build instructions in the README or the
polyglossia.pdf, so I'm rather lost here.

Thanks,

-- 
Josh Holland

^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#35780: texlive-latex-polyglossia package empty
  2019-06-21 15:40     ` bug#35780: [PATCH] attempt to fix polyglossia Josh Holland
@ 2022-05-14  5:22       ` Maxim Cournoyer
  0 siblings, 0 replies; 2+ messages in thread
From: Maxim Cournoyer @ 2022-05-14  5:22 UTC (permalink / raw)
  To: Ricardo Wurmus; +Cc: guix-devel, 35780-done

Hello,

The texlive-polyglossia is no longer empty, and works, at least with
XeLaTeX.  You can see it in action building the doc of our
'python-ipython-documentation' package.

Closing!

Thanks,

Maxim




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-05-14  5:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20190517165152.GA5797@spica.localdomain>
     [not found] ` <20190517212351.8855-1-josh@inv.alid.pw>
     [not found]   ` <87y334ctfu.fsf@elephly.net>
2019-06-21 15:40     ` bug#35780: [PATCH] attempt to fix polyglossia Josh Holland
2022-05-14  5:22       ` bug#35780: texlive-latex-polyglossia package empty Maxim Cournoyer

Code repositories for project(s) associated with this 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).