Re: Missing Africa support vendor

[jpb]

Ross,

Do you have a specific website for your business?  "consultant.com"
appears to be a generic landing page or domain squatter.

Please advise,
Jim B.



On Mon, 4 Nov 2024 09:21:16 +0200
Ross Cameron  wrote:

> Hi Jim,
> 
> Thanks for your prompt response.
> 
> The most suitable page, as far as I can see, would be the consulting
> vendors page over on:
> https://www.freebsd.org/commercial/consult_bycat/
> 
> I'm located in:
> Johannesburg, South Africa
> 
> I provide a broad range of UNIX Systems consulting services.
> Everything from:
>   - Systems administration services (onsite and remote)
>   - Network design and implementation (LANs, WiFi deployments,
> private and public cloud services, custom FreeBSD based firewalls)
>   - Large storage deployments (ZFS, NFS, CIFS)
>   - Hypervisor deployments and management (Bhyve and KVM)
> 
> If there is anything else you'd like to know, please feel free to
> contact me.
> 
> ~~
> Regards,...
> Ross Cameron
> eMail:  rwd.came...@consultant.com
> Mobile:  +27 (0)73 958-3074
> 
> 
> 
> 
> "Opportunity is most often missed by people because it is dressed in
> overalls and looks like work."
> ~  Thomas Alva Edison  ~
> Inventor of 1093 patents, including the light bulb, the phonogram and
> motion pictures.
> 
> On Mon, 4 Nov 2024, 02:01 jpb,  wrote:
> 
> > On Sun, 3 Nov 2024 21:06:28 +0200
> > Ross Cameron  wrote:
> >
> > > Hi there
> > >
> > > Graham Perrin suggested I email this list to bring Bug 282242 to
> > > your attention.
> > >
> > > The website doesn't list any support vendors for Africa and I
> > > happen to be one.
> > >
> > > ~~
> > > Regards,...
> > > Ross Cameron
> > > eMail:  rwd.came...@consultant.com
> > > Mobile:  +27 (0)73 958-3074
> > >
> > >
> > >
> > >
> > > "Opportunity is most often missed by people because it is dressed
> > > in overalls and looks like work."
> > > ~  Thomas Alva Edison  ~
> > > Inventor of 1093 patents, including the light bulb, the phonogram
> > > and motion pictures.
> >
> > Ross,
> >
> > Please send a 2-3 sentence summary of your offerings with a general
> > location.  I'll see if we can add you to our support vendors list.
> >
> > Best Regards,
> > Jim Brown
> > j...@jimby.name
> >

Re: Missing Africa support vendor

[jpb]

On Sun, 3 Nov 2024 21:06:28 +0200
Ross Cameron  wrote:

> Hi there
> 
> Graham Perrin suggested I email this list to bring Bug 282242 to
> your attention.
> 
> The website doesn't list any support vendors for Africa and I happen
> to be one.
> 
> ~~
> Regards,...
> Ross Cameron
> eMail:  rwd.came...@consultant.com
> Mobile:  +27 (0)73 958-3074
> 
> 
> 
> 
> "Opportunity is most often missed by people because it is dressed in
> overalls and looks like work."
> ~  Thomas Alva Edison  ~
> Inventor of 1093 patents, including the light bulb, the phonogram and
> motion pictures.

Ross,

Please send a 2-3 sentence summary of your offerings with a general
location.  I'll see if we can add you to our support vendors list.

Best Regards,
Jim Brown
j...@jimby.name

Re: [Bug 281675] Links to the bug database broken on main (and other pages).

[jpb]

On Mon, 23 Sep 2024 20:27:17 +
bugzilla-nore...@freebsd.org wrote:

> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281675
> 
> Bug ID: 281675
>Summary: Links to the bug database broken on main (and
> other pages).
>Product: Documentation
>Version: Latest
>   Hardware: Any
> OS: Any
> Status: New
>   Severity: Affects Some People
>   Priority: ---
>  Component: Website
>   Assignee: d...@freebsd.org
>   Reporter: dgilb...@eicat.ca
> 
> The link Supports->Bug Reports on the main page doesn't work in
> Firefox 130. In fact, the following link Submitting Bug Reports
> doesn't either.  If I key in the url I see down in the lower left of
> the window ... that works, but somehow clicking does nothing.
> 
> This is using Firefox 130.0 compiled and installed on FreeBSD-14.1p5.
> 


14.1-p4 and Firefox 130 from packages works from my location.


From the FreeBSD home page, clicking on Support->Bug Reports brings me
to  https://bugs.freebsd.org/bugzilla/query.cgi?format=advanced

Support->Submitting Bug Reports  brings me to:
https://www.freebsd.org/support/

Have you tried another browser?  Does it have the same problem you are
describing?

Do you have another system where you can install Firefox from packages?

Best,
Jim B.

Re: Danish translation

[jpb]

On Tue, 26 Nov 2024 13:53:05 +0100 (CET)
Thomas Bleses  wrote:

