Miktex latex distribution

Содержание:

2.9.7300 — 2020-02-17
2.9.7440 — 2020-05-17
- Breaking changes
  - Windows 8.3 file names
  - Package database signing
- Unrestricted shell escape commands and elevated privileges
Sponsors
В-третьих, выберите и настройте редактор
Conclusion
Copying conditions for MiKTeX
- Guidelines for redistribution
- References
21.6.28 — 2021-06-28
- Breaking changes
  - Common TEXMF root directories in a private (current user) installation
Description
Maintenance
- - Mac
Установка
- Установка PSCyr
2.9.6500 — 2017-11-04
- Upgraded libraries
- Bug fixes
Installation
- directories should be distinct
- Switching between MiKTeX and TeX Live
Description
Options

2.9.7300 — 2020-02-17

Group-delimited \input argument

MiKTeX adopted the forthcoming TL 2020 \input enhancement which allows
you to specify file with spaces in the name:

To quote Karl Berry:

Upgraded programs

asymptote 2.62
autosp 2020-02-06
dvipdfmx 20200116
dvipng 1.17
dvips 2020.1
dvisvgm 2.8.2
LuaTeX 1.12.0
pdftex 1.40.21
pmxab 2.9.4

Fixed issues

: Admin mode required but not accessible
: miktexsetup fails — how to advance?
: Increase font_mem_size upper limit
: GSF2PK failed on postscript font
: language patterns in the format can not be changed manually
: Problems with the oberdiek package
: Create «fc-cache.exe» as alias
: Cannot build new format
: miktex-makepk fails if the transcript file does not exist
: Clicking Close button vs pressing Esc key upon finished package installation
: dvipng 1.16 with pk fonts error on Win32
: BibTeX max_glob_strs = 10 or 20 much too small; could we have 100, please?

2.9.7440 — 2020-05-17

Breaking changes

Windows 8.3 file names

Latex 5.0.2 русская версия для windows 10

In the past, it was possible to specify Windows 8.3 file names (aka
short file names) when invoking a TeX engine. As of 2.9.7440, this is
not supported anymore.

Impact: The following use case is broken:

where is the 8.3 variant of the long file name .

Package database signing

In the past, package database signing was optional. As of MiKTeX
2.9.7440, it is required that MiKTeX package database files are
provided with a valid signature.

Reason: In order to support custom remote package repositories (see
Allow local http
mirrors), it must be
ensured that the contents of the custom package repository is
unmodified.

Impact: Users will receive an error message if they visit an outdated
(no signature) or modified (tampered database) package repository.

Unrestricted shell escape commands and elevated privileges

As of MiKTeX 2.9.7440, it is possible to prevent the execution of
unrestricted shell escape commands when a program is running with
elevated privileges:

This prevents the following use case:

where contains:

For more information and discussion, visit the issue page at GitHub:

533: Unrestricted shell escape commands and elevated privileges

: Luatex cannot find input file when using texify on windows
: Empty file error when trying to complete the setup on a Mac
: Long file name support
: Kerberos Proxy support
: Make MiKTeX Console usable for keyboard only users
: Cannot install on Fedora 32
: Ubuntu 20.04 Repositories
: Calling external commands with quotes in path via shell on Windows
: Change BibTeX «I couldn’t open database file» message to include double extension

В-третьих, выберите и настройте редактор

Конвертирование cdr-файла в jpg онлайн

Прочитав некоторое время, я наконец решил выбрать TeXstudio.

Теперь начните настраивать TeXstudio :

1) Скачать TeXstudio

Адрес для скачивания:http://texstudio.sourceforge.net/

Рисунок 1 Домашняя страница загрузки TeXstudio

2) Найти руководство пользователя TeXstudio

3) Установите MikTeX

TeXstudio — это просто редактор, который не включает среду LaTeX, поэтому вам необходимоСкачать MikTeXИ установить (руководство по установке находится по этой ссылке) .

4) Установите TeXstudio

