Hello, the translation of the string "GB" (gigabyte) is used also for the ISO 3166 code of the United Kingdom (GB).
translation where ? "GB" is short for gigabyte according to JEDEC and METRIC standard of course if one want to follow IEC, then it would be GiB
(In reply to Thomas Backlund from comment #1) > translation where ? > > > "GB" is short for gigabyte according to JEDEC and METRIC standard > > of course if one want to follow IEC, then it would be GiB The translation is in: MCC > Software management > Configure media sources for install and update > File menu > Add a specific media mirror.
Created attachment 12088 [details] Screenshot of the problem (ג״ב is the short form to write "gigabyte" in Hebrew)
CC: (none) => omeritzicschwartz
Product: Infrastructure => MageiaCC: (none) => ouaurelienTarget Milestone: --- => Mageia 8Assignee: sysadmin-bugs => bugsquadVersion: unspecified => CauldronComponent: Others => RPM Packages
This is a translation issue. Yuri, can you check this, please?
Source RPM: (none) => drakxtoolsAssignee: bugsquad => i18n-bugs
Summary: The translation of GB (gigabyte) is used for the ISO 3166 code of UK => Wrong translation in Country selection mirrorlist
(In reply to Aurelien Oudelet from comment #4) > This is a translation issue. > Yuri, can you check this, please? As I remember, we use the third-party Perl module for this and these units are untranslatable everywhere in the drak-tools (e.g. in the update windows). I will try to see what can be done.
CC: (none) => yurchorSummary: Wrong translation in Country selection mirrorlist => The translation of GB (gigabyte) is used for the ISO 3166 code of UK
Hello Omer, Do you expect that these codes will be translated, transcribed or stay in latin characters?
CC: (none) => yves.brungard_mageia
(In reply to papoteur from comment #6) > Hello Omer, > Do you expect that these codes will be translated, transcribed or stay in > latin characters? These codes should stay in latin characters.
Created attachment 12104 [details] Proposed patch to rpmdrake The patch that solves the problem for me. Sorry for the delay caused by my misreading the problem description.
Thanks Yuri. Should be fine.
Pushed as 2139bccf
Resolution: (none) => FIXEDStatus: NEW => RESOLVED