msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2026-05-16 03:35+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
msgctxt "_"
msgid "translator-credits"
msgstr ""

#. (itstool) path: page/title
#: C/build_tools.page:10
msgid "Build Tools"
msgstr ""

#. (itstool) path: synopsis/p
#: C/build_tools.page:13
msgid "The purpose of the build tools is to generate a document in the PDF, DVI or PS format."
msgstr ""

#. (itstool) path: section/title
#: C/build_tools.page:20
msgid "Introduction"
msgstr ""

#. (itstool) path: section/p
#: C/build_tools.page:22
msgid "Several different tools can be used for a document compilation. There are some low-level commands, and one higher-level tool: Latexmk."
msgstr ""

#. (itstool) path: table/title
#: C/build_tools.page:26
msgid "Low-level commands"
msgstr ""

#. (itstool) path: td/p
#: C/build_tools.page:29
msgid "Label"
msgstr ""

#. (itstool) path: td/p
#: C/build_tools.page:30
msgid "Command"
msgstr ""

#. (itstool) path: td/p
#: C/build_tools.page:59
msgid "Bibliography"
msgstr ""

#. (itstool) path: td/p
#: C/build_tools.page:63
msgid "Index"
msgstr ""

#. (itstool) path: section/p
#: C/build_tools.page:69
msgid "Compiling a LaTeX document can involve to execute several low-level commands, in a certain order and a certain number of times. Here is an example:"
msgstr ""

#. (itstool) path: section/p
#: C/build_tools.page:78
msgid "Using a higher-level tool such as Latexmk simplify a lot all this process, since only one command is required. Indeed, Latexmk can detect how many times the <cmd>latex</cmd> or <cmd>pdflatex</cmd> command must be called, and whether <cmd>bibtex</cmd> or <cmd>makeindex</cmd> is required. By default, <app>Enter TeX</app> uses Latexmk."
msgstr ""

#. (itstool) path: section/title
#: C/build_tools.page:86
msgid "Execute a Build Tool"
msgstr ""

#. (itstool) path: section/p
#: C/build_tools.page:88
msgid "There are several means to execute a build tool:"
msgstr ""

#. (itstool) path: item/p
#: C/build_tools.page:90
msgid "Open the <gui style=\"menu\">Build</gui> menu."
msgstr ""

#. (itstool) path: item/p
#: C/build_tools.page:91
msgid "Use the buttons in the main toolbar."
msgstr ""

#. (itstool) path: item/p
#: C/build_tools.page:92
msgid "Use the shortcut: <key>F2</key> → <key>F11</key>."
msgstr ""

#. (itstool) path: section/p
#: C/build_tools.page:95
msgid "The build tool is executed on the currently opened file. If the file belongs to a <link xref=\"projects\">project</link>, it is executed on the project's main file."
msgstr ""

#. (itstool) path: note/title
#: C/build_tools.page:99
msgid "Hidden Build Tools"
msgstr ""

#. (itstool) path: note/p
#: C/build_tools.page:100
msgid "By default, a lot of build tools are hidden, so they can't be executed. To view the full list of build tools, activate or configure them, read the <link xref=\"#general_configuration\"/> section."
msgstr ""

#. (itstool) path: section/title
#: C/build_tools.page:107
msgid "General Configuration"
msgstr ""

#. (itstool) path: section/p
#: C/build_tools.page:109
msgid "To configure the build tools, go to: <guiseq> <gui style=\"menu\">Build</gui> <gui style=\"menu\">Manage Build Tools</gui> </guiseq>"
msgstr ""

#. (itstool) path: section/p
#: C/build_tools.page:117
msgid "You will see the list of all the default build tools, and a second list with your personal build tools. There are check buttons to enable or disable them. When a build tool is disabled, it's not possible to execute it. You can perform some actions, like moving a tool up or down, open its properties, delete or copy it, create a new one, etc."
msgstr ""

#. (itstool) path: note/p
#: C/build_tools.page:124
msgid "Double-click on a build tool will open its properties."
msgstr ""

#. (itstool) path: section/title
#: C/build_tools.page:129
msgid "Jobs of a Build Tool"
msgstr ""

#. (itstool) path: section/p
#: C/build_tools.page:131
msgid "In the properties of a build tool, the tricky part is to configure the jobs. A build tool can execute several jobs. Each job contains two pieces of information:"
msgstr ""

#. (itstool) path: item/p
#: C/build_tools.page:135
msgid "The command, which can use placeholders."
msgstr ""

#. (itstool) path: item/p
#: C/build_tools.page:136
msgid "The post processor (see <link xref=\"#post-processors\"/>)."
msgstr ""

#. (itstool) path: section/p
#: C/build_tools.page:139
msgid "When an error occurs during a job's execution, the execution of the build tool is aborted, so the next jobs are not launched."
msgstr ""

#. (itstool) path: section/title
#: C/build_tools.page:144
msgid "Post Processors"
msgstr ""

#. (itstool) path: section/p
#: C/build_tools.page:145
msgid "The purpose of a post processor is to filter the command output and extract the useful information. Four post processors are available:"
msgstr ""

