From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: RTF for emacs Date: Sun, 25 May 2014 22:37:52 +0200 Organization: Aioe.org NNTP Server Message-ID: <87zji5r3vj.fsf@debian.uxu> References: <87fvk012fi.fsf@debian.uxu> <8761kw58n4.fsf@robertthorpeconsulting.com> <87a9a79gvk.fsf@debian.uxu> <8761kus6no.fsf@debian.uxu> 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 1401050425 24285 80.91.229.3 (25 May 2014 20:40:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 25 May 2014 20:40:25 +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 May 25 22:40:20 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 1WofDP-00045t-H2 for geh-help-gnu-emacs@m.gmane.org; Sun, 25 May 2014 22:40:19 +0200 Original-Received: from localhost ([::1]:53291 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WofDP-0001Th-61 for geh-help-gnu-emacs@m.gmane.org; Sun, 25 May 2014 16:40:19 -0400 Original-Path: usenet.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!news.stack.nl!aioe.org!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 52 Original-NNTP-Posting-Host: u+UUXbnu1hlDFr5pMibebQ.user.speranza.aioe.org Original-X-Complaints-To: abuse@aioe.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-Notice: Filtered by postfilter v. 0.8.2 Cancel-Lock: sha1:yESMeutm4yORhYDja1CwPjcyou4= Mail-Copies-To: never Original-Xref: usenet.stanford.edu gnu.emacs.help:205590 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:97861 Archived-At: Yuri Khan writes: > Expressive, yes, but that should be fixed by > developing and standardizing XML schemas for > everything that is not well expressible in > HTML/MathML/SVG. HTML and the Internet is one chaotic hack. LaTeX is a virtually bug-free, domain-specific programming language to produce documents. But it is not even HTML vs. LaTeX (or web vs. PDFs) as those serve two totally different purposes. (Or should, at least.) > Looks the same, yes, and that’s a bad thing. The > shape of content should adapt to the reader [both > human who does the reading, and device which is > used], not the other way round. On paper, I am ok > with 10pt Times and can handle two columns on an A4 > page or two A5 pages side-by-side. On a desktop > screen [at least until 4K displays become widely > available and reasonably priced], I want a highly > legible 12pt sans-serif, hinted for subpixel > rendering, in a single column of adjustable width, > and no subdivision into fixed-size pages. And don’t > even start with me about tablets and > smartphones. (And no, it’s not reasonable to expect > that readers be able or willing to re-render your > LaTeX article for their device capabilities and > personal preferences.) Yes, this is what I'm saying all along! I don't think you should read PDFs on the monitor/projector, and certainly not on "smart"phones - grep the web, you should get web pages (in HTML), print the 600-page manual or Ph.D. thesis with techno-science notation - LaTeX and PDFs. What you can do with HTML cannot at all compare to what you can do with LaTeX, and if you could (which you can't) it would be extremely uncertain if it would work for half browsers - and some people actually need all that stuff. (And I don't even like browsers, anyway.) But I'm the first to say PDFs are used too much and for information that do not benefit from it at all, and then it is much better with ASCII or HTML. -- underground experts united: http://user.it.uu.se/~embe8573