Escreva LaTeX e visualize o PDF

Export the project as a ZIP after important editing sessions and before changing the root file, engine, package set, or folder structure. The archive should contain the source files and added assets needed to continue the project elsewhere. A downloaded PDF is only the compiled result and cannot replace the editable source. Open the ZIP and confirm that chapters, bibliography files, images, custom classes, and style files are present before relying on it as the project copy.

Use the engine already specified by an existing project whenever possible. pdfLaTeX is a practical choice for many established documents and packages. XeLaTeX is often preferable when the source requires broad Unicode text, system fonts, or OpenType font features. Changing engines can affect font metrics, line breaks, package behavior, and output pagination. If the choice is uncertain, check the project documentation and compare a clean compile of representative pages, equations, references, and non-Latin text.

Start with the first useful diagnostic because later messages are often consequences of the same earlier error. Frequent causes include an unknown command, unmatched braces, a missing file, an incorrect path, a package unavailable to the selected engine, or a root document that does not include a document environment. Correct one cause at a time and compile again. When an error points into a generated file, inspect the source command that created the affected table of contents, citation, label, or auxiliary entry.

Cross-references and bibliographies can require more than one successful compilation because LaTeX first writes auxiliary information and then reads it on a later pass. Confirm that every label is unique, each reference uses the exact label name, citation keys match the bibliography entries, and the bibliography file is included with the expected workflow. Fix compilation errors before judging references. If question marks remain, inspect the earliest citation or auxiliary-file diagnostic and verify that the selected engine and bibliography commands match the project.

A successful compile means a PDF was produced, not that the document is correct. Review the title page, page order, headings, tables, figures, equations, footnotes, links, citations, bibliography, headers, footers, margins, and page breaks. Look for overfull lines, clipped graphics, missing glyphs, unresolved question marks, unexpected blank pages, and changed font substitution. For an important document, compare representative pages at normal zoom and print scale, then confirm that links and copied text behave as expected.

Identify the intended root .tex file and keep relative paths consistent for chapters, images, bibliographies, classes, and style files. Projects that depend on shell commands, external programs, unusual system fonts, unavailable packages, or a different TeX distribution may need changes before they compile. File names are safest when their capitalization matches every source reference exactly. After import, compile a small known section first, review diagnostics, and then inspect the full document for package-specific differences or missing assets.