> Hi there
>  
> Id like to help translating the documentation into danish. Are there
> anyone else out there going at it, that hasn't been published to the
> translations page? Best regards Thomas Bleses

Hello Thomas,

Thanks for your interest in translating FreeBSD documentation!

I'm not aware of anyone else working on Danish translations, but you
have asked the right question to the right group of people.  Someone
else may contact you directly.

To get started, have a read through the FreeBSD Documentation Project
Primer for New Contributors ("FDP Primer"):
https://docs.freebsd.org/en/books/fdp-primer/
with particular attention to the chapters on Translation.

There are also activities to help you get started with the Documentation
Project toolkit.

Feel free to reach out if you need help - with the tools and
procedures, not the translating.  I don't know any Danish!

Best Regards,
Jim B.

[FDP] Generating an Index for PDF Documents

[jpb]

Here's a quick summary on how to generate an index for FreeBSD FDP
books, articles, and multi-part documents.  Happily, the indexing
tooling is already built into Asciidoctor.

1. Decide where you want the index.  In my case I added another
"chapter" document directory -  foo-index/_index.adoc.
Edit the _index.adoc and change the title, and any next/prev.  You will
also need to change the weight.  The weight value should be higher than
the highest chapter in the book.  This will place the index at the end
of the document or book.

2. Add this section info to the bottom of the _index.adoc file after
all the front matter and hugo stuff.  This tells Asciidoctor where you
want the index.  This is all you need to add.

[index]
= Index

3. You'll now have to go through all the chapters and tag each line
that has a term you want in the index.  Add the following to the end of
the line:

 indexterm:[foo]  for term 'foo' or
 indexterm:[buzzword,foo]  which will add an entry for foo under the
'buzzword' index.

4. Make the document as you usually do (make DOC_LANG=whatever).
When the book is completed, open the PDF version and check out the
index at the end (or wherever you put it).

NOTES:
You can tag any kind of text - regular text, text inside [NOTEs],
[TIPs], etc. or text inside listings such as [.programlisting],
[.source], [subs=+quotes] etc.

I've found that tagging a singular stem version of a word relieves you
from having to text all other variations.

You don't have to tag every instance of a term. If there are
several sentences together, each having the same term, or even nearby
paragraphs all having the same term, just tag the term once.  The index
entry will be the same for all of them.

Check these examples:

https://www.jimby.name/fbsd/_index.adoc.txt
https://www.jimby.name/fbsd/fdp_index_example.png

Best Regards,
Jim B.
j...@jimby.name

[UPDATED] Re: [FDP] Generating an Index for PDF Documents

[jpb]

[snip]
> 
> NOTES:
> You can tag any kind of text - regular text, text inside [NOTEs],
> [TIPs], etc. or text inside listings such as [.programlisting],
> [.source], [subs=+quotes] etc.
> 

Nope.

It turns out that tagging terms inside listing, messes with the HTML
output.  See attached example.

Looks like the best option for listings is to put all the indexterm
statements on a line before the listing header.  For example:

indexterm:[module, ipfw] indexterm:[NAT64] indexterm:[module, ipfw_nat64]
[subs=+quotes] 

# *kldload ipfw*

The next line loads the NAT64 module. 

# *kldload ipfw_nat64* 


There are a couple of other considerations.  I will do more testing and 
update the links below with better guidance.

https://www.jimby.name/fbsd/_index.adoc.txt 
https://www.jimby.name/fbsd/fdp_index_example.png 

Jim B.

Re: Translation questions

[jpb]

On Sat, 12 Apr 2025 13:47:08 -0700
Sayed Mohammad Badiezadegan  wrote:

> Hello,
> 
> This is Mohamad,
> 
> I'm interested in translating the FreeBSD documents to my native
> language (Persian).
> 
> I saw the list of your available translations, but the Iran BSD User
> Group is not active now, and there is no Persian document available
> on your website.
> 
> I have 3 questions about the process:
> 
> *1. Is there any template (for example, LaTeX or MS. Word,..)
> available that I can use for my translation?*
> 
> *2. How can I get the FreeBSD official email (***@freebsd.org
> ) to communicate with my readers?*
> 
> *3. I also wrote a book recently about FreeBSD customization for HPC
> systems for free (available by scanning the following barcode in my
> signature). Is it possible to publish it on the FreeBSD official
> website?*
> 
> I would appreciate your valuable time and consideration.
> 
> Best regards,
> 
> 

Hello Mohamad,

Thanks for your interest in FreeBSD!  Yes, you can work on translating
the FreeBSD documentation set into Persian.

To get started, please read through the FreeBSD Documentation Project
Primer for New Contributors available here:

https://docs.freebsd.org/en/books/fdp-primer/

Pay special attention to the translation chapters - I'm sure they will
be of interest to you.

There are several actions to take in getting software installed on your
system to be able to edit and translate documentation.

