Update explicit tags for proper Apple/Google format

[chrisreddington]

As per #326, iTunes accepts true/false as the option for the itunes:explicit tag, whereas gogleplay accepts yes/no. This PR changes the rendered RSS feed to convert yes into true, and no into false for itunes:explicit.

Fixes #326

Signed-off-by: Chris Reddington [email protected]

[mattstratton]

I'm wondering if what we want to do is basically allow either "yes/no" as well as "true/false" as valid in the episode file, and then do the translation to the proper Apple/Google versions.

In pseudocode, something like this:

<itunes:explicit>{{ if eq . "yes" or "true" }}true{{ else }}false{{ end }}</itunes:explicit>
<googleplay:explicit>{{ if eq . "yes" or "true" }}yes{{ else }}no{{ end }}</googleplay:explicit>

(the "or" statement in those if examples is NOT accurate syntax; just using pseudocode to explain the logic)

this way you can use either "true/false" or "yes/no" in your episode files, and it will make the right format for Apple and Google.

Make sense?

[mattstratton]

maybe it's like this:

<itunes:explicit>{{ if (and (or (eq . "yes") (eq . "true"))) }}true{{ else }}false{{ end }}</itunes:explicit>
<googleplay:explicit>{{ if (and (or (eq . "yes") (eq . "true"))) }}yes{{ else }}no{{ end }}</googleplay:explicit>

You'll need to check my parens and also test this; I'm "coding" live in the github comment UI here :)

[chrisreddington]

maybe it's like this:

<itunes:explicit>{{ if (and (or (eq . "yes") (eq . "true"))) }}true{{ else }}false{{ end }}</itunes:explicit>
<googleplay:explicit>{{ if (and (or (eq . "yes") (eq . "true"))) }}yes{{ else }}no{{ end }}</googleplay:explicit>

You'll need to check my parens and also test this; I'm "coding" live in the github comment UI here :)

Pretty much that! The and wouldn't be necessary, so have removed from both lines for simplicity and added to the PR :)