Откройте ранее загруженный установочный пакет TeXstudio «texstudio-2.12.10-win-qt5.exe» и установите его по умолчанию.

Рисунок 2 После завершения установки соответствующий значок будет отображаться в строке меню в левом нижнем углу win10

5) Пример демонстрации

После установки MikTeX и TeXstudio создайте новый файл test.tex.

Входные данные:

Нажмите «F5» или двойную стрелку в верхней строке меню, чтобы отобразить документ, соответствующий коду.

Рисунок 3 Скомпилируйте и выполните код

6) Поддержка китайского

Внимательные люди видят, что китайцы в 5) не могут отображаться. Есть два способа отображения китайского (я предпочитаю первый)

1. Во-первых, в верхней строке меню опции-настройки TeXstudio-build. Измените компилятор по умолчанию на XeLaTeX. Затем вставьте в код текстового файла Наконец, нажмите F5, чтобы увидеть успешное отображение китайского языка.

(Примечание: я получил ошибку во время первой компиляции и выполнения F5, сообщение было «expl3.sty is not found». Я проверил и не нашел результатов, и, наконец, я перекомпилировал и выполнил его снова, без проблем .)

Рисунок 4 Способ 1

2. Во-первых, в верхней строке меню опции-настройки TeXstudio-build. Измените компилятор по умолчанию на XeLaTeX. Затем вставьте в код текстового файла Наконец, нажмите F5, чтобы увидеть успешное отображение китайского языка.

Рисунок 5 Метод 2

Conclusion

MiKTeX is a powerful beast. It will definitely make your LaTeX experience — for now on Windows only, but Linux
coming fast — more productive, more pleasant, more flexible, and more powerful. You will learn about additional
features and options of the superb LaTeX language/system, thus making your papers look and behave more smartly.
You will learn about new tools and utilities, new syntax, becoming an ever greater expert in working the right
way with documents.

Today, I hope you’ve learned something new. The striking similarity between the MiKTeX package manager and a
typical Linux package manager, how to search for content, how to setup network connections, and how to install
individual packages is staggering. Now, all that is left for you is to power up LaTeX and start writing cool
stuff. Even if the contents are not that great, they will still look brilliant, you’ll be crowned a geek and
everyone will fear you. It’s a win-win situation in every aspect.

Cheers.

Copying conditions for MiKTeX

To the best of our knowledge, all software in the MiKTeX distribution
is freely redistributable (libre, that is, not necessarily gratis),
within the Free Software Foundation’s definition and the Debian Free
Software Guidelines. Where the two conflict, we generally follow the
FSF. If you find any non-free files included, please contact us
(reference given at the end).

That said, MiKTeX has neither a single copyright holder nor a single
license covering its entire contents, since it is a collection of many
independent packages. Therefore, you may copy, modify, and/or
redistribute software from MiKTeX only if you comply with the
requirements placed thereon by the owners of the respective packages.

To most easily learn these requirements, we suggest checking the
MiKTeX package catalogue (reference given at the end). Of course the
legal statements within the packages themselves are the final
authority.

Guidelines for redistribution

In general, you may redistribute MiKTeX, with or without modification,
for profit or not, according to the usual free software tenets. Here
are some general guidelines for doing this:

If you make any changes to the MiKTeX distribution or any package it
contains, besides complying with any licensing requirements, you
must prominently mention such changes in your modified distribution
so that users do not take your work for ours, and know to contact
you, not us, in case of questions or problems.
Especially (but not necessarily) if changes or additions are made,
we recommend a clearly different title, such as “Your work, based on
MiKTeX x.y.zzzz”, where x.y.zzzz is the Git tag of the MiKTeX
version you are using. This credits both our work and yours.
You absolutely may not place your own copyright on the entire
distribution, since it is not your work. Statements such as “all
rights reserved” and “may not be reproduced” are especially
reprehensible, since they are antithetical to the free software
principles under which MiKTeX is produced.
You may use any cover or media label designs that you wish. Such
packaging and marketing details are not covered by any MiKTeX
license.
Finally, we make the following requests (not legal requirements):

