mirror of
https://github.com/docling-project/docling-parse.git
synced 2026-05-17 13:10:49 +00:00
Eric Van Boxsom
e56632d962
Signed-off-by: Eric Van Boxsom <14831976+evb87-tech@users.noreply.github.com>
43 lines
1.6 KiB
Python
43 lines
1.6 KiB
Python
"""docling-parse: Extract text with coordinates from programmatic PDFs."""
|
|
|
|
import locale as _locale
|
|
import logging as _logging
|
|
|
|
_log = _logging.getLogger(__name__)
|
|
|
|
|
|
def _ensure_safe_numeric_locale() -> None:
|
|
"""Ensure LC_NUMERIC uses a period as decimal separator.
|
|
|
|
PDF coordinate parsing (both in QPDF's C library and in this
|
|
package's C++ layer) relies on '.' as the decimal separator.
|
|
Locales that use ',' (French, German, Portuguese, etc.) silently
|
|
corrupt every floating-point value extracted from a PDF.
|
|
|
|
This function is called at import time as a defence-in-depth
|
|
measure. The primary fix is in the C++ layer (from_chars), but
|
|
this protects against any locale-sensitive path we may have missed
|
|
— including QPDF's own atof() calls that we cannot patch.
|
|
|
|
See: https://github.com/docling-project/docling/issues/1455
|
|
"""
|
|
try:
|
|
current = _locale.getlocale(_locale.LC_NUMERIC)
|
|
# setlocale returns the *actual* locale string; checking the
|
|
# decimal point via localeconv is the most reliable test.
|
|
conv = _locale.localeconv()
|
|
if conv.get("decimal_point", ".") != ".":
|
|
_locale.setlocale(_locale.LC_NUMERIC, "C")
|
|
_log.info(
|
|
"docling-parse: overrode LC_NUMERIC from %s to 'C' "
|
|
"to prevent PDF coordinate corruption",
|
|
current,
|
|
)
|
|
except (_locale.Error, ValueError):
|
|
# If we can't query or set the locale, the C++ from_chars
|
|
# layer will still protect us.
|
|
pass
|
|
|
|
|
|
_ensure_safe_numeric_locale()
|