CTAN sync 202106210301

2 files changed, 13 insertions, 57 deletions

diff --git a/systems/win32/w32tex/ChangeLog b/systems/win32/w32tex/ChangeLog
index a4c432413e..475481a17a 100644
--- a/systems/win32/w32tex/ChangeLog
+++ b/systems/win32/w32tex/ChangeLog
@@ -1,6 +1,19 @@
 
                    W32TeX (x86 & x64) ChangeLog
 
+[2021/06/20]
+(01) cjkzr.tar.xz
+     Update bxjaprnind.
+(02) makeindex-w32.tar.xz
+     Update upmendex.exe.
+(03) tex4htk-w32.tar.xz
+     Update tex4ht-4ht.tex and tex4ht-unicode.tex.
+     Update latex.4ht and unicode.4ht.
+(04) web2c-w32.tar.xz
+     Update latexindent.
+(05) win64/makeindex-w64.tar.xz
+     Update upmendex.exe.
+
 [2021/06/19]
 (01) latex-dev.tar.xz
      Update format files.
diff --git a/systems/win32/w32tex/TLARM64W/00README.TLARM64W b/systems/win32/w32tex/TLARM64W/00README.TLARM64W
deleted file mode 100644
index 485f561717..0000000000
--- a/systems/win32/w32tex/TLARM64W/00README.TLARM64W
+++ /dev/null
@@ -1,57 +0,0 @@
-        How to install arm64 binaries for TeX Live on Windows
-
-
-First, an OS of a device should be arm64 Windows.
-All binaries given here are not tested.
-
-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-arm64-windows.zip in $INSTALLDIR.
-    In the case of update, remove all files in
-    $INSTALLDIR/bin/arm64-windows before expanding
-    tl-arm64-windows.zip, because it is possible that some files are
-    deleted in a new tl-arm64-windows.zip.
-
-(2) After expanding tl-arm64-windows.zip in $INSTALLDIR,
-    change related command PATH from
-    $INSTALLDIR\bin\win32
-    to
-    $INSTALLDIR\bin\arm64-windows;$INSTALLDIR\bin\win32
-
-    Note that a few files are absent in arm64 binaries.
-    Thus $INSTALLDIR\bin\win32 is necessary "after"
-    $INSTALLDIR\bin\arm64-windows. The x86 binaries are assumed to be
-    usable by emulation.
-
-    The arm64 binaries are not tested. If they are not usable,
-    it is easy to recover the original TeX Live win32, by changing
-    back the PATH:
-    $INSTALLDIR\bin\arm64-windows;$INSTALLDIR\bin\win32 --->
-    $INSTALLDIR\bin\win32
-
-(3) gsftopk.exe and dvisvgm.exe require arm64 Ghostscript DLL,
-    which will be difficult to obtain. Here a candidate,
-    gs9533arm64full-gpl.exe, is given. It is the Ghostscript 9.53.3
-    cross-compiled by Visual Studio 2019. The installer itself is an
-    x86 executable file. It is not tested. dvisvgm finds ghostscript
-    DLL by reading a registry, but gsftopk finds the DLL from the
-    PATH variable. The installer gs9533arm64full-gpl.exe does not
-    change the PATH variable, so users should change the PATH to
-    include the location of gsdll64.dll.
-    In various cases x86 Ghostscript, which is preinstalled in the
-    TeX Live for Windows, is also used.
-
-(4) Some binaries in tl-arm64-windows.zip may be newer than those in
-    the present TeX Live. Thus probably it is necessary to recreate
-    format files by
-    fmtutil-sys --all --no-error-if-no-engine=luajittex,luajithbtex
-    Note that luajittex and luajithbtex are not supported in arm64
-    on Windows.
-
--- 
-Akira Kakuto