Re: Why does the freebsd-doc-en port install far eastern languages?

On Thu, 20 Oct 2016, Gary Aitken wrote: If I build the misc/freebsd-doc-en port, it installs chinese, japanese, and korean fonts. Can anyone tell me why? ===>>> The following actions will be taken if you choose to proceed: Install misc/freebsd-doc-en Install chinese/arphicttf

Re: Building docs

On Fri, 6 Jan 2017, scrat wrote: I am trying to render the documentation from the svn repo for the docs. I have followed the fdp-primer as well as I can and installed textproc/docproj. Here is what I did svn checkout https://svn.FreeBSD.org/doc/head ~/doc cd ~/doc/en_US.ISO8859-1/books/hand

Re: Building docs

On Fri, 6 Jan 2017, scrat wrote: On 01/06/17 11:22, Warren Block wrote: On Fri, 6 Jan 2017, scrat wrote: I am trying to render the documentation from the svn repo for the docs. I have followed the fdp-primer as well as I can and installed textproc/docproj. Here is what I did svn

Re: Translation Projects - Language: Català

On Sun, 15 Jan 2017, Josep Maria Gasset wrote: Dear doc members, Does anyone know if there are anybody is translating handbook & faqs to Català language and a main web page of Freebsd.org/cat? Maybe I can contribute to this project. That would be excellent! Please see the FDP Quick Start:

Re: Introduction & question / comment regarding source tree documentation

On Wed, 1 Mar 2017, Peter Looyenga wrote: My current drive: I can't help feel that the steps required to obtain the source tree aren't very well explained, and as a result several people and up confused. To put it more blunt, this thread is what drove me to try and take more action: https://for

Re: mistakes in documentation (ошибки в документации)

If you know of anyone interested in doing a Russian translation, the PO translation system makes it significantly easier than in the past: https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/po-translations.html On Wed, 14 Jun 2017, Maxim Konovalov wrote: Hi Max, On Wed, 14 Jun 2017

Re: Porters Handbook section 4.4

On Mon, 25 Sep 2017, Russell Haley wrote: Thanks! I'll play with this on the weekend. Please create a review at https://reviews.freebsd.org/ and add me as a reviewer. Thanks! ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailm

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

On Thu, 14 Mar 2013, Gabor Kovesdan wrote: Em 27-02-2013 02:24, Warren Block escreveu: Author info is a little off. Compare the authors at the start of the bsdinstall chapter: http://people.freebsd.org/~gabor/db45/en_US.ISO8859-1/books/handbook/bsdinstall.html http://www.freebsd.org/doc

Re: Need help documenting development processes in FreeBSD

On Mon, 1 Apr 2013, Garrett Cooper wrote: In order to bring contributors up to speed on how to interact with FreeBSD, I want to document some of the items that aren't really noted in the FreeBSD developers or committers handbook. Some topics that come to mind are "How do I do a precommit buil

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

On Thu, 4 Apr 2013, Gabor Kovesdan wrote: Em 26-02-2013 22:56, Gabor Kovesdan escreveu: 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

Re: Type Error FreeBSD handbook

On Fri, 5 Apr 2013, ruediger.r...@dlr.de wrote: Hello! I discovered a type error by accident: There is a 'be' (the word, not the letter) missing in the current online version of Chapter 4.3.2: "Several file flags may only added" Fixed in r41373. Thanks! _

Re: [patch] en/handbook/ports: another small cleanup

On Thu, 11 Apr 2013, Taras Korenko wrote: Hi, folks. Could anyone of doc@ review/comment/approve the following small changes to en/books/handbook/ports ? 1) An obvious chunk: Index: en_US.ISO8859-1/books/handbook/

Re: RFC: Changing the documentation's font style.

On Fri, 12 Apr 2013, Isabell Long wrote: Hi all, I sent this idea to the #bsddocs IRC channel a few days ago and no-one there objected, but here you go. I'd like to know your opinions on the documentation font being changed from serif to sans-serif. This would only affect the web-based docs, no

Re: RFC: Changing the documentation's font style.

