# Generated by Makefile. Do not edit.

2026-01-26  Curtis Gedak <gedakc@gmail.com>

    ==========   gparted-1.8.0   ==========

2026-01-26  Curtis Gedak <gedakc@gmail.com>

    Update copyright years

2026-01-11  Baurzhan Muftakhidinov <baurthefirst@gmail.com>

    Update Kazakh translation

2025-08-24  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add widget hierarchy comments into DialogPasswordEntry constructor

2025-12-08  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Make Partition::m_flags private and provide necessary methods
    
    This member variable already has several methods querying and modifying
    it.  However it was also public and directly read and updated.  To be
    consistent make m_flags private and provide the necessary additional
    access and update methods.

2025-12-08  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Rename member variable to Partition::m_flags
    
    To prefix member variable name with m_.

2025-11-30  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add missing includes into Partition.h and .cc
    
    To applying the Include What You Use principle.  See this earlier commit
    for references [1].
    
    Partition.h
        #include <vector>            // For std::vector
    
    Partition.cc
        #include "Utils.h"           // For FS_UNALLOCATED
        #include <algorithm>         // For std::min()
        #include <vector>            // For std::vector
        #include <glibmm/ustring.h>  // For Glib::ustring
    
    [1] commit 3e689d9e563cb5372f64c801484b9e480fb18f87
        Add missing includes into Operation.h and .cc

2025-12-06  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Rename member variable to GParted_Core::m_all_libparted_flags
    
    Rename from 'flags' to give it a more meaningful name and prefix member
    variable with m_.  Also rename for loop counter variables to the
    normative 'i'.
    
    * Why do most of us use 'i' as a loop counter variable?
      https://softwareengineering.stackexchange.com/questions/86904/why-do-most-of-us-use-i-as-a-loop-counter-variable

2025-12-09  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Convert remaining calls to use get_lp_partition()
    
    When developing commit "Set LBA flag when creating extended partitions
    (#300)" set_partition_type() was newly handling extended partitions but
    was still directly calling ped_disk_get_partition_by_sector().  This
    resulted in GParted crashing when trying to set the partition type of an
    extended partition because it doesn't handle extended partitions.  This
    was resolved by calling GParted_Core::get_lp_partition() instead.
    
    None of the remaining direct calls to ped_disk_get_partition_by_sector()
    should ever have to handle extended partitions, so this change is not
    required, but for code consistency use GParted_Core::get_lp_partition()
    everywhere.  get_lp_partition() was added by commit [1].
    
    [1] commit 33a535390e00cf7de42ba2046e1a7093f426159f
        Extract common code into new method get_lp_partition()

2025-11-30  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Remove never reached return statement in GParted_Core::create()

2025-12-04  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Remove unnecessary comment from Dialog_Partition_Copy::get_new_partition()
    
    The comment and two associated lines of code were added by commit [1] on
    2004-09-25.  5 commits later [2] on the same day the first commented
    statement was removed.  So now the first clause of the comment is not
    applicable any more and the second clause "set status for partition" is
    just repeating exactly what can be seen from the remaining statement
    itself and adds no additional information.  Therefore remove.
    
    [1] commit 201fdcb8e8ee8587775b79544ee3ff4bb87d8cd6
        more i18n and some code cleanups
                //set proper name and status for partition
            //  selected_partition.partition = String::ucompose( _("copy from %1"), selected_partition .partition );
                selected_partition.status = GParted::STAT_COPY ;
    
    [2] commit 60b5bb29aad0c29c78df8784c61c8961eb624a8e
        removed commented statement (big deal huh:) )

2025-12-04  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Rename member functions to Dialog_*::get_new_partition()
    
    Change member function names to lower case to match the predominate
    "snake_case" [1] used for such names.
    
    [1] Naming convention (programming),
        Examples of multiple-word identifier formats
        https://en.wikipedia.org/wiki/Naming_convention_(programming)#Examples_of_multiple-word_identifier_formats

