Tricky IV Issues everyone should know about

There are some quite tricky IV issues. This article should help people to find better solutions right away. Remeber that these are NO official rules/suggestions. These are just collections of what seems to be deemed correct.

Contents

1) Unsupported media in <pic>
2) Missing paragraphs/empty lines in blockquote
3) Not @unsupported media
4) NO_MEDIA_FOUND
5) Not clearly identifiable figcaptions
6) Quotes
7) Support for .m3u / .m3u8 files or streams
8) Dates - published, modified, etc.
9) Timezones

1) Unsupported media in <pic>

Some media is not supported in the <pic> tag, such as .gif and .svg.
GIFs shouldn't be used in <pic>. It's a valid issue.
Example issue: IV > politifact.com > template7 > issue1

2) Missing paragraphs/empty lines in blockquote

Paragraphs or rather the empty newlines between these must be preserved inside blockquote. Otherwise it looks like a huge wall of text where the reader could easily get lost in.

Example issue: IV > talkandroid.com > template47 > issue3

3) Not @unsupported media

There are cases where the template author did not @unsupport some elements. It's a valid issue, if the media/embed is simply missing. It's not critical enough to reject the template, if there is no IV anyway. Still it's always better and safer to @unsupport such media/embeds.

Example issue: IV > ed.nl > template6 > issue2

4) NO_MEDIA_FOUND

If IV fails to generate because there is some media which cannot be fetched, that's only an issue when the link used by the template creator is clearly wrong (If the media is present in the source and the template creator used a wrong link). But if the media could not get fetched because the source returned a HTTP 404, then it's not a valid issue.

Example issue: example pending.

5) Not clearly identifiable figcaptions

If there are captions in the source, which are simple paragraphs, or <em> after an <img>, those cannot be identified clearly. There have been cases where a normal text paragraph was merged into the figcaption which is a valid issue. It's safer to not try to make them a figcaption.

Example issue: IV > moika78.ru > template11 > issue2

6) Quotes

Quotes must be formatted as such, as their meaning in the article is (if it's an excerpt from the article, it's a pullquote, if it's a normal quote, it's a blockquote). It's a valid issue if the source uses a class quote and the quote is not formatted anyhow. It's also a valid issue if the wrong quote is being used. If a website uses both, block and pullquotes with the same class, it's not a valid issue.
If a site uses pullquotes marked as class blockquote in the source it's not a valid issue, if it's a blockquote in IV.

Example issue: IV > ed.nl > template6 > issue1

7) Support for .m3u / .m3u8 files or streams

Currently .m3u/m3u8 is not supported. You can either set it as the source of <vid> or you can @unsupport them. Both is accepted as a possible solution.

Example issue: IV > hollywoodlife.com > template8 > issue1

8) Dates - published, modified, etc.

1) If the user sees a time on the page, use that.

2) If the user does not see any time, use date published

Example issue: Internal docs

9) Timezones

Timezone support is optional. If you can fetch it, that's okay. If not, no worries. Time itself is of course obligatory! It is possible for a perfect template to display a date/time that looks different than the original.

Example issue: Checklist - 6.1.2

Heading

This is a copy, so that I don't need to format it myself.

Example issue: IV > domain > template > issue

Contact me if you think that something should be added to this list.