Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [gnus git]  branch master updated: =1= shr.el (shr-tag-div): Added.
Date: Tue, 09 Nov 2010 16:25:31 -0600	[thread overview]
Message-ID: <87oc9yp21w.fsf@lifelogs.com> (raw)
In-Reply-To: <m3wrp0poyt.fsf@quimbies.gnus.org>

On Sat, 30 Oct 2010 01:18:50 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Parsing CSS is not hard.

LMI> Well, yes and no.  Parsing <p style=".."> is easy, but getting a
LMI> machinery in place to handle <p class=".."> and inheritance and stuff is
LMI> a bit of work, I think.

There's also external and inline stylesheets.  Let's say I parse those
out and get the inheritance right, can you go from there?

>> Here's the appearance properties list that IMO would make sense in Emacs:
>> 
>> border
>> background-color
>> color

LMI> color is problematic in the Gwene groups, at least, since the RSS feeds
LMI> don't specify a default background colour.

Ah, but the article's original CSS spec probably does :)

>> text-decoration
>> text-transform
>> line-height

LMI> Hm.  line-height would be awkward to implement, wouldn't it?

Dunno.  It's not really necessary, but the other two are pretty trivial.

text-transform can be uppercase, lowercase, or capitalize (default is
none).

text-decoration can be underline, overline, line-through, or blink
(default is also none).

>> font-family
>> font-style
>> font-size
>> font-weight

LMI> Emacs' support for mixing fonts in the same buffer is so weak that I
LMI> think this is best left unimplemented.  I mean -- you can do it, but it
LMI> usually looks awfully awful since mixing fonts of different widths makes
LMI> all line breaking totally haphazard. 

At least font-style could be useful (it can be normal, oblique, italic,
or inherit).  font-weight specifies bold (it can be bold, bolder,
lighter, normal, or a number between 100 and 900 where 400 is normal and
800 is bold).  So that's possible I think.

>> list-style
>> list-style-type
>> list-style-image
>> list-style-position

LMI> And these I don't even know what is.  :-)

http://www.w3schools.com/css/css_list.asp

Pretty simple stuff.  It just replaces the default list item indicator
with something else.  Definitely needed is the armenian list-style-type :)

>> For DIV vs SPAN, if "display" is "block" then the element should be
>> rendered by itself.  And DIV elements have display:block by default in
>> all user agents.  Also at a minimum "visibility:none" should be honored.

LMI> I've been using shr on my Nokia e72 a bit, and the most annoying thing
LMI> is actually the ALT texts on images.  Most give no information of note,
LMI> but just clutter up the text...

OK.  But display:block and visibility:none are the basic stuff needed to
render HTML semi-properly.  And you can put it on your resume.

Ted




  reply	other threads:[~2010-11-09 22:25 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1PArgx-0006dS-00@quimby.gnus.org>
2010-10-26 23:58 ` Lars Magne Ingebrigtsen
2010-10-27  0:15   ` Katsumi Yamaoka
2010-10-27  0:22     ` Katsumi Yamaoka
2010-10-27  0:28     ` Lars Magne Ingebrigtsen
2010-10-27  0:43       ` Katsumi Yamaoka
2010-10-27 18:06   ` Ted Zlatanov
2010-10-29 23:18     ` Lars Magne Ingebrigtsen
2010-11-09 22:25       ` Ted Zlatanov [this message]
2010-11-09 22:47         ` Lars Magne Ingebrigtsen
2010-11-09 23:02           ` Steinar Bang
2010-11-10  9:54           ` Julien Danjou
2010-11-10 17:49             ` Colourspace (was: [gnus git] branch master updated: =1= shr.el (shr-tag-div): Added.) Lars Magne Ingebrigtsen
2010-11-10 19:09               ` Colourspace Julien Danjou
2010-11-10 19:44                 ` Colourspace Ted Zlatanov
2010-11-10 19:56                   ` Colourspace Julien Danjou
2010-11-10 20:22                     ` ELPA and Gnus (was: Colourspace) Ted Zlatanov
2010-11-10 20:48                       ` ELPA and Gnus Lars Magne Ingebrigtsen
2010-11-10 21:23                         ` Ted Zlatanov
2010-11-10 21:32                           ` Lars Magne Ingebrigtsen
2010-11-11 13:19                             ` Ted Zlatanov
2010-11-14 16:07                               ` Lars Magne Ingebrigtsen
2010-11-15 15:43                               ` Julien Danjou
2010-11-11  9:06                         ` Julien Danjou
2010-11-14 16:07                           ` Lars Magne Ingebrigtsen
2010-11-10 20:48                 ` Colourspace Lars Magne Ingebrigtsen
2010-11-10 20:55                   ` Colourspace Lars Magne Ingebrigtsen
2010-11-11  8:59                     ` Colourspace Julien Danjou
2010-11-18 18:49               ` Colourspace Ted Zlatanov
2010-11-10 13:14           ` [gnus git] branch master updated: =1= shr.el (shr-tag-div): Added Ted Zlatanov
2010-11-19 16:13           ` Julien Danjou
2010-11-21  4:40             ` Lars Magne Ingebrigtsen
2010-11-21 13:55               ` Julien Danjou
2010-11-21 18:38                 ` Colour manipulation (was: [gnus git] branch master updated: =1= shr.el (shr-tag-div): Added.) Lars Magne Ingebrigtsen
2010-11-21 18:55                   ` Colour manipulation Julien Danjou
2010-11-21 19:02                     ` Lars Magne Ingebrigtsen
2010-11-21 19:26                       ` Julien Danjou
2010-11-21 19:42                         ` Lars Magne Ingebrigtsen
2010-11-22 14:49                         ` Julien Danjou
2010-11-24  2:27                           ` Katsumi Yamaoka
2010-11-24  5:45                             ` Katsumi Yamaoka
2010-11-24  6:39                               ` Lars Magne Ingebrigtsen
2010-11-24  8:43                                 ` Julien Danjou
2010-11-24 20:37                                   ` Lars Magne Ingebrigtsen
2010-11-24 20:48                                     ` Lars Magne Ingebrigtsen
2010-11-24 21:18                                     ` Julien Danjou
2010-11-24 21:27                                       ` Lars Magne Ingebrigtsen
2010-11-24  8:52                               ` Julien Danjou
2010-11-24  6:39                             ` Lars Magne Ingebrigtsen
2010-11-24  8:37                             ` Julien Danjou
2010-11-22 15:37                         ` Julien Danjou
2010-11-22 15:59                           ` Lars Magne Ingebrigtsen
2010-11-23  1:38                             ` Lars Magne Ingebrigtsen
2010-11-23  9:15                               ` Julien Danjou
2010-11-23 23:50                                 ` Lars Magne Ingebrigtsen
2010-11-23  9:48                               ` Julien Danjou
2010-11-23 23:52                                 ` Lars Magne Ingebrigtsen
2010-11-21 19:57                     ` Frank Schmitt
2010-11-22 19:47                     ` Ted Zlatanov
2010-11-23  9:10                       ` Julien Danjou
2010-11-23 14:52                         ` Ted Zlatanov
2010-11-23 15:54                           ` Julien Danjou
2010-11-23 16:15                             ` Ted Zlatanov
2010-11-23 18:32                               ` Colour blindness correction (was: Colour manipulation) Julien Danjou
2010-11-23 23:50                             ` Colour manipulation Lars Magne Ingebrigtsen
2010-11-24  8:32                               ` Julien Danjou
2010-11-26 20:17                             ` Adam Sjøgren
2010-11-24  1:09                         ` Greg Troxel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oc9yp21w.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).