Re: Would enough people like a tutorial in freebsd developer handbook

On Tue, 26 Feb 2013, Anthony Brown wrote: Would enough people like a tutorial in freebsd developer handbook on freebsd 64 bit assembly language using the c standard library. Interesting. But maybe a tutorial would be better as a separate article.

Re: [CFR] Migrating the documentation to a real XML toolchain

On Tue, 26 Feb 2013, Gabor Kovesdan wrote: I have some improvements for the doc infrastructures in the xml-tools branch. I think that the changeset is now getting mature enough to be merged back so I'd like to ask for review. It does not affect the web pages, only books and articles. The rende

Re: docs/176455: [patch][book/porters-handbook] convert to optionsNG for NLS, fix a closed literal tag

The following reply was made to PR docs/176455; it has been noted by GNATS. From: Jason Helfman To: bug-follo...@freebsd.org Cc: freebsd-doc@freebsd.org Subject: Re: docs/176455: [patch][book/porters-handbook] convert to optionsNG for NLS, fix a closed literal tag Date: Tue, 26 Feb 2013 16:25:02

Re: docs/176455: [patch][book/porters-handbook] convert to optionsNG for NLS, fix a closed literal tag

For completeness, here is the updated patch: Index: book.xml === --- book.xml(revision 41051) +++ book.xml(working copy) @@ -5749,14 +5749,18 @@ GNU_CONFIGURE= yes -.if !defined(WITHOUT_NLS) +.include

Re: docs/176455: [patch][book/porters-handbook] convert to optionsNG for NLS, fix a closed literal tag

The following reply was made to PR docs/176455; it has been noted by GNATS. From: Jason Helfman To: freebsd-doc@freebsd.org, bug-follo...@freebsd.org Cc: Subject: Re: docs/176455: [patch][book/porters-handbook] convert to optionsNG for NLS, fix a closed literal tag Date: Tue, 26 Feb 2013 14:33

Re: docs/176455: [patch][book/porters-handbook] convert to optionsNG for NLS, fix a closed literal tag

Please forgive me This was something that I was working on that hasn't be committed, I believe at this time The second blob does not need to be applied. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve On Tue

docs/176455: [patch][book/porters-handbook] convert to optionsNG for NLS, fix a closed literal tag

>Number: 176455 >Category: docs >Synopsis: [patch][book/porters-handbook] convert to optionsNG for NLS, >fix a closed literal tag >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-doc >State: open >Quarter: >Keywor

[CFR] Migrating the documentation to a real XML toolchain

Hi, I have some improvements for the doc infrastructures in the xml-tools branch. I think that the changeset is now getting mature enough to be merged back so I'd like to ask for review. It does not affect the web pages, only books and articles. The rendered docs are available at: http://peop

docs/176451: (patch) Handbook Ch 25.7 typos and incidental edits

>Number: 176451 >Category: docs >Synopsis: (patch) Handbook Ch 25.7 typos and incidental edits >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class:

Re: Do we care for manpage links in elements?

On 2013-02-26 10:45, Warren Block wrote: >On Tue, 26 Feb 2013, Giorgos Keramidas wrote: >>On 2013-02-26 09:45, Tom Rhodes wrote: >>>On Tue, 26 Feb 2013 14:44:15 +0100 Giorgos Keramidas >>>wrote: On 2013-02-26 13:49, Giorgos Keramidas wrote: >Hi everyone, >I just noticed that in all

Re: Do we care for manpage links in elements?

On Tue, 26 Feb 2013, Giorgos Keramidas wrote: On 2013-02-26 09:45, Tom Rhodes wrote: On Tue, 26 Feb 2013 14:44:15 +0100 Giorgos Keramidas wrote: On 2013-02-26 13:49, Giorgos Keramidas wrote: Hi everyone, I just noticed that in all the places where a chapter includes a &an.xxx.section; en

Re: Do we care for manpage links in elements?

On 2013-02-26 09:45, Tom Rhodes wrote: >On Tue, 26 Feb 2013 14:44:15 +0100 Giorgos Keramidas >wrote: >>On 2013-02-26 13:49, Giorgos Keramidas wrote: >>> Hi everyone, >>> I just noticed that in all the places where a chapter includes a >>> &an.xxx.section; entity the rendering in HTML output su

Re: Do we care for manpage links in elements?

On Tue, 26 Feb 2013 14:44:15 +0100 Giorgos Keramidas wrote: > On 2013-02-26 13:49, Giorgos Keramidas wrote: > > Hi everyone, > > > > I just noticed that in all the places where a chapter includes a > > &an.xxx.section; entity the rendering in HTML output sucks a bit. Note > > how there are tw

Re: Do we care for manpage links in elements?

On Tue, 26 Feb 2013, Giorgos Keramidas wrote: If not, do we really care for &man.xxx.y; in titles, or should we just replace them with plain text? I'm inclined to say we should not use entities in titles at all. -Ben ___ freebsd-doc@freebsd.org mail

Re: Do we care for manpage links in elements?

On 2013-02-26 13:49, Giorgos Keramidas wrote: > Hi everyone, > > I just noticed that in all the places where a chapter includes a > &an.xxx.section; entity the rendering in HTML output sucks a bit. Note > how there are two separate links in the 'Using rc(8) Under FreeBSD' > title in the followi

Do we care for manpage links in elements?

Hi everyone, I just noticed that in all the places where a chapter includes a &an.xxx.section; entity the rendering in HTML output sucks a bit. Note how there are two separate links in the 'Using rc(8) Under FreeBSD' title in the following screenshot: http://people.freebsd.org/~keramida/rc8

Re: How to build FreeBSD doc web pages?

Em 24-02-2013 22:35, Craig Rodrigues escreveu: I am trying to fix some text in the FreeBSD docs, and am trying to build the FreeBSD docs and web pages so I can view the output HTML as I am fixing things. There are three main use cases: 1, To build the whole documentation set (web and docs) cd d