Date | Commit message (Collapse) |
|
|
|
The former is obsolete, apparently.
|
|
The man2html(1) and groff(1) HTML generation isn't compatible
anchor-wise with what pandoc(1) generated. They also had too
much styling for my liking.
|
|
Minor updates since v1.7.0 a few weeks ago
* dark216: disable text decoration on <a> tags
* dark216: disable text decoration on <a> tags for light users, too
* dark216: adjust heredoc to stop confusing rdoc
|
|
rdoc 6.1.0 seems to have trouble with '' as a heredoc
terminator.
|
|
For consistency with the dark scheme.
|
|
Color-capable displays do not need text-decoration (the common
default being underlines) to distinguish hyperlinks.
Furthermore, underlines add visual noise which makes it tough to
distinguish certain characters (e.g. 'i' vs 'j', 'L' vs '|').
This also saves a small amount of energy on OLEDs and CRTs since
there's fewer pixels lit ;>
|
|
Since most users are on horrible GUI browsers which default
to light backgrounds, implement the "dark216" color scheme
which saves power on OLED and CRT displays. This still
respects "prefers-color-scheme:light" on newer browsers,
so users can burn their eyes out if they wish :P
While we're at it, switch to perlpod for our own documentation
since Perl5 and POD tooling is more common on most *nix systems
than pandoc. Finally, update our documentation to avoid the
term "mailing list" because centralized subscriber lists limit
forkability compared to an "archives first" approach to email.
3 changes since v1.6.0 (2019-01-07):
add dark216 color scheme for power savings
doc: switch to perlpod for documentation
doc: update wording to avoid "mailing list"
|
|
The concept of a "mailing list" infers the existence of a
centralized subscriber list, and hurts forkability. Mail
archives are easily forkable, subscriber lists are not.
|
|
Perl5 and POD tools is installed on far more *nix-like systems
than Haskell or pandoc. Furthermore, POD is better-specified for
generating manpages than the particular flavor of Markdown used
by pandoc.
podtxt2html was written to maintain anchor compatibility.
|
|
"oldweb" remains for compatibility and we still have minimal styling.
Some browsers (e.g. Firefox 67.0a1 via "ui.systemUsesDarkTheme") are
adding support for the "prefers-color-scheme" @media query. So this
allows pages to respect user choice when it comes to dark or light
schemes.
OLED and CRT displays measure significant power savings when using
dark schemes. Dark themes work better with less ambient light, so
favoring darkness can lead to overall power savings even with CCFL
and LED-lit displays.
|
|
4 changes since v1.5.1 (2017-12-15):
oldweb: work around annoying ERB deprecation in Ruby 2.6
update URLs to HTTPS
linkify source commands and URLs
fall back to cgit_url and git_url if "source_code" is not defined
|
|
Some projects are too lazy to update or upgrade, but cgit/git
URLs are "git clone"-able.
|
|
It's common to have gitweb and cgit URLs which are
viewable in the browser AND clonable. So add links
to encourage follows.
|
|
Let's Encrypt is working well, so lets discourage sniffable
traffic.
|
|
Updated patch by: Takashi Kokubun at
https://bugs.ruby-lang.org/issues/15478
|
|
This release supports rdoc 6.0+ (bundled with Ruby 2.5) with
no additional code changes.
|
|
HTTP to HTTPS redirects slow down the user experience and leave
an opening for traffic interception and rewriting.
|
|
Supporting rdoc 6.0 required no actual code changes on our
part, and I'm not seeing any obvious compatibilities when
view git history of https://github.com/ruby/rdoc.git
Diffing the output seems to reveal no changes, either.
|
|
olddoc now avoids changing core RDoc behavior unless it is
actually specified. Thanks to Daniel Ferreira for noticing
this bug in [ruby-talk:437390]:
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/437390
<CAPL_2g25ir4ZBJo652ao1EYB59ZvFHhpGef1V14QOV2SeVXLeA@mail.gmail.com>
We still assume any Ruby process will only use one RDoc template
in its lifetime, and not switch between them.
There are also a few minor documentation and code cleanups.
5 changes since olddoc v1.4.0:
update URLs to HTTPS
oldweb: apply LessHtml monkey patch late, at runtime
oldweb: use flat_map instead of flatten.map chain
oldweb: use native String#encode for (X)HTML escaping
README: add NNTP archive link for mailing list
|
|
And clarify that we will never require subscription.
|
|
This allows us to avoid loading the 'cgi' library.
|
|
`flat_map' was introduced in Ruby 1.9.2 and reduces
the amount of garbage we generate.
|
|
RDoc will load oldweb.rb regardless of whether it is used or
not, so do not apply our monkey patching to reduce HTML
generated by RDoc::Markup::ToHtml until we initialize Oldweb.
Thanks to Daniel Ferreira for noticing this in [ruby-talk:437390]:
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/437390
<CAPL_2g25ir4ZBJo652ao1EYB59ZvFHhpGef1V14QOV2SeVXLeA@mail.gmail.com>
This still assumes any Ruby VM instance (currently synonymous
with an OS process in Ruby 2.4) will only use one RDoc template
in its lifetime and not switch between them. More work will be
required to support switching between `oldweb' and other
templates within the same VM instance, but that's not a priority
for me.
|
|
80x24.org fully supports HTTPS, now, so use it to give users
some measure of protection from spying. A Tor .onion mirror
is planned.
Oops, missed the 1.4.0 release :x
|
|
This release fixes one formatting bug. It also removes the
'builder' dependency to avoid warnings with (<= 3.2.2) and
make this project easier-to-install.
3 changes since v1.3.0 (Dec 2016):
oldweb/class: add space before superclass method name
news_rdoc: fix unused variable warning
remove 'builder' dependency
|
|
Make this project easier-to-install. Builder warns on the
Fixnum deprecation under Ruby 2.4, and it is overkill for what
we need given Ruby 1.9+ has native XML escaping.
|
|
Found via "make check-warnings"
|
|
This fixes the formatting of the "Calls superclass method"
phrase.
|
|
This release supports the newly-released rdoc 5.x, but maintains
support for rdoc 4.2+. A new "source_code" accessor was
introduced to make us less git-centric to support other systems.
7 changes since 1.2.0:
_head: fix Content-Type charset attribute
add source_code accessor for tail footer
build: dynamically generate version number
_tail: do not mutate existing arrays
gemspec: support rdoc 5.x
build: avoid network usage in "install-gem" target
doc: olddoc.5: document "source_code" field
|
|
New features need documentation.
|
|
Installing a locally-built gem should not require network
access in this developer-oriented makefile target.
|
|
rdoc 5.x does not introduce incompatible changes outside
of dropping Ruby 1.8 support. We never actually supported
Ruby 1.8, either(*), so formalize that in the gemspec while
we're at it.
|
|
We need to ensure we have a consistent data structure across pages.
|
|
This should make development a bit easier
|
|
This makes it easier to share URLs and is more flexible
than cgit_url.
|
|
Oops, this breaks rendering with some browser configurations
which do not assume UTF-8.
|
|
Users using .olddoc.yml to add links to mailing list archives
will now be pleased to know "ml_url" and "nntp_url" fields
accept arrays.
This release also fixes bold highlighting of the current
module/class page for APIs.
7 changes since 1.1.2:
bold class bar to highlight current page
copyright updates for 2016
tail: shorten the footer section
head: use old-style <meta> tags for compatibility
nodoc some internals
tail: support multiple URLs for archives
tail: fix divider when private email does not exist
|
|
Not all projects have both email addresses.
|
|
The more archives, the better.
|
|
We don't want to advertise an API we'd have to support
long-term
|
|
This wastes some bandwidth, but we are olddoc, after all,
and care about old browsers more than new ones.
|
|
Not every project uses git, and some misguided ones even
allow HTML email (not sure why those projects would be interested
in olddoc, though).
Anyways, the olddoc-public@80x24.org account will always be
configured to reject HTML email (or it'll be eaten by a spam filter).
|
|
While we're at it, switch to the shorter, SPDX-approved "GPL-3.0+"
identifier instead of the more verbose "GPLv3 or later" for consistency.
The formatting changed slightly to allow us to use the update-copyright
script in gnulib[1] In the future:
git ls-files | UPDATE_COPYRIGHT_HOLDER='all contributors' \
UPDATE_COPYRIGHT_USE_INTERVALS=2 \
xargs /path/to/gnulib/build-aux/update-copyright
[1] git://git.savannah.gnu.org/gnulib.git
|
|
This matches the behavior of the normal (non-RDoc) page bar.
|
|
* news_atom: add missing <div> for XHTML
|
|
This should help the XHTML render properly in more feed readers.
ref: RFC 4287 Section 4.1.3.4
|
|
* oldweb: fix relative path normalization
This was wasting 2 bytes per link on top-level pages.
|
|
We must explicitly convert Pathname to string before comparing
against '.' to prevent ugly './' prefixes in relative paths from
showing up.
|
|
This release adds support for the `nntp_url` in .olddoc.yml
for mailing lists with NNTP gateways (possibly read-only).
This exists because the project mailing list is now readable
over NNTP:
nntp://news.public-inbox.org/inbox.comp.lang.ruby.olddoc
This also relaxes the dependency on the README being
RDoc-formatted, allowing "olddoc prepare" to generate
NEWS/NEWS.atom.xml files for projects which use only
plain-text and not RDoc.
* support for nntp_url, make private_email optional
* gemspec: use SPDX-compatible license
* readme: relax dependency on RDoc formatting
|