#microformats 2016-02-01

2016-02-01 UTC
bret, Garbee, tommorris, tantek, benward___, ivc_, geor_gs, Chordachi, myfreeweb, adactio, AngeloGladding, adactio_, TallTed and OxADADA joined the channel
#
OxADADA
howdy
#
OxADADA
they seem to be attempting to achieve the same goal, but looks like Readability is pushing the latter (re: https://www.readability.com/developers/guidelines#reader)
#
Zegnat
OxADADA: h-entry is a microformats2 standard and thus supersedes hentry, see http://microformats.org/wiki/microformats2
#
OxADADA
thanks Zegnat
#
OxADADA
i'm trying to determine which format i should use so Readability, Instapaper, Pocket (GetPocket.com), Firefox Reader view can most easily parse the content of a few sites. any idea?
#
Zegnat
I am not sure what readers have and have not updated their parsers, so afraid not. You could of course implement both to support both old and new parsers.
#
OxADADA
Zegnat: yup. none of those readers (except readability) document what their parsers support.
#
Zegnat
I would then start by implementing h-entry. See if any readers pick up on it. You can always put the older hEntry on top of it if some readers are left behind
#
KartikPrabhu
I would suggest hentry if you are not sure.
#
KartikPrabhu
mf2 parsers have a backwards-compatibility built in to parse mf1
#
OxADADA
Zegnat: KartikPrabhu thanks for the input, i'll try that approach :thumbsup:
#
KartikPrabhu
OxADADA: it might not be a good idea to add both h-entry and hentry... some parsers get confused
#
KartikPrabhu
here is a list of parsers that you could potentially test against: http://microformats.org/wiki/parsers
#
OxADADA
KartikPrabhu: oh great, this is really useful. thanks
#
kylewm
"some parsers get confused" -- that's only true if you add hentry and h-entry on different elements, e.g. h-entry inside of an hentry
#
kylewm
if they are both on the same class it should be absolutely fine
#
kylewm
same tag*
gRegorLove, geor_gs, tantek, KevinMarks and KartikPrabhu joined the channel