Re: Modernising UNIX manpages.
Hello alls, De : James K. Lowden > The problem is, the solution to a better tool lies not in the etheral > domain of language design, but in the grotty domain of GUI > programming. I would also agree that pointing clearly the problem of unix manpages would help find the correct solution. - if man or mdoc syntaxes have to change, one can create a friendly and semantic macro set with troff, which won't break the man pages environment: .h1 my title .table "col 1" "col 2" "col 3" .link http://example.com "some link" . - If exporting to xml is needed, one can write a dedicated tool, or write a nroff macro if parsing low level troff requests is requested. - if navigating through man pages need to be improved, then, as james says, it's gui programming we need. - going this way, we could also consider a gui for writing troff files without having to read the documentation first. I know troff have little quirks I'd be happy were not present, but so far, in that discussion I have not seen where it's at fault, except it's old and forgotten.
Re: Introducing mu, my new macro package
Hello John, Thank you for sharing your work. I've browsed your documentation, and love your mu package, and your usage of environments. Simplicity is neat ! I feel a bit concerned by your choosen name though, as I fear a name conflict with my own macro set, utmac. While it does not use the single "u" yet, it comes with ul, us, uh, ux, ut, um, uw, and all sorts of u*. Utmac does not have much users, but has some. Maybe those users would be happy to have both utmac and mu in their directory ? I don't know... I just feel important to let you know. Here's the code: https://github.com/pjfichet/utmac And the website: https://pjfichet.github.io/utroff Warm regards, Pierre-Jean.
Re: utmac -muh error on Ubuntu
Hello alls ! > Sujet : Re: utmac -muh error on Ubuntu Thanks for the bug report, and thank you all for the insight ! I should be able to give the bug a look this week end. Warm regards, Pierre-Jean.
Re: Refer database fields (was: Re: Why does refer(1) have no database field for =?UTF-8?Q?=20"edition"?)?=
Hello alls, To add to the discussion concerning refer, here is an excerpt of my past work and choices on that subject. There's an ISO standart which defines the needed and optional fields of a bibliography list, as well as their order: ISO-690. https://en.wikipedia.org/wiki/ISO_690 It's unfortunately not much used, and even worst, not freely available... But the idea to define fields and their order and let the choice of typography and punctuation to the user is valuable. For my thesis, I had to hack refer to make it sort the bibliography list according to the order of fields defined by that standart. I needed the following fields, that I implemented in u-ref.tmac, for utmac: %H information about the publication (first edition, french edition, etc.) %h heading of the section in which the citation appears. %M the collection in which the book in published. %P total number of pages of the book. %p page of the citation. %U co-author, translator, etc. %w which kind of electronic document (CDROM, online, etc.) %x url of an electronic document. %y update date of an electronic document. %z last access to an electronic document. I also implemented: - two formats: one for notes, and another for the bibliography list, - a contextual substitution of the references by "ibid." or "op. cit. p. xx." Cheers, Pierre-Jean.