On Fri, 12 Apr 2013, Erich Dollansky wrote: Hi, On Fri, 12 Apr 2013 10:41:46 +0100 Isabell Long wrote: Hi all, I sent this idea to the #bsddocs IRC channel a few days ago and no-one there objected, but here you go. I'd like to know your opinions on the documentation font being changed from

Re: RFC: Changing the documentation's font style.

On Sun, 14 Apr 2013, Isabell Long wrote: The reason I specified Verdana in the beginning was to have some familiarity between the website font and the documentation font - before (and now) I think it looks disjointed. I have just made font-family sans-serif without a specific default font, howev

Re: RFC: Changing the documentation's font style.

On Sun, 14 Apr 2013, Isabell Long wrote: Hi, On 14 April 2013 16:57, Warren Block wrote: On Sun, 14 Apr 2013, Isabell Long wrote: How's http://tau.devrandom.co.uk/issyl0/en_US.ISO8859-1/books/handbook/ now, as a compromise? Okay, but could you do another without a set font size?

The doc lounge at BSDCan 2013

BSDCan 2013 will be held at the University of Ottawa in May. During the nights of the conference, the FreeBSD documentation team will be hosting a "doc lounge", similar in concept to the traditional "hacker lounge" but aimed at improving FreeBSD documentation. We plan to commit patches, updat

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

On Wed, 8 May 2013, Gabor Kovesdan wrote: I've fixed all the reported problems again. (Except those that were already there before my work, since they are not trivial to fix in this phase.) I've also updated the generated documentation set: http://people.freebsd.org/~gabor/db45/

Re: [HEADSUP] Merging back the xml-tools branch

On Fri, 17 May 2013, Gabor Kovesdan wrote: Em 16-05-2013 12:57, Gabor Kovesdan escreveu: I'll be merging back the XML toolchain changes to head tomorrow around 6pm GTM. I'll temporarily lock head to avoid conflicting changes at the same time and head will be reopen very soon after the merge is

Committing Handbook updates

Please set me straight on how, when, and where to commit updates to the Handbook at present. As I understand it, we are still in doc slush. When is that planned to end? Are small changes allowed, or should we save them for now? There's the ISBN project branch. Should we commit changes ther

Re: 7.2.1.2 ...Flash...

On Wed, 22 May 2013, Dieter Lange wrote: after "To install and enable this plugin:" IMHO text should better read "Compile and install" instead of just "Compile" (twice). "Install" should be adequate. There are also some small other issues there. _

Re: 7.2.1.2 ...Flash...

On Wed, 22 May 2013, Warren Block wrote: On Wed, 22 May 2013, Dieter Lange wrote: after "To install and enable this plugin:" IMHO text should better read "Compile and install" instead of just "Compile" (twice). "Install" should be adequate. Ther

Re: RFC: Upgrading to DocBook 5.0

On Tue, 28 May 2013, Gabor Kovesdan wrote: I have a patch to preview how it would look like: http://kovesdan.org/patches/fbsd-docbook5.diff Please comment on this. It is very important to discuss this kind of changes. I think that keeping up with DocBook versions is important. Leaving out th

Re: removing 'changes' section from the online edition

On Sat, 1 Jun 2013, Gabor Kovesdan wrote: Em 01-06-2013 18:26, Eitan Adler escreveu: The Preface has a few sections 'Changes from the Edition' which enumerate changes made between print editions of the book. I would like to drop them from the online edition as they offer little value and

Re: removing 'changes' section from the online edition

On Sat, 1 Jun 2013, Gabor Kovesdan wrote: Em 01-06-2013 20:52, Warren Block escreveu: No objection from me, I just want to bring it up again that handling these with a single-source solution would be nice, i.e. using DocBook profiling. It would also facilitate merges. This basically consists

print edition (was Re: removing 'changes' section from the online edition)

On Sun, 2 Jun 2013, Gabor Kovesdan wrote: Em 02-06-2013 00:13, Warren Block escreveu: On Sat, 1 Jun 2013, Gabor Kovesdan wrote: Em 01-06-2013 20:52, Warren Block escreveu: No objection from me, I just want to bring it up again that handling these with a single-source solution would be nice

