# 某些翻译键缺少复数形式

**URL:** https://meta.discourse.org/t/missing-plural-on-some-translation-keys/108198
**Category:** Translations
**Created:** [2019年二月2日 08:48 UTC](https://meta.discourse.org/t/missing-plural-on-some-translation-keys/108198 "2019-02-02T08:48:24Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Lure](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lure/32/130462_2.png) [@Lure](https://meta.discourse.org/u/Lure)
#### Post date: [2019年二月2日 08:48 UTC](https://meta.discourse.org/t/missing-plural-on-some-translation-keys/108198/1 "2019-02-02T08:48:24Z")

</div>

I am finalizing plurals for Slovenian and have noticed that in mobile view, the total number of topics is listed for “all time” and “last week.”

 ![Screenshot_20190202-094309~2](https://global.discourse-cdn.com/meta/original/3X/5/c/5ccf76e9056781d6608d3a054d3665b1239ff06d.png)

The problem is that these two keys, `all_time` and `week`, do not have plurals enabled, making it impossible to formulate them correctly for Slovene.

---

<div class="post-metadata">

### Author: ![Lure](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lure/32/130462_2.png) [@Lure](https://meta.discourse.org/u/Lure)
#### Post date: [2019年二月2日 17:18 UTC](https://meta.discourse.org/t/missing-plural-on-some-translation-keys/108198/3 "2019-02-02T17:18:56Z")

</div>

As a workaround, I can use the generic “skupaj” (most similar to “total” in English); however, for `week` it is harder, as it is also used in the desktop view in the following form:

 ![image](https://global.discourse-cdn.com/meta/original/3X/6/e/6e31da56c46d690b4e1a4c3bb60fecac1765bd81.png)

Here it is used as “3 per/this week”, right? While in mobile use, it is without the slash, making it inconsistent.

---

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [2019年二月2日 19:16 UTC](https://meta.discourse.org/t/missing-plural-on-some-translation-keys/108198/4 "2019-02-02T19:16:01Z")

</div>

No worries. I’ll look into it. 😉

---

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [2019年五月22日 20:41 UTC](https://meta.discourse.org/t/missing-plural-on-some-translation-keys/108198/5 "2019-05-22T20:41:53Z")

</div>

> [@Lure](#):
>
> Here it is used as “3 per/this week”, right? While in mobile use it is without /, making it inconsistent.

By now both desktop and mobile use a slash to display the number of new topics in the past week.

Mobile: ![image](https://global.discourse-cdn.com/meta/original/3X/4/6/4604f355377e76a49f7ebf1dd2b13a5d6a872198.png)  
Desktop: ![image](https://global.discourse-cdn.com/meta/original/3X/4/f/4fb5606a79d4bb7458f2a65d69aa5db15dd3579c.png)

I have an ongoing task on my list to eradicate concatenated strings from our codebase, because not including things like full stops or a slash in translations is bad practice. So I’m definitely going to make some changes here. I’m just not sure how much change is needed yet.

@Lure Would you translate “\<number\> / week” differently depending on the number? The same goes for “\<number\> / month” and “\<number\> total”. I’m trying to figure out if pluralization is actually needed or not.

---

<div class="post-metadata">

### Author: ![Lure](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lure/32/130462_2.png) [@Lure](https://meta.discourse.org/u/Lure)
#### Post date: [2019年五月23日 03:56 UTC](https://meta.discourse.org/t/missing-plural-on-some-translation-keys/108198/6 "2019-05-23T03:56:11Z")

</div>

> [@gerhard](#):
>
> @Lure Would you translate “ / week” differently depending on the number? The same goes for “ / month” and “ total”. I’m trying to figure out if pluralization is actually needed or not.

No, in 🇸🇮 we do not need pluralization here. Ensuring that concatenation does not happen in code will help greatly as it provides necessary context and flexibility in reordening to translator.