#. (itstool) path: item/p
#: C/build_tools.page:151
msgid "The output is simply not displayed."
msgstr ""

#. (itstool) path: item/p
#: C/build_tools.page:155
msgid "All the output is displayed, without filter."
msgstr ""

#. (itstool) path: item/p
#: C/build_tools.page:159
msgid "Filter the output of the <cmd>latex</cmd> or <cmd>pdflatex</cmd> commands. There can be three types of errors: critical errors, warnings, or bad boxes. There are also some other useful information: the size of the document, the number of pages, and the number of errors."
msgstr ""

#. (itstool) path: item/p
#: C/build_tools.page:166
msgid "Used for the <cmd>latexmk</cmd> command. Internally, this post processor uses other ones: <em>latex</em> and <em>all-output</em>."
msgstr ""

#. (itstool) path: page/title
#: C/completion.page:10
msgid "Completion of LaTeX commands"
msgstr ""

#. (itstool) path: synopsis/p
#: C/completion.page:13
msgid "The purpose is to facilitate the writing of LaTeX commands, by showing proposals."
msgstr ""

#. (itstool) path: section/title
#: C/completion.page:17
msgid "Interactive completion"
msgstr ""

#. (itstool) path: section/p
#: C/completion.page:18
msgid "By default, when a LaTeX command is typed, proposals will be shown after two characters. This can be configured in the preferences dialog: <guiseq> <gui style=\"menu\">Edit</gui> <gui style=\"menu\">Preferences</gui> <gui style=\"tab\">Other</gui> </guiseq>"
msgstr ""

#. (itstool) path: section/title
#: C/completion.page:30
msgid "Manual completion"
msgstr ""

#. (itstool) path: section/p
#: C/completion.page:31
msgid "At any time, press <keyseq> <key>Ctrl</key> <key>Space</key> </keyseq> to show proposals."
msgstr ""

#. (itstool) path: page/title
#: C/index.page:4
msgid "Enter TeX Help"
msgstr ""

#. (itstool) path: page/title
#: C/projects.page:10
msgid "Projects"
msgstr ""

#. (itstool) path: synopsis/p
#: C/projects.page:13
msgid "When a LaTeX document is split into several *.tex files, creating a project is useful."
msgstr ""

#. (itstool) path: section/title
#: C/projects.page:18
msgid "Manage projects"
msgstr ""

#. (itstool) path: section/p
#: C/projects.page:20
msgid "All actions related to projects are located in the <gui style=\"menu\">Projects</gui> menu. A project contains only two pieces of information:"
msgstr ""

#. (itstool) path: item/p
#: C/projects.page:25
msgid "The directory where the project is located."
msgstr ""

#. (itstool) path: item/p
#: C/projects.page:26
msgid "The main *.tex file."
msgstr ""

#. (itstool) path: section/p
#: C/projects.page:29
msgid "As a consequence, a directory can contain only one project, which is quite logical."
msgstr ""

#. (itstool) path: section/title
#: C/projects.page:35
msgid "Usefulness of projects"
msgstr ""

#. (itstool) path: item/p
#: C/projects.page:37
msgid "A <link xref=\"build_tools\">build tool</link> is executed on the project's main file."
msgstr ""

#. (itstool) path: item/p
#: C/projects.page:39
msgid "<link xref=\"synctex#from_tex_to_pdf\">Jumping from a .tex file to the PDF</link> works for a secondary .tex file belonging to a project."
msgstr ""

#. (itstool) path: page/title
#: C/spell_checking.page:10
msgid "Spell-Checking"
msgstr ""

#. (itstool) path: synopsis/p
#: C/spell_checking.page:13
msgid "The purpose is to correct spelling mistakes easily."
msgstr ""

#. (itstool) path: section/title
#: C/spell_checking.page:17
msgid "Use the spell-checking"
msgstr ""

#. (itstool) path: section/p
#: C/spell_checking.page:18
msgid "The default spell-checking settings can be changed in the preferences dialog: <guiseq> <gui style=\"menu\">Edit</gui> <gui style=\"menu\">Preferences</gui> <gui style=\"tab\">Other</gui> </guiseq>"
msgstr ""

#. (itstool) path: section/p
#: C/spell_checking.page:27
msgid "The settings can also be changed on a file-by-file basis via the <gui style=\"menu\">Tools</gui> menu."
msgstr ""

#. (itstool) path: section/p
#: C/spell_checking.page:32
msgid "If you activate the <gui style=\"menu\">Highlight Misspelled Words</gui> option, the misspelled words will be underlined in red in the document. A right click on a misspelled word will show proposals."
msgstr ""

#. (itstool) path: section/title
#: C/spell_checking.page:40
msgid "Dictionaries"
msgstr ""

#. (itstool) path: section/p
#: C/spell_checking.page:41
msgid "<link href=\"https://gitlab.gnome.org/GNOME/gspell\">gspell</link> is used for the spell-checking in <app>Enter TeX</app>. gspell uses <link href=\"https://rrthomas.github.io/enchant/\">Enchant</link>, which in turn supports several backends such as Hunspell or Aspell for the dictionaries. The Aspell backend doesn't work well with gspell, Hunspell is preferred. If dictionaries for both Aspell and Hunspell are installed for the same language, by default Enchant prefers the Hunspell one."
msgstr ""

