Re: Suggested Change
On Sat, 16 Nov 2019 at 02:51, Michael Crilly wrote: > I'd like to propose a very small change to the following page: > > > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-overview.html > > It states, "However, over 24,000 > <https://www.freebsd.org/ports/index.html> third-party > applications have already been ported to FreeBSD." > > However I believe the ports tree is at roughly 33,000 ( > https://www.freebsd.org/ports/index.html) now? Might it be worth bumping > this number up? > Done! ∴svn ci -F log Sendingen_US.ISO8859-1/htdocs/about.xml Transmitting file data .done Committing transaction... Committed revision 53599. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: update message id link to use https..
On Sat, 3 Nov 2018 at 11:13, John-Mark Gurney wrote: > > I'd like to apply the following patch, so that the link at the bottom > of messages is by default https instead of http: > > Any objections? LGTM -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: The Italian translation has not been updated since 2008
On Fri, 10 Aug 2018 at 01:42, Guido Falsi wrote: > > On 8/10/18 10:37 AM, Guido Falsi wrote: > > > > Apart from that, I wanted to create a page on wiki.FreeBSD.org to start > > coordinating things and give interested people some place to start from. > > > I forgot to mention, considering the situation the endeavor would start > working only on the handbook for the time being. > > Other documents will have to wait to see if enough contributors can be > found. Agreed. I'll remove everything but the handbook and documentation primer. I'm also happy to approve any changes required if someone needs doc committer approval. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
The Italian translation has not been updated since 2008
Hi all, The Italian translation has not been updated since r31375 on 2008-01-27. Future commits were either mechanical or global. - The committers guide still references CVS - The handbook still references sysinstall - Both still reference GNATS In general the documentation is out of date sufficient and not being updated. I'm planning on removing, at minimum, the committers guide. Unless I hear any objections I will also remove the italian handbook. Should anyone want to continue the translation it can be restored from VCS. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: why does "make install" write to files outside of DESTDIR ?
On Sun, 29 Jul 2018 at 17:55, Danilo G. Baio wrote: > > On Tue, Jun 19, 2018 at 06:12:32PM -0700, Eitan Adler wrote: > > On 13 June 2018 at 05:21, Eitan Adler wrote: > > > Steps to reproduce: > > > > > > rm -rf /srv/www/devbox/ > > > mkdir /srv/www/devbox/ > > > env DESTDIR=/srv/www/devbox/docs/docs make -s all install > > > > > > Expected behavior: no files are written to outside of > > > /srv/www/devbox/docs/docs > > > Actual behavior: /srv/www/devbox/articles and /srv/www/devbox/books exist > > > > > > Why is this? Is there some way to avoid this? > > > > anyone? This is particularly annoying when testing subsets of > > documentation. Is there any variable to set that will work similarly > > to MAKEOBJIRPREFIX from src? > > I'd like to run "make install" from a doc directory and have it > > install to the "expected" place so that browsing documentation from > > the webserver still works. > > > You should try DOCDIR instead of DESTDIR. > It will create all the structure, see this: Thank you! That saved me hours of frustration. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Interested in helping with documentation
On Fri, 6 Jul 2018 at 17:09, Sid wrote: > > > I'm pretty new to the community, but I'm interested in helping out in > various ways. I don't know that there's a lot I can contribute yet > (being so new), but I have noticed there are places in the documentation > that are out of date and I could fix. For example, section 5.6.1 lists > the Xorg xdm config files as being in /usr/local/lib/X11/xdm which it > seems they are not in newer versions of FreeBSD. I found them in > /usr/local/etc/X11/xdm. So at least when it comes to noticing errors > like that, and fixing them, I think I can contribute. > > > I know the basics of Docbook and version control, so if there is a > preferred way to submit corrections using diff files or something, I > should be able to pick up on that fairly quickly. > > > Anyway, I'd love to help out, and just looking for some guidance on how > to get started. Sid gave you the correct links to get started. I will also echo that the documentation committers are understaffed. That said, I wouldn't take it the way Sid has: it does take some chasing of people to get commits it, but it means that even small-time contributions can have a big impact. Also, while my development computer is dead, and thus I can't commit to much right now, I take mentoring new people to be much more important than my own commits: if you submit patches I'll try to review and commit them ASAP. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Documentation should rely on stylesheets for XML not txt tools
On Fri, 6 Jul 2018 at 17:41, Sid wrote: > > I'm aware of FreeBSD's XSLT and DSSSL stylesheets, mentioned at > https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/stylesheets.html, > but they should be used exclusively for its Docbook XML. > > XSLT's stylesheet needs to be a part of automating of tabbing and stripping > of spacing outside of element tags for .txt and other formats. Can you give me an example of a text tool we use? I'm not sure of what you mean. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Help needed with entities and headers and such
Hi all,
I recently tried updating the Javascript involved with google
analytics in r51804. Unfortunately I was either incomplete in my
testing or I had something special in my location environment since
the header is now incorrect. In particular it no longer expands ""
although replacing them with just "&" errors out. As a result, I reverted
the change, but I'd like to redo it correctly.
The specific problem looked like:
===
if (typeof navigator.doNotTrack !== 'undefined'
(navigator.doNotTrack == '1')) {
allow_track = false;
}
if (allow_track fbsdregex.test(h)) {
===
I'd like some help fixing this.
I am also aware of a similar change in share/xml/freebsd-xhtml-common.xsl where
needs to be replaced with the same content I added to header.ent.
Can I please get some help? Thanks!
--
Eitan Adler
___
freebsd-doc@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
share/misc/dev.archlist.txt and removed drivers
Is it correct to commit this now, since the drivers have been removed from HEAD, or does one have to wait until 11.x goes EoL ? Index: share/misc/dev.archlist.txt === --- share/misc/dev.archlist.txt (revision 51940) +++ share/misc/dev.archlist.txt (working copy) @@ -81,7 +81,6 @@ ie i386 iir i386,amd64 ips i386,amd64 isci i386,amd64 -ixgb i386,amd64 kue i386,amd64,powerpc lge i386,amd64 mfi i386,amd64 @@ -96,7 +95,6 @@ nfe i386,amd64 ng_bt3c i386,amd64 ng_ubt i386,amd64 nsp i386 -nxge i386,amd64 oce i386,amd64 ohci i386,amd64,powerpc oltr i386 @@ -170,7 +168,6 @@ uvisor i386,amd64 uvscom i386,amd64 vpo i386 vx i386,amd64 -vxge i386,amd64 wb i386,amd64 xe i386,amd64 zyd i386,amd64 -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Should no_NO.ISO8859-1 and sr_YU.ISO8859-2 remain in the tree?
For no_NO.ISO8859-1: The Last Changed Date of no_NO was on 2013-11-07 16:37:11 + (Thu, 07 Nov 2013). Of all the file, only the handbook has any translations of which there are only basics/chapter.xml, bibliography/chapter.xml, and install/chapter.xml. The latter of which still documents sysinstall. I also can't seem to find any reference to the filles here: https://download.freebsd.org/ftp/doc/. For sr_YU.ISO8859-2: I don't see any content in-tree at all. Neither of these are connected to the build. In short, I don't think these two translations are doing much good right now and should be removed. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: why does "make install" write to files outside of DESTDIR ?
On 13 June 2018 at 05:21, Eitan Adler wrote: > Steps to reproduce: > > rm -rf /srv/www/devbox/ > mkdir /srv/www/devbox/ > env DESTDIR=/srv/www/devbox/docs/docs make -s all install > > Expected behavior: no files are written to outside of > /srv/www/devbox/docs/docs > Actual behavior: /srv/www/devbox/articles and /srv/www/devbox/books exist > > Why is this? Is there some way to avoid this? anyone? This is particularly annoying when testing subsets of documentation. Is there any variable to set that will work similarly to MAKEOBJIRPREFIX from src? I'd like to run "make install" from a doc directory and have it install to the "expected" place so that browsing documentation from the webserver still works. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
why does "make install" write to files outside of DESTDIR ?
Steps to reproduce: rm -rf /srv/www/devbox/ mkdir /srv/www/devbox/ env DESTDIR=/srv/www/devbox/docs/docs make -s all install Expected behavior: no files are written to outside of /srv/www/devbox/docs/docs Actual behavior: /srv/www/devbox/articles and /srv/www/devbox/books exist Why is this? Is there some way to avoid this? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: 19.7. Additional Resources
On 17 April 2018 at 22:00, Jakob Rönnbäck <jakob.ronnb...@me.com> wrote: > Greetings, > > On https://www.freebsd.org/doc/handbook/zfs-links.html > <https://www.freebsd.org/doc/handbook/zfs-links.html> the links titled ”ZFS > Evil Tuning Guide” and ”ZFS Best Practices Guide” seem to only lead to ads > and nothing useful. Sendinghandbook/zfs/chapter.xml Transmitting file data .done Committing transaction... Committed revision 51567. Thanks! -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: FYI: FreeBSD-EN-17:10.tzdata.asc appears to be missing on the website
On 2 March 2018 at 00:16, Xin Li <delp...@delphij.net> wrote: > On 2/24/18 00:49, Eitan Adler wrote: >> https://www.freebsd.org/security/advisories/FreeBSD-EN-17:10.tzdata.asc >> results in a 404 for me. Not sure what's wrong but we should fix. > > Isn't it EN-17:09? en_US.ISO8859-1/htdocs/releases/11.1R/errata.html and en_US.ISO8859-1/htdocs/releases/10.4R/errata.html both refer to it EN-17:10 en_US.ISO8859-1/htdocs/releases/11.1R/errata.html 40: panic https://www.FreeBSD.org/security/advisories/FreeBSD-EN-17:10.tzdata.asc; target="_top">FreeBSD-EN-17:10.tzdata2�November�2017http://www.w3.org/TR/xhtml1/transitional;>Timezone database information en_US.ISO8859-1/htdocs/releases/10.4R/errata.html 40: namespace https://www.FreeBSD.org/security/advisories/FreeBSD-SA-17:10.kldstat.asc; target="_top">FreeBSD-SA-17:10.kldstat15�November�2017http://www.w3.org/TR/xhtml1/transitional;>Information leak https://www.FreeBSD.org/security/advisories/FreeBSD-SA-17:11.openssl.asc; target="_top">FreeBSD-SA-17:11.openssl29�November�2017http://www.w3.org/TR/xhtml1/transitional;>Multiple vulnerabilities http://www.w3.org/1999/xhtml; class="title" style="clear: both">3.�Errata NoticesErrataDateTopichttps://www.FreeBSD.org/security/advisories/FreeBSD-EN-17:10.tzdata.asc; target="_top">FreeBSD-EN-17:10.tzdata2�November�2017http://www.w3.org/TR/xhtml1/transitional;>Timezone database information -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Building FreeBSD docs out-of-tree
Is it possible to build the documentation out-of-tree? ∴DESTDIR=/srv/obj/fbsd/doc/ make all is insufficient Setting DOC_PREFIX is also not correct. I can't seem to find the correct variable, if one exists. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
FYI: FreeBSD-EN-17:10.tzdata.asc appears to be missing on the website
https://www.freebsd.org/security/advisories/FreeBSD-EN-17:10.tzdata.asc results in a 404 for me. Not sure what's wrong but we should fix. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Books not building on fresh checkout
On 31 December 2017 at 19:31, Russell Haley <russ.ha...@gmail.com> wrote: > On Sun, Dec 31, 2017 at 12:00 AM, Eitan Adler <li...@eitanadler.com> wrote: >> On 30 December 2017 at 23:57, Russell Haley <russ.ha...@gmail.com> wrote: >>> On Sat, Dec 30, 2017 at 11:39 PM, Eitan Adler <li...@eitanadler.com> wrote: >>>> On 30 December 2017 at 23:36, Russell Haley <russ.ha...@gmail.com> wrote: >>>>> Hi, >>>>> >>>>> I'm getting a build error on a fresh checkout. My base directory is >>>>> ~/freebsd. This is the same error that stumped me some months back. >>>>> Any advice would be grand. As follows: >>>>> >>>>> mkdir docs; svn co https://svn.freebsd.org/doc/head/ docs/ >>>> >>>> do you have the 'docproj' package installed? >>> >>> No I did not (but will shortly). Thank you! >> >> I would also encourage you to read the documentation primer. Available >> here: https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer >> >> >> >> -- >> Eitan Adler > > Hello, Section 7.7.1 discusses using General Entities to reference > other chapters in the book. The section uses an example listing > chapter1.xml, chapter2.xml and chapter3.xml. An introductory section > explained that the books are now organized using a directory per > chapter and the files are now simply called chapter.xml. > > Does the above dichotomy mean the section should use an example of > chapter1/chapter.xml like below? I think that specific section is supposed to be an example. Take a look at en_US.ISO8859-1/books/handbook/book.xml and books/handbook/chapters.ent for how to add a chapter. What you intending to contribute? Are you trying to write specific new content or generally want to learn how the system works. Both are fine, but might have differing approaches for what to do next. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Heads Up: bug status changed for untouched bugs since 2014
On 31 December 2017 at 11:47, Eitan Adler <li...@eitanadler.com> wrote: > Hi all, > > I recently made the following mass change: > > For bugs matching the following criteria: > Status: In Progress > Product: Base System, Community, Documentation, Other > Changed: (is less than) 2014-06-01 > Reset to default assignee and clear in-progress status. > > Note that mail was *skipped* for this change due to the large volume of > changes. > > A list of affected bugs is available at > https://people.freebsd.org/~eadler/files/2017-12-31-bug-change/list.txt Sorry for the spam! Due to the vagaries of bugzilla, in the previous iteration a comment was left, but the actual change did not occur. I just redid this now. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Heads Up: bug status changed for untouched bugs since 2014
Hi all, I recently made the following mass change: For bugs matching the following criteria: Status: In Progress Product: Base System, Community, Documentation, Other Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress status. Note that mail was *skipped* for this change due to the large volume of changes. A list of affected bugs is available at https://people.freebsd.org/~eadler/files/2017-12-31-bug-change/list.txt -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Books not building on fresh checkout
On 30 December 2017 at 23:57, Russell Haley <russ.ha...@gmail.com> wrote: > On Sat, Dec 30, 2017 at 11:39 PM, Eitan Adler <li...@eitanadler.com> wrote: >> On 30 December 2017 at 23:36, Russell Haley <russ.ha...@gmail.com> wrote: >>> Hi, >>> >>> I'm getting a build error on a fresh checkout. My base directory is >>> ~/freebsd. This is the same error that stumped me some months back. >>> Any advice would be grand. As follows: >>> >>> mkdir docs; svn co https://svn.freebsd.org/doc/head/ docs/ >> >> do you have the 'docproj' package installed? > > No I did not (but will shortly). Thank you! I would also encourage you to read the documentation primer. Available here: https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Books not building on fresh checkout
On 30 December 2017 at 23:36, Russell Haley <russ.ha...@gmail.com> wrote: > Hi, > > I'm getting a build error on a fresh checkout. My base directory is > ~/freebsd. This is the same error that stumped me some months back. > Any advice would be grand. As follows: > > mkdir docs; svn co https://svn.freebsd.org/doc/head/ docs/ do you have the 'docproj' package installed? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: FreeBSD web build failed on build-web.ysv.freebsd.org
Fixed in r51296. On 11 December 2017 at 23:04, User Www-data <www-d...@freebsd.org> wrote: > ===> news/1993 > ===> news/1996 > ===> news/1997 > ===> news/1998 > ===> news/1999 > ===> news/2000 > ===> news/2001 > ===> news/2002 > ===> news/2003 > ===> news/2004 > ===> news/2005 > ===> news/2006 > ===> news/2007 > ===> news/2008 > ===> news/2009 > ===> news/status > ===> news/2012-compromise > ===> platforms > --- all --- > ===> platforms/ia64 > ===> portmgr > ===> projects > --- projects.html --- > env > XML_CATALOG_FILES="file:///usr/local/www/build/head/en_US.ISO8859-1/htdocs/projects/catalog-cwd.xml > file:///usr/local/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml > file:///usr/local/www/build/head/share/xml/catalog.xml > file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude > --valid --noout --nonet projects.xml > projects.xml:286: parser error : Opening and ending tag mismatch: ul line 142 > and body > >^ > projects.xml:287: parser error : Opening and ending tag mismatch: body line > 17 and html > >^ > projects.xml:288: parser error : Premature end of data in tag html line 10 > > ^ > *** [projects.html] Error code 1 > > make[1]: stopped in /usr/local/www/build/head/en_US.ISO8859-1/htdocs/projects > 1 error > > make[1]: stopped in /usr/local/www/build/head/en_US.ISO8859-1/htdocs/projects > *** [all] Error code 2 > > make: stopped in /usr/local/www/build/head/en_US.ISO8859-1/htdocs > 1 error > > make: stopped in /usr/local/www/build/head/en_US.ISO8859-1/htdocs > 1.11 real 0.32 user 0.87 sys > > latestrevision.timestamp "2017-12-12 06:46:38" > latestrevision.committer "eadler" > latestrevision.number "51295" > ___ > freebsd-doc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org" -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Old Items
On 20 October 2015 at 21:15, Russell Haley <russ.ha...@gmail.com> wrote: > So is it fair game for me to pick through it and provide patches? If I make > comments, will original posters be notified? Can I make suggestions to > close items? Oh yeah! We'd love the help! -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Reviewing Mocks Designs
Hi all, Some of you might be aware that we have the tool Phabricator to do code review. I wanted to point out an additional feature that isn't being used much now. If you have an idea for FreeBSD artwork, website designs, or other image type reviews feel free to upload them to https://reviews.freebsd.org/pholio/ and send out the link. The https://www.freebsd.org/art.html page could certainly do with more art so please go ahead! -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: doc/release removal?
On 10 May 2015 at 17:48, Glen Barber g...@freebsd.org wrote: On May 10, 2015 8:19:35 PM EDT, Eitan Adler li...@eitanadler.com wrote: On 5 May 2015 at 09:20, Eitan Adler li...@eitanadler.com wrote: Hi all, doc/release/Makefile has many references to cvs checkouts. In addition doc/release/texts/ only has a README which references non-existent directories. Is there any reason not to `svn rm doc/release`? Unless anyone objects I plan on removing this directory soon. I can not see how it is useful to any recent process. Don't, until you get an explicit OK from doceng. Waiting is fine. Lets treat this as the second request to doceng@: are these directories still needed? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: doc/release removal?
On 5 May 2015 at 09:20, Eitan Adler li...@eitanadler.com wrote: Hi all, doc/release/Makefile has many references to cvs checkouts. In addition doc/release/texts/ only has a README which references non-existent directories. Is there any reason not to `svn rm doc/release`? Unless anyone objects I plan on removing this directory soon. I can not see how it is useful to any recent process. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
doc/release removal?
Hi all, doc/release/Makefile has many references to cvs checkouts. In addition doc/release/texts/ only has a README which references non-existent directories. Is there any reason not to `svn rm doc/release`? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: Spanish documentation translations
+doc@ On 12 April 2015 at 10:00, Federico Caminiti demian...@gmail.com wrote: Hi, I have a patch [1] that fixes some problems whith the spanish version of the FAQ. For the most part, the patch just adds opening question marks on those sentences that start with a question. I subscribed to the spanish mailing list ( d...@es.freebsd.org ) about a year and a half ago and sent them an email, but I haven't got a reply since and the list seems to be inactive since 2010. The spanish documentation in general seems to be in dire straits. For starters, the spanish version of the handbook covers FreeBSD 4, 5 and 6 (when all three versions EOLed a long time ago), and the FAQ is even more outdated, dealing with FreeBSD 2.0. I would love to fix those problems (and sync the spanish documentation with the english version) but I don't know where or how to send the patches (I uploaded my first patch to bugzilla about a week ago, but no one stepped up to review it yet so I'm not sure it is the right place). I would appreciate it if anyone could give me some pointers. I don't speak Spanish and so can not directly help with this question, but IMHO Federico deserves an answer here. Who is the right person to help Federico get his patches and translations in? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: doc/share/openoffice
On 6 April 2015 at 02:20, Hiroki Sato h...@freebsd.org wrote: Eitan Adler li...@eitanadler.com wrote in CAF6rxg=qemp0cabvs6gx0vkeshbjb-h-yxxecc2yyxsso68...@mail.gmail.com: li Hey, li li Does anyone know what doc/share/openoffice is actually used for? The li commit message indicates that in 2005: li li Slides written up in DocBook in /usr/doc/LANG/sides can now be output li directly as OpenOffice .sxi files, in addition to the PDF and HTML li output formats already supported. li These files are for creating .sxi file from XML with slides.dtd as the commit log explains. li Are these still needed? Can they be removed? There is no reason to proactively remove them while files in LANG/slides are quite old. What is the problem? Nothing specific. I have just been trying to do cleanup to the doc tree. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
doc/share/openoffice
Hey, Does anyone know what doc/share/openoffice is actually used for? The commit message indicates that in 2005: Slides written up in DocBook in /usr/doc/LANG/sides can now be output directly as OpenOffice .sxi files, in addition to the PDF and HTML output formats already supported. Are these still needed? Can they be removed? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
ports and packages procedure for releng
Hi re, I have a few quick questions: 1) Is anything on https://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng-packages/ar01s02.html which is current or accurate 2a) If not, is there a similar doc that has the correct information? 2b) If not, is it okay to delete the article? 3) Do you use any of the tooling here https://svnweb.freebsd.org/ports/head/Tools/scripts/release/ for releases? I see no commits to that directory from re@ recently. 4) If not, is there any harm in deleting that directory? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: FreeBSD Handbook section 20.3.5 typo
On 1 November 2014 13:33, Winston w...@psr.com wrote: In the FreeBSD Handbook page at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/zfs-zpool.html last changed 2014/11/01 17:20:42 GMT I suggest: s/where it m be/where it may be/ Fixed. Thanks! -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Bad Example Formatting?
Is there a way to signify good example code and bad example code? For example the latter has a light red background, and clearly says don't do this while the former has a light green background with a big checkmark? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: FreeBSD web build failed on build-web.stream.freebsd.org
On 29 June 2014 22:20, User Www-data www-d...@freebsd.org wrote: === doc/articles/wp-toolbox (all) === doc/books (all) === doc/books/arch-handbook (all) === doc/books/design-44bsd (all) === doc/books/dev-model (all) === doc/books/developers-handbook (all) env XML_CATALOG_FILES=file:///home/www/build/head/en_US.ISO8859-1/books/developers-handbook/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog /usr/local/bin/xmllint --nonet --noent --valid --dropdtd --xinclude /home/www/build/head/en_US.ISO8859-1/books/developers-handbook/book.xml book.parsed.xml.tmp /home/www/build/head/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml:632: parser error : Opening and ending tag mismatch: para line 629 and listitem /listitem ^ This is likely my fault, I'll look into it. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: Website now autocleans old files/pages (was: Re: FreeBSD web build failed on build-web.stream.freebsd.org)
On Tue, Feb 18, 2014 at 2:32 PM, Glen Barber g...@freebsd.org wrote: On Tue, Feb 18, 2014 at 12:36:55PM -0500, Glen Barber wrote: On Tue, Feb 18, 2014 at 05:33:53PM +, User Www-data wrote: [...] 13.59 real 6.06 user 8.14 sys mkdir: /usr/local/www/www.freebsd.org-clean: Permission denied *** [realinstall] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs. 0.03 real 0.00 user 0.02 sys Whoops. This is me fixing things. So, what I was working on is making the build clean up after itself, in particular, things that are no longer part of the build. DESTDIR has changed, and is purged before every build (even the quick incremental builds). Once the build finishes, the files are installed to the new DESTDIR, then synced to the public web root. When a full site refresh is done (once a week, as was done before), rsync is called with '--delete', so anything removed from the DESTDIR will be purged from the public web root. This is awesome. Thanks for working on it! -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: [PATCH] Use a bullet list for general policies
On Fri, Jan 31, 2014 at 2:21 PM, John Baldwin j...@freebsd.org wrote: Right now the internal policies page has a paragraph that lists the project's policies inline in one big sentence. I find this harder to work with as if I'm looking for a particular policy I have to scan the entire sentence. I think in this case a bulleted list works better. The patch below changes it (note that I haven't reordered them, and it may be that there is a better order, though I'm not sure what it would be). Alphabetical? Any objections? LGTM -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: c99 project
On Tue, Feb 5, 2013 at 5:35 AM, Giorgos Keramidas keram...@freebsd.org wrote: On 2013-02-04 21:48, Eitan Adler li...@eitanadler.com wrote: Is the following page still useful? Would there be any objection to me removing it? http://www.freebsd.org/projects/c99/index.html I think this is useful until we have full C99 support in at least one compiler toolchain. To the best of my knowledge this is not entirely true for either GCC or LLVM. So we should keep the page alive, until the project is done or canceled. Reviving an old thread here: The C99 compliance page was last updated in 2011 and it currently shows a large amount of outdated information. I see this page being used in many discussion forums, on IRC, etc. to show FreeBSD in a negative light. We need to either (A) move this to the wiki (b) update it on a routine basis or (c) delete it. Can I please have a volunteer go through the page and tell me what to change? I am more than happy to act as the 'doc proxy' but someone needs to commit to monitoring changes. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: docs/184550: bc -q option not documented in man page
On 12/6/13, delp...@freebsd.org delp...@freebsd.org wrote: Synopsis: bc -q option not documented in man page State-Changed-From-To: open-closed State-Changed-By: delphij State-Changed-When: Sat Dec 7 01:06:05 UTC 2013 State-Changed-Why: This is intentional. Won't fix. Responsible-Changed-From-To: freebsd-doc-delphij Responsible-Changed-By: delphij Responsible-Changed-When: Sat Dec 7 01:06:05 UTC 2013 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=184550 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org all options should be documented. An undocumented option is a bug. If we don't want people using it we should document as such. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: docs/184550: bc -q option not documented in man page
On Fri, Dec 6, 2013 at 9:18 PM, Glen Barber g...@freebsd.org 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 documented. case 'q': /* compatibility option */ break; Source code is not documentation. It it surprising to hear that, especially on this list. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: docs/184550: bc -q option not documented in man page
On Sat, Dec 7, 2013 at 1:44 AM, Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 12/6/13, 6:12 PM, Eitan Adler wrote: On 12/6/13, delp...@freebsd.org delp...@freebsd.org wrote: Synopsis: bc -q option not documented in man page State-Changed-From-To: open-closed State-Changed-By: delphij State-Changed-When: Sat Dec 7 01:06:05 UTC 2013 State-Changed-Why: This is intentional. Won't fix. Responsible-Changed-From-To: freebsd-doc-delphij Responsible-Changed-By: delphij Responsible-Changed-When: Sat Dec 7 01:06:05 UTC 2013 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=184550 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org all options should be documented. An undocumented option is a bug. If we don't want people using it we should document as such. Well, no, it's not an undocumented option but a bug-for-bug compatibility shim. Eh? However as Warren pointed out, it's a bug having it in synopsis and usage. It is not a bug. This is fixed in r259058. This is a bug. With our limited manpower, I think it's more important to improve our documentation in the direction that we describe our stuff better, like how to write a vt(4) driver, etc. I agree that we need better documentation for our own features; however, this is not a dichotomy. rather than documenting the bug-for-bug features which would just give the reader an impression like I can write program according to GNU command line standard and expect the BSD people to diligently implement bug-for-bug compatibility. A similar discussion occurred when we implemented '==' for test(1). If a program accepts some flag as input, or some text as input, it must be documented. We may document it as a non-portable, to be avoided feature, but it should not be left alone. ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: docs/184550: bc -q option not documented in man page
On Sat, Dec 7, 2013 at 2:09 AM, Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 12/6/13, 10:48 PM, Eitan Adler wrote: On Sat, Dec 7, 2013 at 1:44 AM, Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 12/6/13, 6:12 PM, Eitan Adler wrote: On 12/6/13, delp...@freebsd.org delp...@freebsd.org wrote: Synopsis: bc -q option not documented in man page State-Changed-From-To: open-closed State-Changed-By: delphij State-Changed-When: Sat Dec 7 01:06:05 UTC 2013 State-Changed-Why: This is intentional. Won't fix. Responsible-Changed-From-To: freebsd-doc-delphij Responsible-Changed-By: delphij Responsible-Changed-When: Sat Dec 7 01:06:05 UTC 2013 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=184550 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org all options should be documented. An undocumented option is a bug. If we don't want people using it we should document as such. Well, no, it's not an undocumented option but a bug-for-bug compatibility shim. Eh? However as Warren pointed out, it's a bug having it in synopsis and usage. It is not a bug. This is fixed in r259058. This is a bug. With our limited manpower, I think it's more important to improve our documentation in the direction that we describe our stuff better, like how to write a vt(4) driver, etc. I agree that we need better documentation for our own features; however, this is not a dichotomy. rather than documenting the bug-for-bug features which would just give the reader an impression like I can write program according to GNU command line standard and expect the BSD people to diligently implement bug-for-bug compatibility. A similar discussion occurred when we implemented '==' for test(1). If a program accepts some flag as input, or some text as input, it must be documented. We may document it as a non-portable, to be avoided feature, but it should not be left alone. Fair enough, how about this? Works for me. Thank you very much! -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: What are the limits for FFS file systems? 10+ years out of date..
On Sun, Nov 24, 2013 at 1:12 AM, John-Mark Gurney j...@funkthat.com 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 limiting factor on FS size... I've had Kirk review the patch, and he's fine w/ it... Shall I just commit it? inbps;386 - i386; After that, it is okay to commit. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: docs/182833: [porters-handbook]: document QMake usage, update Qt section
The following reply was made to PR docs/182833; it has been noted by GNATS. From: Eitan Adler li...@eitanadler.com To: bug-follo...@freebsd.org, m...@freebsd.org Cc: Subject: Re: docs/182833: [porters-handbook]: document QMake usage, update Qt section Date: Sun, 17 Nov 2013 17:04:14 -0500 Patch fails to apply :( Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: en_US.ISO8859-1/books/porters-handbook/book.xml |=== |--- en_US.ISO8859-1/books/porters-handbook/book.xml(revision 42890) |+++ en_US.ISO8859-1/books/porters-handbook/book.xml(working copy) -- Patching file en_US.ISO8859-1/books/porters-handbook/book.xml using Plan A... Hunk #1 failed at 6539. Hunk #2 failed at 6639. Hunk #3 failed at 6656. Hunk #4 failed at 6826. Hunk #5 succeeded at 6894 (offset -1 lines). 4 out of 5 hunks failed--saving rejects to en_US.ISO8859-1/books/porters-handbook/book.xml.rej Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -- |Index: en_US.ISO8859-1/books/porters-handbook/uses.xml |=== |--- en_US.ISO8859-1/books/porters-handbook/uses.xml(revision 42890) |+++ en_US.ISO8859-1/books/porters-handbook/uses.xml(working copy) -- Patching file en_US.ISO8859-1/books/porters-handbook/uses.xml using Plan A... Hunk #1 succeeded at 221 (offset 42 lines). done -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: How to start contributing?
On Sun, Oct 20, 2013 at 6:10 AM, Muhammad Hussein Nasrollahpour iapplechocol...@me.com wrote: Hi, I wanna translate documentation and website to my own language and I need a quick roadmap that how I can start? Are you familer with how to check out the doc repository? You may want to start with http://www.freebsd.org/doc/en/books/fdp-primer/ sections 2.1, 3 and 7. It will some effort to start a translation but as you do some work you will find more people to join you, hopefully :) -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
About FreeBSD.org visitors
Here is an overview of the people that visit FreeBSD.org: http://people.freebsd.org/~eadler/files/Report-10.01.pdf Some takeaways: - More than half (60%) the people that come to our website leave without going to another page (called 'bouncing'). However these users spend more time than any other user per page. - Non-bouncing users had an average of just over 4 pages per session but spent about an average of 0.86/s per page. They spend most of their time on the last page. From these I think we can take away that most people come looking for something very specific. How can we fix this? Better search maybe? Improved navigation bar? Its up to you to work on this. - New users spend a lot *less* time on the site than repeat visitors. Do we need better advocacy data? Less text to confuse new users? Is this trend specific to FreeBSD or is it true across the board? - Internet Explorer is 10% of our traffic. Many of ours users use Windows as there primary desktop platform. Probably more if we include not-IE on Windows. What other insights do you see? What other data might be helpful for us? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: About FreeBSD.org visitors
On Thu, Oct 3, 2013 at 2:23 PM, Remko Lodder re...@freebsd.org wrote: I thought we were going to see There is a lot more information around. I must ask permission for each and every report I send in public. I already asked to share some tables regarding visitor path, most used pages, etc. Also, I am not an SEO / web page analytics expert. I need more advice on what you want / need to see. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: About FreeBSD.org visitors
On Thu, Oct 3, 2013 at 2:23 PM, Remko Lodder re...@freebsd.org wrote: On Oct 3, 2013, at 5:14 PM, Eitan Adler li...@eitanadler.com wrote: Here is an overview of the people that visit FreeBSD.org: http://people.freebsd.org/~eadler/files/Report-10.01.pdf Some takeaways: - More than half (60%) the people that come to our website leave without going to another page (called 'bouncing'). However these users spend more time than any other user per page. - Non-bouncing users had an average of just over 4 pages per session but spent about an average of 0.86/s per page. They spend most of their time on the last page. From these I think we can take away that most people come looking for something very specific. How can we fix this? Better search maybe? Improved navigation bar? Its up to you to work on this. - New users spend a lot *less* time on the site than repeat visitors. Do we need better advocacy data? Less text to confuse new users? Is this trend specific to FreeBSD or is it true across the board? - Internet Explorer is 10% of our traffic. A graph of visitor flow and falloff: http://people.freebsd.org/~eadler/files/reports/report-10.01-flow.pdf Which pages people visit and how long they stay there: http://people.freebsd.org/~eadler/files/reports/report-10.01-pages.pdf This is the same report but sorted by most time spent on page and filtered to exclude pages that match ^/cgi http://people.freebsd.org/~eadler/files/reports/report-10.01-most-time.pdf Of note: if you sort by most time spent on page you get man pages -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Moving __FreeBSD_version to an appendix
Hi, At the moment the listings of __FreeBSD_version values in in the dos and don't section. I'd like to move it to an appendix. This will create a new file similar to how uses.xml is currently implemented. There is a patch for versions.xml but it is deceptively long (I used 'svn cp' to ensure the history is preserved). Index: Makefile === --- Makefile(revision 42681) +++ Makefile(working copy) @@ -21,6 +21,7 @@ INSTALL_ONLY_COMPRESSED?= # XML content SRCS= book.xml SRCS+= uses.xml +SRCS+= versions.xml # Images from the cross-document image library IMAGES_LIB+= callouts/1.png Index: book.xml === --- book.xml(revision 42683) +++ book.xml(working copy) @@ -2,6 +2,7 @@ !DOCTYPE book PUBLIC -//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN ../../../share/xml/freebsd45.dtd [ !ENTITY values.uses SYSTEM uses.xml +!ENTITY values.versions SYSTEM versions.xml ] !-- @@ -11489,4847 +11490,6 @@ Reference: lt;http://www.freebsd.org/ports/portau /para /sect1 -sect1 id=freebsd-versions ... -/sect1 - sect1 id=dads-after-port-mk titleWriting Something After filenamebsd.port.mk/filename/title @@ -17256,5 +12416,45 @@ pre-install: /tgroup /table /sect1 + +sect1 id=freebsd-versions + titleliteral__FreeBSD_version/literal Values/title + + paraHere is a convenient list of + literal__FreeBSD_version/literal values as defined in + ulink + url=http://svnweb.FreeBSD.org/base/head/sys/sys/param.h?view=markup;sys/param.h/ulink:/para + + table frame=none + titleliteral__FreeBSD_version/literal Values/title + + tgroup cols=3 + thead + row + entryValue/entry + entryDate/entry + entryRelease/entry + /row + /thead + + tbody + values.versions; + /tbody + /tgroup + /table + + note + paraNote that 2.2-STABLE sometimes identifies itself as + quote2.2.5-STABLE/quote after the 2.2.5-RELEASE. The + pattern used to be year followed by the month, but we + decided to change it to a more straightforward major/minor + system starting from 2.2. This is because the parallel + development on several branches made it infeasible to + classify the releases simply by their real release dates. + If you are making a port now, you do not have to worry about + old -CURRENTs; they are listed here just for your + reference./para + /note +/sect1 /chapter /book Does anyone have any specific objections to this? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: RFC: Upgrading to DocBook 5.0
On Wed, Jul 3, 2013 at 10:40 AM, Alberto Mijares amijar...@gmail.com wrote: IMHO, is a good thing to keep a visual clue of the level you are going down while writing. So, sect[123...] should be kept, I think. top posting, really? On Wed, Jul 3, 2013 at 3:56 AM, Gabor Kovesdan ga...@freebsd.org One more thing to discuss: shall we maintain the sect1, sect2, ... elements or just use section? How would this be rendered in HTML? Does this change anything? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: Handbook obsolescence scan: The vinum Volume Manager
On Wed, Jun 26, 2013 at 4:23 AM, Warren Block wbl...@wonkity.com 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 section for obsolete information that may still be useful to someone, somewhere, but not most users. I find that articles are less often - updated - translated so I think that downgrading the content to an article is a good step if we think the information is not useful in the general case. However, if the information is obsolete we already have http://docs.freebsd.org/doc/ and it should be removed entirely. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: missing 'single page' link.
On Sat, May 18, 2013 at 7:36 PM, Eitan Adler li...@eitanadler.com wrote: Pages such as http://www.freebsd.org/doc/en/articles/committers-guide/ seem to be missing a link to the 'single page' version of the article (http://www.freebsd.org/doc/en/articles/committers-guide/article.html) Is this a result of the recent XML toolchain changes? ping? -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: Correccion sobre hci
2013/6/2 Luis Manuel Sánchez luissanchez...@gmail.com: Hola... Lei el articulo de Bluetooth en espanol y encuentro que hci host controller interface esta mal traducido. http://www.freebsd.org/doc/es_ES.ISO8859-1/books/handbook/network-bluetooth.html Propongo la siguiente tradiccion... interface maquina controlador Espero vean la razon. Saludos! Hi, I believe very few Spanish speaking committers are actively working on documentation. It would be amazingly helpful if you could help with this effort. I would certainly be willing to work with you on getting changes into the tree. That said, Can you tell me exactly which phrase needs to be changed here? Even if you can't help more than a little I'll try to find someone to review the diffs (I don't speak Spanish) -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: [PATCH] Error in 10.1 of Handbook.
On 5 May 2013 15:55, Steve Kargl s...@troutmask.apl.washington.edu wrote: --- chapter.xml.orig2013-05-05 14:48:52.0 -0700 +++ chapter.xml 2013-05-05 14:49:25.0 -0700 @@ -40,7 +40,7 @@ paraos; can also be configured to act as a print server on a network; in this capacity os; can receive print jobs from a - varietyof other computers, including other os; computers, + variety of other computers, including other os; computers, windows; and macos; hosts. os; will ensure that one job at a time is printed, and can keep statistics on which users and machines are doing the most printing, produce I'll take care of this -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: RFC: Changing the documentation's font style.
On 12 April 2013 13:06, Lowell Gilbert freebsd-li...@be-well.ilk.org wrote: Patrick Powell papow...@astart.com writes: I tried an experiment. At smaller font sizes the San Serif fonts were easier to read. Ummm... and I am definitely an 'Old Timer'. Not only is this a bikeshed discussion, it's the equivalent of arguing what color of papier-mâché to build the bikeshed out of. The FreeBSD style sheet does not and should not specify anything about the display font. We should not override the reader's choice of font, any more than we should force a particular font size. The CSS Cascading mechanics prohibit the FreeBSD style sheet from entirely overriding the user's choice. Please see 6.4.1 of the CSS 2.1 specification. IMHO we should specify a font that a) looks nice b) is easy to read. and support issyl0's changes Users that have different preference may override the style sheet. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: RFC: Changing the documentation's font style.
On 12 April 2013 13:47, Lowell Gilbert freebsd-li...@be-well.ilk.org wrote: Most people have already configured their browsers with what they think is a fairly good font for reading generic text. There's nothing particularly special about our documentation that gives us knowledge they didn't have when they made the choice. Most people have never opened the options screen of their browser, let along modified the default font. The equation is different for people who don't know that they *can* change their browser font settings at all. I wouldn't have thought that there were really that many such people in the grand scheme of things, but I'll admit that this discussion does seem to cast that assumption into question. The vast majority of people don't know they can change their default font. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: Ports web database
On 2 April 2013 09:13, Marko Lerota mler...@claresco.hr wrote: Something is wrong. It says that Last database update is: 2012-11-11 10:45:48 UTC This is a known issue that resulted from shutting off the CVS exporter. Unfortunately, not all the users of CVS were completely enumerated. It is being worked on. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
a proposal for the FAQ
Hi all, Over the past several months I have been working on a project called ThwackAFAQ. For those who don't know this project has been to review, edit, and rewrite the FAQ to be relevant to the modern day. I've removed references to hardware that hasn't been sold in over 10 years or to software features that reached their EoL in FreeBSD 2.x. At this date I feel the project has reached a level of maturity such that it makes sense to write this email: I propose that we merge the handbook into the FAQ. While they both cover the same material the handbook source is over 83892 lines of XML while the FAQ is now at a measly 8242 lines. Further the FAQ is in bite sized chunks while the FAQ requires lots of tedious reading. Translators currently have issues keeping up with the pace of changes in both books, and must translate the same basic content twice. If only we could have one clear and canonical source for translators to work with. Sure there are some topics not covered in the same depth in the FAQ but many Linux distributions solve this in a very nice way: distribute the details and extraneous items to bloggers and tip writers. This releases us, the doc team, from all the extra work of writing and fact checking things that will no longer be true in the next version of FreeBSD. Not only that but it even generates more content for the front page where we publish articles written about the operating system. Over the next few weeks (as soon as the doc slush ends) I intend to move the last few remaining portions of the handbook into the FAQ and commit the removal of the handbook once and for all. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: [patch] en/handbook/ports: a tiny cleanup
On 21 March 2013 14:21, Taras Korenko d...@ukrhub.net wrote: Hi, folks. A couple of noticed typos in $subj are in an attacment. LGTM -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: Where is the freebsd-vendors mailing list?
On 7 March 2013 21:03, Derek Wood ddw...@highdensity.org wrote: On Thu, Mar 07, 2013 at 04:14:12PM -0800, Chris H wrote: Greetings, Where's the freebsd-vendors mailing list? According to: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL It exists. Thank you for all your time, and consideration in this matter. --Chris ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org It looks like it has been retired as of 2010: http://lists.freebsd.org/pipermail/freebsd-vendors/2010-November/40.html I shall remove it from that page. Thanks for letting us know. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
Re: Would enough people like a tutorial in freebsd developer handbook
On 26 February 2013 15:46, Anthony Brown groundup2360917182914...@gmail.com wrote: Would enough people like a tutorial in freebsd developer handbook on freebsd 64 bit assembly language using the c standard library. Yes! These sort of articles are very useful to new developers seeking a platform on which to practice. I'd be happy to review for documentation as well as content. -- Eitan Adler ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org
