Opened 3 weeks ago

Closed 12 days ago

Last modified 12 days ago

#37333 closed Cleanup/optimization (invalid)

Include language de_ch in language info

Reported by: Reto Fahrni Owned by: VIZZARD-X
Component: Internationalization Version: 6.1
Severity: Normal Keywords: l10n, localization
Cc: Reto Fahrni, Claude Paroz, Annabelle Wiegart Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The language de_CH actually exists in conf/locale, but there is no language info in conf/locale/init.py.

Background: The automatic detection of the language fails if there is no entry in init.py. Additionally, providing a translated list of languages to the user is impossible without full manual override. The problems are described as well in https://code.djangoproject.com/ticket/32737. The problem was never solved since the requested languages were not official languages.
Since de_CH is an offical Django language, it should be ok to fix in the way proposed in ​https://github.com/django/django/pull/21100.

(Sorry, if this is not a proper ticket. I'm not (yet) used to provide input.)

Change History (6)

comment:1 by Nikita Kostenko, 3 weeks ago

I'll handle it

comment:2 by Nikita Kostenko, 3 weeks ago

Triage Stage: Unreviewed → Accepted

comment:3 by VIZZARD-X, 3 weeks ago

Owner: set to VIZZARD-X
Status: new → assigned

comment:4 by VIZZARD-X, 3 weeks ago

in reply to:  description comment:5 by Jacob Walls, 12 days ago

Cc: Claude Paroz Annabelle Wiegart added
Component: Uncategorized → Internationalization
Easy pickings: unset
Resolution: → invalid
Status: assigned → closed

Hi, thanks for following up with a ticket.

Replying to Reto Fahrni:

The language de_CH actually exists in conf/locale, but there is no language info in conf/locale/init.py.
...
Since de_CH is an offical Django language, ...

Looking closer, it appears that de_CH is a special case. It exists in conf/locale only for the purpose of providing alternative formats for number separators and the like. There is no LC_MESSAGES folder with translations underneath it.

Given that, I feel uncertain following the chain of reasoning that it should be included in LANG_INFO, following ticket:37237#comment:1. And if we did, what are the backward compatibility implications?

cc'ing other Swiss users who might be able to weigh in.

Btw, Vizzard, retfah already had a PR but just neglected to self-assign.

comment:6 by Reto Fahrni, 12 days ago

Sorry, I just don't know how to use the ticketing system correctly. I'm not used to it (yet).

Note: See TracTickets for help on using tickets.
Back to Top