RFC: Storage/Adding Disks rewrite

Many of the sections in the Storage chapter are very outdated. Here is a rewrite of the Adding Disks section: original version: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-adding.html new version: http://wonkity.com/~wblock/addingdisks/disks-adding.html diff: http://w

RFC: Profiling and merging for the print edition

My proposal for merging the ISBN branch and getting out of our two-branch problem. First, profiling works. A demo file of the Porter's Handbook is here: http://wonkity.com/~wblock/profiledemo/ After applying the patch, build either the online or print version of the book with: make EDITION=o

RFC: acronym tags

The FDP writing guide says: The first three uses of an acronym should be enclosed in acronym tags, with a role attribute with the full term defined. This allows a link to the glossary to be created, and for mouseovers to be rendered with the fully expanded term. I believe this is obsolet

Re: RFC: Profiling and merging for the print edition

On Fri, 21 Jun 2013, Hiroki Sato wrote: Warren Block wrote in : wb> My proposal for merging the ISBN branch and getting out of our wb> two-branch problem. wb> wb> First, profiling works. A demo file of the Porter's Handbook is here: wb> http://wonkity.com/~wblock/profil

RFC: Handbook Storage chapter RAID section removal

The Handbook Storage chapter has a section called RAID that describes the use of ccd(4) and ataraid(4). ccd(4) is obsolete, having been replaced several times by newer drivers. I think ataraid(4) has been supplanted by graid(8). So I propose to remove that RAID section entirely. Yes, people

Re: RFC: Handbook Storage chapter RAID section removal

On Thu, 20 Jun 2013, Allan Jude wrote: On 2013-06-20 14:20, Warren Block wrote: The Handbook Storage chapter has a section called RAID that describes the use of ccd(4) and ataraid(4). ccd(4) is obsolete, having been replaced several times by newer drivers. I think ataraid(4) has been

Re: RFC: Profiling and merging for the print edition

On Thu, 20 Jun 2013, Gabor Kovesdan wrote: Em 20-06-2013 19:03, Warren Block escreveu: There is a complication. Links to sections which have been eliminated by profiling will break, so those would also need profiling. I don't know how big an issue that will be, but suspect it will n

RFC: Handbook Storage chapter floppy backup section removal

Continuing with the project to remove stuff from the Storage chapter that is long overdue... The Backups to Floppies section has been warning that floppies are not suitable backup media for a decade now. New machines have not included floppy drives for a long time. It's time for this section

Handbook obsolescence scan: "The vinum Volume Manager"

Next on the list of potentially outdated things in the Handbook: "The vinum Volume Manager", a whole chapter on vinum. Actually, it is really now about gvinum. Are there any situations where new users should be advised to use gvinum rather than ZFS or gconcat/gstripe/gmirror? What reasons a

Re: Handbook obsolescence scan: "The vinum Volume Manager"

On Tue, 25 Jun 2013, Frank Leonhardt wrote: On 25/06/2013 16:43, Warren Block wrote: Next on the list of potentially outdated things in the Handbook: "The vinum Volume Manager", a whole chapter on vinum. Actually, it is really now about gvinum. Are there any situations where

Re: Handbook obsolescence scan: "The vinum Volume Manager"

On Tue, 25 Jun 2013, Frank Leonhardt wrote: Couldn't agree more! In fact the whole disk mirroring thing still confuses me, as there are too many options and no guide for choosing between them. As far as I understand it, gmirror is the way to go in most cases because you end up with two identic

Re: Handbook obsolescence scan: "The vinum Volume Manager"

On Tue, 25 Jun 2013, Benjamin Kaduk wrote: On Tue, 25 Jun 2013, Warren Block wrote: Next on the list of potentially outdated things in the Handbook: "The vinum Volume Manager", a whole chapter on vinum. Actually, it is really now about gvinum. Are there any situations where

Re: Handbook obsolescence scan: "The vinum Volume Manager"