a. Acknowledging that the MiKTeX distribution is developed as a
joint effort by all TeX user groups, and encouraging the
user/reader to join their user group of choice, as listed on the
web page http://www.tug.org/usergroups.html.

b. Referencing the MiKTeX project page: https://miktex.org/.

Such information may be placed on the label of your media, your
cover, and/or in accompanying text (for instance, in the
acknowledgements section of a book).

Finally, although it is certainly not a requirement, we’d like to
invite any redistributors to make a donation to the project, whether
cash or in-kind, for example via
https://miktex.org/giveback. Thanks.

References

MiKTeX package catalogue: https://miktex.org/packages/

Copying conditions for TeX Live: http://tug.org/texlive/LICENSE.TL

The FSF’s free software definition: https://www.gnu.org/philosophy/free-sw.html

Debian Free Software Guidelines: https://www.debian.org/intro/free

FSF commentary on existing licenses: https://www.gnu.org/licenses/license-list.html

21.6.28 — 2021-06-28

Breaking changes

Common TEXMF root directories in a private (current user) installation

In the past, common TEXMF root directories (e.g., )
were in the input search path, even if MiKTeX was installed for the current user only.
As of 21.6.28, common TEXMF root directories are excluded from the input search path.

This should have no impact for most users, because these directories usually
do not exist when MiKTeX is installed for the current user.

: When a package have been uninstalled, its directories are not removed
: Documentation not found
: miktex update causes issues “go to source/pdf” in TeXstudio

Description

This man page is an adaption of the corresponding TeX Live man page.

Run the TeX typesetter on ,
usually creating
. If the file
argument has no extension, will be appended
to it. Instead of a filename, a set of TeX commands can be given,
the first of which must start with a backslash. With a
argument TeX uses a different set of
precompiled commands, contained in
; it is
usually better to use the
option
instead.

TeX formats the interspersed text and commands contained in
the named files and outputs a typesetter independent file (called
DVI, which is short for DeVice Independent). TeX’s capabilities
and language are described in The TeXbook.
TeX is normally used with a large body of precompiled macros, and
there are several specific formatting systems, such as LaTeX, which
require the support of several macro files.

This version of TeX looks at its command-line to see what name
it was called under. Both initex and virtex are links to the
miktex-tex executable. When called as initex (or when the
option is given) it can be used to
precompile macros into a file. When called
as virtex it will use the plain format. When called under any other
name, TeX will use that name as the name of the format to use. For
example, when called as miktex-tex the tex
format is used, which is identical to the plain format. The commands
defined by the plain format are documented in The
TeXbook. Other formats that are often available include
latex and amstex.

The non-option command line argiments to the TeX program are
passed to it as the first input line. (But it is often easier to type
extended arguments as the first input line, since shells tend to
gobble up or misinterpret TeX’s favorite symbols, like backslashes,
unless you quote them.) As described in The
TeXbook, that first line should begin with a file name,
a \controlsequence, or a
&.

The normal usage is to say to start processing .
The name paper will be the
“jobname”, and is used in forming output file names. If
TeX doesn’t get a file name in the first line, the job name is
. When looking for a file, TeX looks for
the name with and without the default extension
() appended, unless the name already contains
that extension. If paper is the “jobname”, a log of
error messages, with rather more detail than normally appears on the
screen, will appear in , and the output
file will be in .

This version of TeX will look in the first line of the file
to see if it begins with the magic
sequence . If the first line begins with
, then
TeX will use the named format and transation table
to process the source file. Either
the format name or the specification
may be omitted, but not both. This overrides the format selection
based on the name by which the program is invoked. The
option or the configuration value
controls whether this behaviour is enabled.

The response to TeX’s error-recovery
prompt causes the default editor to start up at the current line of
the current file. The configuration value can be used to change the
editor used. It may contain a string with
indicating where the file name goes and
indicating where the decimal line number (if any) goes. For example,
an string for
emacs can be set with the command

Maintenance

