Jeff: > Will change the style as Solaris. But since this is in roff format, the > grammar will be different.
Since these manpages are short, and since the community manpages are not really very well written, it might make sense to port them to SGML. I think manpages are easier to maintain in SGML if we need to make many changes to them. However, if you prefer maintaining the NROFF version, that is okay too. I would recommend filing a bug report upstream to get the non-Solaris specific improvements upstream. Comments: In both manpages, we probably do not want to include a BUGS section in our manpage. It is odd to provide this for these manpages, but not for our manpages in general. seahorse-agent.1: I thought the previous manpage indicated that gnome-std-options(5) are supported. However, I don't see mention of this in the manpages anymore. > This is the agent program for seahorse which keeps a tem- > porary secure storage of your pass phrases in the memory. It I would say "in memory" rather than "in the memory". > Print variable GPG_AGENT_INFO for a C type shell. I would say "Print the variable". > Do not make sure that requests only come from the X > display on which seahorse-agent was started. "Do not make sure" is not good English. I would say "Allow requests which come from X displays other than which seahorse-agent was started". > Display variable GPG_AGENT_INFO instead of editing I would say "Display the variable". Note that manpages which discuss environment variables should have an "ENVIRONMENT VARIABLES" section and mention environ(5) in the "SEE ALSO" section. seahorse-tool.1: Again, I thought the previous manpage indicated that gnome-std-options(5) are supported. However, I don't see mention of this in the manpages anymore. > -T, --uri-list > Read list of URIs on standard in. It is not clear from the manpage what this option does, or why a user would want to use it. Brian
