aboutsummaryrefslogtreecommitdiff
path: root/chinese/hztty
diff options
context:
space:
mode:
authorMatthew Hunt <mph@FreeBSD.org>1998-08-05 18:13:19 +0000
committerMatthew Hunt <mph@FreeBSD.org>1998-08-05 18:13:19 +0000
commitc90bb39b08c4e992b350f3bfd8011923f28425c7 (patch)
tree49c565e4f6eade3004584717e08d4d311c9be59c /chinese/hztty
parentee6be707fb56cbfbbc72aef167678b250b4d9f23 (diff)
downloadports-c90bb39b08c4e992b350f3bfd8011923f28425c7.tar.gz
ports-c90bb39b08c4e992b350f3bfd8011923f28425c7.zip
Grammar, spelling, and usage police. This commit brought to you by
the letters "B" and "C". And some Chinese symbols as well.
Notes
Notes: svn path=/head/; revision=12291
Diffstat (limited to 'chinese/hztty')
-rw-r--r--chinese/hztty/pkg-descr4
1 files changed, 2 insertions, 2 deletions
diff --git a/chinese/hztty/pkg-descr b/chinese/hztty/pkg-descr
index bde75d659ac0..ed4d0abb62d5 100644
--- a/chinese/hztty/pkg-descr
+++ b/chinese/hztty/pkg-descr
@@ -4,14 +4,14 @@
For example, running hztty on cxterm can allow you to read/write
Chinese in HZ format, which was not supported by cxterm.
If you have many applications in different encodings but your
- favor terminal program only supports one, hztty can make life easy.
+ favorite terminal program only supports one, hztty can make life easy.
For example, hztty can your GB cxterm into a HZ terminal, a
Unicode (16bit, or UTF8, or UTF7) terminal, or a Big5 terminal.
The idea is to open a new shell session on top of the current one
and to translate the encoding between the new tty and the orignal.
For example, if your application uses encoding A and your terminal
- supports encoding B. Hztty catches the output of the application
+ supports encoding B, hztty catches the output of the application
and converts them from A to B before sending to the terminal.
Similarly, hztty converts all the terminal input from B to A before
sending to the application.