Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#1341 closed defect (fixed)

date formattings need to use technical message IDs

Reported by: hugo Owned by: hugo
Component: Internationalization Version:
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


The date names currently are used directly. This leads to conflicts between the different versions of "May" (AP-Version, short version, long version - all the same message-ID, but in different languages they might be different). This should be changed so that month names use MAY_SHORT, MAY_AP and MAY_LONG (and other month names accordingly). The 'en' translatio must carry the original values, so that if a language isn't available, the english translation kicks in.

One little problem: if people disable the english translation and only run one translation that doesn't include those technical IDs, they will see the IDs themselves. But they can just update the translation to include the correct month names, so this isn't a big problem.

Change History (3)

comment:1 Changed 13 years ago by hugo

Status: newassigned

comment:2 Changed 13 years ago by Adrian Holovaty

Is this still an issue? I don't understand the problem...

comment:3 Changed 13 years ago by Adrian Holovaty

Resolution: fixed
Status: assignedclosed

I assume this was fixed in [3055] and [3056].

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