The documentation set is written in AsciiDoctor, so you will want to
become familiar with using that.  The project also uses git for
downloading and managing a local repository.

There is also a Discord server used by many teams - here is an invite:

https://discord.gg/d3pjPbzM

Many people hang out in the #lobby channel for a wide variety of
discussions, but there are other channels you can explore.

Welcome aboard.

Best Regards,
Jim B.
j...@jimby.name

Re: Translation questions

[jpb]

Hi Mohamad,

Yes, the document source in AsciiDoc format are available.  Read
through the FDP Primer for details.  It's all in there.

https://docs.freebsd.org/en/books/fdp-primer/

Again, be sure to read through the translation chapters (8, 9, 10) to
get a sense of how it all works.

Best Regards,
Jim B.







On Sat, 12 Apr 2025 15:51:01 -0700
Sayed Mohammad Badiezadegan  wrote:

> Hello Jim,
> 
> Thank you so much for your response. This is exactly what I am
> looking for. I have much experience using the LaTeX for my old
> Mathematics article, but I found that AsciiDoc should be easier to
> use, especially for documentation.
> 
> Are the FreeBSD documents' source (in AsciiDoc format) available to
> download so that I can write corresponding translated sentences with
> the same template format? I want Persian readers to sense more
> FreeBSD document structure.
> 
> Thank you again for your time.
> 
> 
> 
> On Sat, Apr 12, 2025 at 2:26 PM jpb  wrote:
> 
> > On Sat, 12 Apr 2025 13:47:08 -0700
> > Sayed Mohammad Badiezadegan  wrote:
> >  
> > > Hello,
> > >
> > > This is Mohamad,
> > >
> > > I'm interested in translating the FreeBSD documents to my native
> > > language (Persian).
> > >
> > > I saw the list of your available translations, but the Iran BSD
> > > User Group is not active now, and there is no Persian document
> > > available on your website.
> > >
> > > I have 3 questions about the process:
> > >
> > > *1. Is there any template (for example, LaTeX or MS. Word,..)
> > > available that I can use for my translation?*
> > >
> > > *2. How can I get the FreeBSD official email (***@freebsd.org
> > > <http://freebsd.org>) to communicate with my readers?*
> > >
> > > *3. I also wrote a book recently about FreeBSD customization for
> > > HPC systems for free (available by scanning the following barcode
> > > in my signature). Is it possible to publish it on the FreeBSD
> > > official website?*
> > >
> > > I would appreciate your valuable time and consideration.
> > >
> > > Best regards,
> > >
> > >  
> >
> > Hello Mohamad,
> >
> > Thanks for your interest in FreeBSD!  Yes, you can work on
> > translating the FreeBSD documentation set into Persian.
> >
> > To get started, please read through the FreeBSD Documentation
> > Project Primer for New Contributors available here:
> >
> > https://docs.freebsd.org/en/books/fdp-primer/
> >
> > Pay special attention to the translation chapters - I'm sure they
> > will be of interest to you.
> >
> > There are several actions to take in getting software installed on
> > your system to be able to edit and translate documentation.
> >
> > The documentation set is written in AsciiDoctor, so you will want to
> > become familiar with using that.  The project also uses git for
> > downloading and managing a local repository.
> >
> > There is also a Discord server used by many teams - here is an
> > invite:
> >
> > https://discord.gg/d3pjPbzM
> >
> > Many people hang out in the #lobby channel for a wide variety of
> > discussions, but there are other channels you can explore.
> >
> > Welcome aboard.
> >
> > Best Regards,
> > Jim B.
> > j...@jimby.name
> >  

Re: Moving vinum to docs-archive

[jpb]

On the gvinum deprecation wiki page it notes:
"Need to decide what to do with the vinum article - simply deleting it
may be most appropriate "

Personally, I see no need to keep the article now that the code and the
man page are gone.

Best Regards,
Jim B.


On Sun, 13 Apr 2025 01:53:11 + (UTC)
"Alexander Ziaee"  wrote:

> Hello,
> 
> Can we keep the vinum [0] article, but move it to docs-archive?
> gvinum(8) was removed in January, 2025, and vinum(4) was removed in
> March, 2013.
> 
> [0] https://docs.freebsd.org/en/articles/vinum/
> 
> Best,
> Alex

Re: Sound manuals

[jpb]

On Wed, 19 Feb 2025 00:08:59 + (UTC)
"Alexander Ziaee"  wrote:

> Hello,
> 
> I want to do the sound manuals like we do wifi manuals. My snd_uaudio
> device shows up as uaudio0, like if_re shows up as re0, and the
> manual is called re, which is shadow mlinked to if_re. To do this
> nicely, I'd like to pick a consistent pattern for the manual document
> description.
> 
> Thus:
> 
> "audio driver" or "sound driver"?
> 
> P.S. In the past it was often said device instead of driver. I think
> this is more elegant actually, but used less and less as time goes on.
> 
> Thanks,
> Alex

I vote for "audio driver".

Cheers,
Jim B.