summaryrefslogtreecommitdiff
path: root/japanese
diff options
context:
space:
mode:
authorwiz <wiz>2000-06-03 23:37:15 +0000
committerwiz <wiz>2000-06-03 23:37:15 +0000
commitcd057cbfad7518aa68ead28365a1de3f8b5fa23d (patch)
tree79cca2c661541ce53cca3fb48282b1db28aec901 /japanese
parent426cf60a4d540ac0b6f647b5160dd16168b1b9e8 (diff)
downloadpkgsrc-cd057cbfad7518aa68ead28365a1de3f8b5fa23d.tar.gz
Fix a typo, and make it better english. Could use another pass at the
second one...
Diffstat (limited to 'japanese')
-rw-r--r--japanese/nkf/pkg/DESCR13
1 files changed, 7 insertions, 6 deletions
diff --git a/japanese/nkf/pkg/DESCR b/japanese/nkf/pkg/DESCR
index 93d7409537a..3eb4a732c22 100644
--- a/japanese/nkf/pkg/DESCR
+++ b/japanese/nkf/pkg/DESCR
@@ -1,7 +1,8 @@
-Nkf is a yet another kanji code converter among networks, hosts and terminals.
-It converts input kanji code to designated kanji code such as 7-bit
-JIS, MS-kanji (shifted-JIS) or EUC.
+Nkf is a yet another kanji code converter between the different types
+of kanji codes out there. It can convert between 7-bit JIS, MS-kanji
+(shifted-JIS) or EUC.
-One of the most unique facicility of nkf is the guess of the input kanji
-code. It currently recognizes 7-bit JIS, MS-kanji (shifted-JIS) and EUC.
-So users needn't the input kanji code specification.
+One of the most unique facilities of nkf is that it guesses the input
+kanji code. It currently recognizes 7-bit JIS, MS-kanji (shifted-JIS)
+and EUC. So users don't need to specify (or even know) the input
+kanji code type.