Date: Wed, 20 Dec 2000 08:59:16 +0200 From: Ruslan Ermilov <ru@FreeBSD.org> To: Kazuo Horikawa <horikawa@psinet.com> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, doc@FreeBSD.org Subject: Re: mdoc(7)NG questions (Re: cvs commit: src/bin/ed ed.1 src/bin/pax pax.1 src/bin/sh sh.1) Message-ID: <20001220085916.A87094@sunbay.com> In-Reply-To: <20001219155039E.horikawa@psinet.com>; from horikawa@psinet.com on Tue, Dec 19, 2000 at 03:50:39PM -0500 References: <200012181452.eBIEqH000902@freefall.freebsd.org> <20001219155039E.horikawa@psinet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 19, 2000 at 03:50:39PM -0500, Kazuo Horikawa wrote: > Hi Ruslan, > > I just saw several updated files and got several questions. > > What is the purpose of adding '\&' (zero width space) at the end of > line? > In other words, what output will be produced for the previous file > (which does not have '\&') and the new file (which has tailing '\&'), > and are they same or not? > > If output is totally different (not cosmetic change), I will > understand that mdoc(7)NG is not backward compatible to old mdoc(7). > If output is basically same, it is OK for me. > > > I saw trailing '\&' is added in at least pax.1 and wargames.6, and I > was afraid that mdoc(7)NG will change trailing puctuation treatment. > > In pax.1, > .Ar ... > is replaced with > .Ar ...\& > The ``dot'' is the closing punctuation character, which ends the sentence. Groff(1) puts two spaces after closing punctuation characters. mdoc(7)NG has been fixed to interpret these characters correctly in all cases. > and in src/games/wargames/wargames.6, > .Dq Shall we play a game? > is replaced with > .Dq Shall we play a game?\& > The reason is the same, we do not want two spaces after the `?'. Both `?' and `!' have been added to the mdoc(7)NG's list of closing punctuation characters. > I am translating FreeBSD manpages into Japanese (which are stored in > doc/ja_JP.eucJP/man). These manuals are formatted by ports ja-groff > (/usr/ports/japanese/groff), which uses FreeBSD's tmac.mdoc. I am > trying to continue to add changes which are applied to src tree > manpages (RELENG_4) in order to sync up with src. > So, I would like to know whether any impact exists or not once > mdoc(7)NG macro is incorporated into FreeBSD tree. > I don't know for sure if this affects Japanese manuals, you can try the current groff from ftp.ffii.org, and see if this produces the difference. What I am basically doing is checking all the manuals for differences between current mdoc(7) and mdoc(7)NG. > I think new functionality such as ".Ar -nosplit" is cool and > I do not intend to discourage your tasks. > This has been accepted in mdoc(7)NG, and will be available in the Groff 1.17 distribution. Please let me know if you will have any specific questions. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001220085916.A87094>