[trimmed ccs and quoted text]
On 2023-01-31 08:02, Mathieu Arnold wrote:
On Mon, Jan 30, 2023 at 12:43:27PM +0100, Sergio Carlavilla wrote:
On Mon, 30 Jan 2023 at 12:31, Mathieu Arnold wrote:
>
> On Mon, Jan 30, 2023 at 11:36:05AM +0100, Sergio Carlavilla wrote:
> > El jue., 26 ene. 2023
On 2022-10-26 16:07, Mitchell Horne wrote:
Hello,
Currently, hier(7) contains detailed but outdated [1] documentation of
the directory structure under /usr/src. The src tree's README.md file
duplicates much of this information by maintaining a distinctly
incomplete table.
Noting that (on 13.1
On 2022-08-07 13:53, Danilo G. Baio wrote:
Doc committers are encouraged to update the source .po files
whenever
there are updates in the English documentation part.
Do the FDP primer and or the Committer's Guide need a mention of this?
--
#BlackLivesMatter #TransWomenAreWomen
The examples in
https://docs.freebsd.org/en/books/fdp-primer/manual-pages/#manual-pages-sample-structures
use quotes around the .Nd argument, but only about 1/6 of actual manual
pages (outside contrib/) use them:
~/FreeBSD/src% git grep -E '^\.Nd "[^ ]* ' | grep -v -E '^contrib/' | wc
-l #
On 2022-06-04 07:18, Bjoern A. Zeeb wrote:
On Fri, 3 Jun 2022, Pau Amma wrote:
Currently, 3 section 4 manual pages say to use kld_list in rc.conf for
loading: acpi_video(4), iwlwifi(4), and rtw88(4). Contrasting this
with 367 following share/examples/mdoc/example.4's lead and
instructing
Currently, 3 section 4 manual pages say to use kld_list in rc.conf for
loading: acpi_video(4), iwlwifi(4), and rtw88(4). Contrasting this with
367 following share/examples/mdoc/example.4's lead and instructing to
use loader(8)-time loading, the current approach appears to be:
loader(8)-time
ebsd.org/bugzilla/show_bug.cgi?id=257481: (no
images in epub) if still applicable
- https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257404: review
or otherwise move forward
Original Message
Subject: FreeBSD Handbook improvement survey
Date: 2022-04-16 13:04
From: Pau Amma
To
The FreeBSD Foundation contracted me to develop a prioritized plan for
improving and updating the FreeBSD Handbook. For the first stage of this
project, I have identified a number of issues needing improvement. To
prioritize the issues, please tell me which are important to you
personally.
On 2022-03-08 05:25, Azrael JD wrote:
Greetings,
I would like to translate the FreeBSD documentation to Indonesian.
Please let me know where to start, as there is no one listed on the
documentation project's translation teams page that are translating the
FreeBSD documentation to Indonesian.
Better late than never? I just noticed that (at least in the Porter's
Handbook - I haven't checked others) there's no anchor for chapters
themselves, only sections under them, and thus no way to link to a whole
chapter. While you can link to the first subsection instead, that
assumes no text
Summary: Two recent Bugzilla reports about poor UX caused by manual page
name collisions between different ports
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256676 and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254466) were both
closed as "Works As Intended". I think the current
On 2021-11-22 22:16, Rocky Hotas wrote:
On nov 21 17:31, Sergio Carlavilla wrote:
And the dark theme.
Apart from that, you can see the new Documentation Portal here[6].
- A dark theme would be very useful (and also very cool!).
Agreed, especially for photosensitive users (accessibility).
On 2021-09-23 17:41, Rannug Blah wrote:
On Thu, Sep 23, 2021 at 5:29 PM Pau Amma wrote:
*nod* Good point. I was thinking about making the FreeBSD installer
itself do it but your approach works instead (or in addition) and
would
be much quicker to implement and release.
Even better if we
On 2021-09-23 16:58, Rannug Blah wrote:
Yeah I know it's easy to get the package, what I'm referring to is that
the
average user might find it too cumbersome to do, as you have to now;
install the package, find and pick a codex out of a list of many which
you don't know anything about, manually
On 2021-09-23 11:26, Rannug Blah wrote:
On Wed, Sep 22, 2021 at 1:10 AM Pau Amma wrote:
I for one don't think you are. Would you be willing and able to
contribute draft language or review a draft addition?
I think so, I already set up a VM and am messing around with yasr and
stuff, I
On 2021-09-21 17:12, Rannug Blah wrote:
I was browsing through the amazing volume that is the handbook and
realized
that you have as far as I can tell
no section about accessibility. So I felt I should mention the need,
just a
simple chapter about setting up yasr or something
and providing
On 2021-07-21 13:45, Ceri Davies wrote:
On Tue, Jul 20, 2021 at 06:35:24PM +, Pau Amma wrote:
"6.4.1. Ordered lists" is an example of a bulleted list and "6.4.2.
Unordered lists" is an example of a numbered list, but I would expect
"ordered" to refer to
"6.4.1. Ordered lists" is an example of a bulleted list and "6.4.2.
Unordered lists" is an example of a numbered list, but I would expect
"ordered" to refer to numbered lists and "unordered" to bulleted lists.
Am I missing something? (Unless someone tells me I am, I'll either open
a bug or -
Executive summary: The '' line in
share/xml/urls.ent doesn't respect DOCDIR, but I'm not sure whether and
how to best fix it (in the toolchain or in the FDP primer), or even if
it needs to be fixed at all (eg I could be missing something).
Longer version, lightly paraphrased and expanded from
While trying to duplicate the PDF output error reported in
https://reviews.freebsd.org/D22708#502794 (using "make FORMATS=pdf" in
~/doc/en_US.ISO8859-1/books/handbook), I got the following error
instead:
...
/usr/bin/env FOP_OPTS="-Xss1024k -Xmx1431552k" /usr/local/bin/fop -c
On Wed, November 13, 2019 2:59 am, Pau Amma wrote:
> [...}
> Why? Did I make a mistake I'm not seeing?
Never mind. Turns out that "~docobj" and "~/docobj" are not the same.
___
freebsd-doc@freebsd.org mailing list
https:/
Following a Freenode IRC discussion with tsoome on the unadvisability of
using whole disks in vdevs, I wanted to add the following to
en_US.ISO8859-1/books/handbook/zfs/chapter.xml:
Using an entire disk as part of a bootable
pool is
On Sat, November 2, 2019 4:55 am, Danilo G. Baio wrote:
> On Sat, Nov 02, 2019 at 04:05:26AM -0000, Pau Amma wrote:
>>
>> % env DESTDIR=/usr/home/pauamma/docobj make all install
>>
>> This gave me, after a while:
>
> Try DOCDIR instead of DESTDIR.
Thanks, tha
So I decided to try making a minor change to the FreeBSD Handbook myself,
and to test it, I ran (from ~/doc where the raw files live):
% env DESTDIR=/usr/home/pauamma/docobj make all install
This gave me, after a while:
/bin/mv pgpkeyring.txt.tmp pgpkeyring.txt
Warning: Object directory not
I just finished reading through
https://www.freebsd.org/doc/en_US.ISO8859-1/books/dev-model/ for the first
time, and I believe it would be a better document with some or all of the
following changes, not all of which I have the required information to
specify completely:
- The text should use
On Tue, October 8, 2019 3:45 pm, Benjamin Kaduk wrote:
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/writing-style-guidelines.html
> says "use the serial comma".
Thanks.
___
freebsd-doc@freebsd.org mailing list
I've seen examples of both styles in the handbook, eg
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/audit-administration.html
and
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-usb-tethering.html,
so I'm unsure.
Important note: I'm only asking which one (if not
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/using-gnome.html
(in 6.10.1. Introduction) contains a mention of adding DEVELOPER=yes to
/etc/make.conf that to me looks out of place and redundant with that in
section 3,
28 matches
Mail list logo
