ABOUT CATEGORIES ARCHIVE

Posts tagged with "i18n"

There are a total of 3 posts.

Handling Homonyms in Django Internationalization: Avoiding the "Polish" Tragedy with Contextual Markers

2026-01-13

Handling Homonyms in Django Internationalization: Avoiding the "Polish" Tragedy with Contextual Markers

This guide explains how to resolve translation conflicts in Django when the same word has multiple meanings. By using template `{% translate "…" context "…" %}` and Python `pgettext`, `pgettext_lazy`, `npgettext`, you add `msgctxt` to .po files, improving translation quality and maintainability.

#django #i18n #gettext #translation +3
Clearing Up the gettext vs gettext_lazy Confusion in Django (Understanding When Translation Happens)

2026-01-05

Clearing Up the gettext vs gettext_lazy Confusion in Django (Understanding When Translation Happens)

Clear up the confusion between Django’s `gettext` and `gettext_lazy`. Learn when to translate immediately versus lazily, avoid common pitfalls with module constants, model fields, and form labels, and master tools like `format_lazy` and `force_str` for robust i18n implementation.

#django #python #i18n #gettext_lazy +3

2025-01-16

Differences and Uses of get_language() and request.LANGUAGE_CODE in Django

Explore the differences and uses of get_language() and request.LANGUAGE_CODE in Django. Learn how to effectively manage multilingual support in your applications.

#django #get_language() #i18n