diff options
author | Norbert Preining <norbert@preining.info> | 2023-03-06 03:05:29 +0000 |
---|---|---|
committer | Norbert Preining <norbert@preining.info> | 2023-03-06 03:05:29 +0000 |
commit | 75cd005305bd2c2a0ec383f30ee5b1749ed15183 (patch) | |
tree | 65b5e6b912547ab4610badf5a7f61ce70e5aad02 /systems/win32/TLW64 | |
parent | a2d17a09f7ecd91acd8826216349bb14cc5602cd (diff) |
CTAN sync 202303060305
Diffstat (limited to 'systems/win32/TLW64')
-rw-r--r-- | systems/win32/TLW64/00README.TLW64 | 72 |
1 files changed, 2 insertions, 70 deletions
diff --git a/systems/win32/TLW64/00README.TLW64 b/systems/win32/TLW64/00README.TLW64 index 2f60e24c37..16e884efdb 100644 --- a/systems/win32/TLW64/00README.TLW64 +++ b/systems/win32/TLW64/00README.TLW64 @@ -1,72 +1,4 @@ - How to install 64bit binaries for TeX Live on Windows +tl-win64.zip is removed because Windows binaries in TeX Live +are 64bit from TeX Live 2023. -In the following, $INSTALLDIR is $SELFAUTOPARENT in the TeX Live, -that is, the parent directory of "texmf-dist". Actually the -directory $INSTALLDIR is shown by a command: - - kpsewhich --var-value=SELFAUTOPARENT - - -(1) Expand the file tl-win64.zip in $INSTALLDIR. - In the case of update, remove all files in $INSTALLDIR/bin/win64 - before expanding tl-win64.zip, because it is possible that - some files are deleted in a new tl-win64.zip. - -(2) After expanding tl-win64.zip in $INSTALLDIR, - change related command PATH from - $INSTALLDIR\bin\win32 - to - $INSTALLDIR\bin\win64;$INSTALLDIR\bin\win32 - - Note that the following 32bit binaries in $INSTALLDIR\bin\win32 - are still used on WOW64: - - jbig2.exe latexindent.exe psviewer.exe tex2xindy.exe - tlaunch.exe tlshell.exe unzip.exe xindy-lisp.exe - xindy.mem zip.exe texaccents.exe - - Moreover, tlmgr.bat does not exist in $INSTALLDIR\bin\win64 - due to an obvious reason. - - Thus $INSTALLDIR\bin\win32 is necessary "after" - $INSTALLDIR\bin\win64. - - If there are problems in 64bit binaries, it is easy to recover - the original TeX Live win32, by changing back the PATH: - $INSTALLDIR\bin\win64;$INSTALLDIR\bin\win32 ---> - $INSTALLDIR\bin\win32 - -(3) Ghostscript is assumed to be 64bit. The dvisvgm.exe searches - for gsdll64.dll by reading registry, and gsftopk.exe searches - for gsdll64.dll in the command PATH. Therefore users should - install 64bit Ghostscript and set the command PATH for the - Ghostscript. However, don't define TEXLIVE_WINDOWS_EXTERNAL_GS - in texmf.cnf, because the preinstalled 32bit Ghostscript is - also used in several cases. - - gs1000w64full-gpl.exe in this directory is Ghostscript 10.0.0 - for 64bit Windows compiled with COMPILE_INITS=0. Users can install - their favorite 'traineddata' files obtained from - https://github.com/tesseract-ocr/tessdata_best - into the predefined directory Resource/Tesseract in order to use - ocr devices. Three files, eng.traineddata, jpn.traineddata - and jpn_vert.traineddata, are already installed as examples. - The eng.traineddata is the default for ocr devices. - - From TeX Live 2020, the version of 64bit binaries will be - synchronized with that of 32bit binaries. It is expected that - common format files can be usable for 32bit/64bit binaries. - - Recently in TeX Live 2021 and 2022, it is reported that luatex - family requires different format files and luaotfload data - in 64bit binaries compared with those in 32bit binaries. Thus - The following commands may be necessary: - fmtutil-sys --byengine luahbtex - fmtutil-sys --byengine luatex - fmtutil-sys --byengine luajithbtex - fmtutil-sys --byengine luajittex - luaotfload-tool -f -u -vvv - --- -Akira Kakuto |