1. 08 Jan, 2023 5 commits
  2. 04 Jan, 2023 6 commits
  3. 07 Dec, 2022 6 commits
    • Lubomir Rintel's avatar
      mobile-providers: fall back to <name> if country has no ISO 3166-1 code · 7dc7d30d
      Lubomir Rintel authored
      We use the iso-codes database to get a nice country name for a level 1
      (country) alpha-2 (two-letter) code used in the mobile-broadband-database.
      This generally works well, as the areas where mobile providers operate
      generally have ISO 3166-1 codes assigned. That is, all but Kosovo.
      
      The mobile-broadband-database uses the "user-assigned" "xk" code for
      Kosovo, like many countries and international organizations alike use.
      This, unfortunatelly, means that we can't use iso-codes to get the full
      name.
      
      We could, in theory, use the level 2 code "rs-km", which places the area
      inside the Republic of Serbia. That would not affect how we structure
      things, but would require us to load the level 2 (districts) database that
      is considerably larger than level 1 (countries). Also, the naming in the
      iso-codes database is a little confusing at the moment (see
      https://salsa.debian.org/iso-codes-team/iso-codes/-/merge_requests/29).
      
      Instead, let's allow including a human-readable name in the database itself
      like this:
      
        <country>
          <name>...<name>
          <provider>
          ...
      
      The name serves as a fallback. It stays in English and is not
      translated, but still better than nothing I suppose.
      
      Related mobile-broadband-providers change:
      mobile-broadband-provider-info!90
      7dc7d30d
    • Lubomir Rintel's avatar
      mobile-providers: hardwire Kosovo · 0ae9d003
      Lubomir Rintel authored
      We use the iso-codes database to get a nice country name for a level 1
      (country) alpha-2 (two-letter) code used in the mobile-broadband-database.
      This generally works well, as the areas where mobile providers operate
      generally have ISO 3166-1 codes assigned. That is, all but Kosovo.
      
      The mobile-broadband-database uses the "user-assigned" "xk" code for
      Kosovo, like many countries and international organizations alike use.
      This, unfortunatelly, means that we can't use iso-codes to get the full
      name.
      
      We could, in theory, use the level 2 code "rs-km", which places the area
      inside the Republic of Serbia. That would not affect how we structure
      things, but would require us to load the level 2 (districts) database that
      is considerably larger than level 1 (countries). Also, the naming in the
      iso-codes database is a little confusing at the moment (see
      https://salsa.debian.org/iso-codes-team/iso-codes/-/merge_requests/29).
      
      Let's just make sure Kosovo is always there until ISO makes its mind up.
      0ae9d003
    • Lubomir Rintel's avatar
    • Lubomir Rintel's avatar
      tests/mobile-wizard: print the details of a chosen operator · abe88fd3
      Lubomir Rintel authored
      This helps us ensure the mobile wizard returns the correct results.
      abe88fd3
    • Lubomir Rintel's avatar
      mobile-providers: fix path for iso_3166 translations · 6f393a70
      Lubomir Rintel authored
      We were looking for them in /usr/locale instead of /usr/share/locale.
      
      That said, /usr/share/locale still might not be an entirely correct path
      for the iso-codes installation, because the iso-codes files are looked
      for in other directories than the global /usr.
      
      Let's look for the translations in the same prefix as the xml files
      themselves.
      6f393a70
    • Lubomir Rintel's avatar
      tests/mobile-wizard: set gettext domain · aba6d99d
      Lubomir Rintel authored
      This helps us make check that the translations work properly.
      aba6d99d
  4. 30 Nov, 2022 4 commits
  5. 22 Nov, 2022 4 commits
    • Lubomir Rintel's avatar
      po: fix metadata in many .po files · 3076167a
      Lubomir Rintel authored
      It's probably an uphill battle against translator tast to keep this
      too tidy, but let's at least obviously wrong things. These include:
      bogus copytight notices, untemplated things, wrong project name.
      
      The motivation behind this is that some of the gunk left behind (such as
      old branch names) don't meet our conscious language standards.
      3076167a
    • Lubomir Rintel's avatar
      po: remove obsolete strings · 5d591574
      Lubomir Rintel authored
      Done with "msgattrib --no-obsolete".
      
      This drops a fairly large amount of strings inherited from
      network-manager-applet.
      
      The motivation behind this is to get rid of strings that don't meet
      our conscious language standards.
      5d591574
    • Lubomir Rintel's avatar
      po: update-po · b263f4aa
      Lubomir Rintel authored
      b263f4aa
    • Lubomir Rintel's avatar
      gitlab: fix main branch name · 8fe405a7
      Lubomir Rintel authored
      8fe405a7
  6. 08 Nov, 2022 1 commit
  7. 07 Nov, 2022 4 commits
    • Lubomir Rintel's avatar
      5bbc349c
    • Lubomir Rintel's avatar
      release: bump version to 1.10.4 · ec11ca12
      Lubomir Rintel authored
      ec11ca12
    • Lubomir Rintel's avatar
      build: unbreak build with gcr-3.92 · 2116cbd2
      Lubomir Rintel authored
      Newer gcr pre-release removed the widgets and therefore the library is
      not reliant on Gtk anymore, no matter which version. That's good -- we
      were only using the GcrCertificate, not the widgets.
      
      Details here:
      gcr#100
      
      In fact, we weren't even needing the UI part of gcr-3, just the
      gcr-base-3 part. That would've not conflicted with Gtk4.
      
      This allows use to simplify things considerably: both gcr-base-3 and
      gcr-4 are fine for use for either Gtk3 or Gtk4.
      
      !43
      2116cbd2
    • Lubomir Rintel's avatar
      gschema: split org.gnome.nm-applet.eap off · 91661643
      Lubomir Rintel authored
      In commit 50cda26a ('gschema: move "org.gnome.nm-applet.gschema.xml"
      from network-manager-applet to libnma'), this schema was moved over from
      nm-applet even though all we need is "org.gnome.nm-applet.eap".
      
      That's rather unfortunate, because it's sort of difficult to undo
      without breaking some versions of nm-connection-editor.
      
      Let's split off the part we need (org.gnome.nm-applet.eap), but keep the
      other half (org.gnome.nm-applet) in place for now, until we give
      nm-applet users a chance to upgrade to a version that has has it.
      
      Packagers can just choose to remove the file (e.g. %ignore in RPM) and
      ensure their nm-applet is new enough.
      
      !42
      91661643
  8. 09 Sep, 2022 4 commits
  9. 08 Sep, 2022 2 commits
  10. 07 Sep, 2022 4 commits