=E2=98=91

From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Frankel Subject: Re: [Patch] Few small fixes to html header Date: Fri, 28 Mar 2014 12:00:04 -0400 Message-ID: <9c22cfc1384fde6554e716534cb3b9c3@mail.rickster.com> References: <87vbuz1kky.fsf@neutrico-themes.pl> <20701b6c1cc0f8eda606e30a052e8e68@mail.rickster.com> <87txaijqug.fsf@neutrico-themes.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41792) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTZCb-0007Lb-NP for emacs-orgmode@gnu.org; Fri, 28 Mar 2014 12:00:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WTZCV-0004C6-IB for emacs-orgmode@gnu.org; Fri, 28 Mar 2014 12:00:17 -0400 In-Reply-To: <87txaijqug.fsf@neutrico-themes.pl> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Marcin Antczak Cc: Bastien , emacs-orgmode@gnu.org On 2014-03-28 11:16, Marcin Antczak wrote: > Rick Frankel writes: >=20 > On 2014-03-27 15:57, Marcin Antczak wrote: > I've attached patch below, but I'm affraid that there is something > wrong > with indentation. > I'm not sure if there is problem with my settings or just entire > ox-html.el is indented badly. >=20 > Unfortunately, ox-html is indented with a combination of tabs and > spaces, you can turn on whitespace-mode to see. I'm not sure why your > saving the file has touched areas you didn't edit. Did you do a > re-indent or have a whitespace-cleanup or convert-tabs-to-spaces hook > turned on? >=20 > Why ox-html is indented in a way that doesn't follow guidelines > described on Emacs Lisp Coding Conventions? good question. I think because it's actually a very old file. > Could we fix it? Another good question. Bastien- Do you think it makes sense to do a whitespace cleanup only commit of ox-html to master? >=20 > My patch fixes HTML meta data produced on export by ox-html.el >=20 > 1. Meta charset definition should be set before title as document > title can contain > some unicode symbols etc. >=20 > But it's still bug. >=20 > 1. Most modern browsers fallback to UTF-8 currently. > 2. Charset is often set by server content type. >=20 > So, this is why you can see your example rendered correctly. > But there could be a case where it will not render properly. Not true. This file renders incorrectly when opened from the file system in ie 9 and chrome: #+BEGIN_SRC html =E2=98=91

=E2=98=91 checkbox

#+END_SRC But this one renders correctly: #+BEGIN_SRC html =E2=98=91

=E2=98=91 checkbox

#+END_SRC > From logical point of view - charset should be first. And it's in most > html frameworks such as HTML5 Boilerplate, Twitter Bootstrap etc. That may be, but it's a stylistic issue, not a bug. My read of the html dtd does not specify the order of elements in the head. Can you show me an example where the order of the elements causes incorrect display of the title? >=20 > 2. Added viewport declaration as described here: >=20 > https://github.com/h5bp/html5-boilerplate/blob/v4.3.0/doc/html.md >=20 > here: >=20 > https://developer.apple.com/library/safari/documentation/AppleApplicati= ons/Reference/SafariWebContent/UsingtheViewport/UsingtheViewport.html >=20 > I don't believe it's appropriate to have as a default in ox-html as > the current exporter makes no attempt at "responsive design". If you > would like your exported documents to include it, you can use the > HTML_HEAD_EXTRA property on a per-file basis, or customize the > variable `org-html-head-extra'. >=20 > Ok. >=20 > 3. Fixed unnecessary "\n" at the end of Description meta. > 4. Removed unnecessary spaces in meta tags. >=20 > Are these bugs or simply stylistic cleanup? >=20 > 3. This is a bug for me. Meta shouldn't render closing > in new > line. Does it cause output which is incorrectly displayed? Otherwise it's not really a bug, but i will look at changing it the next time i need to touch the file. I'm worried about touching (4) w/o tests, as sometimes attributes are concatenated, and removing a leading whitespace could cause breakage. While source whitespace and output formatting are annoying, our approach to modifications of this (quite old) file has been to not make changes which don't materially affect functionality or fix bugs (the rule of least damage :). rick