*h2RSrSSKJrJrJr SSKrSSKrSSKrSSKrSSK r \RRS:a\ r \ rSSKJr SSKJr O\rSSKJr \R,"\5rSSKJr S S KJrJrJrJrJ r J!r!J"r" S S K#J$r$ 0r%SS jr&S r'\RP"\'S9r)SSjr*g)u The `latexencode` module provides a set of routines that allows you to convert a unicode string to LaTeX escape sequences. For basic usage you can use the :py:func:`unicode_to_latex()` function directly:: >>> from pylatexenc.latexencode import unicode_to_latex >>> print(unicode_to_latex('À votre santé')) \`A votre sant\'e >>> print(unicode_to_latex('The length of samples #3 & #4 is 3μm')) The length of samples \#3 \& \#4 is 3\ensuremath{\mu}m The conversion is handled by the class :py:class:`UnicodeToLatexEncoder`. If you are converting multiple strings, you may create an instance with the flags you like and invoke its method :py:meth:`~UnicodeToLatexEncoder.unicode_to_latex()` as many times as necessary:: >>> from pylatexenc.latexencode import UnicodeToLatexEncoder >>> u = UnicodeToLatexEncoder(unknown_char_policy='replace') >>> print(u.unicode_to_latex('À votre santé')) \`A votre sant\'e >>> print(u.unicode_to_latex('The length of samples #3 & #4 is 3μm')) The length of samples \#3 \& \#4 is 3\ensuremath{\mu}m >>> print(u.unicode_to_latex('À votre santé: 乾杯')) No known latex representation for character: U+4E7E - ‘乾’ No known latex representation for character: U+676F - ‘杯’ \`A votre sant\'e: {\bfseries ?}{\bfseries ?} Example using custom conversion rules:: >>> from pylatexenc.latexencode import UnicodeToLatexEncoder, \ ... UnicodeToLatexConversionRule, RULE_REGEX >>> u = UnicodeToLatexEncoder( ... conversion_rules=[ ... UnicodeToLatexConversionRule(rule_type=RULE_REGEX, rule=[ ... (re.compile(r'-->'), r'\\textrightarrow'), ... (re.compile(r'<--'), r'\\textleftarrow'), ... ]), ... 'defaults' ... ] ... ) >>> print(u.unicode_to_latex("Cheers --> À votre santé")) Cheers {\textrightarrow} \`A votre sant\'e See :py:class:`UnicodeToLatexEncoder` and :py:class:`UnicodeToLatexConversionRule`. Note for regex rules, the replacement text is expanded like the second argument of `re.sub()` and backslashes need to be escaped even inside raw strings. .. versionadded:: 2.0 The class :py:class:`UnicodeToLatexEncoder` along with its helper functions and classes were introduced in `pylatexenc 2.0`. The earlier function :py:func:`utf8tolatex()` that was available in `pylatexenc 1.x` is still provided unchanged, so code written for `pylatexenc 1.x` should work without changes. New code is however strongly encouraged to employ the new API. )print_functionabsolute_importunicode_literalsN)MappingProxyType)getfullargspec) getargspec)_util)get_builtin_uni2latex_dict RULE_DICT RULE_REGEX RULE_CALLABLEUnicodeToLatexConversionRuleget_builtin_conversion_rulesUnicodeToLatexEncoder)PartialLatexToLatexEncodercXUU4nU[;a [UnO[UUUUS9nU[U'URU5$)a` Shorthand for constructing a :py:class:`UnicodeToLatexEncoder` instance and calling its :py:meth:`~UnicodeToLatexEncoder.unicode_to_latex()` method. The :py:class:`UnicodeToLatexEncoder` instances for given option settings are cached, making repeated calls to :py:func:`unicode_to_latex()` possible without creating a new instance upon each call. The parameters `non_ascii_only`, `replacement_latex_protection`, `unknown_char_policy`, and `unknown_char_warning` are directly passed on to the :py:class:`UnicodeToLatexEncoder` constructor. See the class doc for :py:class:`UnicodeToLatexEncoder` for more information about what they do. You may only use arguments to this function that are python hashable (like `True`, `False`, or simple strings) to help us keep a cache of previously constructed :py:class:`UnicodeToLatexEncoder` instances. For instance, it is not possible to provide a callable to `unknown_char_policy`. It is also not possible to specify custom conversion rules with this helper function. If you need any of these features, simply create a :py:class:`UnicodeToLatexEncoder` instance directly. )non_ascii_onlyreplacement_latex_protectionunknown_char_policyunknown_char_warning)_u2l_obj_cacherunicode_to_latex)srrrrkeyus \/home/mande/repo/quber/.venv/lib/python3.13/site-packages/pylatexenc/latexencode/__init__.pyrrs[0 9L  !C n 3  !?[6I7K M s  a  c.SSKJn UR5$)Nr ) uni2latex) _uni2latexmapr!copy) _uni2latexs r_get_deprecated_utf82latexr%s"7 ?? r)generate_dict_fnc[U5n[R"SU5nU(dgSnUHnU(a[U5S:aXV- nM[R [U5S5nUbXR(aUSSS:XaSU-S -OU- nM_[U5S :a[U5S::dUS ;aXV- nMS [U5U4-nU(a [ U5e[RU5 U(aUS - nMXV- nM U$)u< .. note:: Since `pylatexenc 2.0`, it is recommended to use the the :py:func:`unicode_to_latex()` function or the :py:class:`UnicodeToLatexEncoder` class instead of the earlier function `utf8tolatex()`. The new routines provide much more flexibility and versatility. For instance, you can specify custom escape sequences for certain characters. Some cheap benchmarks seem to indicate that the new routines are not significantly slower than the `utf8tolatex()` function. Also, the name `utf8tolatex()` was poorly chosen, since the argument is in fact not 'utf-8'-encoded but rather a Python unicode string object. The function `utf8tolatex()` is still provided unchanged from `pylatexenc 1.x`. We do not plan to remove this function in the near future so it is not (yet) considered as deprecated and we will continue to provide it in near future versions of `pylatexenc`. Bug reports, improvements, and new features will however be directed to :py:func:`UnicodeToLatexEncoder()`. Encode a UTF-8 string to a LaTeX snippet. If `non_ascii_only` is set to `True`, then usual (ascii) characters such as ``#``, ``{``, ``}`` etc. will not be escaped. If set to `False` (the default), they are escaped to their respective LaTeX escape sequences. If `brackets` is set to `True` (the default), then LaTeX macros are enclosed in brackets. For example, ``santé`` is replaced by ``sant{\'e}`` if `brackets=True` and by ``sant\'e`` if `brackets=False`. .. warning:: Using `brackets=False` might give you an invalid LaTeX string, so avoid it! (for instance, ``maître`` will be replaced incorrectly by ``ma\^\itre`` resulting in an unknown macro ``\itre``). If `substitute_bad_chars=True`, then any non-ascii character for which no LaTeX escape sequence is known is replaced by a question mark in boldface. Otherwise (by default), the character is left as it is. If `fail_bad_chars=True`, then a `ValueError` is raised if we cannot find a character substitution for any non-ascii character. .. versionchanged:: 1.3 Added `fail_bad_chars` switch NFCNrr \{} z z5Character cannot be encoded into LaTeX: U+%04X - `%s'z {\bfseries ?}) unicode unicodedata normalizeord utf82latexget ValueErrorloggerwarning) rrbracketssubstitute_bad_charsfail_bad_charsresultchlchmsgs r utf8tolatexr?sd  AeQ'A  F s2w} LF..R$/CHQqT9ISWS[ $r7b=SW^> ORUVXRY[]Q^^!$S/)s#'..FLF9< Mr)FbraceskeepT)FTFF)+__doc__ __future__rrrr0loggingsys functools itertools version_infomajorstrr/ basestringtypesr_MappingProxyTypeinspectrdictr getLogger__name__r6r)r _unicode_to_latex_encoderr r rrrrr_partial_latex_encoderrrrr%LazyDictr3r?rrrVs4;zIH AGJ;&4   8 $ LTFJ$!\*^^-G H 8NS$Wr