Jamie Nguyen
jamie****@tomoy*****
Sat Mar 26 06:11:47 JST 2011
Tetsuo Handa wrote: > Finished translation (revision 4755), but it is not ready for replacing with > current documentation. Great, thanks! > Several topics I noticed: > > (1) In the world of TOMOYO, I'm using /path/to/dir/ for representing directory > and /path/to/file for representing non-directory. There are cases where > directories are represented without trailing / , and vice versa. Sorry, I'm not sure if you mean cases still exist, or whether you have already fixed them and are simply advising for the future? Perhaps I'm too tired today, but after scanning through briefly I'm not sure that I can spot any cases. > (2) How <code>program</code> should be used? There are cases where "program" is > used instead of <code>program</code>. Also, there are cases where used for > <code>program cmdline_arguments</code>. I used <code> tags for referring to commands within inline text. I found one case of using the <code> tag with command line arguments in chapter 7.1, which I have now changed. Though I can't find cases where "program" is used instead of <code>program</code>. Again, is this something you have already fixed? > (3) The example programs in chapter-12.html are explained without the location. > Since these programs are not compiled/installed by default, I think source > code for these programs should be linked from chapter-12.html like > <a href="http://sourceforge.jp/projects/tomoyo/svn/view/ ..somewhere..">honey.c</a> . Good idea, I've added one link to the web interface. > (4) Should there be <domain>domainname_representation</domain> tag? I'm not sure we need it. We would have to consider what to do for domain names within exception policy, or in other cases. It might complicate things more than help, but I'm open to suggestion. To me it seems readable as it is now. > (5) chapter-10.html has not enumerated all conditions. I need to add. Sure. I need to upload new html man pages too. Kind regards, Jamie
TOMOYO
Fork