You can use MiKTeX Console to get the latest package updates.

If you want to install your own files, then you should copy the files into
the directory relative to a new TEXMF root directory.

Example (Mac/Linux):

Create a new TEXMF root:
Create a sub directory:
Copy your and/or files to
Register the TEXMF root directory

The last step can be carried out in MiKTeX Console.

You can create a scheduled a task (cron job) which uses the setup utility to manage a local package repository. See this article, for the details.

New MiKTeX binaries for Mac and Linux will be made available from time to time (say, 6 times a year).

Mac

If a new disk image () is available, you can use it to reinstall the executables. Your MiKTeX configuration will not be affected.

Установка

Порядок установки:

Ghostscript (и GSview);
MiKTex;
PSCyr;
WinEdt;
MetafileToEPSConverter.

Все приложения и пакеты устанавливаются стандартно, за исключением шрифтов PSCyr.

Установка PSCyr

pscyr-0.4-beta9exp2-tex.tar.gz;
pscyr-0.4-beta9exp2-type1.tar.gz.

Нужно распаковать оба в один каталог, после чего скопировать содержимое каталога по пути, где установлен MiKTeX, сохраняя структуру папок.

Запустить перейти по пути установленного MiKTeX, в каталог с его утилитами, например .

Ниже перечислены требуемые действия:

выполнить команду:

initexmf --edit-config-file dvips

и ввести в открывшийся текстовый файл:

p +pscyr.map

выполнить команду:

initexmf --edit-config-file pdftex

и ввести в открывшийся текстовый файл:

+pscyr.map

выполнить команду:

initexmf --edit-config-file updmap

и ввести в открывшийся текстовый файл:

Map pscyr.map

выполнить команду:

updmap

и дождаться окончания её выполнения.

выполнить команду:

initexmf --edit-config-file dvipdfm

и ввести в открывшийся текстовый файл:

f pscyr2.map

выполнить команду:

initexmf -u

и дождаться окончания её выполнения.

В конце, после ввода и выполнения всех перечисленных команд, выглядеть это будет примерно так:

Теперь нужно запустить приложение конфигурации MiKTeX , находящееся в том же каталоге, и нажать кнопку Refresh FNDB.

После чего приложение можно закрывать.

Последнее, что надо сделать (в командной строке, находясь всё в том же каталоге), это выполнить команду:

mkfntmap

После этого шрифты PSCyr установлены и MiKTeX настроен на работу с ними.

2.9.6500 — 2017-11-04

Upgraded libraries

fontconfig 2.12.6
FreeType 2.8.1
HarfBuzz 1.6.3
ICU 60.1
libcurl 7.56.1
LibGD 2.2.5
libpng 1.6.34
Poppler 0.60.1
Qt 5.9.2

Bug fixes

: with options supplied as to XeLaTeX results in error
: Package manager «Miktex encountered an internal error»
: option —user-install of MiKTeX setup utility is ignored
: miktex is noticably slower than texlive
: Unknown filter «JPXDecode» Syntax Error
: xetex can’t input files with BOM anymore
: shell commands are not executed correctly
: Problem with \pdfresettimer & \pdfelapsedtime
: Package installation fails as normal user account

Installation

MiKTeX runs natively on Windows, macOS and selected Linux distributions.
Please check this KB article, for detailed information.

A Docker image is also available. This allows you to run MiKTeX on any computer that supports Docker.

It is recommended that you download the Basic MiKTeX Installer.
This allows you set up a basic MiKTeX installation.
Please see this tutorial.

You can download the Basic MiKTeX installer here.

MiKTeX is distributed as a macOS disk image. You can read the tutorial, to learn more.

The disk image can be downloaded here.

MiKTeX is available for selected Linux distributions.
Please read the tutorial, for more information.

You can install all packages which are not currently installed:

start
click
sort the list view by column to make the following step easy
select all packages which are not installed
click the add button to start the installation

MiKTeX and TeX Live can be installed in parallel if you observe the following.

directories should be distinct