On Wed, 26 Jun 2013, Eitan Adler wrote: On Wed, Jun 26, 2013 at 4:23 AM, Warren Block wrote: Moving it to an article should cover all the bases. It won't be first-line information in the Handbook, but can still be found. And eventually, if not already, we can have an archive sectio

Re: Fixing the man page for renice

On Sat, 6 Jul 2013, Frank Leonhardt wrote: On 06/07/2013 16:28, Glen Barber wrote: Thanks Glen - the "patch" business is what's putting me off! I'm sure once I've done it, nothing will stop me. Is there a page or *really simple* guide to doing it, that assumes nothing? Assuming the source in

Re: Fixing the man page for renice

On Sun, 7 Jul 2013, Frank Leonhardt wrote: On 06/07/2013 22:19, Warren Block wrote: On Sat, 6 Jul 2013, Frank Leonhardt wrote: On 06/07/2013 16:28, Glen Barber wrote: Thanks Glen - the "patch" business is what's putting me off! I'm sure once I

Re: RFC: Upgrading to DocBook 5.0

On Wed, 3 Jul 2013, Alberto Mijares wrote: On Wed, Jul 3, 2013 at 3:56 AM, Gabor Kovesdan wrote: Em 24-05-2013 19:35, Gabor Kovesdan escreveu: I'm working on upgrading our documentation set to DocBook 5.0 and I'd like to discuss some details. We have some customizations and strange uses, whic

Re: svn commit: r42201 - head/en_US.ISO8859-1/books/fdp-primer/docbook-markup

On Tue, 9 Jul 2013, Benjamin Kaduk wrote: I have done my share of fitting relatively large font text into a small space and trying to get the wrapping to look nice; with a nbsp there will almost certainly be some font size+page width combinations that look bad. We should probably discuss and

Re: svn commit: r42201 - head/en_US.ISO8859-1/books/fdp-primer/docbook-markup

On Wed, 10 Jul 2013, Gabor Kovesdan wrote: Em 10-07-2013 03:36, Warren Block escreveu: For "FreeBSD 9.2", numbers and units like "8 GB", and guibutton uses, I think using nbsp is probably okay. For "Ports Collection" or other instances of multiple full words,

Re: svn commit: r42201 - head/en_US.ISO8859-1/books/fdp-primer/docbook-markup

On Wed, 10 Jul 2013, Gabor Kovesdan wrote: Em 10-07-2013 13:19, Warren Block escreveu: what do you mean by guibutton uses? I remember of Cancel, OK and such but do we have two-word guibuttons? nbsp is used to glue together the square brackets and the label: [ Save ] And what if we don&#

Re: RFC: Upgrading to DocBook 5.0

On Sun, 14 Jul 2013, Gábor Kövesdán wrote: Some more things: - Admonitions (top, note, warning boxes) look quite strange in lists and such places. I think we should add a policy to avoid them and start changing the markup. Admonitions are overused in some places. They are visually jarring,

Re: RFC: Upgrading to DocBook 5.0

On Sun, 14 Jul 2013, Gabor Kovesdan wrote: Em 14-07-2013 14:52, Warren Block escreveu: On Sun, 14 Jul 2013, Gábor Kövesdán wrote: Some more things: - Admonitions (top, note, warning boxes) look quite strange in lists and such places. I think we should add a policy to avoid them and start

Title formatting (was Re: RFC: Upgrading to DocBook 5.0)

On Sun, 14 Jul 2013, Gabor Kovesdan wrote: I find different fonts for filenames and commands to be useful, even in titles. The O'Reilly style guide doesn't mention anything about title styles, and in a quick search I did not find anything else. Ok, it doesn't specify it explicitly but can you

Project GRUDS: Handbook disk reorg

Project GRUDS (Grand Unified Disk Storage) Goal: Edit and rewrite the scattered, repetitive, and conflicting Handbook sections on disk storage into a unified group. This would be a separate in the Handbook, starting where chapter 19, Storage, currently begins. The problem: Right now there are

Entities: DocBook versus XHTML

The FDP Primer, which I have been bludgeoning lately, has no section that really tells the basic FreeBSD-specific entities available, either in XHTML or DocBook or both. The XHTML section does not show the correct way to refer to a Handbook chapter or an article. &os; is only used a couple o