#. (itstool) path: section/p
#: C/spell_checking.page:51
msgid "If your language is not listed in <app>Enter TeX</app>, install a dictionary for one of the supported Enchant backends (for most languages the best choice is to install an Hunspell dictionary)."
msgstr ""

#. (itstool) path: page/title
#: C/structure.page:10
msgid "Document's Structure"
msgstr ""

#. (itstool) path: synopsis/p
#: C/structure.page:13
msgid "The list of chapters, sections, sub-sections and other things like tables, figures, … of a document, to easily navigate in it."
msgstr ""

#. (itstool) path: section/title
#: C/structure.page:18
msgid "Display the structure"
msgstr ""

#. (itstool) path: section/p
#: C/structure.page:20
msgid "The structure can be displayed in the side panel. If the side panel is hidden, go to <guiseq> <gui style=\"menu\">View</gui> <gui style=\"menu\">Side panel</gui> </guiseq>."
msgstr ""

#. (itstool) path: section/p
#: C/structure.page:29
msgid "The structure's content is not automatically updated. That's why there is a refresh button. If text is inserted in the document, the position of an item (e.g. a section) remains correct, as far as the item is still there, and is not modified."
msgstr ""

#. (itstool) path: section/title
#: C/structure.page:37
msgid "Actions"
msgstr ""

#. (itstool) path: section/p
#: C/structure.page:39
msgid "Some actions such as \"cut\", \"copy\" or \"comment\" can be performed on a structure's item. Either by a right click, or via the <gui style=\"menu\">Structure</gui> menu."
msgstr ""

#. (itstool) path: section/title
#. Do not translate the words TODO and FIXME. They are special comments
#. that can be inserted in LaTeX documents.
#: C/structure.page:48
msgid "TODOs and FIXMEs"
msgstr ""

#. (itstool) path: section/p
#. Do not translate the words TODO and FIXME. They are special comments
#. that can be inserted in LaTeX documents.
#: C/structure.page:50
msgid "It can be useful to add TODOs and FIXMEs comments in the document. They will be displayed in the structure. Example:"
msgstr ""

#. (itstool) path: section/code
#. Do not translate the words TODO and FIXME. They are special comments
#. that can be inserted in LaTeX documents.
#: C/structure.page:55
#, no-wrap
msgid ""
"\n"
"%TODO a remaining task\n"
"%FIXME something is broken"
msgstr ""

#. (itstool) path: page/title
#: C/synctex.page:10
msgid "Jumping Between .tex and PDF"
msgstr ""

#. (itstool) path: synopsis/p
#: C/synctex.page:13
msgid "Jumping between the document's *.tex files and the resulting PDF output, opened with the <app>Evince</app> document viewer."
msgstr ""

#. (itstool) path: note/p
#: C/synctex.page:18
msgid "For more information, read the <link href=\"help:evince#synctex\"><app>Evince</app> documentation</link>."
msgstr ""

#. (itstool) path: section/title
#: C/synctex.page:23
msgid "Jumping from .tex to PDF"
msgstr ""

#. (itstool) path: section/p
#: C/synctex.page:25
msgid "From a certain position in the .tex source file, jump to the corresponding position in the PDF file. Also called “forward search”."
msgstr ""

#. (itstool) path: section/p
#: C/synctex.page:28
msgid "There are different ways to do this action:"
msgstr ""

#. (itstool) path: item/p
#: C/synctex.page:30
msgid "In the menu: <guiseq> <gui style=\"menu\">Search</gui> <gui style=\"menu\">Jump to PDF</gui> </guiseq>"
msgstr ""

#. (itstool) path: item/p
#: C/synctex.page:36
msgid "By pressing <keyseq> <key>Ctrl</key> <key>left click</key> </keyseq>"
msgstr ""

#. (itstool) path: section/p
#: C/synctex.page:44
msgid "If a document is split into several .tex files, create a <link xref=\"projects\">project</link>. Unlike what is explained in the <link href=\"help:evince/synctex-search#forward-search\"><app>Evince</app> documentation</link>, there is no need to mention the main file with a LaTeX comment in each secondary .tex file."
msgstr ""

#. (itstool) path: section/title
#: C/synctex.page:52
msgid "Jumping from PDF to .tex"
msgstr ""

#. (itstool) path: section/p
#: C/synctex.page:54
msgid "From a certain position in the PDF file, jump to the corresponding position in the .tex source file. Also called “backward search”."
msgstr ""

#. (itstool) path: section/p
#: C/synctex.page:57
msgid "In <app>Evince</app>, press <keyseq> <key>Ctrl</key> <key>left click</key> </keyseq>, and the corresponding position in the .tex file will be opened in <app>Enter TeX</app>."
msgstr ""

#. (itstool) path: section/p
#: C/synctex.page:65
msgid "<app>Evince</app> has to be launched by <app>Enter TeX</app>. Else, jumping from the PDF to the .tex file will not work."
msgstr ""

