Re: Localized versions of freebsd.org outdated and linked to by google
On Thu, May 23, 2024, at 17:50, Michael Gmelin wrote: >> On 23. May 2024, at 22:08, Lorenzo Salvadore >> wrote: >> >> On Thursday, May 23rd, 2024 at 18:41, Michael Gmelin >> wrote: >> >>> I think this situation needs to be resolved, either by updating these >>> pages by whatever means or by giving up localization - at least for the >>> languages we cannot support. >>> >>> Best >>> Michael >>> >>> -- >>> Michael Gmelin >> >> Hi, >> >> Some attempts to choose a path between the alternatives you propose has >> already >> been done: >> https://wiki.freebsd.org/Doc/Translation/Website >> >> However, due to some planned changes to the website which had to be delayed, >> no work to save any localization has started yet. >> >> Anyway, it looks like that there is not much interest in saving those >> translations, so they will probably just die... It is a pity, I believe >> localization is important, but FreeBSD is a voluntary project: if no >> one would like to work on it, nobody will work on it. > > It’s sad on many levels indeed, but based on the current state of > affairs I think users are better off using the English website (and the > in-built translation feature of their web browser, if needed). There is > no point offering localized pages if they don’t provide current > information on even the most basic facts like the current release > version. Imagine googling “FreeBSD latest release” and ending up on a > page telling that it happened four years ago. That’s not helping > anybody. > > So, facing the facts, I would suggest one of the following: > 1. put a warning on localized pages that they’re outdated (not a good > solution, imho) > 2. automatically translate to localized pages and put a warning on top > that the translation was generated automatically (meh) > 3. replace localized pages with redirects to the English originals > > To me, given our target audience and the stage of tooling, 3. sounds > the most straightforward solution to me. Regarding the website, it appears that only the zh-tw language has been updated. We should also remove 'de' and 'it' from the tree, leaving only the main website and zh-tw. The translations can always be retrieved from Git if necessary. Regards, -- Danilo G. Baio
Re: Localized versions of freebsd.org outdated and linked to by google
> On 23. May 2024, at 22:08, Lorenzo Salvadore > wrote: > > On Thursday, May 23rd, 2024 at 18:41, Michael Gmelin > wrote: > >> I think this situation needs to be resolved, either by updating these >> pages by whatever means or by giving up localization - at least for the >> languages we cannot support. >> >> Best >> Michael >> >> -- >> Michael Gmelin > > Hi, > > Some attempts to choose a path between the alternatives you propose has > already > been done: > https://wiki.freebsd.org/Doc/Translation/Website > > However, due to some planned changes to the website which had to be delayed, > no work to save any localization has started yet. > > Anyway, it looks like that there is not much interest in saving those > translations, so they will probably just die... It is a pity, I believe > localization is important, but FreeBSD is a voluntary project: if no > one would like to work on it, nobody will work on it. It’s sad on many levels indeed, but based on the current state of affairs I think users are better off using the English website (and the in-built translation feature of their web browser, if needed). There is no point offering localized pages if they don’t provide current information on even the most basic facts like the current release version. Imagine googling “FreeBSD latest release” and ending up on a page telling that it happened four years ago. That’s not helping anybody. So, facing the facts, I would suggest one of the following: 1. put a warning on localized pages that they’re outdated (not a good solution, imho) 2. automatically translate to localized pages and put a warning on top that the translation was generated automatically (meh) 3. replace localized pages with redirects to the English originals To me, given our target audience and the stage of tooling, 3. sounds the most straightforward solution to me. Cheers Michael
Re: Localized versions of freebsd.org outdated and linked to by google
On Thursday, May 23rd, 2024 at 18:41, Michael Gmelin wrote: > I think this situation needs to be resolved, either by updating these > pages by whatever means or by giving up localization - at least for the > languages we cannot support. > > Best > Michael > > -- > Michael Gmelin Hi, Some attempts to choose a path between the alternatives you propose has already been done: https://wiki.freebsd.org/Doc/Translation/Website However, due to some planned changes to the website which had to be delayed, no work to save any localization has started yet. Anyway, it looks like that there is not much interest in saving those translations, so they will probably just die... It is a pity, I believe localization is important, but FreeBSD is a voluntary project: if no one would like to work on it, nobody will work on it. Cheers, Lorenzo Salvadore
Re: Localized versions of freebsd.org outdated and linked to by google
Michael Gmelin wrote: > What I noticed while getting to localized versions is that some of > these pages are really outdated and/or broken, even those central to > the project. Tangentally related, in the past I got caught out by googling the FreeBSD manpage for something, and the google hit went to the version for Linux. This wasn't even for a port, but a specific Linix distro. On the FreeBSD website, with the FreeBSD logo and the heading "FreeBSD Manual Pages", I missed the small drop down box saying "Redhat", or whatever. I can't remember the command/URL off hand, but here are some examples. The command I looked up gave a result less obvious than these, but you get the point: https://man.freebsd.org/cgi/man.cgi?query=ionice&apropos=0&sektion=1&manpath=Ubuntu+24.04+noble&arch=default&format=html https://man.freebsd.org/cgi/man.cgi?query=ls&apropos=0&sektion=1&manpath=SunOS+4.1.3&arch=default&format=html I don't think that the man.freebsd.org site should hold man pages for other operating systems, or discontinued FreeBSD versions. At the very least, they should not have a FreeBSD banner, and/or be hosted on a different URL and/or marked as non-indexable in search engines. Cheers, Jamie
Localized versions of freebsd.org outdated and linked to by google
Hi, As I long term user I always use the English documentation of the project and like many of us, I simply rely on google to get there. In the past I could simply avoid search results that linked to localized versions, but thanks to some changes google did, it's not obvious anymore (without hovering) if the link goes to a localized version or not, as google is stripping out the language part of the URL when showing where it would link to, as in: https://www.freebsd.org › releases › errata It seems like this is done based on source IP address and not based on the actual locale used in the browser. What I noticed while getting to localized versions is that some of these pages are really outdated and/or broken, even those central to the project. Examples: - https://www.freebsd.org/de/releases/ This seems to have been updated last in the first year of the pandemic, listing 11.4 and 12.1 as current releases. - https://www.freebsd.org/de/security/advisories/ This is actually in English and not German, therefore it has the current content. Unfortunately all links to security advisories are broken. I think this situation needs to be resolved, either by updating these pages by whatever means or by giving up localization - at least for the languages we cannot support. Best Michael -- Michael Gmelin
[Bug 279249] quotactl(2) out of date w.r.t. ZFS, and missing information
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279249 Bug ID: 279249 Summary: quotactl(2) out of date w.r.t. ZFS, and missing information Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: g...@nxg.name CC: d...@freebsd.org The quotactl(2) manpage states bluntly that ‘Currently quotas are supported only for the "ufs" file system.’ But (a) bug #234413 from 2019/12.0, states that ‘ZFS implements quotactl(2) as of r336017; the man page needs to be updated.’ Also (b) quotactl does seem to work when called on a ZFS filesystem. Though it seems to work, does this work only by accident? (ie, is it going to stop working unexpectedly?). It would be good for the manpage to be explicit about this. Separately, the manpage doesn't give, or point to, relevant information on how to interpret the results of the call. I can call quotactl(2) on a ZFS filesystem and it produces numbers, which quota.h tells me are in units of disk blocks, and which are right if the block-size is 512B. But I can find nothing, neither in quotactl() nor in ufs/ufs/quota.h, which tells me that unequivocally, and in a way which I'm confident will work on a pool with a different ashift value. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 279248] Submit new ISP provider company
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279248 Bug ID: 279248 Summary: Submit new ISP provider company Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Website Assignee: d...@freebsd.org Reporter: ad...@3v-host.com Hello. My name is Vadislav, I am the founder and CEO of 3v-Hosting (https://3v-host.com/) , a hosting provider with head office in Ukraine and data centers in Ukraine and the Netherlands. We have been working in the web hosting industry since 2016. By offering our clients the rental of VPS or dedicated servers, we provide them with a choice of several pre-installed operating systems, including FreeBSD. Based on this, we would be very grateful if information about our company appeared on the page https://www.freebsd.org/commercial/isp/ of your website. Tell me, is this possible and if so, under what conditions? Thanks and have a nice day! -- You are receiving this mail because: You are the assignee for the bug.