2025-12-06  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Clear all other flags when composing the operation in GParted (#300)
    
    Test case:
        Table   Partition num, FS, flag     Preview operation
        MSDOS   1   unknown      raid       Format to ext4
        GPT     1   linux-swap   swap       Paste fat16 into
        GPT     2   fat16        msftdata   Format to swap
    
    Preview of the format and paste into existing operations shows the
    existing partition flag being maintained, however when applied those
    flags are cleared and any new flags libparted uses to represent on-disk
    partition types are set.
    
    Make all operation which modify the partition flags behave the same.
    Make format and paste into existing preview as implemented and the same
    as create new and paste into new.  That all flags are cleared, other
    than any flag being explicitly set by GParted which might be one of:
    ESP, LVM or LBA.
    
    Closes #300 - Consider setting LBA flag for FAT32 primary partitions
                  automatically when needed

2025-12-06  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Clear all flags when setting partition type by fstype (#300)
    
    Here are several examples of the same issue.  Have an existing partition
    on the relevant table with the specified libparted flag set and apply
    the operation to that partition.
        Table   Partition num, FS, flag     Apply operation
        MSDOS   1   unknown      raid       Format to ext4
        GPT     1   linux-swap   swap       Paste fat16 into
        GPT     2   fat16        msftdata   Format to swap
    
    In each case after refresh the existing partition flag was maintained
    even though the the type of the new file system was set using libparted.
    This is because the libparted flags are overriding the request being
    made by setting the partition's file system type in setting the on-disk
    partition type.
    
    So far set_filesystem_type_using_fstype() only clears the ESP and LVM
    flags.  Fix this by clearing all libparted partition flags when setting
    the on-disk partition type by file system type.
    
    Closes #300 - Consider setting LBA flag for FAT32 primary partitions
                  automatically when needed

2025-11-27  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Set LBA flag when creating extended partitions (#300)
    
    Extended partitions on MSDOS tables still get created as type ID 0x05.
    As discussed in earlier commit "Set LBA flag for FAT16/32 file systems
    on MSDOS tables (#300)" the Parted command creates them with type ID
    0x0F "W95 Extended (LBA)".
    
    Set the LBA flag when creating extended partitions to get the partition
    type ID set to 0x0F.
    
    Updated operation details looks like:
        * Create Extended Partition #1 (extended, 64.00 MiB) on... (SUCCESS)
          * create empty partition                                 (SUCCESS)
    >>    * set partition type on /dev/sdb1                        (SUCCESS)
    >>        new partition flag: lba                              (SUCCESS)
    
    Closes #300 - Consider setting LBA flag for FAT32 primary partitions
                  automatically when needed

2025-12-04  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Set LBA flag when pasting FAT16/32 into new MSDOS partition (#300)
    
    Copy an existing FAT16/32 partition without the LBA flag set on an MSDOS
    drive into a new partition.  The operation previews and implements not
    setting the LBA flag.  Where as copying the same partition into an
    existing partition previews and implements as setting the LBA flag.
    
    Fix this so copying into a new partition also sets the partition flags
    consistently so when previewing and implementing this operation the LBA
    flag is set.
    
    Closes #300 - Consider setting LBA flag for FAT32 primary partitions
                  automatically when needed

2025-11-26  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Provide second name for set_partition_type_using_flag() (#300)
    
    Libparted uses the file system type, overridden or modified by flags to
    set the on-disk partition type appropriately.  For example on an MSDOS
    table the libparted ESP flag sets the on-disk partition type ID to 0xEF
    "EFI System Partition", alternatively setting the file system type to
    "ext4" sets the on-disk partition type ID to 0x83 "Linux".  This is
    handled in GParted_Core::set_partition_type() by calling either:
        set_partition_type_using_flag()
        set_partition_type_using_fstype()
    
    Since the previous commit "Set LBA flag for FAT16/32 file systems on
    MSDOS tables (#300)" set_partition_type_using_flag() is also called in
    the set_partition_type_using_fstype() case to set the optional LBA flag
    and modify the on-disk partition type.  Conceptually these are two
    different things:
    1.  Set the libparted partition flag to override any file system type to
        set the on-disk partition type.
            E.g. (Partition type ID on an MSDOS table)
            ESP flag                       -> 0xEF "EFI System Partition"
    2.  Set the optional libparted partition flag when also setting the file
        system type to amend the on-disk partition type.
            E.g.
            FAT32 file system              -> 0x0B "W96 FAT32"
            FAT32 file system and LBA flag -> 0x0C "W96 FAT32 (LBA)"
    
    However both cases need to do exactly the same thing; create an
    operation detail to report what is being done and call the libparted API
    to set the flag.  Therefore rename
    GParted_Core::set_partition_type_using_flag() to set_partition_flag()
    and provide a function wrapper for the original name.  So in the first
    flag overrides the file system case continue to call
    set_partition_type_using_flag() and in the second set optional flag to
    modify the file system case call the new set_partition_flag() name.
    
    Closes #300 - Consider setting LBA flag for FAT32 primary partitions
                  automatically when needed

2025-12-01  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Set LBA flag for FAT16/32 file systems on MSDOS tables (#300)
    
    A user requested that GParted set the LBA flag when creating FAT32 file
    systems.
    
    Libparted only supports the LBA flag for fat16 / fat32 and extended
    partitions on MSDOS partition tables [1] and no where else.  The Parted
    command always enables the LBA flag when it is available [2].  Therefore
    always creates these MSDOS partition types:
        Id  Type
        0E  W95 FAT16 (LBA)
        0C  W95 FAT32 (LBA)
        0F  W95 Extended (LBA)
    
    And testing of GNOME Disks shows it creates these MSDOS partition types
    and file systems:
        Id  Type             File System
        0C  W95 FAT32 (LBA)  fat16 [*]
        0C  W95 FAT32 (LBA)  fat32 [*]
        05  Extended         (None)
    [*] It doesn't appear possible to choose between fat16 and fat32 file
        systems.  Instead you just select a fat file system and it
        automatically chooses 16 or 32-bit FAT (File Allocation Table)
        depending on the size of the partition.
    
    Where as GParted, which doesn't set the LBA flag, always creates these
    MSDOS partition types and file systems:
        Id  Type       File System
        06  FAT16      fat16
        0B  W95 FAT32  fat32
        05  Extended   (None)
    
    Since there is precedent with the above mentioned partitioning tools
    always enabling the LBA flag and as Logical Block Addressing was first
    introduced in 1996 [3] enable the LBA flag.  This applies to these
    operations: create new, paste into existing and format for fat16/32 file
    systems in an MSDOS partition table.  If anybody is using MS-DOS before
    7.1 (included in Windows 95 Release 2) that doesn't support LBA
    addressing [4] the LBA flag can still be toggled off after the operation
    is applied.
    
    Now GParted creates these MSDOS partition types and file systems:
        Id  Type             File System
        0E  W95 FAT16 (LBA)  fat16
        0C  W95 FAT32 (LBA)  fat32
    
    Updated operation details looks like:
        * Create Primary Partition #1 (fat16, 64.00 MiB) on /de... (SUCCESS)
          * create empty partition                                 (SUCCESS)
          * clear old file system signatures in /dev/sdb1          (SUCCESS)
          * set partition type on /dev/sdb1                        (SUCCESS)
              new partition type: fat16                            (SUCCESS)
    >>        new partition flag: lba                              (SUCCESS)
          * create new fat16 file system                           (SUCCESS)
    
    [1] parted/libparted/labels/dos.c dos_type_id_supports_lba()
        https://cgit.git.savannah.gnu.org/cgit/parted.git/tree/libparted/labels/dos.c?h=v3.6#n226
            dos_type_id_supports_lba(unsigned char type_id)
            {
                switch (type_id)
                {
                    case PARTITION_FAT16:
                    case PARTITION_FAT16...
                    ...
                    case PARTITION_FAT32:
                    case PARTITION_FAT32...
                    ...
                    case PARTITION_DOS_EXT:
                    case PARTITION_EXT_LBA:
                        return true:
    
                    default:
                        return false:
                }
            }
    
    [2] parted/parted/parted.c do_mkpart()
        https://cgit.git.savannah.gnu.org/cgit/parted.git/tree/parted/parted.c?h=v3.6#n850
            static int
            do_mkpart (PedDevice** dev, PedDisk** diskp)
                ...
                if (ped_partition_is_flag_available (part, PED_PARTITION_LBA))
                    ped_partition_set_flag (part, PED_PARTITION_LBA, 1);
    
    [3] Hard Disks
        https://www.dosdays.co.uk/topics/hard_disks.php
            Hard Disk Capacities Over the Years
            Year  Capacity         Information
            1996  300 MB - 1.5 GB  Introduced LBA (Logical Block Addressing)
                                   for larger drives up to 8.4 GB
    
    [4] MS-DOS 7/8 (as part of Windows 9x)
        https://en.wikipedia.org/wiki/MS-DOS#MS-DOS_7/8_(as_part_of_Windows_9x)
            * MS-DOS 7.1 was included in Windows 95's OEM Service Release 2
              through Windows 98 Second Edition.  It added support for the
              FAT32 file system and logical block addressing (LBA)
    
    Closes #300 - Consider setting LBA flag for FAT32 primary partitions
                  automatically when needed

2025-12-01  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Consolidate setting of libparted partition flags (#300)
    
    After merge request !146 [1] addressing issue #288 [2], code
    implementing rules setting and clearing the ESP and LVM libparted
    partition flags ended up in multiple methods for each relevant
    operation.  However all the rules are compatible so merge merge them
    into a single function and call as necessary.
    
    [1] !146 - Maintain EFI System Partition type when copying to new
        partition
        https://gitlab.gnome.org/GNOME/gparted/-/merge_requests/146
    [2] #288 - GPT partition type GUID (code) does not get copied in
        partition copy & paste feature
        https://gitlab.gnome.org/GNOME/gparted/-/issues/288
    
    Closes #300 - Consider setting LBA flag for FAT32 primary partitions
                  automatically when needed

2025-12-02  Aurimas Aurimas Černius <aurimas.cernius@mailo.com>

    Update Lithuanian translation

2025-11-29  Emin Tufan Çetin <etcetin@gmail.com>

    Update Turkish translation

2025-10-26  Мирослав Николић <miroslavnikolic@rocketmail.com>

    Update Serbian translation

2025-10-22  Anders Jonsson <anders.jonsson@norsjovallen.se>

    Update Swedish translation

2025-10-11  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Also update unit test code to new closing namespace comment style

2025-10-11  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update to new closing namespace comment style
    
    Use a new closing namespace comment style everywhere.  Follows what the
    Gtkmm source code does:
        $ egrep -rh '}.*//' /usr/include/gtkmm-3.0/ | sort | uniq -c | fgrep -v ' 1 ' | sort -n
              2 }  //namespace Gtk
              2 } // namespace TreeView_Private
             58 } //namespace Gtk
            145 } //namespace Glib
            147 } // namespace Glib
            521 } // namespace Gtk

2025-10-08  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Refactor linux_swap::read_uuid() into if fail return early

2025-10-08  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Refactor linux_swap::read_label() into if fail return early

2025-08-29  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Refactor linux_swap::set_used_sectors() into if fail return early
    
    ... code pattern.  This is to make the code easier to understand by not
    having to remember multiple condition context for multiple levels of
    indented code.

2025-10-08  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Erase file system signatures before all FS copies (#297)
    
    Two further test cases:
    1. Copy EXFAT over NILFS2 in a larger partition
       Partition is unrecognised because it contains signatures for 2
       different file systems which neither blkid nor parted report as
       recognised.
    2. Copy FAT32 over BCACHEFS in a larger partition
       Partition is recognised as FAT32 by parted but it contains signatures
       for 2 different file systems.
    
    These test cases use GParted internal block copy to copy the source
    partition over a larger destination partition so all sectors are
    overwritten up to the size of the smaller source partition.  Then, when
    supported, which is FAT32 only for these tests, the file system is grown
    to fill the larger partition.  The overwritten file systems of NILFS2
    and BCACHEFS were chosen because they contain signatures at the
    beginning and end of the partition.
    
    Test case 1: Copy EXFAT over NILFS2 in a larger partition
    Before:
        # wipefs /dev/sdb1
        DEVICE OFFSET TYPE  UUID      LABEL
        sdb1   0x3    exfat 6AE6-4A1B Source
        sdb1   0x1fe  dos
    
        # wipefs /dev/sdb2
        DEVICE OFFSET     TYPE   UUID                                 LABEL
        sdb2   0x406      nilfs2 0fb3907a-e8ab-4d86-8781-8feb7334dfc3 Overwritten
        sdb2   0x1ffff006 nilfs2 0fb3907a-e8ab-4d86-8781-8feb7334dfc3 Overwritten
    
    After:
        # wipefs /dev/sdb2
        DEVICE OFFSET     TYPE   UUID                                 LABEL
        sdb2   0x1ffff006 nilfs2 0fb3907a-e8ab-4d86-8781-8feb7334dfc3 Overwritten
        sdb2   0x3        exfat  6AE6-4A1B                            Source
        sdb2   0x1fe      dos
    
        # blkid /dev/sdb2
        # echo $?
        2
    
        # parted /dev/sdb unit s print
        Model: ATA VBOX HARDDISK (scsi)
        Disk /dev/sdb: 16777216s
        Sector size (logical/physical): 512B/512B
        Partition Table: gpt
        Disk Flags:
    
        Number  Start    End       Size      File system  Name  Flags
         1      2048s    657407s   655360s                      msftdata
         2      657408s  1705983s  1048576s                     msftdata
    
    Two different signatures afterwards which neither blkid nor parted
    report as recognised.
    
    Test case 2: Copy FAT32 over BCACHEFS in a larger partition
    Before:
        # wipefs /dev/sdb1
        DEVICE OFFSET TYPE UUID      LABEL
        sdb1   0x52   vfat C1E7-9353 SOURCE
        sdb1   0x0    vfat C1E7-9353 SOURCE
        sdb1   0x1fe  vfat C1E7-9353 SOURCE
    
        # wipefs /dev/sdb2
        DEVICE OFFSET     TYPE     UUID                                 LABEL
        sdb2   0x1018     bcachefs bfbb6290-5237-49d5-b323-4161139bf2a5 Overwritten
        sdb2   0x1ff00018 bcachefs bfbb6290-5237-49d5-b323-4161139bf2a5 Overwritten
    
    After:
        # wipefs /dev/sdb2
        DEVICE OFFSET     TYPE     UUID                                 LABEL
        sdb2   0x1ff00018 bcachefs bfbb6290-5237-49d5-b323-4161139bf2a5 Overwritten
        sdb2   0x52       vfat     C1E7-9353                            SOURCE
        sdb2   0x0        vfat     C1E7-9353                            SOURCE
        sdb2   0x1fe      vfat     C1E7-9353                            SOURCE
    
        # blkid /dev/sdb2
        # echo $?
        2
    
        # parted /dev/sdb unit s print
        Model: ATA VBOX HARDDISK (scsi)
        Disk /dev/sdb: 16777216s
        Sector size (logical/physical): 512B/512B
        Partition Table: gpt
        Disk Flags:
    
        Number  Start    End       Size      File system  Name  Flags
         1      2048s    657407s   655360s   fat32              msftdata
         2      657408s  1705983s  1048576s  fat32              msftdata
    
    Two different signatures afterwards, blkid doesn't recognise it however
    parted recognises it as FAT32.
    
    So at least FAT32 grow doesn't clear signatures in space the file system
    is being grown into.  And if the file system doesn't support being grown
    or that support is not available then again previous signatures in the
    extra space are not cleared.  Therefore the partition contains multiple
    different file system signatures which may result in the last written
    file system not being recognised.  Fix this by erasing all signatures
    before all file system copies, whether using the GParted internal block
    copy or FS specific copy commands.
    
    Closes #297 - Copied EXT2/3/4 FS into existing FAT16/32 partition is
                  unrecognised

2025-10-06  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Erase file system signatures before FS specific copy method (#297)
    
    Copy an EXT2/3/4 file system into an existing partition containing a
    FAT16/32 file system.  After applying and refreshing GParted reports the
    partition as unrecognised.
    
    Initial signatures of EXT4 in sdb1 and FAT32 in sdb2:
        # wipefs /dev/sdb1
        DEVICE OFFSET TYPE UUID                                 LABEL
        sdb1   0x438  ext4 0a2df8eb-63d9-4467-83d6-9ecf2c1d95af Source
    
        # wipefs /dev/sdb2
        DEVICE OFFSET TYPE UUID      LABEL
        sdb2   0x52   vfat F986-9BA0 OVERWRITTEN
        sdb2   0x0    vfat F986-9BA0 OVERWRITTEN
        sdb2   0x1fe  vfat F986-9BA0 OVERWRITTEN
    
    Operation details reporting successful copy of sdb1 (EXT4) into sdb2:
        * Copy /dev/sdb1 to /dev/sdb2                              (SUCCESS)
          * calibrate /dev/sdb1                                    (SUCCESS)
          * calibrate /dev/sdb2                                    (SUCCESS)
          * set partition type on /dev/sdb2                        (SUCCESS)
          * copy file system from /dev/sdb1 to /dev/sdb2           (SUCCESS)
            * e2image -ra -p '/dev/sdb1' '/dev/sdb2'               (SUCCESS)
                e2image 1.47.2 (1-Jan-2025)
                Scanning inodes...
                Copied 26717 / 26717 blocks (100%) in 00:00:01 at 26.09 MB/s
          * check file system on /dev/sdb2 for errors and (if p... (SUCCESS)
    
    Afterwards sdb2 contains signatures of both FAT32 and EXT4:
        # wipefs /dev/sdb2
        DEVICE OFFSET TYPE UUID                                 LABEL
        sdb2   0x52   vfat F986-9BA0
        sdb2   0x0    vfat F986-9BA0
        sdb2   0x1fe  vfat F986-9BA0
        sdb2   0x438  ext4 0a2df8eb-63d9-4467-83d6-9ecf2c1d95af Source
    
    But neither blkid nor parted (libparted) recognise the contents of sdb2,
    therefore neither does GParted:
        # blkid /dev/sdb2
        # echo $?
        2
    
        # parted /dev/sdb unit s print
        Model: ATA VBOX HARDDISK (scsi)
        Disk /dev/sdb: 16777216s
        Sector size (logical/physical): 512B/512B
        Partition Table: msdos
        Disk Flags:
    
        Number  Start    End       Size     Type     File system  Flags
         1      2048s    526335s   524288s  primary  ext4
         2      526336s  1050623s  524288s  primary
    
    e2image copied only the used blocks of the EXT4 file system from sdb1
    into sdb2 which left the FAT32 signatures in sector 0 intact hence the
    above result.
    
    Also have the same issue with copying any EXT2/3/4 file system over the
    top of XFS because that also has it's signature in sector 0 which is not
    overwritten by the copy e2image implements.
        # wipefs /dev/sdb2
        DEVICE OFFSET TYPE UUID                                 LABEL
        sdb2   0x0    xfs  9f2e2cc1-82ee-4000-9742-a54c3e35548b Overwritten
        sdb2   0x438  ext4 5ac22fa1-e678-478a-9f85-8b313f577f5c Source
    
    As external file system specific copy commands are free to implement
    whatever they choose GParted can't depend on them erasing old signatures
    before or as part of copying the new file system data.  Therefore
    GParted needs to erase all signatures before hand, just like it already
    does before creating a new file system as part of the Create and Format
    operations [1].
    
    [1] commit 3c75f3f5b103bc158b0f70ea63459aa362b0bab8
        Use wipefs to clear old signatures before creating new file systems
        (#688882)
    
    Closes #297 - Copied EXT2/3/4 FS into existing FAT16/32 partition is
                  unrecognised

2025-10-13  Sergej A. <asvmail.as@gmail.com>

    Update Russian translation

2025-10-10  Juliano de Souza Camargo <julianosc@protonmail.com>

    Update Brazilian Portuguese translation

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Fix spelling mistake in help/Makefile.am comment

2025-09-24  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update screenshot md5sum in the gd, sl and te Manual translations (!152)
    
    These 4 translations of the GParted Manual don't have an existing
    screenshot:
        Code   Language           GParted Manual percentage translated [1]
        gd     Scottish Gaelic    14%
        sl     Slovenian           0%
        te     Telugu             10%
        th     Thai                0%
    
    However 3 of their PO (Portable Object) files do have the md5sum of the
    file help/C/figures/gparted_window.png so update that with the new hash.
    
    [1] The GNOME Project Translation Platform > Modules > gparted
        https://l10n.gnome.org/module/gparted/
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Updated Ukrainian screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Updated Swedish screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Updated Serbian (Latin) screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Updated Serbian screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update Russian screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Updated Romanian screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update Brazilian Portuguese screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update Italian screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Add Indonesian screenshot for the translated Manual (!152)
    
    As noted earlier the Indonesian screenshot was a symbolic link to the C
    locale screenshot.
        $ ls -l help/id/figures/gparted_window.png
        lrwxrwxrwx. ... help/id/figures/gparted_window.png -> ../../C/figures/gparted_window.png
    
    This displayed the English screenshot in the Indonesian GParted Manual
    and caused a warning against the translation in the GNOME translation
    website [1][2].  The GParted application and GParted Manual are well
    translated to Indonesian, 100% and 98% respectively.  Therefore provide
    an Indonesian screenshot.
    
    [1] The GNOME Project Translation Platform > Modules > gparted
        https://l10n.gnome.org/module/gparted/
    
    [2] gparted > master > Indonesian [User Guide]
        https://l10n.gnome.org/vertimus/gparted/master/help/id/
            /!\ Figures should not be copied when identical to original
            (/var/www/damnedlies/data/scratchdir/git/gparted/help/id/figures/gparted_window.png).
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update French screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update Spanish screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update Greek screenshot for the translated Manual (!152)
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-23  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update German screenshot for the translated Manual (!152)
    
    Note that the German translation PO (Portable Object) file uses a
    different (older?) style of referencing the external image [1] compared
    to that used in the Czech translation.  As a result the GNOME website
    marks the image as fuzzy instead of translated [2][3][4].
    
    All these GParted Manual translations use the same "@@image:" style of
    referencing the external image and all report the translation of the
    image as fuzzy whether the image exists or not!
        Code       Language          Image           Translation
        de         German            exists          fuzzy
        el         Greek             exists          fuzzy
        gd         Scottish Gaelic   doesn't exist   fuzzy
        it         Italian           exists          fuzzy
        sl         Slovenian         doesn't exist   fuzzy
        sr         Serbian           exists          fuzzy
        sr@latin   Serbian (Latin)   exists          fuzzy
        te         Telugu            doesn't exist   fuzzy
    
    Getting the [Current translated file (PO)] from the gparted > master >
    German page [2] provides a reformatted file that looks like it would
    remove the fuzzy status of the image translation.  However it reformats
    the whole file generating this level of change:
        1857 insertions(+), 915 deletions(-)
    Changes include updating itstool comments, re-ordering translations and
    re-line wrapping source and translated text.  Expect that this shouldn't
    affect the translation but it seems like something that should be left
    to the translation teams to perform and verify.
    
    So just update German screenshot and the md5sum hash of the C locale
    screenshot in the German PO file.
    
    [1] GParted German PO file
        help/de/de.po
            #. When image changes, this message will be marked fuzzy or
            #. untranslated for you. It doesn't matter what you translate it
            #. to: it's not used at all.
            #: C/gparted.xml:382(None)
            msgid ""
            "@@image: 'figures/gparted_window.png'; md5=0c6eb27cd7d5d614b4ea752846ccb50b"
            msgstr "translated"
    
    [2] gparted > master > German
        https://l10n.gnome.org/vertimus/gparted/master/help/de/
            including 0/1/0 image   [Translated/Fuzzy/Untranslated]
    
    [3] User Guide (German), Figures translation status
        https://l10n.gnome.org/module/gparted/help/master/de/images/
    
    [4] gparted > master > German > Differences for fuzzy strings
        https://l10n.gnome.org/vertimus/stats/31689/msgiddiff/
            512#, fuzzy
                -@@image: 'figures/gparted_window.png'; md5=0c6eb27cd7d5d614b4ea752846ccb50b
                +msgctxt "_external ref='figures/gparted_window.png' md5='0c6eb27cd7d5d614b4ea752846ccb50b'
            525msgctxt "_"
            526msgid ""
            527"external ref='figures/gparted_window.png' "
            528"md5='0c6eb27cd7d5d614b4ea752846ccb50b'"
            529msgstr "translated"
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-22  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update Czech screenshot for the translated Manual (!152)
    
    Also update the Czech PO (Portable Object) file with the md5sum of the
    new C locale screenshot to indicate that the screenshot has been
    translated [1][2].
    
    [1] GParted Czech PO file
        help/cs/cs.po
            #. (itstool) path: imageobject/imagedata
            #. This is a reference to an external file such as an image or
            #. video. When the file changes, the md5 hash will change to let
            #. you know you need to update your localized copy. The msgstr
            #. is not used at all. Set it to whatever you like once you have
            #. updated your copy of the file.
            #: C/index.docbook:382
            msgctxt "_"
            msgid ""
            "external ref='figures/gparted_window.png' "
            "md5='0c6eb27cd7d5d614b4ea752846ccb50b'"
            msgstr ""
            "external ref='figures/gparted_window.png' "
            "md5='0c6eb27cd7d5d614b4ea752846ccb50b'"
    
    [2] ITS Tool > Documentation > ITS Data Categories
        https://itstool.org/documentation/its.html
            External Resource
    
            ITS Tool creates a PO message for each translatable external
            resource.  It does not attempt to parse external resources or
            put their contents into PO files.  Rather, it calculates an MD5
            checksum for each resource and puts that in the PO file message
            along with the resource URI.  ITS Tool uses the special msgctxt
            "_" for all special messages that don't correspond to text in
            the XML document.
    
            For example, the built-in Mallard ITS rules contain the
            following:
    
                <itst:externalResourceRefRule selector="//mal:media"
                  externalResourceRefPointer="@src"/>
    
            Here is an example of the output:
    
                msgctxt "_"
                msgid "external ref='nautilus.png' md5='cbc3bbf0d998ed7a6567eb3b0c402195'"
                msgstr ""
    
            Translators can set the msgstr to anything they like to specify
            that they've created a localized copy of the file.  The actual
            msgstr doesn't matter.  It's only for tracking purposes.  When
            new external files are added, new messages will be added.  When
            existing files change, their MD5 checksums will change, causing
            the msgid to change.  This tells translators they need to update
            their localized copy of the file.
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-22  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Update main window screenshot in the GParted Manual (!152)
    
    The screenshots on the website (https://gparted.org/screenshots.php)
    were recently updated using the latest GParted application version and
    to have a consistent look by all having been taken on the same desktop
    environment.  Now update the main window screenshots in the GParted
    Manual and its translations to match.
    
    The screenshots were taken on a Fedora 42 VM with XFCE desktop.  The
    default application font and window title font were set to Cantarell
    Regular 11 and Cantarell Bold 11 respectively.  (This font was chosen
    for clarity and because it matches the font used in GNOME 3 and GNOME 4,
    before release 48).
    
    Run GParted in each language and capture the screenshots thus:
        ...
        $ sudo make install
        $ LANGUAGE=C sudo gparted
    Take screenshot and quit app.
    (The default main window size was 775 x 500 pixels, 785 x 534 with
    window manager decoration).
    
        $ LANGUAGE=el sudo gparted
    If necessary, make the GParted window wide enough to show all columns.
    The Greek translation had the longest column heading names and needed
    the widest main window.  Take screenshot and quit app.
    (Main window screenshot in Greek with window manager decoration was
    905 x 534 pixels).
    
    Repeat for each translation of the GParted Manual with a screenshot.
        $ ls -l help/*/figures/gparted_window.png
    
    Note that the Indonesian translation explicitly (committed in git [1])
    has it's screenshot symlinked to the C locale copy, so the Indonesian
    translation of the GParted Manual displayed the English screenshot.
        $ ls -l help/id/figures/gparted_window.png
        lrwxrwxrwx. ... help/id/figures/gparted_window.png -> ../../C/figures/gparted_window.png
    
    The GParted application and GParted Manual are both well translated to
    Indonesian.  Therefore also provide an updated Indonesian screenshot for
    the Manual.
    
    The GParted Manual has a comment [2] that the GNOME Document Style Guide
    [3] recommends a maximum image width of 510 pixels.  However that
    document no longer appears to exist on the GNOME web site.  The nearest
    found current document was the Developer Documentation Style Guidelines
    [4] but that doesn't mentions anything about screenshots.
    
    Having a screenshot as close to it's original size as possible makes the
    text easier to read.  Therefore determine the maximum image size
    ourselves.  Use the Greek screenshot, as it's the widest one, so all
    screenshots are resized by the same percentage for consistency.  Copy
    the image into the installed GParted Manual:
        $ cd ~/Pictures
        $ sudo cp gparted_window.el.png /usr/local/share/help/C/gparted/figures/gparted_window.png
        $ sudo cp gparted_window.el.png /usr/local/share/help/el/gparted/figures/gparted_window.png
    
    And view the English and Greek manuals:
        $ LANGUAGE=C yelp help:gparted
        $ LANGUAGE=el yelp help:gparted
    
    With trial and error found that the largest possible size for the Greek
    screenshot was 70% (width 634 pixels).  Larger than this then when yelp
    rendered the page for printing to A4 it had to scale down the contents
    to make the image fit, which also shrank the Manual's text.  Choose A4
    paper (width 210 mm) as it's slightly narrower that US letter (width 8.5
    inches, ~216 mm).  Viewed on a screen the yelp window can be narrowed to
    800 pixels and the GParted screenshot is still fully displayed.
    
    Resize all the screenshots in place to 70% using this GraphicsMagick
    command:
        $ cd ~/Pictures
        $ gm mogrify -filter Sinc -resize 70% gparted_window.*.png
    
    Evaluated all the filters GraphicsMagick provides and found that Sinc
    provided the clearest text in the shrunk screenshots.
    
    This commit just updates the C locale screenshot and the comment in the
    Manual with the discovered maximum image width.
    
    [1] commit f250697c58268c92e8c3bff74145c23bb6133ed5
        Add initial Indonesian translation of help (!90)
    
    [2] commit 8bc1377c2232934eb50bcb84454560312b9acbc9
        Add comment for documentation maximum image width recommendation
    
    [3] GNOME Documentation Style Guide V1.6, 10.3 Image Width
        http://web.archive.org/web/20210306042742/https://developer.gnome.org/gdp-style-guide/stable/screenshot-4.html.en
            The maximum image width is 510 pixels.  At this width, images
            fit on a printed page.  You might need to scale down the image
            before you add any callouts, to ensure that the total width of
            the image is less than 510 pixels.  You can use GIMP to scale
            images before you add callouts.  To scale an image in GIMP,
            right-click on the image, then choose Image > Scale image.
    
    [4] Developer Documentation Style Guidelines
        https://developer.gnome.org/documentation/guidelines/devel-docs.html
    
    Closes !152 - Update main window screenshot in the GParted Manual and
                  its translations

2025-09-30  luming zh <lumingzh@qq.com>

    Update Chinese (China) translation

2025-09-29  Yuri Chornoivan <yurchor@ukr.net>

    Update Ukrainian translation

2025-09-29  Martin <miles@filmsi.net>

    Update Slovenian translation

2025-09-24  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Fix spelling mistake in Dialog_Partition_New::set_data() comment

2025-06-04  Mike Fleetwood <mike.fleetwood@googlemail.com>

    Simplify setting the about copyright message
    
    In preparing the variable passed to Gtk::AboutDialog::set_copyright()
    the code did the following:
    1.  Default construct empty std::string
    2.  Copy assign from first string literal
    3.  Operator plus with second string literal
    4.  Operator plus with third string literal
    5.  Construct temporary Glib::ustring from std::string in order to pass
        to set_copyright() which only takes a Glib::ustring [1]
    
[--snip--]
