| 1 |
# THE POLYGLOSSIA PACKAGE v2.10 |
| 2 |
## Multilingual typesetting with XeLaTeX and LuaLaTeX |
| 3 |
|
| 4 |
This package provides an alternative to Babel for users of XeLaTeX and LuaLaTeX. |
| 5 |
This version includes support for over 80 different languages, some of which in |
| 6 |
different regional or national varieties, or using a different writing system. |
| 7 |
|
| 8 |
Polyglossia makes it possible to automate the following tasks: |
| 9 |
|
| 10 |
* Loading the appropriate hyphenation patterns. |
| 11 |
* Setting the script and language tags of the current font (if possible and |
| 12 |
available), using the package fontspec. |
| 13 |
* Switching to a font assigned by the user to a particular script or language. |
| 14 |
* Adjusting some typographical conventions in function of the current language |
| 15 |
(such as afterindent, frenchindent, spaces before or after punctuation marks, |
| 16 |
etc.). |
| 17 |
* Redefining the document strings (like “chapter”, “figure”, “bibliography”). |
| 18 |
* Adapting the formatting of dates (for non-gregorian calendars via external |
| 19 |
packages bundled with polyglossia: currently the Hebrew, Islamic and Farsi |
| 20 |
calendars are supported). |
| 21 |
* For languages that have their own numeration system, modifying the formatting |
| 22 |
of numbers appropriately. |
| 23 |
* Ensuring the proper directionality if the document contains languages |
| 24 |
written from right to left (via the packages bidi and luabidi, available |
| 25 |
separately). |
| 26 |
|
| 27 |
# LICENCE |
| 28 |
|
| 29 |
Copyright (c) 2008-2010 François Charette, 2013 Élie Roux, 2011-2026 Arthur Reutenauer, |
| 30 |
Copyright (c) 2019-2023 Bastien Roucariès, 2019-2026 Jürgen Spitzmüller, 2023-2026 Udi Fogiel |
| 31 |
|
| 32 |
Except where otherwise noted, Polyglossia is placed under the terms of the MIT licence |
| 33 |
(https://opensource.org/licenses/MIT). |
| 34 |
|
| 35 |
# BUGS |
| 36 |
|
| 37 |
If you run into a bug, or suspect you do, or you have a request or comment, please |
| 38 |
use the issue tracker: https://codeberg.org/polyglossia/polyglossia/issues |
| 39 |
|
| 40 |
This is more efficient than contacting the maintainer by email as it allows us |
| 41 |
to track the issues and follow progress. |