MiKTeX and TeX Live shouldn’t share the same directories. On Windows, this is usually not an issue.

On Mac/Linux, you can run this test before installing MiKTeX:

Switching between MiKTeX and TeX Live

You have to adjust the environment variable in order to switch between MiKTeX and TeX Live.
Alternatively, you can use absolute path names.

On Windows you can use the standalone version of the MiKTeX Setup Utility:

Visit the download page page to get the MiKTeX Setup Utility for Windows.

On a Mac, you simply mount the disk image file:

On Linux, the system package manager tools are command-line oriented anyway.

It is possible to remove MiKTeX from your computer using the command line. Open a command prompt window as administrator and execute these commands:

Description

This man page is an adaption of the corresponding TeX Live man page.

METAFONT reads the program in the specified files and outputs
font rasters (in GF format) and font metrics (in
TFM format). The METAFONT language is described
in The METAFONTbook.

Like TeX, METAFONT is normally used with a large body of
precompiled macros, and font generation in particular requires the
support of several macro files. This version of METAFONT looks at
its command line to see what name it was called under. Both inimf
and virmf are links to the miktex-mf executable. When called as
inimf (or when the option is given) it
can be used to precompile macros into a
file. When called as virmf it will use the
plain base. When called under any other name,
METAFONT will use that name as the name of the base to use. For
example, when called as miktex-mf the mf base is
used, which is identical to the plain base.
Other bases than plain are rarely used.

The commands given on the command line to the METAFONT program
are passed to it as the first input line. (But it is often easier to
type extended arguments as the first input line, since shells tend to
gobble up or misinterpret METAFONT’s favorite symbols, like
semicolons, unless you quote them.) As described in The
METAFONTbook, that first line should begin with a
filename, a \controlsequence, or a
.

The normal usage is to say to start processing
. (Or you can
just say miktex-mf and give the other stuff on the next line.) Other
control sequences, such as (for
silent operation) can also appear. The name
will be the “jobname”,
and is used in forming output file names. If METAFONT doesn’t get a
file name in the first line, the job name is
. The default extension,
, can be overridden by specifying an extension
explicitly.

A log of error messages goes into the file
. The
output files are
and
,
where depends on the resolution and
magnification of the font. The mode in this example is shown
generically as , a symbolic term
for which the name of an actual device or, most commonly, the name
(see below) must be substituted. If
the mode is not specified or is not valid, METAFONT will default to
proof mode which produces large character images for use in font
design and refinement. Proof mode can be recognized by the suffix
after the job name. Examples of proof
mode output can be found in Computer Modern
Typefaces (VolumeE of Computers and
Typesetting). The system of magsteps is
identical to the system used by TeX, with values generally in the
range 0.5, 1.0, 2.0, 3.0, 4.0 and 5.0.

Magnification can also be specified not as a magstep but as an
arbitrary value, such as 1.315, to create special character
sizes.

Before font production can begin, it is necessary to set up the
appropriate base files. The minimum set of components for font
production for a given printengine is the
macro file and the local mode_def file. The macros in
can be studied in an appendix to
The METAFONTbook; they were developed by
DonaldE. Knuth, and this file should never be altered except
when it is officially upgraded. Each mode_def specification helps adapt fonts to a
particular printengine. The local ones in use on this

computer should be in .

The response to METAFONT’s
error-recovery prompt causes the default editor to start up at the
current line of the current file. The configuration value can be used to change the
editor used. It may contain a string with
indicating where the file name goes and
indicating where the decimal line number (if any) goes. For example,
an string for
emacs can be set with the command

Options

When the LuaTeX executable starts, it looks for the
commandline option. If there is no
option, the commandline is interpreted in a
similar fashion as in traditional pdfTeX. But if the option is
present, LuaTeX will enter an alternative mode of commandline
parsing in comparison to the standard MiKTeX programs. The presence
of makes most of other options unreliable,
because the Lua initialization file can disable path searching
and/or hook functions into various callbacks.

Load and execute a

