summaryrefslogtreecommitdiffstats
path: root/chinese/hztty
diff options
context:
space:
mode:
authormph <mph@FreeBSD.org>1998-08-05 18:13:19 +0000
committermph <mph@FreeBSD.org>1998-08-05 18:13:19 +0000
commitd7501cfe9756d5376752a04e8b2b11f019dd8552 (patch)
tree4fc833b7b7302d14f8cf036602a23d72026e6323 /chinese/hztty
parent8522f16d62ccce3e15ed2a4c99df9796fd3982ee (diff)
downloadFreeBSD-ports-d7501cfe9756d5376752a04e8b2b11f019dd8552.zip
FreeBSD-ports-d7501cfe9756d5376752a04e8b2b11f019dd8552.tar.gz
Grammar, spelling, and usage police. This commit brought to you by
the letters "B" and "C". And some Chinese symbols as well.
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 bde75d6..ed4d0ab 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.
OpenPOWER on IntegriCloud