Re: Project GRUDS: Handbook disk reorg

On Mon, 15 Jul 2013, Allan Jude wrote: Notes: Quick-start section should probably cover installation with 'root on zfs' Excellent point! We really need to make the quick start sections almost mandatory. Added to outline. Hardware chapter might mention SAS and things like SAS expanders an

Re: Trouble building release with docs

On Sat, 20 Jul 2013, Daniel O'Connor wrote: Hi, I am trying to do a full (customised) release of 9.1 but I am having trouble building the docs. If I use NODOC it builds fine, but without that I get.. [andenes 7:04] /usr/src/release #/usr/bin/time make release BUILDNAME=$BUILDNAME make -C /usr/s

Re: Trouble building release with docs

On Sun, 21 Jul 2013, Glen Barber wrote: On Sun, Jul 21, 2013 at 05:19:23PM +0930, Daniel O'Connor wrote: On 21/07/2013, at 16:19, Glen Barber wrote: On Sat, Jul 20, 2013 at 04:44:56PM +0930, Daniel O'Connor wrote: Hi, I am trying to do a full (customised) release of 9.1 but I am having tro

FDP Primer: emacs and vim

Multiple people have said the emacs configuration shown in the FDP Primer is outdated. Of particular interest is the section at the end of the emacs chapter: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/psgml-mode.html There is also a vim configuration shown in the Writing Sty

Re: CFR: documentation rendered in PDF with FOP

On Tue, 23 Jul 2013, Gabor Kovesdan wrote: I'm working on new rendering solutions for our documentation. One renderer will be dblatex, which doesn't depend on Java but doesn't give such high quality output. The other one will be FOP, which is written is Java but produces better quality. Here

Re: CFR: documentation rendered in PDF with FOP

On Tue, 23 Jul 2013, Gabor Kovesdan wrote: Hi, I'm working on new rendering solutions for our documentation. One renderer will be dblatex, which doesn't depend on Java but doesn't give such high quality output. The other one will be FOP, which is written is Java but produces better quality.

Re: CFR: documentation rendered in PDF with FOP

The line-wrap characters are very welcome! They still need some tuning (see PDF page 26). Or maybe that's in the source XML, but it's good to see a start on that! ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/free

screen elements and userinput in XHTML

In XHTML documents, our current CSS stylesheet does not distinguish between user-typed input and system output. That's my fault, Gabor had user input in bold but I felt it had so much contrast that it distracted rather than clarified. Our screen elements are not separated from other text, eit

Re: CFR: documentation rendered in PDF with FOP

On Wed, 24 Jul 2013, Gabor Kovesdan wrote: On 2013.07.23. 23:11, Warren Block wrote: There is something weird about bulleted lists and sub-lists, starting on page 35 of the PDF Handbook (page 7-9 of the content). Some entries in the first list are blank, the ones in the second list have an

and other tag usage

When writing sections, I've generally not used other markup inside those sections except for . For example: rm /tmp/foo However, there are some spots in the Handbook where tags are also used: rm /tmp/foo This looks different in the XHTML output, with the filename rendered in green.

Another CSS suggestion: pre-wrap

Long lines in screen and programlisting elements run off the right side of the screen with the current CSS. It would be great to have them wrap and include a visible a line wrap indicator, but that may not be possible, or may require Javascript. Better than nothing is to have them at least ha

Re: Another CSS suggestion: pre-wrap

On Sun, 28 Jul 2013, Gabor Kovesdan wrote: On 2013.07.28. 19:45, Gabor Kovesdan wrote: On 2013.07.28. 19:00, Warren Block wrote: Long lines in screen and programlisting elements run off the right side of the screen with the current CSS. It would be great to have them wrap and include a

Re: Another CSS suggestion: pre-wrap

On Sun, 28 Jul 2013, Gabor Kovesdan wrote: On 2013.07.28. 21:17, Warren Block wrote: This seems to does the XSLT-part, although it may be done in a better way since it breaks some DocBook features that we don't use: http://kovesdan.org/patches/xhtml-wrap.diff Nice! Which DocBook fea