Lua initialization script.

The following two options alter the executable behaviour:

Start LuaTeX as a Lua interpreter.

In this mode, it will set Lua’s to the found
script name, pushing preceding options in negative values and the rest
of the commandline in the positive values, just like the Lua
interpreter. LuaTeX will exit immediately after executing the
specified Lua script.

Start LuaTeX as a Lua byte compiler.

In this mode, LuaTeX is exactly like
from the standalone Lua distribution, except that it does not have
the switch, and that it accepts (but ignores) the
switch.

Then the regular options:

Pretend to be program ,
i.e., set program (and memory dump) name to
.

This may affect the search paths and other values used. Using this
option is equivalent to copying the program file to
and invoking
.

Set as the directory to
which

auxiliary files are written. Also look for input files in
first, before along the normal search
path.

Change the way, error messages are printed. The
alternate style looks like error messages from many compilers and is
easier to parse for some editors.

Display

credits and exit.

Enable format

debugging.

Disable automatic installation of packages.
Specifying this
option overrules settings in the
MiKTeX configuration data store.

Disable the \write18{}
construct.

Switch on draft mode.

luaTeX; doesn’t write a
PDF and doesn’t read any included images, thus speeding up
execution.

Enable automatic installation of packages.
Specifying this
option overrules settings in the
MiKTeX configuration data store.

Fully enable the \write18{}
construct. It is only partially enabled by default to avoid security
problems. When fully enabled, the command (which undergoes the usual
TeX expansions) is passed to the command interpreter. The output of
the command is not diverted anywhere, so it will not appear in the log
file. The command execution either happens at \output time or right away, according to the
absence or presence of the \immediate
prefix.

Quit after the

first error.

Give help and exit.

Add the directory to the

head of the list of directories to be searched for input
files.

Become the INI variant

of the program.

Set the interaction mode.
Must be one of ,

, and
. The meaning of these modes is the
same as the corresponding commands.

Set the name of the job (\jobname).

This has an affect on the output file names.

Enable generation, where
must be either or
.

Don’t change the way, error messages are printed.

Disable generation, where
must be either or
.

Disable the Lua socket library.

Use for DVI file comment

instead of date.

Write output files in .

instead of the current directory. Look up input files in
first, then along the normal search
path.

Use for job output

(one of: , ).

Enable the file name recorder. This leaves a trace of the files
opened for input and output in a file

with the extension .

Partially enable the \write18{}
construct.

Disable

easily exploitable Lua commands.

Generate SyncTeX data for previewers.

If is zero, no
file is created. If
is negative, the
file is a text file. If
is positive, the
file is compressed with
gzip and the file name extension is added.

Furthermore, is interpreted as a bit field:

Bit 1 ( AND 2): Don’t add the file name extension.
Bit 2 ( AND 4): Activate form support.
Bit 3 ( AND 8): Activate better compression.

Use as the name of the format to

be used, instead of the name by which the program was called or a

%&

line.

Init

time to UTC.

Show version information and exit.

The following options are ignored:

, , ,

These are always on.

Miktex latex distribution

2.9.7300 — 2020-02-17

Group-delimited \input argument

Upgraded programs

Fixed issues

2.9.7440 — 2020-05-17

Breaking changes

Windows 8.3 file names

Package database signing

Unrestricted shell escape commands and elevated privileges

Sponsors

В-третьих, выберите и настройте редактор

1) Скачать TeXstudio

2) Найти руководство пользователя TeXstudio

3) Установите MikTeX

4) Установите TeXstudio

5) Пример демонстрации

6) Поддержка китайского

Conclusion

Copying conditions for MiKTeX

Guidelines for redistribution

References

21.6.28 — 2021-06-28

Breaking changes

Common TEXMF root directories in a private (current user) installation

Description

Maintenance

Mac

Установка

Установка PSCyr

2.9.6500 — 2017-11-04

Upgraded libraries

Bug fixes

Installation

directories should be distinct

Switching between MiKTeX and TeX Live

Description

Options