Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 08 Nov 2022 12:51:14 +0000
From:      bugzilla-noreply@freebsd.org
To:        doc@FreeBSD.org
Subject:   [Bug 267636] The colon in the file name of the security report of the FreeBSD doc is not compatible with Microsoft Windows
Message-ID:  <bug-267636-9@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267636

            Bug ID: 267636
           Summary: The colon in the file name of the security report of
                    the FreeBSD doc is not compatible with Microsoft
                    Windows
           Product: Documentation
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Website
          Assignee: doc@FreeBSD.org
          Reporter: yklaxds@gmail.com

As Hnadbook, The name of the security advisory always begins with FreeBSD-S=
A-
(for FreeBSD Security Advisory), for FreeBSD-SA-14:04.bind, followed by the
year in two digit format (14:), followed by the advisory number for that ye=
ar
(04.), followed by the name of the affected application or subsystem (bind).
The advisory shown here is the fourth advisory for 2014 and it affects BIND.

https://github.com/Chinese-FreeBSD-Community/freebsd-doc/tree/main/website/=
static/security/patches

The colon in the above path folder and file names is an illegal file name in
Microsoft windows. Microsoft Windows does not allow the colon to appear as =
part
of a folder or file name. Therefore svn or git operations will fail. Only
UNIX-like or MacOS operating systems allow this. This severely hinders users
from editing FreeBSD documents on the Microsoft Windows platform. To be abl=
e to
edit this documentation you must first have a class UNIX, and it is well kn=
own
that the editing experience on these platforms is just not very good, some =
of
them cannot even be configured for input methods.

And the colon doesn't seem necessary, it's not that intuitive, and if I did=
n't
read the Handbook I'd have thought it was the time of publication (hours or
minutes). It's perfectly possible to consider using another character inste=
ad
such as an underscore.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267636-9>