Re: Another CSS suggestion: pre-wrap

On Sun, 28 Jul 2013, Gabor Kovesdan wrote: On 2013.07.28. 21:37, Warren Block wrote: Line numbering is nice sometimes, although sometimes it's easy to confuse with content. Syntax highlighting could be useful in places like the Architecture Handbook, but as you say, we don't h

Re: Another CSS suggestion: pre-wrap

On Mon, 29 Jul 2013, Gabor Kovesdan wrote: On 2013.07.29. 0:09, Warren Block wrote: On Sun, 28 Jul 2013, Gabor Kovesdan wrote: On 2013.07.28. 21:37, Warren Block wrote: Line numbering is nice sometimes, although sometimes it's easy to confuse with content. Syntax highlighting cou

Re: Another CSS suggestion: pre-wrap

On Mon, 29 Jul 2013, Gabor Kovesdan wrote: On 2013.07.29. 0:21, Warren Block wrote: Do you mean Java is needed to do the linewrap on XHTML, or that it would be needed to do line numbers and syntax highlighting? For the latter two only. Excellent! What do you think about adding it after

Re: [CALL FOR REVIEW] Upgrading to DocBook 5.0

On Fri, 2 Aug 2013, Gabor Kovesdan wrote: 3, A dblatex-based rendering toolchain. This toolchain is more limited. Its customization is more difficult and non-Latin text is not wrapped properly. Also, it fails with programlistings in tables so it cannot build the whole documentation set. This i

Updating translation workflow

We have some problems with our translation workflow, and updating it could make life easier for everyone. Note that as an American, I barely speak English, so there may be misconceptions in the following. Please correct me if necessary. * Translators work too hard. No automation, no assista

Re: Updating translation workflow

On Tue, 20 Aug 2013, Gabor Pali wrote: Hi Warren, On Mon, Aug 19, 2013 at 6:07 PM, Warren Block wrote: * Translators work too hard. No automation, no assistance from the computer to see what needs to be translated I am not sure of this. A few years ago we seem to have a consensus on an

Re: Updating translation workflow

On Tue, 20 Aug 2013, Gabor Pali wrote: On Tue, Aug 20, 2013 at 4:13 PM, Warren Block wrote: Well, yes, but this appears to be manual and does not automatically translate the same strings that are found in other documents. That is part of what the newer automated systems do. Erm, I am a bit

Re: Updating translation workflow

On Tue, 20 Aug 2013, Gabor Kovesdan wrote: Em 20-08-2013 19:10, Warren Block escreveu: On Tue, 20 Aug 2013, Gabor Pali wrote: On Tue, Aug 20, 2013 at 4:13 PM, Warren Block wrote: Well, yes, but this appears to be manual and does not automatically translate the same strings that are found

Re: Updating translation workflow

I think we can use a combination of tools to work with our existing documents.  The workflow would be like this: 1. Use textproc/itstool to create a "strings to be translated" file    (.pot) from an XML file. 2. Use pootle as a database to translate any of those strings

Feedback wanted: wrapping long lines in HTML docs

