You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cyberduck displays several texts containing units: bytes, MB, KB, MB/sec (in Transfers window).
But some languages don't use "bytes" as standard word for that unit (for instance it's octets in French, abbreviated with o in ko, Mo, Go). And some languages follow more closely the International System of Units abbreviations (https://en.wikipedia.org/wiki/International_System_of_Units#Units_and_prefixes), and avoid "sec" for "s", or avoid uppercase "K" for lowercase "k".
So, 3 additional localizable strings would be nice in order to make Cyberduck software use those base strings to build all the correct texts based on the basic texts. For instance, in French:
"bytes" -> "octets"
"B" -> "o"
"sec" -> "s"
Note1: Cyberduck use "MB/s" in Bandwitdh preferences, but displays "MB/sec in the Transfers window
Note2: These only 3 strings do not solve the problem of displaying "K" instead of "k" for prefix kilo.
The text was updated successfully, but these errors were encountered:
Hello,
Cyberduck displays several texts containing units: bytes, MB, KB, MB/sec (in Transfers window).
But some languages don't use "bytes" as standard word for that unit (for instance it's octets in French, abbreviated with o in ko, Mo, Go). And some languages follow more closely the International System of Units abbreviations (https://en.wikipedia.org/wiki/International_System_of_Units#Units_and_prefixes), and avoid "sec" for "s", or avoid uppercase "K" for lowercase "k".
So, 3 additional localizable strings would be nice in order to make Cyberduck software use those base strings to build all the correct texts based on the basic texts. For instance, in French:
"bytes" -> "octets"
"B" -> "o"
"sec" -> "s"
Note1: Cyberduck use "MB/s" in Bandwitdh preferences, but displays "MB/sec in the Transfers window
Note2: These only 3 strings do not solve the problem of displaying "K" instead of "k" for prefix kilo.
The text was updated successfully, but these errors were encountered: