From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: despen@verizon.net (Dan.Espen) Newsgroups: gmane.emacs.help Subject: Re: I'm looking for a project management system for Emacs Date: Sun, 30 Mar 2014 16:30:42 -0400 Organization: A noiseless patient Spider Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1396211726 14606 80.91.229.3 (30 Mar 2014 20:35:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 30 Mar 2014 20:35:26 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Mar 30 22:35:22 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WUMRt-00082F-4e for geh-help-gnu-emacs@m.gmane.org; Sun, 30 Mar 2014 22:35:21 +0200 Original-Received: from localhost ([::1]:45689 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUMRs-000637-Ms for geh-help-gnu-emacs@m.gmane.org; Sun, 30 Mar 2014 16:35:20 -0400 Original-Path: usenet.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!news-1.dfn.de!news.dfn.de!newsfeed.fsmpi.rwth-aachen.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 81 Injection-Info: mx05.eternal-september.org; posting-host="aabc59b8ce9cdce0c2995912677c9e55"; logging-data="7389"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19yig8bgAcoKn2sN8Njb0olpgJDVwvla2w=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:ZEMOjmQ1J3koQGUQWJIdV8ipGE0= sha1:elkUoeC72wNDP5Ix97MBho1wTa0= Original-Xref: usenet.stanford.edu gnu.emacs.help:204602 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:96871 Archived-At: Marcin Borkowski writes: > Dnia 2014-03-30, o godz. 10:18:40 > despen@verizon.net (Dan.Espen) napisał(a): > >> >> Nope, big Gnumake fan here. >> >> Any directory/project I do work in is going to have Makefile(s). >> > >> > Well, then I deduce that you are not a heavy LaTeX user. (Am I >> > right, dear Watson? ;) ) The problem is that the make model (using >> > timestamps) is a bit too simplistic for LaTeX: due to the way >> > references (& friends) work, the .aux file basically depends on >> > itself, but only if it contains a line saying >> >> Right. Latex is for printing isn't it? > > Rather typesetting, usually to a pdf file (at least nowadays). Of > course, most of the time this means that something will eventually find > its way to a dead tree. (OTOH, there /are/ TeX-based engines which can > output HTML/XML, too.) > >> I do a lot of documentation writing. >> But HTML/CSS (and Makefiles) are my weapon of choice. > > This is a very good choice, /if/ you do not aim for high typographical > quality and/or atypical applications (typesetting of chemical > formulae, musical notation, dictionaries etc.). Yep, I can care less about paper, but the display quality is to some extent a function of the browser. > Out of curiosity: are there /any/ HTML/CSS rendering solutions > (browsers, ebook readers etc.) which handle breaking paragraphs into > lines in an aesthetically satisfactory way (i.e., employ the > Knuth-Plass algorithm, for instance)? Well, browsers do re-flow when you change window size. Hmm, Google says there are some Javascript implementations of Knuth-Plass. >> I have rules for content generation (like a TOC), uploading, thumbnail >> creation, packaging... > > Do you aim for online browsing only, or for a printed version, too? If > the latter, how do you handle the problem of (potentially) unstable > forward page references? When you identify your CSS there is a "media" option. I do most of my work for browsing, but for the few people that print, I do have a "print" CSS. As for forward references, I just do "See X below". If you print, you've got to search. If you are browsing, "See below" is a link. I've adopted a convention so that headings point back to the next higher level heading. So, H2 points to the enclosing H1, H3 points to it's parent H2, and so on. It makes navigating, even big documents a breeze. Each TOC only goes one level deep. So the main TOC references the H1 headings. If there are a few H2 headings, there is a nested TOC. At the same time, I use DIVs to indent heading levels a little more. This makes up for not having numbered sections. I especially like the "Change History" section offering links to the changes. Someone that's just looking for new stuff gets there pretty quickly. A really neat HTML feature is a Javascript package I found that makes s sortable. It's so neat to put a table into a document and know the user can sort it on any of the columns. I've been advocating for dumping Word and PDFs but people are slow to change, so I lead by example. -- Dan Espen