diff options
| author | Ulrich Drepper <drepper@redhat.com> | 1999-01-15 13:10:43 +0000 |
|---|---|---|
| committer | Ulrich Drepper <drepper@redhat.com> | 1999-01-15 13:10:43 +0000 |
| commit | a58fe83962f6c0389fcd2215433547117059938a (patch) | |
| tree | 58d17fbbff81f58fbc656ae76866443dd9503bcd | |
| parent | b7aee91f71f36d9ec30e92bf9a3274764b10d90e (diff) | |
| download | glibc-a58fe83962f6c0389fcd2215433547117059938a.tar.gz | |
Update.
* manual/charset.texi: More misspelling fixes.
Reported by Tom Tromey <tromey@cygnus.com>.
| -rw-r--r-- | ChangeLog | 3 | ||||
| -rw-r--r-- | manual/charset.texi | 6 |
2 files changed, 6 insertions, 3 deletions
@@ -1,5 +1,8 @@ 1999-01-15 Ulrich Drepper <drepper@cygnus.com> + * manual/charset.texi: More misspelling fixes. + Reported by Tom Tromey <tromey@cygnus.com>. + * sysdeps/unix/sysv/linux/vfork.c: Removed. * sysdeps/unix/sysv/linux/i386/vfork.S: New file. diff --git a/manual/charset.texi b/manual/charset.texi index d9e1689bfd..1242cc06ac 100644 --- a/manual/charset.texi +++ b/manual/charset.texi @@ -198,7 +198,7 @@ oriented character set. @cindex multibyte character @cindex EBCDIC For all the above reasons, an external encoding which is different -from the internal encoding is often used if the later is UCS2 or UCS4. +from the internal encoding is often used if the latter is UCS2 or UCS4. The external encoding is byte-based and can be chosen appropriately for the environment and for the texts to be handled. There exist a variety of different character sets which can be used for this external @@ -263,7 +263,7 @@ systems such as video text. @item @cindex UTF-8 Instead of converting the Unicode or @w{ISO 10646} text used internally -it is often also sufficient to simply use an encoding different then +it is often also sufficient to simply use an encoding different than UCS2/UCS4. The Unicode and @w{ISO 10646} standards even specify such an encoding: UTF-8. This encoding is able to represent all of @w{ISO 10464} 31 bits in a byte string of length one to seven. @@ -288,7 +288,7 @@ works with use. If there are no constraints the selection is based on the requirements the expected circle of users will have. I.e., if a project is expected to only be used in, say, Russia it is fine to use KOI8-R or a similar character set. But if at the same time people from, -say, Greek are participating one should use a character set which allows +say, Greece are participating one should use a character set which allows all people to collaborate. The most widely useful solution seems to be: go with the most general |