Ignore:
Timestamp:
11/07/13 02:04:26 (9 months ago)
Author:
PC-BSD Auto Commit Bot <auto-commit-bot@…>
Branches:
master, 9.2-release, releng/10.0, releng/10.0.1, releng/10.0.2
Children:
287fef9
Parents:
199284b
Message:

Auto-Commit of i18n data from Pootle

File:
1 edited

Legend:

Unmodified
Added
Removed
  • src-qt4/pc-zmanager/i18n/ZManager_en_ZA.ts

    raebf244 rc5b6872  
    66    <message> 
    77        <source>Dialog</source> 
    8         <translation type="unfinished"> 
    9             </translation> 
     8        <translation>Dialog</translation> 
    109    </message> 
    1110    <message> 
    1211        <source>Apply changes recursively to all descendants</source> 
    13         <translation type="unfinished"> 
    14             </translation> 
     12        <translation>Apply changes recursively to all descendants</translation> 
    1513    </message> 
    1614    <message> 
    1715        <source>Property</source> 
    18         <translation type="unfinished"> 
    19             </translation> 
     16        <translation>Property</translation> 
    2017    </message> 
    2118    <message> 
    2219        <source>Value</source> 
    23         <translation type="unfinished"> 
    24             </translation> 
     20        <translation>Value</translation> 
    2521    </message> 
    2622    <message> 
    2723        <source>Source</source> 
    28         <translation type="unfinished"> 
    29             </translation> 
     24        <translation>Source</translation> 
    3025    </message> 
    3126    <message> 
    3227        <source>Add user property</source> 
    33         <translation type="unfinished"> 
    34             </translation> 
     28        <translation>Add user property</translation> 
    3529    </message> 
    3630    <message> 
    3731        <source>...</source> 
    38         <translation type="unfinished"> 
    39             </translation> 
     32        <translation>...</translation> 
    4033    </message> 
    4134    <message> 
    4235        <source>Remove user property</source> 
    43         <translation type="unfinished"> 
    44             </translation> 
     36        <translation>Remove user property</translation> 
    4537    </message> 
    4638    <message> 
    4739        <source>Inherit from parent</source> 
    48         <translation type="unfinished"> 
    49             </translation> 
     40        <translation>Inherit from parent</translation> 
    5041    </message> 
    5142    <message> 
    5243        <source>Revert changes</source> 
    53         <translation type="unfinished"> 
    54             </translation> 
     44        <translation>Revert changes</translation> 
    5545    </message> 
    5646    <message> 
    5747        <source>Controls how ACL entries are inherited when files and directories are created. The values are 
    5848discard, noallow, restricted, and passthrough. For a description of these values, see ACL Properties.</source> 
    59         <translation type="unfinished"> 
    60             </translation> 
     49        <translation>Controls how ACL entries are inherited when files and directories are created. The values are 
     50discard, noallow, restricted, and passthrough. For a description of these values, see ACL Properties.</translation> 
    6151    </message> 
    6252    <message> 
     
    6454The values are discard, groupmask, and passthrough. For a description of 
    6555these values, see ACL Properties.</source> 
    66         <translation type="unfinished"> 
    67             </translation> 
     56        <translation>Controls how an ACL entry is modified during a chmod operation. 
     57The values are discard, groupmask, and passthrough. For a description of 
     58these values, see ACL Properties.</translation> 
    6859    </message> 
    6960    <message> 
     
    7263can result in significant performance gains, though it might confuse mailers and 
    7364similar utilities.</source> 
    74         <translation type="unfinished"> 
    75             </translation> 
     65        <translation>Controls whether the access time for files is updated when they are read. 
     66Turning this property off avoids producing write traffic when reading files and 
     67can result in significant performance gains, though it might confuse mailers and 
     68similar utilities.</translation> 
    7669    </message> 
    7770    <message> 
     
    8073shared within a pool, available space can be limited by various factors including 
    8174physical pool size, quotas, reservations, and other datasets within the pool.</source> 
    82         <translation type="unfinished"> 
    83             </translation> 
     75        <translation>Read-only property that identifies the amount of disk space available to a dataset 
     76and all its children, assuming no other activity in the pool. Because disk space is 
     77shared within a pool, available space can be limited by various factors including 
     78physical pool size, quotas, reservations, and other datasets within the pool.</translation> 
    8479    </message> 
    8580    <message> 
     
    9388both datasets appear in the same directory, but might have different 
    9489inherited characteristics.</source> 
    95         <translation type="unfinished"> 
    96             </translation> 
     90        <translation>If this property is set to off, the file system cannot be mounted, 
     91and is ignored by &apos;zfs mount -a&apos;.  Setting this property to off is 
     92similar to setting the mountpoint property to none, except that the 
     93dataset still has a normal mountpoint property, which can be inherited 
     94Setting this property to off allows datasets to be used solely as a 
     95mechanism to inherit properties. One example of setting canmount=off is 
     96to have two datasets with the same mountpoint, so that the children of 
     97both datasets appear in the same directory, but might have different 
     98inherited characteristics.</translation> 
    9799    </message> 
    98100    <message> 
     
    102104value off disables integrity checking on user data. Disabling 
    103105checksums is NOT a recommended practice.</source> 
    104         <translation type="unfinished"> 
    105             </translation> 
     106        <translation>Controls the checksum used to verify data integrity. The default 
     107value is on, which automatically selects an appropriate algorithm 
     108(currently, fletcher4, but this may change in future releases). The 
     109value off disables integrity checking on user data. Disabling 
     110checksums is NOT a recommended practice.</translation> 
    106111    </message> 
    107112    <message> 
     
    110115effect as setting this property to on. Enabling compression on a file system with 
    111116existing data only compresses new data. Existing data remains uncompressed.</source> 
    112         <translation type="unfinished"> 
    113             </translation> 
     117        <translation>Enables or disables compression for a dataset. The values are on, off, lzjb, zle, gzip, 
     118and gzip-N. Currently, setting this property to lzjb, gzip, or gzip-N has the same 
     119effect as setting this property to on. Enabling compression on a file system with 
     120existing data only compresses new data. Existing data remains uncompressed.</translation> 
    114121    </message> 
    115122    <message> 
     
    119126amount of referenced physical data. It includes explicit savings through the use of 
    120127the compression property.</source> 
    121         <translation type="unfinished"> 
    122             </translation> 
     128        <translation>Read-only property that identifies the compression ratio achieved for a dataset, 
     129expressed as a multiplier. Compression can be enabled by the zfs set compression=on 
     130dataset command. The value is calculated from the logical size of all files and the 
     131amount of referenced physical data. It includes explicit savings through the use of 
     132the compression property.</translation> 
    123133    </message> 
    124134    <message> 
     
    130140this property when the file system is created because changing this property 
    131141on an existing file system only affects newly written data.</source> 
    132         <translation type="unfinished"> 
    133             </translation> 
     142        <translation>Sets the number of copies of user data per file system. These copies 
     143are in addition to any pool-level redundancy. Disk space used by 
     144multiple copies of user data is charged to the corresponding file and 
     145dataset, and counts against quotas and reservations. In addition, the 
     146used property is updated when multiple copies are enabled. Consider setting 
     147this property when the file system is created because changing this property 
     148on an existing file system only affects newly written data.</translation> 
    134149    </message> 
    135150    <message> 
    136151        <source>Read-only property that identifies the date and time that a dataset was created.</source> 
    137         <translation type="unfinished"> 
    138             </translation> 
     152        <translation>Read-only property that identifies the date and time that a dataset was created.</translation> 
    139153    </message> 
    140154    <message> 
     
    147161two blocks having the same signature to make sure the block contents 
    148162are identical.</source> 
    149         <translation type="unfinished"> 
    150             </translation> 
     163        <translation>Configures deduplication for a dataset. The default value is off. 
     164The default deduplication checksum is sha256 (this may change in the 
     165future).  When dedup is enabled, the checksum defined here overrides 
     166the checksum property. Setting the value to verify has the same 
     167effect as the setting sha256,verify. 
     168If set to verify, ZFS will do a byte-to-byte comparsion in case of 
     169two blocks having the same signature to make sure the block contents 
     170are identical.</translation> 
    151171    </message> 
    152172    <message> 
    153173        <source>The devices property is currently not supported on FreeBSD.</source> 
    154         <translation type="unfinished"> 
    155             </translation> 
     174        <translation>The devices property is currently not supported on FreeBSD.</translation> 
    156175    </message> 
    157176    <message> 
    158177        <source>Controls whether processes can be executed from within this file 
    159178system. The default value is on.</source> 
    160         <translation type="unfinished"> 
    161             </translation> 
     179        <translation>Controls whether processes can be executed from within this file 
     180system. The default value is on.</translation> 
    162181    </message> 
    163182    <message> 
    164183        <source>Read-only property that indicates whether a file system, clone, or snapshot 
    165184is currently mounted.</source> 
    166         <translation type="unfinished"> 
    167             </translation> 
     185        <translation>Read-only property that indicates whether a file system, clone, or snapshot 
     186is currently mounted.</translation> 
    168187    </message> 
    169188    <message> 
     
    174193previously legacy or none, or if they were mounted before the property was changed. 
    175194In addition, any shared file systems are unshared and shared in the new location.</source> 
    176         <translation type="unfinished"> 
    177             </translation> 
     195        <translation>Controls the mount point used for this file system. When the mountpoint property 
     196is changed for a file system, the file system and any descendents that inherit the 
     197mount point are unmounted. If the new value is legacy, then they remain unmounted. 
     198Otherwise, they are automatically remounted in the new location if the property was 
     199previously legacy or none, or if they were mounted before the property was changed. 
     200In addition, any shared file systems are unshared and shared in the new location.</translation> 
    178201    </message> 
    179202    <message> 
     
    182205set to none, neither user data nor metadata is cached. If set to metadata, only 
    183206metadata is cached.</source> 
    184         <translation type="unfinished"> 
    185             </translation> 
     207        <translation>Controls what is cached in the primary cache (ARC). Possible values are all, 
     208none, and metadata. If set to all, both user data and metadata are cached. If 
     209set to none, neither user data nor metadata is cached. If set to metadata, only 
     210metadata is cached.</translation> 
    186211    </message> 
    187212    <message> 
     
    190215destroyed (even with the -r or -f option) as long as a clone exists. 
    191216Non-cloned file systems have an origin of none.</source> 
    192         <translation type="unfinished"> 
    193             </translation> 
     217        <translation>Read-only property for cloned file systems or volumes that identifies 
     218the snapshot from which the clone was created. The origin cannot be 
     219destroyed (even with the -r or -f option) as long as a clone exists. 
     220Non-cloned file systems have an origin of none.</translation> 
    194221    </message> 
    195222    <message> 
     
    199226Setting a quota on a descendent of a dataset that already has a quota does not 
    200227override the ancestor&apos;s quota, but rather imposes an additional limit.</source> 
    201         <translation type="unfinished"> 
    202             </translation> 
     228        <translation>Limits the amount of disk space a dataset and its descendents can consume. 
     229This property enforces a hard limit on the amount of disk space used, 
     230including all space consumed by descendents, such as file systems and snapshots. 
     231Setting a quota on a descendent of a dataset that already has a quota does not 
     232override the ancestor&apos;s quota, but rather imposes an additional limit.</translation> 
    203233    </message> 
    204234    <message> 
    205235        <source>Controls whether a dataset can be modified. When set to on, 
    206236no modifications can be made.</source> 
    207         <translation type="unfinished"> 
    208             </translation> 
     237        <translation>Controls whether a dataset can be modified. When set to on, 
     238no modifications can be made.</translation> 
    209239    </message> 
    210240    <message> 
     
    218248The size specified must be a power of two greater than or equal to 
    219249512 and less than or equal to 128 Kbytes.</source> 
    220         <translation type="unfinished"> 
    221             </translation> 
     250        <translation>Specifies a suggested block size for files in the file system. This 
     251property is designed solely for use with database workloads that 
     252access files in fixed-size records.  ZFS automatically tunes block 
     253sizes according to internal algorithms optimized for typical access 
     254patterns. 
     255Use of this property for general purpose file systems is strongly 
     256discouraged, and may adversely affect performance. 
     257The size specified must be a power of two greater than or equal to 
     258512 and less than or equal to 128 Kbytes.</translation> 
    222259    </message> 
    223260    <message> 
     
    921958    </message> 
    922959    <message> 
    923         <source>Controls the system behavior in the event of catastrophic pool fail‐ 
    924 ure. This condition is typically a result of a loss of connectivity 
     960        <source>Controls the system behavior in the event of catastrophic pool failure 
     961This condition is typically a result of a loss of connectivity 
    925962to the underlying storage device(s) or a failure of all devices 
    926 within the pool. The behavior of such an event is determined as fol‐ 
    927 lows: 
     963within the pool. The behavior of such an event is determined as follows 
     964wait 
     965Blocks all I/O access until the device connectivity is recovered 
     966and the errors are cleared. This is the default behavior 
     967continue 
     968Returns EIO to any new write I/O requests but allows reads to 
     969any of the remaining healthy devices. Any write requests that 
     970have yet to be committed to disk would be blocked. 
    928971 
    929 wait    Blocks all I/O access until the device connectivity is recov‐ 
    930         ered and the errors are cleared.  This is the default behav‐ 
    931         ior. 
    932  
    933 continue 
    934         Returns EIO to any new write I/O requests but allows reads to 
    935         any of the remaining healthy devices. Any write requests that 
    936         have yet to be committed to disk would be blocked. 
    937  
    938 panic   Prints out a message to the console and generates a system 
    939         crash dump. 
     972panic 
     973Prints out a message to the console and generates a system 
     974crash dump. 
    940975</source> 
    941976        <translation type="unfinished"></translation> 
Note: See TracChangeset for help on using the changeset viewer.