latex thesis glossary

LaTeX/Glossary

Many technical documents use terms or acronyms unknown to the general population. It is common practice to add a glossary to make such documents more accessible.

The glossaries package can be used to create glossaries. It supports multiple glossaries, acronyms, and symbols. This package replaces the glossary package and can be used instead of the nomencl package. [1] Users requiring a simpler solution should consider hand-coding their entries by using the description environment, or the longtabu environment provided by the tabu package.

• 1 Jump start
• 2 Using glossaries
• 3 Defining glossary entries
• 4.1 Defining symbols
• 4.2 Defining acronyms
• 5.1 General references
• 5.2 Referring acronyms
• 6.1.1 Dual entries with reference to a glossary entry from an acronym
• 6.2 Custom Name
• 6.3 Remove the point
• 6.4 Changing Glossary Entry Presentation Using Glossary Styles
• 6.5 Building your document
• 7.1 Compile glossary with xindy - In Windows with Texmaker
• 7.2 Document preamble
• 7.3 Glossary definitions
• 7.4 Include glossary definitions and print glossary
• 7.5 References

Jump start [ edit | edit source ]

Place \usepackage { glossaries } and \makeglossaries in your preamble (after \usepackage { hyperref } if present). Then define any number of \newglossaryentry and \newacronym glossary and acronym entries in your preamble (recommended) or before first use in your document proper. Finally add a \printglossaries call to locate the glossaries list within your document structure. Then pepper your writing with \gls { mylabel } macros (and similar) to simultaneously insert your predefined text and build the associated glossary. File processing must now include a call to makeglossaries document_name_without_extension followed by at least one further invocation of latex or pdflatex .

Using glossaries [ edit | edit source ]

To use the glossaries package, you have to load it explicitly:

if you wish to use xindy (superior indexing tool [2] ) for the indexing phase, as opposed to makeindex (the default), you need to specify the xindy option:

For the glossary to show up in your Table of Contents, you need to specify the toc option:

See also Custom Name at the bottom of this page.

Finally, place the following command in your document preamble in order to generate the glossary:

Any links in resulting glossary will not be "clickable" unless you load the glossaries package after the hyperref package.

In addition, users who wish to make use of makeglossaries will need to have Perl installed — this is not normally present by default on Microsoft Windows platforms. That said, makeglossaries simply provides a convenient interface to makeindex and xindy and is not essential.

Defining glossary entries [ edit | edit source ]

To use an entry from a glossary you first need to define it. There are few ways to define an entry depending on what you define and how it is going to be used.

Note that a defined entry won't be included in the printed glossary unless it is used in the document. This enables you to create a glossary of general terms and just \include it in all your documents.

Defining terms [ edit | edit source ]

To define a term in glossary you use the \newglossaryentry macro:

<label> is a unique label used to identify an entry in glossary, <settings> are comma separated key=value pairs used to define an entry.

For example, to define a computer entry:

The above example defines an entry that has the same label and entry name. This is not always the case as the next entry will show:

When you define terms, you need to remember that they will be sorted by makeindex or xindy . While xindy is a bit more LaTeX aware, it does it by omitting latex macros ( \" { \i } ) thus incorrectly sorting the above example as nave . makeindex won't fare much better, because it doesn't understand TeX macros, it will interpret the word exactly as it was defined, putting it inside symbol class, before words beginning with naa . Therefore it's needed to extend our example and specify how to sort the word:

You can also specify plural forms, if they are not formed by adding “s” (we will learn how to use them in next section):

Or, for acronyms:

This will avoid the wrong long plural: Frame per Seconds.

So far, the glossary entries have been defined as key-value lists. Sometimes, a description is more complex than just a paragraph. For example, you may want to have multiple paragraphs, itemized lists, figures, tables, etc. For such glossary entries use the command longnewglossaryentry in which the description follows the key-value list. The computer entry then looks like this:

Defining symbols [ edit | edit source ]

Defined entries can also be symbols:

You can also define both a name and a symbol:

Note that not all glossary styles show defined symbols.

Defining acronyms [ edit | edit source ]

To define a new acronym you use the \newacronym macro:

where <label> is the unique label identifying the acronym, <abbrv> is the abbreviated form of the acronym and <full> is the expanded text. For example:

Defined acronyms can be put in separate list if you use acronym package option:

Using defined terms [ edit | edit source ]

When you have defined a term, you can use it in a document. There are many different commands used to refer to glossary terms.

General references [ edit | edit source ]

A general reference is used with \gls command. If, for example, you have glossary entries defined as those above, you might use it in this way:

Description of commands used in above example:

This command prints the term associated with <label> passed as its argument. If the hyperref package was loaded before glossaries it will also be hyperlinked to the entry in glossary.

This command prints the plural of the defined term, other than that it behaves in the same way as gls .

This command prints the singular form of the term with the first character converted to upper case.

This command prints the plural form with first letter of the term converted to upper case.

This command creates the link as usual, but typesets the alternate text instead. It can also take several options which changes its default behavior (see the documentation).

This command prints what ever is defined in \newglossaryentry{<label>}{symbol={Output of glssymbol}, ...}

This command prints what ever is defined in \newglossaryentry{<label>}{description={Output of glsdesc}, ...}

Referring acronyms [ edit | edit source ]

Acronyms behave a bit differently to normal glossary terms. On first use the \gls command will display "<full> (<abbrv>)". On subsequent uses only the abbreviation will be displayed.

To reset the first use of an acronym, use the command:

or, if you want to reset the use status of all acronyms:

Similarly, to unset the first use of an acronym so that only the abbreviation will be displayed, use:

or, for all acronyms:

If you just want to print the long version of an acronym without the abbreviation "<full>", use :

If you just want to print the long version of an acronym with the abbreviation "<full> (<abbrv>)", use :

If you just want to print the abbreviation "<abbrv>", use :

Displaying the Glossary [ edit | edit source ]

To display the sorted list of terms you need to add:

at the place you want the glossary and the list of acronyms to appear.

If all entries are to be printed the command

can be inserted before \printglossaries . You may also want to use \usepackage [nonumberlist] { glossaries } to suppress the location list within the glossary.

Separate Glossary and List of Acronyms [ edit | edit source ]

\printglossaries will display all the glossaries in the order in which they were defined. [3] If no custom glossaries are defined, the default glossary and the list of acronyms will be displayed.

The glossary and the list of acronyms can be displayed separately in different places [4] :

Dual entries with reference to a glossary entry from an acronym [ edit | edit source ]

It may be useful to have both an acronym and a glossary entry for the same term. To link these two, define the acronym with a reference to the glossary entry like this:

To make this easier, we can use this command (modified from example in the official docs):

then, define new (dual) entries for glossary and acronym list like this:

Custom Name [ edit | edit source ]

The name of the glossary section can be replaced with a custom name or translated to a different language. Add the option title to \printglossary to specify the glossary's title. Add the option toctitle to specify a the title used in the table of content (if not used, title is used as default). [5]

Remove the point [ edit | edit source ]

To omit the dot at the end of each description, use this code:

Changing Glossary Entry Presentation Using Glossary Styles [ edit | edit source ]

A number of pre-built styles are available, and can be changed easily using

Commonly used styles include list

altlist (inserts newline after term and indents description)

altlistgroup or listgroup (group adds grouping based on the first letters of the terms)

altlisthypergroup or listhypergroup (hyper adds an hyperlinked 'index' at the top of each glossary to jump to a group)

Building your document [ edit | edit source ]

Building your document and its glossary requires three steps:

• build your LaTeX document — this will also generate the files needed by makeglossaries
• invoke makeglossaries — a script which selects the correct character encodings and language settings and which will also run xindy or makeindex if these are specified in your document file
• build your LaTeX document again — to produce a document with glossary entries

where latex is your usual build call (perhaps pdflatex ) and doc is the name of your LaTeX master file.

If your entries are interlinked (entries themselves link to other entries with \gls calls), you will need to run steps 1 and 2 twice, that is, in the following order: 1, 2, 1, 2, 3.

If you encounter problems, view the doc.log and doc.glg files in a text editor for clues.

Example for use in windows with Texmaker [ edit | edit source ]

Compile glossary with xindy - in windows with texmaker [ edit | edit source ].

In TeX Live and since June 2015 in MikTeX xindy is already included.

There is only one issue with path of the install directory of MikTeX containing spaces. It can be solved via the following edit: http://tex.stackexchange.com/questions/251221/miktex-and-xindy-problems/251801#251801

You need to restart Texmaker after installation of xindy , to update PATH references to xindy and Perl binaries.

Then, in Texmaker, go to User -> User Commands -> Edit User Commands . Choose command 1

• Menuitem = makeglossaries
• Command = makeglossaries %

Now push Alt+Shift+F1 and then -> F1

Note , for use with the "use build directory" option of Texmaker: makeglossaries needs to find the aux file. Thankfully, while Texmaker does not help there, the option -d <dir> of makeglossaries provides for the subdirectory case. Hence the Command in this case should be: Command = makeglossaries -d build % instead.

Document preamble [ edit | edit source ]

In preamble should be included (note, hyperref should be loaded before the glossaries ):

Glossary definitions [ edit | edit source ]

Write all your glossaries/acronyms in a file: Ex: INP-00-glossary.tex

Include glossary definitions and print glossary [ edit | edit source ]

Include glossary definitions in the preamble (Before "\begin{document}")

Print glossaries, near end

References [ edit | edit source ]

• ↑ http://www.ctan.org/pkg/nomencl
• ↑ Differences between “xindy” and “makeindex”
• ↑ http://mirror.ox.ac.uk/sites/ctan.org/macros/latex/contrib/glossaries/glossaries-user.html#dx1-35001
• ↑ http://mirror.ox.ac.uk/sites/ctan.org/macros/latex/contrib/glossaries/glossaries-user.html#dx1-43001
• ↑ User Manual for glossaries.sty v4.02 as of 2014.01.13 http://mirror.ox.ac.uk/sites/ctan.org/macros/latex/contrib/glossaries/glossaries-user.html#sec:printglossary
• The glossaries documentation, http://tug.ctan.org/tex-archive/macros/latex/contrib/glossaries/
• Using LaTeX to Write a PhD Thesis , Nicola L.C. Talbot, [1]
• glossaries FAQ , Nicola L. C. Talbot, glossaries FAQ
• Glossaries, Nomenclature, Lists of Symbols and Acronyms , Nicola L. C. Talbot, link

• Wikibooks pages with to-do lists

Navigation menu

© 2013 Dickimaw Books. "Dickimaw", "Dickimaw Books" and the Dickimaw parrot logo are trademarks. The Dickimaw parrot was painted by Magdalene Pritchett.

Terms of Use Privacy Policy Cookies Site Map FAQs

1. Getting Started [link]

2. defining terms [link], 3. using entries [link], 4. displaying a list of entries [link], 5. customising the glossary [link], 6. multiple glossaries [link], 7. hyperlinks ( glossaries and hyperref ) [link], 8. cross-references [link], 9. further information [link], symbols [link], glossary [link], command summary [link], index [link].

List of Tables [link]

List of examples [link], 1. introduction [link], 1.1. rollback [link], 1.2. integrating other packages and known issues [link], 1.3. indexing options [link], 1.3.1. option 1 ( “noidx” ) [link], 1.3.2. option 2 ( makeindex ) [link], 1.3.3. option 3 ( xindy ) [link], 1.3.4. option 4 ( bib2gls ) [link], 1.3.5. option 5 ( “unsrt” ) [link], 1.3.6. option 6 ( “standalone” ) [link], 1.4. dummy entries for testing [link], 1.5. multi-lingual support [link], 1.5.1. changing the fixed names [link], 1.5.2. creating a new language module [link], 1.6. generating the associated glossary files [link], 1.6.1. using the makeglossaries perl script [link], 1.6.2. using the makeglossaries-lite lua script [link], 1.6.3. using xindy explicitly (option 3) [link], 1.6.4. using makeindex explicitly (option 2) [link], 1.7. note to front-end and script developers [link], 1.7.1. makeindex and xindy [link], 1.7.2. entry labels [link], 1.7.3. bib2gls [link], 2. package options [link], 2.1. general options [link], 2.2. sectioning, headings and toc options [link], 2.3. glossary appearance options [link], 2.4. indexing options [link], 2.5. sorting options [link], 2.6. glossary type options [link], 2.7. acronym and abbreviation options [link], 2.8. deprecated acronym style options [link], 2.9. other options [link], 2.10. setting options after the package is loaded [link], 3. setting up [link], 3.1. option 1 [link], 3.2. options 2 and 3 [link], 4. defining glossary entries [link], 4.1. plurals [link], 4.2. other grammatical constructs [link], 4.3. additional keys [link], 4.3.1. document keys [link], 4.3.2. storage keys [link], 4.4. expansion [link], 4.5. sub-entries [link], 4.5.1. hierarchy [link], 4.5.2. homographs [link], 4.6. loading entries from a file [link], 4.7. moving entries to another glossary [link], 4.8. drawbacks with defining entries in the document environment [link], 4.8.1. technical issues [link], 4.8.2. good practice issues [link], 5. referencing entries in the document [link], 5.1. links to glossary entries [link], 5.1.1. options [link], 5.1.2. the \gls -like commands (first use flag queried) [link], 5.1.3. the \glstext -like commands (first use flag not queried) [link], 5.1.4. changing the format of the \gls -like link text [link], 5.1.5. hooks [link], 5.1.6. enabling and disabling hyperlinks to glossary entries [link], 5.2. using glossary terms without indexing [link], 6. acronyms and other abbreviations [link], 6.1. displaying the long, short and full forms (independent of first use) [link], 6.2. changing the acronym style [link], 6.2.1. predefined acronym styles [link], 6.2.1.1. long (short) [link], 6.2.1.2. short (long) [link], 6.2.1.3. long (short) user supplied description [link], 6.2.1.4. short (long) user supplied description [link], 6.2.1.5. do not use acronym (dua) [link], 6.2.1.6. footnote [link], 6.2.2. defining a custom acronym style [link], 6.3. displaying the list of acronyms [link], 6.4. upgrading from the glossary package [link], 7. unsetting and resetting entry flags [link], 7.1. counting the number of times an entry has been used (first use flag unset) [link], 8. displaying a glossary [link], 8.1. \print 〈 … 〉 glossary options [link], 8.2. glossary markup [link], 9. defining new glossaries [link], 10. adding an entry to the glossary without generating text [link], 11. cross-referencing entries [link], 11.1. customising cross-reference text [link], 12. number lists [link], 12.1. encap values (location formats) [link], 12.2. range formations [link], 12.3. locations [link], 12.4. page precedence [link], 12.5. problematic locations [link], 12.6. iterating over locations [link], 13. glossary styles [link], 13.1. predefined styles [link], 13.1.1. list styles [link], 13.1.2. longtable styles [link], 13.1.3. longtable styles (ragged right) [link], 13.1.4. longtable styles ( booktabs ) [link], 13.1.5. supertabular styles [link], 13.1.6. supertabular styles (ragged right) [link], 13.1.7. tree-like styles [link], 13.1.8. multicols style [link], 13.1.9. in-line style [link], 13.2. defining your own glossary style [link], 13.2.1. commands for use in glossary styles [link], 13.2.2. hyper group navigation [link], 13.2.3. glossary style commands [link], 14. xindy (option 3) [link], 14.1. required styles [link], 14.2. language and encodings [link], 14.3. locations and number lists [link], 14.4. glossary groups [link], 15. utilities [link], 15.1. hyperref [link], 15.2. case-changing [link], 15.3. loops [link], 15.4. conditionals [link], 15.5. measuring [link], 15.6. fetching and updating the value of a field [link], 16. prefixes or determiners [link], 17. accessibility support [link], 17.1. accessibility keys [link], 17.2. incorporating accessibility support [link], 17.3. incorporating the access field values [link], 17.4. obtaining the access field values [link], 17.5. developer’s note [link], 18. sample documents [link], 18.1. basic [link], 18.2. acronyms and first use [link], 18.3. non-page locations [link], 18.4. multiple glossaries [link], 18.5. sorting [link], 18.6. child entries [link], 18.7. cross-referencing [link], 18.8. custom keys [link], 18.9. xindy (option 3) [link], 18.10. no indexing application (option 1) [link], 18.11. other [link], 19. troubleshooting [link], symbols [link], terms [link], glossary entry keys summary [link], \gls -like and \glstext -like options summary [link], \print 〈 … 〉 glossary options summary [link], acronym style summary [link], glossary styles summary [link], command summary [link], glsxtr [link], environment summary [link], package option summary [link], index [link].

No Search Results

How to Write a Thesis in LaTeX (Part 1): Basic Structure

Part 1 | Part 2 | Part 3 | Part 4 | Part 5

Author: Josh Cassidy (August 2013)

This five-part series of articles uses a combination of video and textual descriptions to teach the basics of writing a thesis using LaTeX. These tutorials were first published on the original ShareLateX blog site during August 2013; consequently, today's editor interface (Overleaf) has changed considerably due to the development of ShareLaTeX and the subsequent merger of ShareLaTeX and Overleaf. However, much of the content is still relevant and teaches you some basic LaTeX—skills and expertise that will apply across all platforms.

Your thesis could be the longest and most complicated document you'll ever write, which is why it's such a good idea to use L a T e X instead of a common word processor. L a T e X makes tasks that are difficult and awkward in word processors, far simpler.

When writing something like a thesis its worth splitting up the document into multiple .tex files. It's also wise to organise the project using folders; therefore, we'll create two new folders, one for all the images used in the project and one for all the .tex files making up the main body of the thesis.

• 1 The preamble
• 2 The frontmatter
• 3 The main body
• 4 The endmatter
• 5 All articles in this series

The preamble

In this example, the main.tex file is the root document and is the .tex file that will draw the whole document together. The first thing we need to choose is a document class. The article class isn't designed for writing long documents (such as a thesis) so we'll choose the report class, but we could also choose the book class.

We can also change the font size by adding square brackets into the \documentclass command and specifying the size—we'll choose 12pt. Let's also prepare the document for images by loading the graphicx package. We'll also need to tell L a T e X where to look for the images using the \graphicspath command, as we're storing them in a separate folder.

The start of our preamble now looks like this:

Now we can finish off the preamble by filling in the title, author and date information. To create the simplest title page we can add the thesis title, institution name and institution logo all into the \title command; for example:

This isn't the best way to alter the title page so we'll look at more elaborate ways of customising title pages later on in the series, but this will suffice for now.

This is what the \maketitle command now produces for us:

The frontmatter

After the title page we need to add in an abstract, dedication, declaration and acknowledgements section. We can add each of these in on separate pages using unnumbered chapters. To do this we use the \chapter command and add an asterisk. After these sections we'll add a table of contents using the \tableofcontents command:

The main body

Now for the main body of the document. In this example we will add-in five chapters, one of which will be an introduction and another will be a conclusion. However, instead of just composing these chapters in the main .tex file, we'll create a separate .tex file for each chapter in the chapters folder. We can then fill in these chapters with text remembering to split them up into sections and subsections.

Then to add these chapters into the document, we use the \input command in the root document. Remember to add in chapters/ before the file name so that L a T e X knows where to find it.

The endmatter

We will now add in an appendix at the end of the document. To do this we use the \appendix command to tell L a T e X that what follows are appendices. Again We'll write the appendix in a separate file and then input it.

If we now compile the document, all our chapters will be added to the document and the table of contents will be automatically generated.

Now we have a basic structure for a thesis set up. In the next post I will show you how to change the page layout and add headers.

All articles in this series

• Part 1: Basic Structure ;
• Part 2: Page Layout ;
• Part 3: Figures, Subfigures and Tables ;
• Part 4: Bibliographies with BibLaTeX ;
• Part 5: Customising Your Title Page and Abstract .
• Documentation Home
• Learn LaTeX in 30 minutes

Overleaf guides

• Creating a document in Overleaf
• Uploading a project
• Copying a project
• Creating a project from a template
• Using the Overleaf project menu
• Including images in Overleaf
• Exporting your work from Overleaf
• Working offline in Overleaf
• Using Track Changes in Overleaf
• Using bibliographies in Overleaf
• Sharing your work with others
• Using the History feature
• Debugging Compilation timeout errors
• How-to guides
• Guide to Overleaf’s premium features

LaTeX Basics

• Creating your first LaTeX document
• Choosing a LaTeX Compiler
• Paragraphs and new lines
• Bold, italics and underlining

Mathematics

• Mathematical expressions
• Subscripts and superscripts
• Brackets and Parentheses
• Fractions and Binomials
• Aligning equations
• Spacing in math mode
• Integrals, sums and limits
• Display style in math mode
• List of Greek letters and math symbols
• Mathematical fonts
• Using the Symbol Palette in Overleaf

Figures and tables

• Inserting Images
• Positioning Images and Tables
• Lists of Tables and Figures
• Drawing Diagrams Directly in LaTeX
• TikZ package

References and Citations

• Bibliography management with bibtex
• Bibliography management with natbib
• Bibliography management with biblatex
• Bibtex bibliography styles
• Natbib bibliography styles
• Natbib citation styles
• Biblatex bibliography styles
• Biblatex citation styles
• Multilingual typesetting on Overleaf using polyglossia and fontspec
• Multilingual typesetting on Overleaf using babel and fontspec
• International language support
• Quotations and quotation marks

Document structure

• Sections and chapters
• Table of contents
• Cross referencing sections, equations and floats
• Nomenclatures
• Management in a large project
• Multi-file LaTeX projects
• Lengths in L a T e X
• Headers and footers
• Page numbering
• Paragraph formatting
• Line breaks and blank spaces
• Text alignment
• Page size and margins
• Single sided and double sided documents
• Multiple columns
• Code listing
• Code Highlighting with minted
• Using colours in LaTeX
• Margin notes
• Font sizes, families, and styles
• Font typefaces
• Supporting modern fonts with X Ǝ L a T e X

Presentations

• Environments

Field specific

• Theorems and proofs
• Chemistry formulae
• Feynman diagrams
• Molecular orbital diagrams
• Chess notation
• Knitting patterns
• CircuiTikz package
• Pgfplots package
• Typesetting exams in LaTeX
• Attribute Value Matrices

Class files

• Understanding packages and class files
• List of packages and class files
• Writing your own package
• Writing your own class

Advanced TeX/LaTeX

• In-depth technical articles on TeX/LaTeX

Have you checked our knowledge base ?

Message sent! Our team will review it and reply by email.

because LaTeX matters

Multiple glossaries in latex.

Recently I was asked how to produce multiple glossaries in the same document . The glossaries package , which supersedes glossary , provides such functionality. In this post, I primarily focus on adding topic-specific glossaries besides the main glossary and list of acronyms. Links to further readings are given for glossaries package basics as well as for chapter-/section-/equation-wise glossaries.

• Glossary basics
• Adding topic-specific glossaries
• Minimal working example
• Glossary for each chapter/section/equation

1. Glossary basics

This recent post introduces the basics of how to use the glossaries package to produce a glossary. A minimal example is given here . You might also want to look through the package documentation which comes in form of a beginner’s guide and a more comprehensive user manual .

2. Adding topic-specific glossaries

The glossaries package defines a default/main glossary with the option to produce a list of acronyms. All entries are automatically assigned to the default glossary or list of acronyms. The package also provides functionality to define additional glossaries, such as a list of symbols in an equation or a topic-specific glossary. Here is an example of a topic-specific glossary for top-level domains:

tlg , tld , and tdn are arguments used as meta-file endings. These files are required when the glossary is generated. The meta-file endings for the main glossary are: glg , gls , and glo . For the list of acronyms, alg , acn , and acr are reserved. The second argument to newglossary , here domain , specifies the glossary type. It’s a keyword that is used to assign new entries to this specific glossary. The last argument defines the glossary title.

Having defined the new glossary, we can now add glossary entries to it. This works the same way as for the default glossary, with the only difference being the additional type keyword:

Using a label of the form tld:com is not a requirement, but a recommendation. This convention helps to avoid multiply defined entries for different glossaries. Furthermore, it makes it easier to identify which glossary an entry belongs to.

Using glossary entries isn’t different from the default glossary, i.e. \gls{tld:com} , etc. Only glossary entries used in the text will appear in the respective glossary.

Finally, to print all glossaries, simply type:

In case the order matters or you’d like to produce different glossaries in different positions of your document, you can print each glossary individually using the type keyword:

3. Minimal working example

4. Glossary for each chapter/section/equation

Although, you might want to think twice whether to have a glossary per chapter/section/equation, here is a solution for chapters/sections and with some modification for equations .

Share this:

Leave a reply cancel reply.

Search code, repositories, users, issues, pull requests...

Provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications

武汉大学本科毕业论文 LaTeX 模版 2024

Hong-WJ/whu-thesis-2024

Folders and files, repository files navigation, 武汉大学毕业论文 latex 模板.

本项目为武汉大学本科毕业论文 LaTeX 模板，基于WHUTUG的模板 武汉大学毕业论文 LaTeX 模版 进行了修改以符合计算机学院2024的格式要求

已更新Overleaf模板： whu-thesis-2024 - Overleaf, Online LaTeX Editor

**注意, Overleaf 模板中目前需手动将导师参数头advisor改为advisor-name **

* 由于模板更新频繁，请确保使用 whu-thesis 的最新版本，并在使用之前将所有宏包更新至最新。

根据 《武汉大学本科生毕业论文（设计）书写印制规范》 、 武汉大学博士学位论文撰写及印制规格的规定 、 武汉大学硕士学位论文印制规定 编写，力求合规，简洁，易于实现，用户友好。

正文样例可以参照 whu-thesis-demo

开题报告样例可以参照 opening-demo

使用前请阅读 使用文档

推荐两种方式进行编辑和编译：

Overleaf 在线编译

本地编译需要安装 TeX 发行版软件, 具体可参见 本地安装使用指南

Overleaf 是一个简洁的在线 LaTeX 编辑器。无需安装，实时共享，版本控制。该模板支持了 Overleaf 的在线编辑，可以从上面的模板链接直接创建自己的项目。

使用该模板时，需要设置 XeLaTeX 或 LuaLaTeX 为编译器，具体步骤请查看 Overleaf 在线编辑

关于模板使用、参考文献引用等常见问题请移步 Wiki

如果在使用中发现 bug ，或遇到了「 与预期效果不一致 」的情况，请按照以下步骤操作：

• 阅读学校的 书写印制规范文件 ，判断是否符合要求；
• 前往项目 Wiki 查看相关说明；
• 将 TeX 发行版和宏包升级到最新，并且将模板升级到 Github 上最新版本，查看问题是否已经修复；
• 在 GitHub Issues 中搜索该问题的关键词；
• 提出新的 Issue ，并说明系统、TeX 版本、出现的问题等关键信息， 如果信息不全、语焉不详，您可能将不会得到很好的解答 。

如果只是「 如何使用 」上的问题，可以前往 Discussions 进行讨论；其他问题，请尽量提供完整信息，在 Issues 区提出。

• 关于认真做好2024届本科生毕业论文（设计）答辩工作的通知
• 支持打印模式、课程报告模式。

欢迎提交 Pull Request。

• bsThesisWHU
• HUSTPaperTemp
• TJU-thesis-template
• xdba-thesis
• NEUBachelorThesis