paperist / texlive-ja Goto Github PK

I'm satisfied with my ./manuscript.tex is compiled correctly with command
docker-compose run --rm latexmk manuscript.tex

But I want to move *.tex and *.pdf into ./docs/ next.

I tried the procedures below but compilation failed finally.

My trial

Move manuscript

mkdir docs
mv .manuscript.tex ./docs

Edit docker-compose.yml

  volumes:
-    - './:/workdir'
+   - './docs/:/workdir

Rebuild docker-compose

docker-compose up -d

Compile .tex

docker-compose run --rm latexmk manuscript.tex

• 64bit ARM64 (I have M1 Mac)
• 32bit ARMvX (I have Raspberry PI 4)

Thanks to the answer to #2, I managed to set workflow using latexmk up.

I tried to watch *.tex file update using -pvc option,
but it failed because acroread is not installed to the Docker image.

Would you tell me how can I install acroread to the image?

Thanks,

The size difference between debian and alpine is mainly due to fontconfig-dev and freetype-dev.
I assume this difference can be shrunk. TeX Live does usually not require any dev packages and dev packages are large in debian.

(Investigated with https://github.com/wagoodman/dive)

Debian

Alpine

Debian without dev packages

Alpine without dev packages

Sizes

REPOSITORY                                      TAG             IMAGE ID       CREATED         SIZE
texlive-ja-debian                               latest          5de04b0ec948   9 hours ago     1.2GB
texlive-ja-alpine                               latest          f64403c05737   9 hours ago     1.05GB
texlive-ja-debian-2                             latest          7ce6aff728eb   7 minutes ago   1.12GB
texlive-ja-alpine-2                             latest          5c2e89f28d1c   2 minutes ago   1.04GB

Hi, your image was working perfect until recently, but now tlmgr fails with the following error:

tlmgr install fontawesome multibib

tlmgr: Remote repository is newer than local (2018 < 2019)
Cross release updates are only supported with
  update-tlmgr-latest(.sh/.exe) --update
Please see https://tug.org/texlive/upgrade.html for details.
Exited with code 1

I guess it's because TeX Live 2019 has been released?

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Thank you for developing a great container. It worked and a pdf file was created.
But would you tell me how can I open the pdf file from docker image (I'm a novice of Docker, so excuse me for asking a stupid question)?

I compiled example.tex from a shell script like

platex example
pbibtex example
platex example
platex example
dvipdfmx example
open example.pdf.

The last command containing open command fails because the command did not work in the docker image.

What command should I use to open a file in the image?
I found a word linux in the Dockerfile, so I tested

• xgd-open
• evince-open
• gnome-open
• etc...
  but none of them worked.

HI, this is noe. I use it with write paper with latex.
I saw this error when I use .eps file in latex.

latex-test-latex-1  | Running 'dvipdfmx  -o "template.pdf" "template.dvi"'
latex-test-latex-1  | ------------
latex-test-latex-1  | template.dvi -> template.pdf
latex-test-latex-1  | [1][2][3][4][5][6
latex-test-latex-1  | dvipdfmx:warning: Could not open conversion result "/tmp/dvipdfm-x.5884038f1a3641531dc1e7b804bdf7dd" for image "./sampleimage.eps". Why?
latex-test-latex-1  | dvipdfmx:fatal: Image inclusion failed for "sampleimage.eps" (page=1).

This seems to be an error caused by ghostscript not being installed on debian or alpine. (If I installed ghostscript in docker container, this problem was solved).

When writing a paper, eps files are minor, but sometimes used.
In this case, can I ask you to add the installation of ghostscript? Or should we customize our own Dockerfile and install it additionally?

Have a nice day!

Hi!

It seems xelatex is missing some librairies in this image:

bash-4.4# xelatex -help
Error loading shared library libfontconfig.so.1: No such file or directory (needed by /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex)
Error loading shared library libfreetype.so.6: No such file or directory (needed by /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex)
Error relocating /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex: FcPatternDestroy: symbol not found
Error relocating /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex: FcObjectSetDestroy: symbol not found
Error relocating /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex: FcConfigGetCurrent: symbol not found
Error relocating /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex: FcGetVersion: symbol not found
Error relocating /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex: FcPatternGetString: symbol not found
Error relocating /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex: FcPatternGetInteger: symbol not found
Error relocating /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex: FcFontList: symbol not found
Error relocating /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex: FcObjectSetBuild: symbol not found
Error relocating /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex: FcInit: symbol not found
Error relocating /usr/local/texlive/2018/bin/x86_64-linuxmusl/xelatex: FcNameParse: symbol not found

Hi,

I'd like to know how to change from Japanese based to English based.
Which code do I need to update?

Thank you.