Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#23989 closed Bug (invalid)

Korean translation of timesince filter is wrong.

Reported by: JuneHyeon Bae Owned by: JuneHyeon Bae
Component: Translations Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: yes

Description

Current version ignore all time units (eg: "16 minutes" will be translate into "16". It should be "16 분"(boon)).
This problem shall break localization of | timesince filter.

Change History (8)

comment:1 by JuneHyeon Bae, 9 years ago

Status: newassigned

comment:2 by Tim Graham, 9 years ago

Resolution: invalid
Severity: Release blockerNormal
Status: assignedclosed

Thanks for the report, but translations are handled at Transifex. See https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#translations.

comment:3 by Claude Paroz, 9 years ago

As this is rather serious, I'm available to commit a fix after the corresponding strings are fixed in Transifex. devunt, can you ping me when those strings are fixed in Transifex?

in reply to:  3 comment:4 by JuneHyeon Bae, 9 years ago

Replying to claudep:

As this is rather serious, I'm available to commit a fix after the corresponding strings are fixed in Transifex. devunt, can you ping me when those strings are fixed in Transifex?

Translation fixed in Transifex. Thank you.

comment:5 by Claude Paroz <claude@…>, 9 years ago

In eb632bfba51263f9a91e1699be25dac7b7bab53e:

[1.7.x] Fixed timesince translations for Korean

Refs #23989.

comment:6 by Claude Paroz <claude@…>, 9 years ago

In 9495989265306b773fdc7f6ac8d6739c7e294444:

Fixed timesince translations for Korean

Refs #23989.
Forward port of eb632bfba from stable/1.7.x.

comment:7 by JuneHyeon Bae, 9 years ago

I'm sorry but I missed one translation. By the way, this one is not urgent, but little important.

Version 1, edited 9 years ago by JuneHyeon Bae (previous) (next) (diff)

comment:8 by Claude Paroz, 9 years ago

Your latest fix will be integrated automatically with Django 1.8 through the normal translation workflow.

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