mirror of
git://sourceware.org/git/glibc.git
synced 2025-03-19 13:40:59 +08:00
c7266a2d82
The previous (11th) version of the Hungarian spelling rules (released in 1984) said that the separator had to be a dot, e.g. 10.35 meaning 10 o'clock 35 minutes. glibc correctly implements this. The brand new (12th) version, in effect since September 1, 2015 adopts to the common use of colon (especially in the digital world) and allows to use either separator, without even expressing a preference. For computer systems, using colons is way more typical and probably easier to recognize. Dot is typically used in printed materials. It also avoids an almost ambiguous situation where a space makes a difference, e.g. "10.15-ig" means "until 10 o'clock 15 minutes" whereas "10. 15-ig" means "until 15th of October". So I believe using the colon as the separator is not only more frequent in the computer world, but is also easier and quicker to recognize for the brain that it's about hour:minute rather than month and day. And luckily it's now equally correct according to the official rules. 11th edition: http://helyesiras.mta.hu/helyesiras/default/akh11 12th edition: http://helyesiras.mta.hu/helyesiras/default/akh12 In both editions it's the very last (299th and 300th, respectively) rule. Microsoft also uses and recommends a colon since at least May 2011: http://download.microsoft.com/download/e/6/1/e61266b2-d8b4-4fe0-a553-f01dc3976675/hun-hun-StyleGuide.pdf The time format is different in common language and in the language of IT. In common texts we usually do not abbreviate, so the full forms are used: “7 óra 10 perckor csörgött a telefon”. However, the short format, consisting of numerals only, can also be used. In this case a period must be used between the two numbers and there must not be a space between them: “találkozzunk 10.45-kor”. However, in software mostly the short format is used, and the numbers are separated by a colon. An obvious example is the clock in the bottom right corner of your screen, thus 18:31.
This directory contains the sources of the GNU C Library. See the file "version.h" for what release version you have. The GNU C Library is the standard system C library for all GNU systems, and is an important part of what makes up a GNU system. It provides the system API for all programs written in C and C-compatible languages such as C++ and Objective C; the runtime facilities of other programming languages use the C library to access the underlying operating system. In GNU/Linux systems, the C library works with the Linux kernel to implement the operating system behavior seen by user applications. In GNU/Hurd systems, it works with a microkernel and Hurd servers. The GNU C Library implements much of the POSIX.1 functionality in the GNU/Hurd system, using configurations i[4567]86-*-gnu. The current GNU/Hurd support requires out-of-tree patches that will eventually be incorporated into an official GNU C Library release. When working with Linux kernels, this version of the GNU C Library requires Linux kernel version 2.6.32 or later. Also note that the shared version of the libgcc_s library must be installed for the pthread library to work correctly. The GNU C Library supports these configurations for using Linux kernels: aarch64*-*-linux-gnu alpha*-*-linux-gnu arm-*-linux-gnueabi hppa-*-linux-gnu Not currently functional without patches. i[4567]86-*-linux-gnu x86_64-*-linux-gnu Can build either x86_64 or x32 ia64-*-linux-gnu m68k-*-linux-gnu microblaze*-*-linux-gnu mips-*-linux-gnu mips64-*-linux-gnu powerpc-*-linux-gnu Hardware or software floating point, BE only. powerpc64*-*-linux-gnu Big-endian and little-endian. s390-*-linux-gnu s390x-*-linux-gnu sh[34]-*-linux-gnu sparc*-*-linux-gnu sparc64*-*-linux-gnu tilegx-*-linux-gnu tilepro-*-linux-gnu If you are interested in doing a port, please contact the glibc maintainers; see http://www.gnu.org/software/libc/ for more information. See the file INSTALL to find out how to configure, build, and install the GNU C Library. You might also consider reading the WWW pages for the C library at http://www.gnu.org/software/libc/. The GNU C Library is (almost) completely documented by the Texinfo manual found in the `manual/' subdirectory. The manual is still being updated and contains some known errors and omissions; we regret that we do not have the resources to work on the manual as much as we would like. For corrections to the manual, please file a bug in the `manual' component, following the bug-reporting instructions below. Please be sure to check the manual in the current development sources to see if your problem has already been corrected. Please see http://www.gnu.org/software/libc/bugs.html for bug reporting information. We are now using the Bugzilla system to track all bug reports. This web page gives detailed information on how to report bugs properly. The GNU C Library is free software. See the file COPYING.LIB for copying conditions, and LICENSES for notices about a few contributions that require these additional notices to be distributed. License copyright years may be listed using range notation, e.g., 1996-2015, indicating that every year in the range, inclusive, is a copyrightable year that would otherwise be listed individually.