miktex-users Mailing List for MiKTeX (Page 2)
MiKTeX source code moved to GitHub
Brought to you by:
csc
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(123) |
Sep
(228) |
Oct
(340) |
Nov
(203) |
Dec
(195) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(318) |
Feb
(253) |
Mar
(185) |
Apr
(239) |
May
(156) |
Jun
(202) |
Jul
(153) |
Aug
(110) |
Sep
(179) |
Oct
(122) |
Nov
(211) |
Dec
(147) |
2004 |
Jan
(163) |
Feb
(116) |
Mar
(130) |
Apr
(164) |
May
(132) |
Jun
(150) |
Jul
(118) |
Aug
(188) |
Sep
(149) |
Oct
(135) |
Nov
(100) |
Dec
(140) |
2005 |
Jan
(105) |
Feb
(136) |
Mar
(68) |
Apr
(89) |
May
(118) |
Jun
(89) |
Jul
(112) |
Aug
(160) |
Sep
(109) |
Oct
(136) |
Nov
(114) |
Dec
(68) |
2006 |
Jan
(117) |
Feb
(79) |
Mar
(79) |
Apr
(88) |
May
(116) |
Jun
(147) |
Jul
(73) |
Aug
(239) |
Sep
(152) |
Oct
(207) |
Nov
(88) |
Dec
(104) |
2007 |
Jan
(131) |
Feb
(72) |
Mar
(148) |
Apr
(177) |
May
(187) |
Jun
(139) |
Jul
(113) |
Aug
(115) |
Sep
(154) |
Oct
(126) |
Nov
(133) |
Dec
(103) |
2008 |
Jan
(175) |
Feb
(124) |
Mar
(104) |
Apr
(128) |
May
(99) |
Jun
(149) |
Jul
(100) |
Aug
(59) |
Sep
(46) |
Oct
(120) |
Nov
(56) |
Dec
(36) |
2009 |
Jan
(57) |
Feb
(51) |
Mar
(64) |
Apr
(54) |
May
(28) |
Jun
(26) |
Jul
(63) |
Aug
(75) |
Sep
(159) |
Oct
(95) |
Nov
(64) |
Dec
(97) |
2010 |
Jan
(116) |
Feb
(50) |
Mar
(91) |
Apr
(134) |
May
(134) |
Jun
(94) |
Jul
(54) |
Aug
(52) |
Sep
(75) |
Oct
(147) |
Nov
(99) |
Dec
(148) |
2011 |
Jan
(87) |
Feb
(70) |
Mar
(87) |
Apr
(66) |
May
(89) |
Jun
(125) |
Jul
(145) |
Aug
(43) |
Sep
(42) |
Oct
(19) |
Nov
(22) |
Dec
(21) |
2012 |
Jan
(16) |
Feb
(25) |
Mar
(21) |
Apr
(20) |
May
(33) |
Jun
(20) |
Jul
(16) |
Aug
(36) |
Sep
(48) |
Oct
(19) |
Nov
(34) |
Dec
(22) |
2013 |
Jan
(53) |
Feb
(64) |
Mar
(37) |
Apr
(45) |
May
(26) |
Jun
(53) |
Jul
(72) |
Aug
(22) |
Sep
(45) |
Oct
(71) |
Nov
(48) |
Dec
(12) |
2014 |
Jan
(22) |
Feb
(48) |
Mar
(31) |
Apr
(28) |
May
(52) |
Jun
(56) |
Jul
(45) |
Aug
(17) |
Sep
(12) |
Oct
(40) |
Nov
(19) |
Dec
(43) |
2015 |
Jan
(10) |
Feb
(16) |
Mar
(25) |
Apr
(60) |
May
(59) |
Jun
(86) |
Jul
(24) |
Aug
(35) |
Sep
(35) |
Oct
(40) |
Nov
(18) |
Dec
(69) |
2016 |
Jan
(49) |
Feb
(15) |
Mar
(35) |
Apr
(57) |
May
(74) |
Jun
(20) |
Jul
(30) |
Aug
(9) |
Sep
(60) |
Oct
(22) |
Nov
(66) |
Dec
(58) |
2017 |
Jan
(70) |
Feb
(37) |
Mar
(26) |
Apr
(21) |
May
(13) |
Jun
(14) |
Jul
(24) |
Aug
(11) |
Sep
(5) |
Oct
(10) |
Nov
(23) |
Dec
(7) |
2018 |
Jan
(19) |
Feb
(8) |
Mar
(10) |
Apr
(9) |
May
(5) |
Jun
(5) |
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(4) |
Nov
|
Dec
(2) |
2019 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(3) |
May
(1) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
(2) |
Nov
(6) |
Dec
(3) |
2020 |
Jan
(5) |
Feb
|
Mar
|
Apr
(3) |
May
(1) |
Jun
(4) |
Jul
(1) |
Aug
|
Sep
|
Oct
(5) |
Nov
|
Dec
|
2021 |
Jan
(2) |
Feb
(3) |
Mar
(5) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
(1) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
|
2024 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Ralf H. <ral...@ya...> - 2021-03-17 18:30:17
|
With the last update (packages updated on 3/16/2021) I have a problem with xelatex, while pdflatex or lualatex both work fine. ..\AppData\Local\MiKTeX\2.9\miktex\log\initexmf.log shows: 2021-03-17 18:46:46,891+0100 FATAL xelatex.core - Die Speicher-Dump-Datei konnte nicht gefunden werden. 2021-03-17 18:46:46,891+0100 FATAL xelatex.core - Data: fileName="xelatex.fmt" 2021-03-17 18:46:46,891+0100 FATAL xelatex.core - Source: Libraries\MiKTeX\TeXAndFriends\texmfapp.cpp:717 2021-03-17 18:46:46,891+0100 FATAL xelatex - Die Speicher-Dump-Datei konnte nicht gefunden werden. 2021-03-17 18:46:46,891+0100 FATAL xelatex - Info: fileName="xelatex.fmt" 2021-03-17 18:46:46,891+0100 FATAL xelatex - Source: Libraries\MiKTeX\TeXAndFriends\texmfapp.cpp 2021-03-17 18:46:46,891+0100 FATAL xelatex - Line: 717 2021-03-17 18:46:46,893+0100 INFO xelatex - this process (1888) finishes with exit code 1 I tried to build the format xelatex via the console app. The result was Das MiKTeX-Konfigurationswerkzeug ist aus irgend einem Grund gescheitert. Die Ausgabe wurde in eine Datei gespeichert. fileName="E:\TeX\MiKTeX29\miktex/bin/x64\initexmf.exe", exitCode="1", savedOutput="%localappdata%\MiKTeX\2.9\miktex\log\initexmf_2021-03-17-190910.out" There was the information: Sorry, but "MiKTeX Configuration Utility" did not succeed. The log file hopefully contains the information to get MiKTeX going again: %localappdata%\MiKTeX\2.9\miktex\log\initexmf.log There was the information: 2021-03-17 19:09:04,146+0100 INFO initexmf - this is MiKTeX Configuration Utility 4.3 (MiKTeX 21.3) 2021-03-17 19:09:04,146+0100 INFO initexmf - this process (12000) started by 'miktex-console' with command line: initexmf --dump=xelatex 2021-03-17 19:09:04,146+0100 INFO initexmf - Operating on the private (per-user) MiKTeX setup 2021-03-17 19:09:04,153+0100 INFO initexmf - running: miktex-makefmt.exe --engine=xetex --dest-name=xelatex --no-dump xelatex.ini --miktex-disable-maintenance --miktex-disable-diagnose 2021-03-17 19:09:04,205+0100 INFO initexmf.core - start process: miktex-makefmt.exe --engine=xetex --dest-name=xelatex --no-dump xelatex.ini --miktex-disable-maintenance --miktex-disable-diagnose 2021-03-17 19:09:10,124+0100 ERROR initexmf - sub-process error output has been saved to '%localappdata%\MiKTeX\2.9\miktex\log\miktex-makefmt_2021-03-17-190910.out' 2021-03-17 19:09:10,124+0100 FATAL initexmf - The executed process did not succeed. 2021-03-17 19:09:10,124+0100 FATAL initexmf - Info: fileName="E:\TeX\MiKTeX29\miktex\bin\x64\miktex-makefmt.exe", exitCode="1" 2021-03-17 19:09:10,124+0100 FATAL initexmf - Source: 2021-03-17 19:09:10,124+0100 FATAL initexmf - Line: 0 2021-03-17 19:09:10,125+0100 INFO initexmf - this process (12000) finishes with exit code 1 Is there a problem with the latest update or is it my fault? Thanks in advance Ralf |
From: Ariovaldo V G. <gar...@gm...> - 2021-03-14 19:10:17
|
I tried to update my MikTeX installation today and received the error message below: ---------------------------------------------------------------------------- Msg: "The operation could not be completed because a required file failed verification." Details: package="miktex-curl-bin-x64-2.9", arhiveFile="C:\Users\garci\AppData\Local\Temp\mik98A4.tmp", expectedMD5="4c0e3bd72a090ffc73d50c407beb5267", actualMD5="52c53acc3e808374e618404f50e0f55c" More information: GENERAL MIKTEX INFORMATION ReportDate: 2021-03-14 15:59:50 CurrentVersion: 21.2 SetupDate: 2020-06-15 15:25:00 SetupVersion: 2.9 Configuration: Regular GitInfo: 7a7e645 / 2021-02-20 10:38:14 OS: Windows 10 Pro, 64-bit, build 19042 SharedSetup: yes LinkTargetDirectory: C:\Program Files\MiKTeX 2.9\miktex\bin\x64 PathOkay: yes LastUpdateCheckAdmin: 2021-03-14 15:58:44 LastUpdateAdmin: 2021-03-11 09:24:10 LastUpdateDbAdmin: 2021-03-14 15:58:38 SystemAdmin: yes RootPrivileges: yes AdminMode: yes Root0: C:\ProgramData\MiKTeX\2.9 Root1: C:\Program Files\MiKTeX 2.9 CommonInstall: C:\Program Files\MiKTeX 2.9 CommonConfig: C:\ProgramData\MiKTeX\2.9 CommonData: C:\ProgramData\MiKTeX\2.9 Invokers: ---------------------------------------------------------------------------- Any help? Thanks Ariovaldo |
From: Evan C. <eva...@gm...> - 2021-03-11 15:08:03
|
Suppose I've create a format file, which I'll call mybook.fmt. How can I make it 'permanently available' for my MikTeX install? I know there a tab in the console for 'formats', but this doesn't quite look like what I need. I don't need to 'build' (compile) the .fmt file, I simply need to put it somewhere to make it available? I've found a few MikTeX docs that seem to indicate that MikTeX puts formats in c:\ProgramData\MikTeX 2.9, but I've done a 'for me only' install -- I have a MikTeX folder on the desktop for my account, into which I've installed MikTeX. To that end, there is no c:\ProgramData\MikTex 2.9 folder on my machine. So, is there a way I can make the .fmt files I've created permanently available ('in the path') for my local, user-only install? I suppose I could create a local format folder and add it to TEXMF root directories (I did that once before with a .sty file I tweaked up), but is that correct for .fmt files? Thanks in advance... |
From: Ralf H. <ral...@ya...> - 2021-02-12 17:51:13
|
Ulrike Fischer schrieb am 12.02.2021 um 11:22: > >> ... >> ! LaTeX Error: Encoding scheme `PU' unknown. > > that will be resolved in the next update (version 7.00j) which is > already on ctan. For now move settings like pdfauthor=XXX from the > hyperref options to \hypersetup. See also > github.com/latex3/hyperref/issues/172 Thank you for the helpful answer and the new version. I had not found the issue at github.com/latex3/hyperref/issues/172. Regards Ralf |
From: Ulrike F. <ne...@ni...> - 2021-02-12 10:23:03
|
Am Thu, 11 Feb 2021 22:19:56 +0100 schrieb Ralf Heckmann via MiKTeX-Users: > After the latest update (which included an update of the package > hyperref) without any change to a (large) document I get a compiling error: > > > ! LaTeX Error: Encoding scheme `PU' unknown. that will be resolved in the next update (version 7.00j) which is already on ctan. For now move settings like pdfauthor=XXX from the hyperref options to \hypersetup. See also github.com/latex3/hyperref/issues/172 -- Ulrike Fischer http://www.troubleshooting-tex.de/ |
From: Ralf H. <ral...@ya...> - 2021-02-11 21:50:39
|
After the latest update (which included an update of the package hyperref) without any change to a (large) document I get a compiling error: ! LaTeX Error: Encoding scheme `PU' unknown. See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ... l.4058 \ProcessKeyvalOptions{Hyp} What can I do to get the document compiled again as it worked some two days before? Thanks in advance Ralf |
From: Aradenatorix V. A. <ar...@gm...> - 2021-01-26 02:55:49
|
If you're typing using babel or polyglossia with the polish option and the package inputenc with utf8 option you should be able to type the ł without troubles directly from your keyboard. If you could bring us an MWE would be easier to help you. Regards. |
From: Victor K. <vkr...@ra...> - 2021-01-24 08:38:43
|
Dear MikTex users, I expected that the \l command should produce the Polish ł (l with stroke). However the \l command produces just a blank and the usual l character. Last update two days ago. See also https://tex.stackexchange.com/questions/280116/tex-history-what-was-the-diagonal-dash-at-codepoint-32-in-cmr10-intended-for https://tex.stackexchange.com/questions/406179/how-to-type-the-letter-%C5%81 Sincerely Victor |
From: Jennifer H. <jjh...@on...> - 2020-10-31 10:24:26
|
This email jjh...@on... is now defunct please delete from your mailing list and replace with my new email jjh...@wo... and let me know that you have done so. Jennifer Harding > On 30 October 2020 at 12:39 mik...@li... wrote: > > > Send MiKTeX-Users mailing list submissions to > mik...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/miktex-users > or, via email, send a message with subject or body 'help' to > mik...@li... > > You can reach the person managing the list at > mik...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MiKTeX-Users digest..." > > > Today's Topics: > > 1. Re: MiKTeX-Users Digest, Vol 164, Issue 3 (Jennifer Harding) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 29 Oct 2020 15:54:29 +0000 (GMT) > From: Jennifer Harding <jjh...@on...> > To: mik...@li... > Subject: Re: [MiKTeX] MiKTeX-Users Digest, Vol 164, Issue 3 > Message-ID: <423...@ap...> > Content-Type: text/plain; charset=UTF-8 > > My email is on longer jjh...@on... but jjh...@wo.... Please note and email on my new email to let me know? you have done this. Thank you, Jennifer Harding > > On 27 October 2020 at 13:54 mik...@li... wrote: > > > > > > Send MiKTeX-Users mailing list submissions to > > mik...@li... > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.sourceforge.net/lists/listinfo/miktex-users > > or, via email, send a message with subject or body 'help' to > > mik...@li... > > > > You can reach the person managing the list at > > mik...@li... > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of MiKTeX-Users digest..." > > > > > > Today's Topics: > > > > 1. MikTeX with shared package repo on App-V (Michael Strack) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Tue, 27 Oct 2020 05:13:14 -0000 > > From: Michael Strack <mi...@st...> > > To: mik...@li... > > Subject: [MiKTeX] MikTeX with shared package repo on App-V > > Message-ID: <160...@st...> > > Content-Type: text/plain; charset="utf-8" > > > > Our organisation has a very restrictive computing environment. Users are not > > permitted to install their own software. Furthermore, we make heavy use of > > non-persistent virtual machines and virtualised applications (Win10, App-V), > > which of course makes software administration tricky. > > > > > > > > The utility which "virtualises" programs for App-V supposedly has a hard limit > > of 15k files, and a complete MikTeX installation exceeds this by some margin. > > > > > > > > I am trying to figure out how we might offload packages to a shared repository > > on our intranet, from which users can load or install as required. > > > > > > > > The first step is not so hard: I understand that the MikTeX Setup Utility > > [provides](https://miktex.org/howto/local-repository) this functionality. > > > > > > > > The second is rather more difficult. Users cannot install to the system > > partition (_i.e._ the C: drive), and in any case even if they could this would > > be ephemeral as the non-persistent virtual machines are destroyed and re- > > created each shutdown/boot. > > > > > > > > Users _do_ have a separate home drive to which they can permanently install > > files. Let's call it the H: drive. I was hoping to achieve something similar > > to what we do with the R language: have a corporate repository of packages > > which can be loaded directly into the RAM of the R session, or have users > > install a package to their H: drive and add this location to the PATH of the R > > session. > > > > > > > > I suppose the "Specifying Alternative Input Directories" section of the manual > > gives one way of specifying a non-default personal library installation > > location? Or is it the custom TEXMF directory that I should create? > > > > > > > > Also, some packages (such as "glossaries") rely on (non-TeX) scripts. Can the > > installation location of these be customised as well? > > > > > > > > Thanks for your time. > > > > > > > > ------------------------------ > > > > > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > MiKTeX-Users mailing list > > MiK...@li... > > https://lists.sourceforge.net/lists/listinfo/miktex-users > > > > > > ------------------------------ > > > > End of MiKTeX-Users Digest, Vol 164, Issue 3 > > ******************************************** > > > > ------------------------------ > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > MiKTeX-Users mailing list > MiK...@li... > https://lists.sourceforge.net/lists/listinfo/miktex-users > > > ------------------------------ > > End of MiKTeX-Users Digest, Vol 164, Issue 4 > ******************************************** |
From: Jennifer H. <jjh...@on...> - 2020-10-29 16:09:01
|
My email is on longer jjh...@on... but jjh...@wo.... Please note and email on my new email to let me know you have done this. Thank you, Jennifer Harding > On 27 October 2020 at 13:54 mik...@li... wrote: > > > Send MiKTeX-Users mailing list submissions to > mik...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/miktex-users > or, via email, send a message with subject or body 'help' to > mik...@li... > > You can reach the person managing the list at > mik...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MiKTeX-Users digest..." > > > Today's Topics: > > 1. MikTeX with shared package repo on App-V (Michael Strack) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 27 Oct 2020 05:13:14 -0000 > From: Michael Strack <mi...@st...> > To: mik...@li... > Subject: [MiKTeX] MikTeX with shared package repo on App-V > Message-ID: <160...@st...> > Content-Type: text/plain; charset="utf-8" > > Our organisation has a very restrictive computing environment. Users are not > permitted to install their own software. Furthermore, we make heavy use of > non-persistent virtual machines and virtualised applications (Win10, App-V), > which of course makes software administration tricky. > > > > The utility which "virtualises" programs for App-V supposedly has a hard limit > of 15k files, and a complete MikTeX installation exceeds this by some margin. > > > > I am trying to figure out how we might offload packages to a shared repository > on our intranet, from which users can load or install as required. > > > > The first step is not so hard: I understand that the MikTeX Setup Utility > [provides](https://miktex.org/howto/local-repository) this functionality. > > > > The second is rather more difficult. Users cannot install to the system > partition (_i.e._ the C: drive), and in any case even if they could this would > be ephemeral as the non-persistent virtual machines are destroyed and re- > created each shutdown/boot. > > > > Users _do_ have a separate home drive to which they can permanently install > files. Let's call it the H: drive. I was hoping to achieve something similar > to what we do with the R language: have a corporate repository of packages > which can be loaded directly into the RAM of the R session, or have users > install a package to their H: drive and add this location to the PATH of the R > session. > > > > I suppose the "Specifying Alternative Input Directories" section of the manual > gives one way of specifying a non-default personal library installation > location? Or is it the custom TEXMF directory that I should create? > > > > Also, some packages (such as "glossaries") rely on (non-TeX) scripts. Can the > installation location of these be customised as well? > > > > Thanks for your time. > > > > ------------------------------ > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > MiKTeX-Users mailing list > MiK...@li... > https://lists.sourceforge.net/lists/listinfo/miktex-users > > > ------------------------------ > > End of MiKTeX-Users Digest, Vol 164, Issue 3 > ******************************************** |
From: Michael S. <mi...@st...> - 2020-10-27 05:33:12
|
Our organisation has a very restrictive computing environment. Users are not permitted to install their own software. Furthermore, we make heavy use of non-persistent virtual machines and virtualised applications (Win10, App-V), which of course makes software administration tricky. The utility which "virtualises" programs for App-V supposedly has a hard limit of 15k files, and a complete MikTeX installation exceeds this by some margin. I am trying to figure out how we might offload packages to a shared repository on our intranet, from which users can load or install as required. The first step is not so hard: I understand that the MikTeX Setup Utility [provides](https://miktex.org/howto/local-repository) this functionality. The second is rather more difficult. Users cannot install to the system partition (_i.e._ the C: drive), and in any case even if they could this would be ephemeral as the non-persistent virtual machines are destroyed and re- created each shutdown/boot. Users _do_ have a separate home drive to which they can permanently install files. Let's call it the H: drive. I was hoping to achieve something similar to what we do with the R language: have a corporate repository of packages which can be loaded directly into the RAM of the R session, or have users install a package to their H: drive and add this location to the PATH of the R session. I suppose the "Specifying Alternative Input Directories" section of the manual gives one way of specifying a non-default personal library installation location? Or is it the custom TEXMF directory that I should create? Also, some packages (such as "glossaries") rely on (non-TeX) scripts. Can the installation location of these be customised as well? Thanks for your time. |
From: Vincent B. <vin...@ho...> - 2020-10-13 13:10:02
|
Finally, it seems that I have the problem again and it is connected to this that I am configuring the place where MiKTeX places the smylinks to the executables to a place different than the default. On MACOS the default place is /usr/local/bin. Because I am using TeXDist in order to have several TeX distros on the same machine I reconfigured this place to /Library/TeX/Distributions/MiKTeX.texdist/Contents/texbin using the MiKTeX console / Administrator / Settings / Directories / Link target directory. V. ________________________________ De : Vincent Belaïche <vin...@ho...> Envoyé : vendredi 9 octobre 2020 22:19 À : MikTeX user group list <mik...@li...> Objet : RE: Problems with kpsewhich on MACOS Just to say that I have solved my problem as follows: 1) open the MiKTeX console 2) select administrator mode 3) go to cleanup pannel (select it on the left choice list) 4) select restore « factory default » Now things work again as expected, but the sad news is that I had to reinstall a few packages… Vincent. ________________________________ De : Vincent Belaïche Envoyé : vendredi 9 octobre 2020 17:45 À : MikTeX user group list <mik...@li...> Objet : Problems with kpsewhich on MACOS Hello, I have MiKTeX installed on MACOS, and it seems that for some reason kpsewhich got broken, so the whole install is broken indeed. I already had that sort of problem, the root cause it that MiKTeX uses some dynamic library with a name that is versionned instead of asking for the latest version, so when there is a system update sometimes it happens that MiKTeX gets broken. So if I type kpsewhich I get: ERROR: collate_byname<char>::collate_byname failed to construct for Sorry, but kpsewhich did not succeed. And if I try to compile a document with content \documentclass{minimal}\begin{document}Hello.\end{document}, then I get: ERROR: collate_byname<char>::collate_byname failed to construct for Sorry, but pdflatex did not succeed. libc++abi.dylib: terminating with uncaught exception of type MiKTeX::Core::MiKTeXException: MiKTeX encountered an internal error. Abort trap: 6 |
From: Alex D. <de...@fe...> - 2020-10-06 17:03:47
|
I have just noticed a strange behavior of one of the auto-completion macros. I have a label "eq.|S|" (without quotes). When I type \eqref{ and pop-up the list of labels to choose this one, I get "\eqref{eq.S|}|" inserted! |
From: Uzoqboy U. <uz...@ma...> - 2020-07-09 12:22:01
|
I have been working on my paper with at TexStudio. It was working well and compiling without any error, but, now I can not compile it, and showing an error message « Sorry, but pdflatex.exe did not succeed. The log file hopefully contains the information to get MiKTeX going again: C pdflatex: major issue: So far, you have not checked for MiKTeX updates. Process exited with error(s) » Please help me to fix this issue. With regards, Uzoqboy Ummatov |
From: Ulrike F. <ne...@ni...> - 2020-06-16 13:56:39
|
Am Mon, 15 Jun 2020 21:40:28 +0300 schrieb Igor Ya. Spectorsky: > > So, the question: is it possible to include several (2 in my case) > hyphenation tables in the format file, and choose one of them in the > preamble of paper? See the hyphsubst package. -- Ulrike Fischer http://www.troubleshooting-tex.de/ |
From: Paul T. <pat...@gm...> - 2020-06-16 02:02:15
|
Why don't you set up 2 format files, and put 1 hyphenation table in the first, Hyphenation table 2 in the second. Then you pick the format file that is most appropriate. Paul A. Thompson On Mon, Jun 15, 2020 at 1:40 PM Igor Ya. Spectorsky <i.s...@gm...> wrote: > Hello, > > I have a lot of LaTeX papers in Ukrainian, some of them prepared in DOS > code page, other ones prepared in Unicode. For DOS code page the > following encodings are used: > > \usepackage[LCY]{fontenc} > \usepackage[cp866nav]{inputenc} > \usepackage[ukrainian]{babel} > > For Uncicode, the following ones are used: > > \usepackage[T2A]{fontenc} > \usepackage[utf8]{inputenc} > \usepackage[ukrainian]{babel} > > It works well, but I need to slightly modify hyphenation file > ukrhyphen.tex and rebuild formats anytime when switch to work with paper > with another codepage. Surprisingly: babel allows to choose language > with hyphenation table and even to switch to other language inside > paper, but I cannot find the feature to have several hyphenation tables > within one language (and choose one of them) . > > So, the question: is it possible to include several (2 in my case) > hyphenation tables in the format file, and choose one of them in the > preamble of paper? > > Thanks in advance, > > Igor Spectorsky, > Kyiv, Ukraine > > > > _______________________________________________ > Q: How can I leave the mailing list? > A: See https://miktex.org/faq/how-can-i-leave-the-mailing-list > |
From: Igor Y. S. <i.s...@gm...> - 2020-06-15 18:40:38
|
Hello, I have a lot of LaTeX papers in Ukrainian, some of them prepared in DOS code page, other ones prepared in Unicode. For DOS code page the following encodings are used: \usepackage[LCY]{fontenc} \usepackage[cp866nav]{inputenc} \usepackage[ukrainian]{babel} For Uncicode, the following ones are used: \usepackage[T2A]{fontenc} \usepackage[utf8]{inputenc} \usepackage[ukrainian]{babel} It works well, but I need to slightly modify hyphenation file ukrhyphen.tex and rebuild formats anytime when switch to work with paper with another codepage. Surprisingly: babel allows to choose language with hyphenation table and even to switch to other language inside paper, but I cannot find the feature to have several hyphenation tables within one language (and choose one of them) . So, the question: is it possible to include several (2 in my case) hyphenation tables in the format file, and choose one of them in the preamble of paper? Thanks in advance, Igor Spectorsky, Kyiv, Ukraine |
From: Gerard E. S. <ger...@ou...> - 2020-06-07 21:41:39
|
On Sun, 07 Jun 2020 13:42:53 -0700, SGalmes stated: >> >> >> Seems that you do not have permissions for `C:\Program Files`. >> Choose a per-user installation. > >Thnak you very much, though it seems the reason was that Program Files >already contained an old MiKTeK 2.9 folder. That is a problem I have experienced several times before when reinstalling MiKTeX. From experience, I have found that I need to sign in as an 'administrator' and delete every last ounce of MiKTeX before attempting a fresh installation. Obviously, I do a reboot and sign in as my regular user before the reinstall. -- Gerard |
From: Ariovaldo V G. <gar...@gm...> - 2020-05-18 12:24:15
|
Dear All, I tried to install miktex on Ubuntu 18.04 (32 bits) following the steps in the tutorial at https://miktex.org/howto/install-miktex-unx When I give the command: "sudo apt-get update" I got the following warning: "Skipping acquire of configured file 'universe / binary-i386 / Packages' as repository 'http://miktex.org/download/ubuntu bionic InRelease' doesn't support architecture 'i386'" And so I couldn't install miktex Does anyone know if there is a 32-bit version of miktex for Ubuntu Thank you Ariovaldo |
From: Ulrike F. <li...@ni...> - 2020-04-25 14:05:12
|
Am Sat, 25 Apr 2020 16:01:48 +0200 schrieb Ulrike Fischer: > Am Sat, 5 Oct 2019 12:45:40 +0000 (UTC) schrieb Jeff Miller via > MiKTeX-Users: > >> After a substantial MikTex update today (about a week since my last update), > >> LaTeX2e <2018-12-01> > > This format is clearly too old. > > Try to recreate the formats in the miktex console -- probably user > mode. Sorry I didn't see that the question was older. -- Ulrike Fischer https://www.troubleshooting-tex.de/ |
From: Ulrike F. <li...@ni...> - 2020-04-25 14:02:02
|
Am Sat, 5 Oct 2019 12:45:40 +0000 (UTC) schrieb Jeff Miller via MiKTeX-Users: > After a substantial MikTex update today (about a week since my last update), > LaTeX2e <2018-12-01> This format is clearly too old. Try to recreate the formats in the miktex console -- probably user mode. -- Ulrike Fischer https://www.troubleshooting-tex.de/ |
From: Evan C. <eva...@gm...> - 2020-04-24 16:51:45
|
I've been using MikTeX on my Mint-based Linux machines for several months now, and really enjoy the fact that (i) it works, and (ii) well-enough that I don't have to fuss with TeXlive and the silly way it handles package management, ever again. ;-) However, while fooling and tweaking with various things, I managed to 'break' the MikTeX install on one of my Linux machines, so much so that I couldn't even uninstall it. So, in case anyone else runs into this problem, here is how do do a full, complete uninstall of MikTeX on Ubuntu-derivatives like Mint. [Worked for me - your results might vary.] sudo mv /var/lib/dpkg/info/miktex.* /tmp/ sudo dpkg --remove --force-remove-reinstreq miktex You *might* also need to do a final cleanup running the following: sudo apt-get purge miktex These steps work for me. || |
From: George N. W. I. <gn...@gm...> - 2020-01-27 17:38:47
|
On Mon, 27 Jan 2020 at 06:18, Virgil Stokes <vs...@it...> wrote: > Thanks again George, > > On 2020-01-27 00:26, George N. White III wrote: > > > > On Sun, 26 Jan 2020 at 18:18, Virgil Stokes <vs...@it...> wrote: > >> A better question I hope :-P >> -------- Forwarded Message -------- >> Subject: Installation of my own *.cls or *.sty file -- How? >> Date: Sun, 26 Jan 2020 22:08:37 +0100 >> From: Virgil Stokes <vs...@it...> <vs...@it...> >> To: mik...@li... >> <mik...@li...> <mik...@li...> >> >> I recently submitted an email with subject: Installation of my own >> Package -- How? >> Before submitting this new email, I tried both suggestions by Paul >> Thompson and George N. White III. Unfortunately, the links and suggestions >> given were not applicable to my problem it seems. I also tried many other >> approaches and none of these solved my problem. I now believe that I asked >> the wrong question.:-[ >> >> Perhaps I need to go into more detail on my installation of MikTeX 2.9. >> >> Here is the complete path to my LaTeX packages: C:\Program Files\MiKTeX >> 2.9\tex\latex >> I would like to add the following *.cls file to my MikTeX 2.9 >> installation: elsarticleC.cls >> >> I have attached an image of my miktex-console_admin because some of the >> suggestions given just do not apply as you can see from the attached images. >> I would appreciate a 2nd look by Paul and George. >> > > If you select the "Settings" panel and then the "Directories" tab, you > should see a link "Which is the best directory to keep my .sty files?" > This link shows you how to create the TDS structure for a LaTeX class. > You need to do this is a location outside the MiKTeX package directories. > > Yes, I have looked at this when trying different methods: > > Example (Mac/Linux): > > 1. Create a new TEXMF root: mkdir ~/mytexmf > 2. Create a sub directory: mkdir -p ~/mytexmf/tex/latex/mystuff > 3. Copy your .cls and/or .sty files to ~/mytexmf/tex/latex/mystuff > 4. Register the TEXMF root directory ~/mytexmf > > But, I have windows 10 not Mac/Linux > The steps on Windows are the same, but the examples are for the bash command line (it is much easier to write documentation using text commands for the examples). You are expected to know how to create a folder/directory, then create the nested sub-directories inside that, copy files, and use the MiKTeX Utility to register your new TEXMF root. Note that the "~" character, is just a shorthand notation for the user's "home" directory. On Windows it is common to put a personal user's own Documents folder. If you have trouble with one of these steps you need to provide more details of the step giving you problems. -- George N. White III |
From: Paul T. <pat...@gm...> - 2020-01-27 01:06:57
|
And the reason that you wish to use an external directory is simple: If you delete the main MikTeX tree when you wish to add a new version, you don't want to delete private files. As I noted earlier, you need to ensure that you don't save system files on your private tree. They are brought in first. If they are out of date, you can get version inconsistency. Paul A. Thompson On Sun, Jan 26, 2020 at 5:26 PM George N. White III <gn...@gm...> wrote: > > > On Sun, 26 Jan 2020 at 18:18, Virgil Stokes <vs...@it...> wrote: > >> A better question I hope :-P >> -------- Forwarded Message -------- >> Subject: Installation of my own *.cls or *.sty file -- How? >> Date: Sun, 26 Jan 2020 22:08:37 +0100 >> From: Virgil Stokes <vs...@it...> <vs...@it...> >> To: mik...@li... >> <mik...@li...> <mik...@li...> >> >> I recently submitted an email with subject: Installation of my own >> Package -- How? >> Before submitting this new email, I tried both suggestions by Paul >> Thompson and George N. White III. Unfortunately, the links and suggestions >> given were not applicable to my problem it seems. I also tried many other >> approaches and none of these solved my problem. I now believe that I asked >> the wrong question.:-[ >> >> Perhaps I need to go into more detail on my installation of MikTeX 2.9. >> >> Here is the complete path to my LaTeX packages: C:\Program Files\MiKTeX >> 2.9\tex\latex >> I would like to add the following *.cls file to my MikTeX 2.9 >> installation: elsarticleC.cls >> >> I have attached an image of my miktex-console_admin because some of the >> suggestions given just do not apply as you can see from the attached images. >> I would appreciate a 2nd look by Paul and George. >> > > If you select the "Settings" panel and then the "Directories" tab, you > should see a link "Which is the best directory to keep my .sty files?" > This link shows you how to create the TDS structure for a LaTeX class. > You need to do this is a location outside the MiKTeX package directories. > > >> >> Note, I had no problem with handling this with a previous (older) version >> of MikTeX with a different console. >> > > At one time it may have been possible to add a file to one of the MiKTeX > directories, but it has always been > recommended that user files go in a new TDS tree outside the MiKTeX > directories. > > -- > George N. White III > > |
From: George N. W. I. <gn...@gm...> - 2020-01-26 23:26:21
|
On Sun, 26 Jan 2020 at 18:18, Virgil Stokes <vs...@it...> wrote: > A better question I hope :-P > -------- Forwarded Message -------- > Subject: Installation of my own *.cls or *.sty file -- How? > Date: Sun, 26 Jan 2020 22:08:37 +0100 > From: Virgil Stokes <vs...@it...> <vs...@it...> > To: mik...@li... > <mik...@li...> <mik...@li...> > > I recently submitted an email with subject: Installation of my own > Package -- How? > Before submitting this new email, I tried both suggestions by Paul > Thompson and George N. White III. Unfortunately, the links and suggestions > given were not applicable to my problem it seems. I also tried many other > approaches and none of these solved my problem. I now believe that I asked > the wrong question.:-[ > > Perhaps I need to go into more detail on my installation of MikTeX 2.9. > > Here is the complete path to my LaTeX packages: C:\Program Files\MiKTeX > 2.9\tex\latex > I would like to add the following *.cls file to my MikTeX 2.9 > installation: elsarticleC.cls > > I have attached an image of my miktex-console_admin because some of the > suggestions given just do not apply as you can see from the attached images. > I would appreciate a 2nd look by Paul and George. > If you select the "Settings" panel and then the "Directories" tab, you should see a link "Which is the best directory to keep my .sty files?" This link shows you how to create the TDS structure for a LaTeX class. You need to do this is a location outside the MiKTeX package directories. > > Note, I had no problem with handling this with a previous (older) version > of MikTeX with a different console. > At one time it may have been possible to add a file to one of the MiKTeX directories, but it has always been recommended that user files go in a new TDS tree outside the MiKTeX directories. -- George N. White III |