Date: Thu, 25 May 2017 14:22:01 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: tj <tj@enoti.me> Cc: Glen Barber <gjb@FreeBSD.org>, arch@freebsd.org, doc@FreeBSD.org, current@FreeBSD.org, doceng@freebsd.org Subject: Re: The futur of the roff toolchain Message-ID: <20170525122201.7v5zfspu35a3qx47@ivaldir.net> In-Reply-To: <20170525121251.GB55153@tom-desk.erg.abdn.ac.uk> References: <20170521125733.bmd4tmq6iqpsbvgl@ivaldir.net> <20170525114519.GB17188@FreeBSD.org> <20170525120629.kv2bi4yjtzcegx4e@ivaldir.net> <20170525121251.GB55153@tom-desk.erg.abdn.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--3fpbd6igd3luxhs4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 25, 2017 at 01:12:51PM +0100, tj wrote: > On Thu, May 25, 2017 at 02:07:00PM +0200, Baptiste Daroussin wrote: > > On Thu, May 25, 2017 at 11:45:19AM +0000, Glen Barber wrote: > > > On Sun, May 21, 2017 at 02:57:33PM +0200, Baptiste Daroussin wrote: > > > > No the problem left is documentations available in share/doc. > > > >=20 > > > > I would like to push them elsewhere. Those documents are mostly use= ful for > > > > historical reason (hence we want to keep them) but not really for d= aily use of > > > > modern FreeBSD. > > > > Another issue with those documentation, they are installed as text/= ascii version > > > > in base, which makes most of them not really readable (as the docum= ents has not > > > > be written for a ascii/text target but more for a PDF/html view - u= sing pic(1) > > > > for example) > > > >=20 > > > > A plan was to push as sources in the svn doc repository and continu= e to build > > > > them. This approach also have an issue: over the time roff evolved = a bit and > > > > while working on heirloom doctools import I had to fix a bunch of m= arkup to make > > > > the rendering of those documents clean (also meaning almost noone s= hould read > > > > them considering some were not really readable). > > > >=20 > > > > What I want to propose now, it to render them as PDF (html?) once a= nd push them > > > > somewhere (to be defined) as static document on our documentation w= ebsite. > > > > Please doceng@ provide me a location where to push them. > > > >=20 > > >=20 > > > Unless anyone on doceng@ objects within the next three days, I will > > > create a new directory for the PDFs under doc/head/en_US.ISO8859-1/. > > >=20 > >=20 > > Thank you, > >=20 > > For the record I have pushed the generated PDF: > > https://people.freebsd.org/~bapt/pdfdocs/ > >=20 > > The have been built with a modern groff and I forced the embedded fonts= for all > > fonts used. > >=20 >=20 > Multicolumn doesn't render correct in firefox for this: >=20 > https://people.freebsd.org/~bapt/pdfdocs/papers/timecounter.pdf >=20 > but is fine for this: >=20 > https://people.freebsd.org/~bapt/pdfdocs/papers/devfs.pdf >=20 Good catch thanks! I will see what I can do Bapt --3fpbd6igd3luxhs4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlkmzGYACgkQY4mL3PG3 Plrl1A/9HWlW6GLv1EXf9ER47FzYBvz5okI6F99oCV53L6mpPc5lWKMb2Pwu8m+W cZumcsXtNpjS31GvG5BVifKoLZzBdYjHb5L6FyO1niFUWgPYrrOvtl0ZJixNEvpk 3M9PFTTURwIXJXlhEg5BkXcFEKowfrDibg8aQ0848/Wq0pOHuxvlg8bAVWU7BcLb N46av5gh3nW4gdt23wFtiSdM+/GnMZAbF3+RHDdtrmS8vhQsW2GRHJqx0sHApYSy TEt/n7F1kvyXGZbTOS7xuVMmYTH52+/XoQe3X/sxVzLT94Mf/1CMBh3lTvYoMaqI KGU5oLoIPYD0X/HSg31aCH6RwF8njiF6qdfBGmckZJymg33Vg1pJyDYkDF/u2GZ+ buUnjR5u3sNHIrWmyQI/syuZJlp1JhrgAvQU0AmxB1K2LE1z4WHeT3eCWeV3kM5C AJChnsmttYKDq0vVqR51RKLW4aWcGVH/MGF3YN5Odp/x4ruhI5o4hw/DNmf2/MqH LbTNnICfd84vnlKqNKG6gBezIJPUtvtwFE7KA92gS/dtcExYdmmB3UGT3MHAC/mr bDqgEp2VBrNh9I9ja/DOPgEJObyIMuv21xZ3xsJmOpXmci2ltTiS88Ddo0/7wxle ALPdQLjpi/kM4bmfn20Iio6Uyssquz48LRTV7BB1z409OkmTelg= =nB81 -----END PGP SIGNATURE----- --3fpbd6igd3luxhs4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170525122201.7v5zfspu35a3qx47>