public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: Michael Tremer <michael.tremer@ipfire.org>,
	Bernhard Bitsch <bbitsch@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: [PATCH] Translated using Weblate (German)
Date: Thu, 19 Feb 2026 18:26:51 +0100	[thread overview]
Message-ID: <27b80383-1942-4199-803a-67280b9437a8@ipfire.org> (raw)
In-Reply-To: <0A773C0D-D759-4930-9449-76AA62187AAF@ipfire.org>

Hi All,

On 19/02/2026 17:52, Michael Tremer wrote:
> Hello,
> 
>> On 19 Feb 2026, at 16:49, Bernhard Bitsch <bbitsch@ipfire.org> wrote:
>>
>> Hello Michael,
>>
>> First a short explanation. I discovered IPFire Translate while reading a community thread and just tried to discover the purpose and using.
>>
>> The units for data amount are Bit and Byte, which give the transfer rates Bit/second an Byte/second.
>> Your example shows the memory usage graph ( measured in Byte ).
>> To be exact, the unit of the graph should read 'Byte'.
>>
>> I know, that the terminology isn't that exactly in IPFire. But couldn't change this step by step? ;)
> 
> This is why we are having this conversation.
> 
> It should then, however, be changed in the code first.
> 
> Strictly the word “Bytes” should be “Bytes” in German, too. Plural to plural. There should be a singular string as well which should have been used in the first place.
> 
> So, I will change the code. Do we all agree it should be Byte and “Bit Per Second”?

No I don't agree with that.

With the full word Byte would only apply when it is one byte. More than One Byte becomes Bytes. Same with Bit and Bits.

Now if you are using the abbreviation of MBps then for 1 MBps it is One Mega Byte per second but for 10 MBps it means Ten Mega Bytes per second.

The same occurs with 1 Mbps and 10 Mbps for the bits situation.

If you want the German language one to show Byte and Bit for both singular and plural then that is your language and I don't know it well enough to comment but for English it should be Bytes and Bits or KBytes and KBits or MBytes and MBits.

Quick search for multiple Bytes or Bits always calls them Bytes and Bits and bot Byte and Bit.

Regards,

Adolf.

> 
> -Michael
> 
>> BR
>> Bernhard
>>
>> Am 19.02.2026 um 17:11 schrieb Michael Tremer:
>>> Hello Bernhard,
>>> Thank you for helping to improve the translation of telemetry.
>>> I think you are intending to change any units to singular which grammatically would be correct.
>>> However, the “Bytes” thing is potentially confusing:
>>>   https://git.ipfire.org/?p=telemetry.git;a=blob;f=src/daemon/graph.c;hb=00b4fd6e254508cf958fa0144d2e2722a93b479d#l567
>>> So this is being used on the left hand side of the graphs in the legend. Screenshot attached.
>>> Intuitively I would have chosen “Bytes”. This is just a feeling.
>>> However, if we want to change all those units to singular, we should not only do this in German, but in English, too. I assume that these parts of the grammar are the same.
>>> -Michael
>>>> On 18 Feb 2026, at 07:40, IPFire Translate <translate@ipfire.org> wrote:
>>>>
>>>> From: Bernhard Bitsch <bernhard.bitsch@ipfire.org>
>>>>
>>>> Currently translated at 83.3% (70 of 84 strings)
>>>>
>>>> Translation: Telemetry/Telemetry
>>>> Translate-URL: https://translate.ipfire.org/projects/telemetry/telemetry/de/
>>>> ---
>>>> po/de.po | 6 +++---
>>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/po/de.po b/po/de.po
>>>> index cb36fd0..a6c180f 100644
>>>> --- a/po/de.po
>>>> +++ b/po/de.po
>>>> @@ -11,7 +11,7 @@ msgstr ""
>>>> "Report-Msgid-Bugs-To: \n"
>>>> "POT-Creation-Date: 2025-11-11 21:26+0000\n"
>>>> "PO-Revision-Date: 2026-02-17 17:45+0000\n"
>>>> -"Last-Translator: Amazon Translate <noreply-mt-aws@weblate.org>\n"
>>>> +"Last-Translator: Bernhard Bitsch <bernhard.bitsch@ipfire.org>\n"
>>>> "Language-Team: German <https://translate.ipfire.org/projects/telemetry/"
>>>> "telemetry/de/>\n"
>>>> "Language: de\n"
>>>> @@ -22,10 +22,10 @@ msgstr ""
>>>> "X-Generator: Weblate 5.15.2\n"
>>>>
>>>> msgid "Bits Per Second"
>>>> -msgstr "Bits pro Sekunde"
>>>> +msgstr "Bit pro Sekunde"
>>>>
>>>> msgid "Bytes"
>>>> -msgstr "Bytes"
>>>> +msgstr "Byte"
>>>>
>>>> msgid "Days"
>>>> msgstr "Tage"
>>>> -- 
>>>> 2.47.3
>>>>
>>>>
>>
>>
> 
> 



  reply	other threads:[~2026-02-19 17:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-18  7:40 IPFire Translate
2026-02-18  7:40 ` IPFire Translate
2026-02-19 16:11   ` Michael Tremer
2026-02-19 16:41     ` Adolf Belka
2026-02-19 16:49     ` Bernhard Bitsch
2026-02-19 16:52       ` Michael Tremer
2026-02-19 17:26         ` Adolf Belka [this message]
2026-02-20 11:02           ` Michael Tremer
2026-02-20 11:48             ` Bernhard Bitsch
  -- strict thread matches above, loose matches on Subject: below --
2026-04-11  7:37 IPFire Translate
2026-04-11  7:37 ` IPFire Translate
2026-04-11  7:37 IPFire Translate
2026-04-08  7:40 IPFire Translate
2026-03-28  7:38 IPFire Translate
2026-02-21  7:38 IPFire Translate
2026-02-19 19:13 IPFire Translate
2026-01-28  7:35 IPFire Translate
2026-01-27 15:41 IPFire Translate
2025-11-24  7:37 [PATCH] Deleted translation using Weblate (Catalan) IPFire Translate
2025-11-24  7:37 ` [PATCH] Translated using Weblate (German) IPFire Translate
2025-11-24  7:37 ` IPFire Translate
2025-11-24  7:37 ` IPFire Translate

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27b80383-1942-4199-803a-67280b9437a8@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=bbitsch@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=michael.tremer@ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox