GNU gettext - Bugs: bug #49598, Allow ngettext to be used with...
You are not allowed to post comments on this tracker with your current authentication level.
bug #49598: Allow ngettext to be used with non-English source language with more than two plural forms
Submitter: | None | ||
Submitted: | Mon 14 Nov 2016 08:49:15 AM UTC | ||
Category: | Other | Severity: | 3 - Normal |
Item Group: | None | Status: | Not a Bug |
Privacy: | Public | Assigned to: | haible |
Open/Closed: | Closed |
Fri 01 Sep 2017 10:50:30 PM UTC, comment #5: |
Serhiy Zahoriya <int_ua> |
Mon 28 Aug 2017 06:46:34 PM UTC, comment #4: Serhiy,
|
Bruno Haible <haible> |
Mon 28 Aug 2017 02:32:18 PM UTC, comment #3: I understand that it can be quite a challenge to implement and that you have limited resources. I guess that you don't want to support it because you don't know any language with 3+ plural forms. Maybe it's not the best place to discuss it because it's a feature request / wishlist item and not really a bug.
|
Serhiy Zahoriya <int_ua> |
Tue 15 Nov 2016 08:44:33 AM UTC, comment #2: Thanks for the follow up, Bruno. Closing. |
Daiki Ueno <ueno> |
Mon 14 Nov 2016 04:46:27 PM UTC, comment #1: If you are using GNU gettext with a non-English source language, you are not doing yourself a favour. How would you find translators? You need to either have translators from your language to many languages of the world - which you will have difficulty to find -, or you need a two-step translation process, where one translator first translates to English and the other translators then go from English to the target language - but this process produces many wrong and ambiguous translations.
|
Bruno Haible <haible> |
Mon 14 Nov 2016 08:49:15 AM UTC, original submission:
Currently, if I use ngettext there is no way to specify all plural forms for non-English source language.
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-11-27 | haible | Category | None | Other | |
2016-11-15 | ueno | Status | None | Not a Bug | |
Assigned to | None | haible | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-758e.
Corresponding source code
But I've already described a project and added a detailed explanation on why it's more problematic with English as main language. Maybe the only detail left is that it's a Django project.
In short: there are projects now that use gettext and may not even have English in supported languages. At least it's some local web projects on Django.
About the first part of comment 4: I was just trying to put myself in your shoes, respect your time, appreciate your work, etc.