Re: RFS: xiterm+thai (updated)
On Tue, Jan 10, 2012 at 2:59 PM, Neutron Soutmun <firstname.lastname@example.org> wrote:
> Please review again
> dget -x http://mentors.debian.net/debian/pool/main/x/xiterm+thai/xiterm+thai_1.10-2.dsc
More on txiterm.1:
- It should be better to wrap the file at 80 columns.
- Using .br to break lines manually in paragraphs is bad typography.
Note that you can also use .PP if you mean to break it into new
- Wording could be improved. (See attached patch for example.)
- Please update the date in the .TH line every time you revise the
man page. And it should be in YYYY-MM-DD format. (See "man
man-pages" for more info.)
- You may also remove comment lines in the man page as
Paul previously suggested.
--- txiterm.1.orig 2012-01-11 01:25:56.409459181 +0700
+++ txiterm.1 2012-01-11 01:49:15.697505464 +0700
@@ -25,20 +25,20 @@
.\" TeX users may be more comfortable with the \fB<whatever>\fP and
.\" \fI<whatever>\fP escape sequences to invode bold face and italics,
-\fBtxiterm\fP is a wrapper around the \fBxiterm+thai(1)\fP program that invokes the latter program with Thai support and also loads the Thai font.
-All arguments to \fBtxiterm\fP are passed to xiterm+thai without processing;
-the \-fn option should not be specified because it is used by the wrapper.
+\fBtxiterm\fP is a wrapper around the \fBxiterm+thai(1)\fP program that
+invokes the latter program with proper Thai environment and font setup.
+All arguments to \fBtxiterm\fP are passed as-is to xiterm+thai with additional
+preset \-fn option, so that you do not need to set it again.
-See the xiterm+thai manual page for more information on \fIxiterm+thai-options\fP.
+See the xiterm+thai manual page for more information on
\fBNote: txiterm\fP needs \fBnectec18\fP - Thai TIS-620 X font from the
-\fBxfonts-thai-nectec\fP package to allow the program to render the proper Thai text in the terminal.
+\fBxfonts-thai-nectec\fP package to allow the program to render Thai TIS-620
+text properly in the terminal.
.SH SEE ALSO
txiterm was written by Chanop Silpa-Anan <email@example.com>.