From: Mario Blättermann Date: Fri, 26 Mar 2021 19:55:26 +0000 (+0100) Subject: Asciidoc: Update .pot template X-Git-Tag: v2.37-rc1~34^2~12 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7a29fa6fe4238098534337c7486588c415349c43;p=thirdparty%2Futil-linux.git Asciidoc: Update .pot template --- diff --git a/man-common/util-linux-man.pot b/man-common/util-linux-man.pot index abe4629c6b..f8c746d299 100644 --- a/man-common/util-linux-man.pot +++ b/man-common/util-linux-man.pot @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-03-26 20:17+0100\n" +"POT-Creation-Date: 2021-03-26 20:54+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -21351,9 +21351,9 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:50 msgid "" -"This epoch value is used whenever *­hwclock* reads or sets the Hardware " -"Clock on an Alpha machine. For ISA machines the kernel uses the fixed " -"Hardware Clock epoch of 1900." +"This epoch value is used whenever *hwclock* reads or sets the Hardware Clock " +"on an Alpha machine. For ISA machines the kernel uses the fixed Hardware " +"Clock epoch of 1900." msgstr "" #. type: Labeled list @@ -21481,8 +21481,8 @@ msgstr "" msgid "" "Drift compensation can be inhibited by setting the drift factor in " "_{ADJTIME_PATH}_ to zero. This setting will be persistent as long as the " -"*­--update-drift* option is not used with *­--systohc* at shutdown (or " -"anywhere else). Another way to inhibit this is by using the *­--noadjfile* " +"*--update-drift* option is not used with *--systohc* at shutdown (or " +"anywhere else). Another way to inhibit this is by using the *--noadjfile* " "option when calling the *--hctosys* function. A third method is to delete " "the _{ADJTIME_PATH}_ file. *Hwclock* will then default to using the UTC " "timescale for the Hardware Clock. If the Hardware Clock is ticking local " @@ -21519,9 +21519,9 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:84 msgid "" "Set the Hardware Clock to the time given by the *--date* option, and update " -"the timestamps in _{ADJTIME_PATH}_. With the *­--update-drift* option also " -"(re)calculate the drift factor. Try it without the option if *­--set* " -"fails. See *­--update-drift* below." +"the timestamps in _{ADJTIME_PATH}_. With the *--update-drift* option also " +"(re)calculate the drift factor. Try it without the option if *--set* " +"fails. See *--update-drift* below." msgstr "" #. type: Labeled list @@ -21533,7 +21533,7 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:87 msgid "" -"This is an alternate to the *­--hctosys* function that does not read the " +"This is an alternate to the *--hctosys* function that does not read the " "Hardware Clock nor set the System Clock; consequently there is not any drift " "correction. It is intended to be used in a startup script on systems with " "kernels above version 2.6 where you know the System Clock has been set from " @@ -21543,7 +21543,7 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:89 msgid "" -"It does the following things that are detailed above in the *­--hctosys* " +"It does the following things that are detailed above in the *--hctosys* " "function:" msgstr "" @@ -21568,7 +21568,7 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:95 msgid "" -"The first two are only available on the first call of ­*settimeofday*(2) " +"The first two are only available on the first call of *settimeofday*(2) " "after boot. Consequently this option only makes sense when used in a startup " "script. If the Hardware Clocks timescale configuration is changed then a " "reboot would be required to inform the kernel." @@ -21584,9 +21584,9 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:98 msgid "" "Set the Hardware Clock from the System Clock, and update the timestamps in " -"_{ADJTIME_PATH}_. With the *­--update-drift* option also (re)calculate the " -"drift factor. Try it without the option if *­--systohc* fails. See " -"*­--update-drift* below." +"_{ADJTIME_PATH}_. With the *--update-drift* option also (re)calculate the " +"drift factor. Try it without the option if ­*--systohc* fails. See " +"*--update-drift* below." msgstr "" #. type: Labeled list @@ -21603,13 +21603,13 @@ msgstr "" #. type: Labeled list #: ../sys-utils/hwclock.8.adoc:110 #, no-wrap -msgid "**­--date=**__date_string__" +msgid "**--date=**__date_string__" msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:112 msgid "" -"This option must be used with the *--set* or *­--predict* functions, " +"This option must be used with the *--set* or *--predict* functions, " "otherwise it is ignored." msgstr "" @@ -21622,16 +21622,16 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:116 #, no-wrap -msgid "*hwclock --predict --date='2525-08-14 07:11:05'*\n" +msgid "*hwclock --predict --date='2525-08-14 07:11:05'*\n" msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:118 msgid "" "The argument must be in local time, even if you keep your Hardware Clock in " -"UTC. See the *­--localtime* option. Therefore, the argument should not " +"UTC. See the *--localtime* option. Therefore, the argument should not " "include any timezone information. It also should not be a relative time like " -"\"+5 minutes\", because *­hwclock*'s precision depends upon correlation " +"\"+5 minutes\", because *hwclock*'s precision depends upon correlation " "between the argument's value and when the enter key is pressed. Fractional " "seconds are silently dropped. This option is capable of understanding many " "time and date formats, but the previous parameters should be observed." @@ -21640,7 +21640,7 @@ msgstr "" #. type: Labeled list #: ../sys-utils/hwclock.8.adoc:119 #, no-wrap -msgid "**­--delay=**__seconds__" +msgid "**--delay=**__seconds__" msgstr "" #. type: Plain text @@ -21673,7 +21673,7 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:126 msgid "" -"Use *--verbose*. The *­--debug* option has been deprecated and may be " +"Use *--verbose*. The *--debug* option has been deprecated and may be " "repurposed or removed in a future release." msgstr "" @@ -21687,9 +21687,9 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:129 msgid "" "This option is meaningful for ISA compatible machines in the x86 and x86_64 " -"family. For other machines, it has no effect. This option tells *­hwclock* " -"to use explicit I/O instructions to access the Hardware Clock. Without this " -"option, *­hwclock* will use the rtc device file, which it assumes to be " +"family. For other machines, it has no effect. This option tells *hwclock* to " +"use explicit I/O instructions to access the Hardware Clock. Without this " +"option, *hwclock* will use the rtc device file, which it assumes to be " "driven by the Linux RTC device driver. As of v2.26 it will no longer " "automatically use directisa when the rtc driver is unavailable; this was " "causing an unsafe condition that could allow two processes to access the " @@ -21707,7 +21707,7 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:132 msgid "" -"This option is required when using the *­--setepoch* function. The minimum " +"This option is required when using the *--setepoch* function. The minimum " "_year_ value is 1900. The maximum is system dependent (*ULONG_MAX - 1*)." msgstr "" @@ -21720,9 +21720,9 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:135 msgid "" -"Override *­hwclock*'s default rtc device file name. Otherwise it will use " -"the first one found in this order: _/dev/rtc0_, _/dev/rtc_, " -"_/dev/misc/rtc_. For *IA-64:* _/dev/efirtc_ _/dev/misc/efirtc_" +"Override *hwclock*'s default rtc device file name. Otherwise it will use the " +"first one found in this order: _/dev/rtc0_, _/dev/rtc_, _/dev/misc/rtc_. For " +"*IA-64:* _/dev/efirtc_ _/dev/misc/efirtc_" msgstr "" #. type: Labeled list @@ -21741,18 +21741,18 @@ msgstr "" msgid "" "The Hardware Clock may be configured to use either the UTC or the local " "timescale, but nothing in the clock itself says which alternative is being " -"used. The *­--localtime* or *--utc* options give this information to the " -"*­hwclock* command. If you specify the wrong one (or specify neither and " -"take a wrong default), both setting and reading the Hardware Clock will be " +"used. The *--localtime* or *--utc* options give this information to the " +"*hwclock* command. If you specify the wrong one (or specify neither and take " +"a wrong default), both setting and reading the Hardware Clock will be " "incorrect." msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:142 msgid "" -"If you specify neither *--utc* nor *­--localtime* then the one last given " -"with a set function (*--set*, *­--systohc*, or *­--adjust*), as recorded " -"in _{ADJTIME_PATH}_, will be used. If the adjtime file doesn't exist, the " +"If you specify neither *--utc* nor *--localtime* then the one last given " +"with a set function (*--set*, *--systohc*, or *--adjust*), as recorded in " +"_{ADJTIME_PATH}_, will be used. If the adjtime file doesn't exist, the " "default is UTC." msgstr "" @@ -21772,9 +21772,9 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:147 msgid "" -"Disable the facilities provided by _{ADJTIME_PATH}_. *­hwclock* will not " -"read nor write to that file with this option. Either *--utc* or " -"*­--localtime* must be specified when using this option." +"Disable the facilities provided by _{ADJTIME_PATH}_. *hwclock* will not read " +"nor write to that file with this option. Either *--utc* or *--localtime* " +"must be specified when using this option." msgstr "" #. type: Labeled list @@ -21787,7 +21787,7 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:150 msgid "" "Do not actually change anything on the system, that is, the Clocks or " -"_{ADJTIME_PATH}_ (*­--verbose* is implicit with this option)." +"_{ADJTIME_PATH}_ (*--verbose* is implicit with this option)." msgstr "" #. type: Labeled list @@ -21800,7 +21800,7 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:153 msgid "" "Update the Hardware Clock's drift factor in _{ADJTIME_PATH}_. It can only be " -"used with *--set* or *­--systohc*." +"used with *--set* or *--systohc*." msgstr "" #. type: Plain text @@ -21815,7 +21815,7 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:157 msgid "" "This option was added in v2.26, because it is typical for systems to call " -"*­hwclock --systohc* at shutdown; with the old behaviour this would " +"*hwclock --systohc* at shutdown; with the old behavior this would " "automatically (re)calculate the drift factor which caused several problems:" msgstr "" @@ -21847,13 +21847,13 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:162 msgid "" "Significantly increased system shutdown times (as of v2.31 when not using " -"*­--update-drift* the RTC is not read)." +"*--update-drift* the RTC is not read)." msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:164 msgid "" -"Having *­hwclock* calculate the drift factor is a good starting point, but " +"Having *hwclock* calculate the drift factor is a good starting point, but " "for optimal results it will likely need to be adjusted by directly editing " "the _{ADJTIME_PATH}_ file. For most configurations once a machine's optimal " "drift factor is crafted it should not need to be changed. Therefore, the old " @@ -21875,7 +21875,7 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:169 -msgid "Display more details about what *­hwclock* is doing internally." +msgid "Display more details about what *hwclock* is doing internally." msgstr "" #. type: Title === @@ -21912,8 +21912,8 @@ msgstr "" msgid "" "This clock is commonly called the hardware clock, the real time clock, the " "RTC, the BIOS clock, and the CMOS clock. Hardware Clock, in its capitalized " -"form, was coined for use by *­hwclock*. The Linux kernel also refers to it " -"as the persistent clock." +"form, was coined for use by *hwclock*. The Linux kernel also refers to it as " +"the persistent clock." msgstr "" #. type: Plain text @@ -21952,12 +21952,11 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:189 msgid "" "It is important that the System Time not have any discontinuities such as " -"would happen if you used the ­*date*(1) program to set it while the system " -"is running. You can, however, do whatever you want to the Hardware Clock " -"while the system is running, and the next time Linux starts up, it will do " -"so with the adjusted time from the Hardware Clock. Note: currently this is " -"not possible on most systems because *­hwclock --systohc* is called at " -"shutdown." +"would happen if you used the *date*(1) program to set it while the system is " +"running. You can, however, do whatever you want to the Hardware Clock while " +"the system is running, and the next time Linux starts up, it will do so with " +"the adjusted time from the Hardware Clock. Note: currently this is not " +"possible on most systems because *hwclock --systohc* is called at shutdown." msgstr "" #. type: Plain text @@ -21983,8 +21982,8 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:193 #, no-wrap msgid "" -"*­hwclock* sets the kernel's timezone to the value indicated by *TZ* or " -"_­/etc/localtime_ with the *­--hctosys* or *­--systz* functions.\n" +"*hwclock* sets the kernel's timezone to the value indicated by *TZ* or " +"_/etc/localtime_ with the *--hctosys* or *--systz* functions.\n" msgstr "" #. type: Plain text @@ -21995,7 +21994,7 @@ msgid "" "lags behind UTC, and 2) a field tz_dsttime indicating the type of Daylight " "Savings Time (DST) convention that is in effect in the locality at the " "present time. This second field is not used under Linux and is always " -"zero. See also *­settimeofday*(2)." +"zero. See also *settimeofday*(2)." msgstr "" #. type: Title === @@ -22008,12 +22007,12 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:199 #, no-wrap msgid "" -"*­hwclock* uses many different ways to get and set Hardware Clock " -"values. The most normal way is to do I/O to the rtc device special file, " -"which is presumed to be driven by the rtc device driver. Also, Linux systems " -"using the rtc framework with udev, are capable of supporting multiple " -"Hardware Clocks. This may bring about the need to override the default rtc " -"device by specifying one with the *--rtc* option.\n" +"*hwclock* uses many different ways to get and set Hardware Clock values. The " +"most normal way is to do I/O to the rtc device special file, which is " +"presumed to be driven by the rtc device driver. Also, Linux systems using " +"the rtc framework with udev, are capable of supporting multiple Hardware " +"Clocks. This may bring about the need to override the default rtc device by " +"specifying one with the *--rtc* option.\n" msgstr "" #. type: Plain text @@ -22027,11 +22026,11 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:203 msgid "" -"On an ISA compatible system, *­hwclock* can directly access the \"CMOS " +"On an ISA compatible system, ­*hwclock* can directly access the \"CMOS " "memory\" registers that constitute the clock, by doing I/O to Ports 0x70 and " "0x71. It does this with actual I/O instructions and consequently can only do " "it if running with superuser effective userid. This method may be used by " -"specifying the *­--directisa* option." +"specifying the *--directisa* option." msgstr "" #. type: Plain text @@ -22039,9 +22038,9 @@ msgstr "" msgid "" "This is a really poor method of accessing the clock, for all the reasons " "that userspace programs are generally not supposed to do direct I/O and " -"disable interrupts. *­hwclock* provides it for testing, troubleshooting, " -"and because it may be the only method available on ISA systems which do not " -"have a working rtc device driver." +"disable interrupts. *hwclock* provides it for testing, troubleshooting, and " +"because it may be the only method available on ISA systems which do not have " +"a working rtc device driver." msgstr "" #. type: Title === @@ -22055,34 +22054,34 @@ msgstr "" msgid "" "The Hardware Clock is usually not very accurate. However, much of its " "inaccuracy is completely predictable - it gains or loses the same amount of " -"time every day. This is called systematic drift. *­hwclock*'s *­--adjust* " +"time every day. This is called systematic drift. *hwclock*'s *--adjust* " "function lets you apply systematic drift corrections to the Hardware Clock." msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:211 msgid "" -"It works like this: *­hwclock* keeps a file, _{ADJTIME_PATH}_, that keeps " +"It works like this: *hwclock* keeps a file, _{ADJTIME_PATH}_, that keeps " "some historical information. This is called the adjtime file." msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:213 msgid "" -"Suppose you start with no adjtime file. You issue a *­hwclock --set* " -"command to set the Hardware Clock to the true current time. *­hwclock* " -"creates the adjtime file and records in it the current time as the last time " -"the clock was calibrated. Five days later, the clock has gained 10 seconds, " -"so you issue a *­hwclock --set --update-drift* command to set it back 10 " -"seconds. *­hwclock* updates the adjtime file to show the current time as " -"the last time the clock was calibrated, and records 2 seconds per day as the " -"systematic drift rate. 24 hours go by, and then you issue a *­hwclock " -"--adjust* command. *­hwclock* consults the adjtime file and sees that the " +"Suppose you start with no adjtime file. You issue a *hwclock --set* command " +"to set the Hardware Clock to the true current time. *hwclock* creates the " +"adjtime file and records in it the current time as the last time the clock " +"was calibrated. Five days later, the clock has gained 10 seconds, so you " +"issue a *hwclock --set --update-drift* command to set it back 10 " +"seconds. *hwclock* updates the adjtime file to show the current time as the " +"last time the clock was calibrated, and records 2 seconds per day as the " +"systematic drift rate. 24 hours go by, and then you issue a *hwclock " +"--adjust* command. *hwclock* consults the adjtime file and sees that the " "clock gains 2 seconds per day when left alone and that it has been left " "alone for exactly one day. So it subtracts 2 seconds from the Hardware " "Clock. It then records the current time as the last time the clock was " -"adjusted. Another 24 hours go by and you issue another *­hwclock " -"--adjust*. *­hwclock* does the same thing: subtracts 2 seconds and updates " +"adjusted. Another 24 hours go by and you issue another *hwclock " +"--adjust*. *hwclock* does the same thing: subtracts 2 seconds and updates " "the adjtime file with the current time as the last time the clock was " "adjusted." msgstr "" @@ -22090,8 +22089,8 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:215 msgid "" -"When you use the *­--update-drift* option with *--set* or *­--systohc*, " -"the systematic drift rate is (re)calculated by comparing the fully drift " +"When you use the *--update-drift* option with *--set* or *--systohc*, the " +"systematic drift rate is (re)calculated by comparing the fully drift " "corrected current Hardware Clock time with the new set time, from that it " "derives the 24 hour drift rate based on the last calibrated timestamp from " "the adjtime file. This updated drift factor is then saved in " @@ -22102,9 +22101,9 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:217 msgid "" "A small amount of error creeps in when the Hardware Clock is set, so " -"*­--adjust* refrains from making any adjustment that is less than 1 " +"*--adjust* refrains from making any adjustment that is less than 1 " "second. Later on, when you request an adjustment again, the accumulated " -"drift will be more than 1 second and *­--adjust* will make the adjustment " +"drift will be more than 1 second and *--adjust* will make the adjustment " "including any fractional amount." msgstr "" @@ -22112,13 +22111,13 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:219 #, no-wrap msgid "" -"*­hwclock --hctosys* also uses the adjtime file data to compensate the " -"value read from the Hardware Clock before using it to set the System " -"Clock. It does not share the 1 second limitation of *­--adjust*, and will " -"correct sub-second drift values immediately. It does not change the Hardware " -"Clock time nor the adjtime file. This may eliminate the need to use " -"*­--adjust*, unless something else on the system needs the Hardware Clock " -"to be compensated.\n" +"*hwclock --hctosys* also uses the adjtime file data to compensate the value " +"read from the Hardware Clock before using it to set the System Clock. It " +"does not share the 1 second limitation of *--adjust*, and will correct " +"sub-second drift values immediately. It does not change the Hardware Clock " +"time nor the adjtime file. This may eliminate the need to use *--adjust*, " +"unless something else on the system needs the Hardware Clock to be " +"compensated.\n" msgstr "" #. type: Title === @@ -22146,7 +22145,7 @@ msgid "" "Line 1: Three numbers, separated by blanks: 1) the systematic drift rate in " "seconds per day, floating point decimal; 2) the resulting number of seconds " "since 1969 UTC of most recent adjustment or calibration, decimal integer; 3) " -"zero (for compatibility with ­*clock*(8)) as a floating point decimal." +"zero (for compatibility with *clock*(8)) as a floating point decimal." msgstr "" #. type: Plain text @@ -22164,14 +22163,14 @@ msgstr "" msgid "" "Line 3: \"UTC\" or \"LOCAL\". Tells whether the Hardware Clock is set to " "Coordinated Universal Time or local time. You can always override this value " -"with options on the *­hwclock* command line." +"with options on the *hwclock* command line." msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:233 msgid "" -"You can use an adjtime file that was previously used with the *­clock*(8) " -"program with *­hwclock*." +"You can use an adjtime file that was previously used with the *clock*(8) " +"program with *hwclock*." msgstr "" #. type: Title === @@ -22209,7 +22208,7 @@ msgid "" "It takes an outside influence, like the NTP daemon to put the kernel's clock " "discipline into a synchronized state, and therefore turn on '11 minute " "mode'. It can be turned off by running anything that sets the System Clock " -"the old fashioned way, including *­hwclock --hctosys*. However, if the NTP " +"the old fashioned way, including *hwclock --hctosys*. However, if the NTP " "daemon is still running, it will turn '11 minute mode' back on again the " "next time it synchronizes the System Clock." msgstr "" @@ -22229,11 +22228,11 @@ msgstr "" msgid "" "The first userspace command to set the System Clock informs the kernel what " "timescale the Hardware Clock is using. This happens via the " -"_­persistent_clock_is_local_ kernel variable. If *­--hctosys* or " -"*­--systz* is the first, it will set this variable according to the adjtime " -"file or the appropriate command-line argument. Note that when using this " -"capability and the Hardware Clock timescale configuration is changed, then a " -"reboot is required to notify the kernel." +"_­persistent_clock_is_local_ kernel variable. If *--hctosys* or *--systz* " +"is the first, it will set this variable according to the adjtime file or the " +"appropriate command-line argument. Note that when using this capability and " +"the Hardware Clock timescale configuration is changed, then a reboot is " +"required to notify the kernel." msgstr "" #. type: Plain text @@ -22252,16 +22251,16 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:251 msgid "" "There is some sort of standard that defines CMOS memory Byte 50 on an ISA " -"machine as an indicator of what century it is. *­hwclock* does not use or " -"set that byte because there are some machines that don't define the byte " -"that way, and it really isn't necessary anyway, since the year-of-century " -"does a good job of implying which century it is." +"machine as an indicator of what century it is. *hwclock* does not use or set " +"that byte because there are some machines that don't define the byte that " +"way, and it really isn't necessary anyway, since the year-of-century does a " +"good job of implying which century it is." msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:253 msgid "" -"If you have a bona fide use for a CMOS century byte, contact the *­hwclock* " +"If you have a bona fide use for a CMOS century byte, contact the *hwclock* " "maintainer; an option may be appropriate." msgstr "" @@ -22307,13 +22306,13 @@ msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:265 msgid "" -"Early during startup the following are called, in this order: *­adjtimex " -"--tick* _value_ *--frequency* _value_ *­hwclock --hctosys*" +"Early during startup the following are called, in this order: *adjtimex " +"--tick* _value_ *--frequency* _value_ *hwclock --hctosys*" msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:266 -msgid "During shutdown the following is called: *­hwclock --systohc*" +msgid "During shutdown the following is called: *hwclock --systohc*" msgstr "" #. type: Plain text @@ -22347,39 +22346,39 @@ msgstr "" msgid "" "This problem can be avoided when configuring drift correction for the System " "Clock by simply not shutting down the machine. This, plus the fact that all " -"of *­hwclock*'s precision (including calculating drift factors) depends " -"upon the System Clock's rate being correct, means that configuration of the " +"of *hwclock*'s precision (including calculating drift factors) depends upon " +"the System Clock's rate being correct, means that configuration of the " "System Clock should be done first." msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:276 msgid "" -"The System Clock drift is corrected with the *­adjtimex*(8) command's " -"*--tick* and *­--frequency* options. These two work together: tick is the " +"The System Clock drift is corrected with the *adjtimex*(8) command's " +"*--tick* and *--frequency* options. These two work together: tick is the " "coarse adjustment and frequency is the fine adjustment. (For systems that do " -"not have an *­adjtimex* package, *­ntptime -f* _ppm_ may be used instead.)" +"not have an *adjtimex* package, *ntptime -f* _ppm_ may be used instead.)" msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:278 msgid "" "Some Linux distributions attempt to automatically calculate the System Clock " -"drift with *­adjtimex*'s compare operation. Trying to correct one drifting " +"drift with *adjtimex*'s compare operation. Trying to correct one drifting " "clock by using another drifting clock as a reference is akin to a dog trying " "to catch its own tail. Success may happen eventually, but great effort and " "frustration will likely precede it. This automation may yield an improvement " "over no configuration, but expecting optimum results would be in error. A " -"better choice for manual configuration would be *­adjtimex*'s *--log* " +"better choice for manual configuration would be *adjtimex*'s *--log* " "options." msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:280 msgid "" -"It may be more effective to simply track the System Clock drift with " -"*­sntp*, or *­date -Ins* and a precision timepiece, and then calculate the " -"correction manually." +"It may be more effective to simply track the System Clock drift with *sntp*, " +"or *date -Ins* and a precision timepiece, and then calculate the correction " +"manually." msgstr "" #. type: Plain text @@ -22465,13 +22464,13 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:306 msgid "" "Immediately use *hwclock* to set the correct time, adding the " -"*­--update-drift* option." +"*--update-drift* option." msgstr "" #. type: Plain text #: ../sys-utils/hwclock.8.adoc:308 msgid "" -"Note: if step 6 uses *­--systohc*, then the System Clock must be set " +"Note: if step 6 uses *--systohc*, then the System Clock must be set " "correctly (step 6a) just before doing so." msgstr "" @@ -22483,8 +22482,7 @@ msgid "" "the _{ADJTIME_PATH}_ file. Continue to test and refine the drift factor " "until the Hardware Clock is corrected properly at startup. To check this, " "first make sure that the System Time is correct before shutdown and then use " -"*­sntp*, or *­date -Ins* and a precision timepiece, immediately after " -"startup." +"*sntp*, or *date -Ins* and a precision timepiece, immediately after startup." msgstr "" #. type: Title === @@ -22528,8 +22526,8 @@ msgstr "" msgid "" "Linux handles daylight saving time changes transparently only when the " "Hardware Clock is kept in the UTC timescale. Doing so is made easy for " -"system administrators as *­hwclock* uses local time for its output and as " -"the argument to the *­--date* option." +"system administrators as *hwclock* uses local time for its output and as the " +"argument to the *--date* option." msgstr "" #. type: Plain text @@ -22584,12 +22582,12 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:334 msgid "" "To configure a system to use a particular database all of the files located " -"in its directory must be copied to the root of " -"_­/usr/share/zoneinfo_. Files are never used directly from the posix or " -"'right' subdirectories, e.g., ­TZ='_right/Europe/Dublin_'. This habit was " -"becoming so common that the upstream zoneinfo project restructured the " -"system's file tree by moving the posix and 'right' subdirectories out of the " -"zoneinfo directory and into sibling directories:" +"in its directory must be copied to the root of _/usr/share/zoneinfo_. Files " +"are never used directly from the posix or 'right' subdirectories, e.g., " +"­TZ='_right/Europe/Dublin_'. This habit was becoming so common that the " +"upstream zoneinfo project restructured the system's file tree by moving the " +"posix and 'right' subdirectories out of the zoneinfo directory and into " +"sibling directories:" msgstr "" #. type: Plain text @@ -22609,9 +22607,9 @@ msgid "" "database is still configured to exclude them. Then when an application such " "as a World Clock needs the South_Pole timezone file; or an email MTA, or " "*hwclock* needs the UTC timezone file; they fetch it from the root of " -"_­/usr/share/zoneinfo_ , because that is what they are supposed to " -"do. Those files exclude leap seconds, but the System Clock now includes " -"them, causing an incorrect time conversion." +"_/usr/share/zoneinfo_ , because that is what they are supposed to do. Those " +"files exclude leap seconds, but the System Clock now includes them, causing " +"an incorrect time conversion." msgstr "" #. type: Plain text @@ -22733,9 +22731,8 @@ msgstr "" #: ../sys-utils/hwclock.8.adoc:384 msgid "" "Written by mailto:bryanh@giraffe-data.com[Bryan Henderson], September 1996, " -"based on work done on the *­clock*(8) program by Charles Hedrick, Rob " -"Hooft, and Harald Koenig. See the source code for complete history and " -"credits." +"based on work done on the *clock*(8) program by Charles Hedrick, Rob Hooft, " +"and Harald Koenig. See the source code for complete history and credits." msgstr "" #. Copyright 2008 Hayden A. James (hayden.james@gmail.com)