HTML versions of our documents show long lines in and elements. At present, these lines run right out of the boxes they are in. Some lines are very long. An example in the FDP Primer is 473 characters: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/xml-primer-elements.html (s

Re: 4.12 Binary Formats

On Thu, 29 Aug 2013, John Baldwin wrote: On Wednesday, August 07, 2013 8:08:17 pm Hugh O'Brien wrote: Hi there, I'm a relatively long time user but was recently reading through the handbook to see if there was anything I could learn when I found this section: http://www.freebsd.org/doc/en_US.

Re: Tweaks to the wait(2) manpage

On Sat, 14 Sep 2013, Konstantin Belousov wrote: On Thu, Sep 12, 2013 at 04:43:46PM -0400, John Baldwin wrote: I have some tweaks to the wait(2) manpage, in particular to the sections on wait6() and idtypes. I did also change two other places to use uppercase for ID since that seems to be what

Re: Docbook: programlisting and screen

On Mon, 30 Sep 2013, Randy Pratt wrote: I've noticed that trying to copy content from the rendered Handbook from a browser does not retain the line breaks in some places. This occurs for material that are contained within a or elements. As an example, try to copy and paste some content from

Re: ZFS docs from vBSDCon

On Tue, 29 Oct 2013, Allan Jude wrote: Attached find a patch for the zfsupdate-201307 project branch of stuff I wrote during the vBSDCon Doc Sprint More coming soon Commited. I also worked through about the first third of the chapter in an edit.

Developers' Handbook on the web server

http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/index.html The copyrights only go to 2010. Also: "Last modified on August 2000 by ." That seems just a tad off. ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mai

Re: Developers' Handbook on the web server

On Tue, 29 Oct 2013, Taras Korenko wrote: On Tue, Oct 29, 2013 at 02:57:55PM -0600, Warren Block wrote: ... Also: "Last modified on August 2000 by ." ... may be simply fixed with: Index: en_US.ISO8859-1/books/developers-handboo

Re: TODO item: Add info on USB printers

Forgot to send this to the list also... On Wed, 30 Oct 2013, Warren Block wrote: On Wed, 30 Oct 2013, Juris Kaminskis wrote: Some first trial to create better coverage for USB printing support in FreeBSD documentation. There are some more chapters to revise but this is definetly one

Re: TODO item: Add info on USB printers

On Mon, 4 Nov 2013, Juris Kaminskis wrote: Thank you for working on this.  The entire printing chapter really needs a rewrite, and I've been meaning to write an outline for what a new printing chapter should cover.  In the meantime, please look at http://ww

Re: ZFS Handbook Update

On Tue, 5 Nov 2013, Allan Jude wrote: On 2013-11-05 00:08, Allan Jude wrote: Attached find ~320 new lines and 87 modified lines of the ZFS chapter of the FreeBSD Handbook that I wrote on the plane to and from the FreeBSD 20th Anniversary Party. Note: this is for, and is a patch against, the pr

Re: [HEADSUP] Merging DocBook 5.0 update

On Thu, 7 Nov 2013, Gábor Kövesdán wrote: On 2013.11.07. 16:12, Gábor Kövesdán wrote: Hi, I will soon merge the DocBook 5.0 updates to head. The tree will temporarily be locked until the merge is done. I will send out another email I have finished. The merge is done, head is now open agai

Re: [HEADSUP] Merging DocBook 5.0 update

On Fri, 8 Nov 2013, Warren Block wrote: On Thu, 7 Nov 2013, Gábor Kövesdán wrote: On 2013.11.07. 16:12, Gábor Kövesdán wrote: Hi, I will soon merge the DocBook 5.0 updates to head. The tree will temporarily be locked until the merge is done. I will send out another email I have finished

Re: Problems with handbook/book.pdf.bz2

On Mon, 11 Nov 2013, Johannes Meixner wrote: I've been alerted in #freebsd/freenode to the fact that a user had issues with ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/book.pdf.bz2, in which he'd only see # after extracting and opening the file with SumatraPDF. I'v

Re: [HEADSUP] Merging DocBook 5.0 update

On Tue, 12 Nov 2013, Gábor Kövesdán wrote: On 2013.11.08. 16:58, Warren Block wrote: In HTML, programlistings used to be a div ( but are now . Likewise for . The existing CSS has no entries for this. Userinput is also not bold, another CSS issue. Fixed, thanks! By the way, when was

Re: draft of proposed handbook info on bhyve and virtualization

On Thu, 14 Nov 2013, Dee Nixon wrote: As promised back in September, the following page contains a draft of some proposed additions to the FreeBSD handbook: http://petitecloud.org/handbook.jsp The proposed new sections concern bhyve, the new hypervisor that is part of the base system of FreeBS

Re: What are the limits for FFS file systems? 10+ years out of date..

On Sat, 23 Nov 2013, John-Mark Gurney wrote: Attached is a patch that bring this up to date.. This was written back when we were using UFS1 w/ 32bit block addresses... Things have changes now that UFS2 is standard... The big thing is listing the memory requirements for fsck as the main limiti

Re: What are the limits for FFS file systems? 10+ years out of date..

On Sun, 24 Nov 2013, John-Mark Gurney wrote: Warren Block wrote this message on Sun, Nov 24, 2013 at 07:21 -0700: On Sat, 23 Nov 2013, John-Mark Gurney wrote: Attached is a patch that bring this up to date.. This was written back when we were using UFS1 w/ 32bit block addresses... Things

Re: [HEADSUP] Merging DocBook 5.0 update

Some automated conversions in the FDP Primer had problems. is not allowed inside , so some of the entities in the FreeBSD Entities table lost their markup. Is there a better solution than using < and >? Example: Usage: The manual page for cp is &man.cp.1;. The usage is supposed to sho

Re: typo

On Tue, 26 Nov 2013, Alexander Oblovatniy wrote: Hello, There are couple of typos at page 4.9 Shells . Both foobar and foo.bar start with fo. By typing ., then pressing *Tab* again, the shell is able to fill in the rest of the filename. Both

Re: en/handbook/users: proposed corrections

On Tue, 26 Nov 2013, Taras Korenko wrote: Good day, doc@ folks. I'd like to introduce some corrections to handbook/users chapter. However, there might be moot points, so any comments will be appreciated. Thanks. Thanks for working on this! Comments inline below, preceded with WB: for ea

Re: en/handbook/users: proposed corrections

On Thu, 28 Nov 2013, Taras Korenko wrote: There's a second lap, which includes received suggestions. One note: @@ -960,7 +957,7 @@ In this example, the argument to -m is a comma-delimited list of users who are to be added to the group. Unlike the previous example, these us

Re: en/handbook/users: proposed corrections

As before, notes marked with WB: below. On Thu, 28 Nov 2013, Taras Korenko wrote: ... and the last (previously unnoticed) chunk follows: Index: en_US.ISO8859-1/books/handbook/users/chapter.xml === --- en_US.ISO8859-1/books/handb

Re: en/handbook/users: proposed corrections

On Fri, 29 Nov 2013, Taras Korenko wrote: Updated version of the second patch follows. Looks good to me! P.S.: the funniest thing is that contents of users chapter was integrated into basics chapter in r42953, users chapter was removed (again r42953), and reappeared after db5 merg

Re: en/handbook/basics: proposed corrections

On Sat, 30 Nov 2013, Taras Korenko wrote: On Thu, Nov 28, 2013 at 04:59:30PM -0700, Warren Block wrote: ... ... So, next, I am to adapt current two patches to the new location: basics chapter :-/ I thought some of that looked familiar. My apologies, I just did a big

Re: Help requested for bhyve(8) mdoc markup

On Wed, 4 Dec 2013, Peter Grehan wrote: Hi, bcr@ suggested that I email this list to get some mdoc assistance for the bhyve(8) man page. Also, any content and grammar review is welcome and appreciated :) The raw text is at http://people.freebsd.org/~grehan/bhyve_8-v0.2.txt I will work

Re: docs/184550: bc -q option not documented in man page

On Fri, 6 Dec 2013, Eitan Adler wrote: On Fri, Dec 6, 2013 at 9:18 PM, Glen Barber wrote: On Fri, Dec 06, 2013 at 09:12:30PM -0500, Eitan Adler wrote: all options should be documented. An undocumented option is a bug. If we don't want people using it we should document as such. It is docu

Re: Updates to the Uses section (twisted) in the porter's handbook

On Sun, 8 Dec 2013, Marcus von Appen wrote: Dear doc@ people, find attached a minor patch for the Uses section (a brief entry for twisted) and a minor cleanup of the zope leftovers. Modified version committed. Thanks! ___ freebsd-doc@freebsd.org ma

Re: en/handbook/basics: proposed corrections #2

On Thu, 12 Dec 2013, Taras Korenko wrote: Good day, doc@ folks. The following notes were made while working on translation of "Users and Basic Account Management" of our handbook. I'd like to put them into the source file (basics/chapter.xml). Could anyone review that? P.S.: my (xml-style

  1   2   3   >